docs: deployed-addresses.md still lists the v4.0.0 testnet factory (0.0.7708432); the current deployment is v8 at 0.0.9213391

## Where

`docs/ats/developer-guides/contracts/deployed-addresses.md` on `main` (checked 2026-09-11). The page is titled "Latest deployed smart contract addresses", and says:

- line 14: `**Smart Contract Version:** 4.0.0`
- line 21: `BLR Proxy | 0.0.7707874 | 0xEFEF4CAe9642631Cfc6d997D6207Ee48fa78fe42`
- line 23: `Factory Proxy | 0.0.7708432 | 0x5fA65CA30d1984701F10476664327f97c864A9D3`
- line 30: version history tops out at `4.0.0 | 0.0.7707874 | 0.0.7708432 | 2026-01-22`

## What the repo itself says is current

`packages/ats/contracts/deployments/hedera-testnet/` holds five dated files; the last four postdate the page:

```
newBlr-2026-01-29T16-49-02.json
newBlr-2026-02-05T12-21-16.json
newBlr-2026-04-16T14-20-25-080.json
newBlr-2026-05-19T16-49-31-449.json
newBlr-2026-06-12T11-19-42-198.json <- latest
```

From `newBlr-2026-06-12T11-19-42-198.json` (the deployment that matches tag `v.8.0.0-ats` / npm `@hashgraph/asset-tokenization-contracts@8.0.0`):

| Contract | Contract ID | EVM address |
| --- | --- | --- |
| Factory proxy | 0.0.9213391 | 0xd1F118A40f3b02883D35909eF2517e7EDd78379d |
| Factory implementation | 0.0.9212655 | 0xe6E7cd61CAB14d26b80B8181B26F45D181BF7504 |
| BLR proxy | 0.0.9212226 | 0xBA2D5FC2083A0b8f164c50e65d782087fBA18E0a |
| BLR implementation | 0.0.9212222 | 0x86ba690fA76625162501EC1e773056870E56a06D |

and the configuration ids an integrator needs for `deployBond` / `deployEquity` (all version 1): equity `0x…01`, bond `0x…02`, bondFixedRate `0x…03`, bondKpiLinkedRate `0x…04`, depositToken `0x…05`, loan `0x…06`, loansPortfolio `0x…07`, factory `0x…08`. None of these appear on the page.

## Expected vs actual

Expected: the "latest addresses" page matches the newest deployment file. Actual: it is four deployments and four major versions behind, so anyone who follows it targets a v4 factory whose ABI and config ids are not the v8 ones. #1398 reports the same drift in `packages/ats/sdk/README.md` (0.0.6797832 / 0.0.6797955), which is a third, different set of coordinates. Three places, three different factories, none of them dated.

We found the live one by reading the dated JSON directly, then guarded every address with an `eth_getCode` length check before use. That is good practice but should not be how you learn which deployment is current. The wiring we ended up with, with provenance for each address, is in https://github.com/AbhimanyuAjudiya/bond-desk/blob/main/ats/README.md.

## Suggested fix

1. Update the page to the 2026-06-12 deployment (version 8.0.0, the four contracts above) and add the configuration-id table, since `deployBond` cannot be called without a config id.
2. Longer term, generate this page and the SDK README snippet from #1398 from the newest `deployments/hedera-testnet/newBlr-*.json` at docs-build time, so the three sources cannot drift again.
3. Until then, a dated one-liner at the top of the page pointing at `packages/ats/contracts/deployments/hedera-testnet/` would already save a day.

Read docs/ats/developer-guides/contracts/deployed-addresses.md alongside packages/ats/contracts/deployments/hedera-testnet/newBlr-2026-06-12T11-19-42-198.json, the latest deployment named in the issue. Update the page to version 8.0.0 with the four listed contract addresses and configuration IDs, and add provenance or dating so the latest source is clear.

Written by the indexing model from the issue text.