docs(LP-0017): bump pin to 365273d; registry re-deployed + re-anchored on live v0.2.0 testnet

solutions/LP-0017.md

@@ -19,7 +19,7 @@ is extracted into a reusable `logos-chronicle` module with a documented API.
 ## Repository
 
 - **Repo:** https://github.com/aegonmyy/logoz
-- **Branch / commit:** `main` @ `d35981c`
+- **Branch / commit:** `main` @ `365273d`
 - **v0.2.0 port branch:** [`port/v0.2.0`](https://github.com/aegonmyy/logoz/tree/port/v0.2.0)
 - **Key paths:**
   - `logos-chronicle/` — reusable Logos module: upload, broadcast, anchor, publish pipeline (the extracted document-indexing module)
@@ -128,24 +128,25 @@ the app exists.
 
 ### Supportability
 
-- [x] **Registry deployed & tested on LEZ testnet** — deployed and exercised on the public **rc5** testnet (`https://testnet.lez.logos.co`, LEZ pin `27360cb7`) with a live privacy-preserving `index_batch` (tx `f14e39c9…`). See "Testnet note" below: rc5 was wiped for Testnet v0.2.0 during the submission window; the program ID is reproducible from the repo (`make build`) and a clean v0.2.0 port is provided on `port/v0.2.0`.
+- [x] **Registry deployed & tested on LEZ testnet** — deployed and exercised end-to-end on the live **Testnet v0.2.0** (`https://testnet.lez.logos.co`, LEZ `v0.2.0` / commit `a58fbce2`) at `RISC0_DEV_MODE=0`: program `96ad78fe…`, registry PDA `HvCtoPL6…` (reproducing the documented IDs exactly), a CID anchored via a **real Groth16 proof** (`index_batch` tx `02d8781403…`, confirmed on-chain and independently verified via `wallet chain-info transaction`), and `lookup` confirms it (a bogus CID is not-registered). Full evidence + reproduction steps: [`docs/testnet-v020-live-evidence-20260702.md`](https://github.com/aegonmyy/logoz/blob/main/docs/testnet-v020-live-evidence-20260702.md).
 - [x] **E2E integration tests in CI** — upload → broadcast → batch anchor run against a LEZ sequencer in standalone mode in CI (`publish` + `anchor` jobs).
-- [x] **CI green on default branch** — `main` CI run for `d35981c` completed successfully (fmt, build+test, publish smoke, on-chain anchor e2e).
+- [x] **CI green on default branch** — `main` CI completed successfully on the code baseline (fmt, build+test, publish smoke, on-chain anchor e2e); `365273d` changes only docs (README + testnet evidence), no code or workflow files.
 - [x] **README** — covers build steps, deployment addresses, running the Basecamp app, running the batch anchor tool, and querying the registry.
 - [x] **Reproducible demo at `RISC0_DEV_MODE=0`** — `scripts/demo.sh` runs the full pipeline against a real local sequencer with real Groth16 proofs; verified end-to-end on a clean run.
 - [x] **Narrated video demo** showing terminal output incl. proof generation at `RISC0_DEV_MODE=0` — https://youtu.be/e0rzVVsw-w4
 
-> **Testnet note (honest scope).** The on-chain evidence above was captured live on
-> the **rc5** testnet, which was **wiped and replaced by Testnet v0.2.0** during
-> this submission window, so those specific records are no longer queryable on the
-> current network. The application code ports to v0.2.0 cleanly (`port/v0.2.0`: bump
-> the LEZ pin + five `Program::new(x.into())` call-sites; both CLI and guest build
-> clean). Re-anchoring on v0.2.0 is currently **blocked upstream, not in this
-> repo**: released `lgs` tooling does not yet support v0.2.0's on-disk layout
-> ([scaffold#230](https://github.com/logos-co/scaffold/issues/230)). This is the
-> situation the prize's "Potential for Subsequent λ Prizes" section anticipates;
-> the submission is scoped to the rc5 testnet it was verified against, with the
-> v0.2.0 port ready for when the tooling lands.
+> **Testnet note.** On-chain evidence was originally captured on the **rc5** testnet,
+> which was wiped and replaced by **Testnet v0.2.0** mid-submission. The hosted
+> testnet is **now live again at the `v0.2.0` tag**, and the registry has been
+> **re-deployed and re-anchored there** (see the Supportability evidence above): the
+> program ID `96ad78fe…` and PDA `HvCtoPL6…` reproduce the documented values exactly,
+> and a CID was anchored with a real Groth16 proof (`index_batch` tx `02d8781403…`,
+> confirmed on-chain). This was done by talking to the hosted sequencer directly with
+> a `v0.2.0`-final wallet plus the `batch-anchor` CLI — the released `lgs` *localnet*
+> tooling still lags v0.2.0's on-disk layout ([scaffold#230](https://github.com/logos-co/scaffold/issues/230)), but that only affects local bring-up, not testnet
+> interaction. The earlier rc5 records (tx `f14e39c9…`) are no longer queryable on the
+> current network but are retained as the original run record; the program is
+> reproducible from source (`make build`), and a clean code port is on `port/v0.2.0`.
 
 ## FURPS Self-Assessment