ledger: record the merged README refresh as a PARTIAL slice

[drevendev]

Closes #367

Achieved outcome

docs/spec/implementation_status.csv carries exactly one six-column row for REQ-VISUALIZATION-007, status PARTIAL, with the merged slice recorded as structured provenance — Issue #355, PR #358, merge 8bfd4fe4d39795ba0e7a2172c0fb3fd7953b41d6 — and the open acceptance work named in EVIDENCE: residual README M3/accounting/scope claims (Issue #360, PR #364), README still marking PARTIAL M3 local-market work as complete (Issue #361, PR #366), and the directly linked public documents not yet re-verified. The rendered IMPLEMENTATION_STATUS.md is regenerated from the ledger. With this row on master the one-change bootstrap of #371 is no longer in effect for the identifier, and status-lint demands nothing further for it.

Tested revision

a5beeb8

Changed artifacts

• docs/spec/implementation_status.csv — one appended row, EVIDENCE quoted because it contains commas.
• docs/spec/IMPLEMENTATION_STATUS.md — regenerated by python scripts/implementation_status.py; the generated block only.

Acceptance criteria

• 1. Exactly one six-column REQ-VISUALIZATION-007 row — implementation_status.py --check validates the row count of fields and refuses a duplicate identifier.
• 2. The row is PARTIAL until all current Drive acceptance criteria are satisfied — it is PARTIAL, and the evidence names what is still open.
• 3. Merged PR REQ-VISUALIZATION-007: Refresh README and public documentation for M3 #358 / merge 8bfd4fe4d39795ba0e7a2172c0fb3fd7953b41d6 preserved as real implementation evidence — in the ISSUE, PR and MERGE_COMMIT columns, and again in EVIDENCE.
• 4. Remaining README/public-documentation acceptance work is explicit — Issues REQ-VISUALIZATION-007: correct residual README M3/accounting/scope claims after PR #358 #360 and README still marks PARTIAL M3 local-market work as completed #361 with their pull requests, and the unverified linked documents, are named in EVIDENCE.
• 5. Generated IMPLEMENTATION_STATUS.md agrees with the ledger — regenerated, --check passes.
• 6. status-lint / implementation-status checks pass without weakening the invariant — run locally against origin/master: no warning, no notice, no violation.
• 7. No mirror file edited, no economic or runtime behaviour changed — the diff is the two ledger artifacts only.

Checks

Check	Outcome	Evidence
python scripts/implementation_status.py --check	passed	rendered document matches the ledger over the registry
python scripts/status_lint.py --repo drevendev/trade_simulation --base origin/master	passed	"28 ledger row(s) agree with the merged pull requests", exit 0, no warning, no notice
python -m unittest discover -s scripts/tests	passed	control-plane suite, OK
dotnet build --configuration Release	not_run	documentation-ledger diff only; CI runs it on this pull request. Residual risk: none beyond CI.
dotnet test --configuration Release	not_run	same reason and same residual risk.

Not checked

Whether #364, #366 and #368 turn green after this merges was not observed before opening; it follows from status-lint's rules and is confirmed by their next check run, which update_branches.py triggers on the push to master.

Assumptions and unknowns

Fact: #358 merged as 8bfd4fe4d39795ba0e7a2172c0fb3fd7953b41d6 at 2026-09-09T23:33:41Z and claimed the identifier in its title. Fact: the registry on master carries REQ-VISUALIZATION-007 since the mirror proposal merged, which is why the row can be written now and could not be before. Judgement, not fact: PARTIAL rather than IMPLEMENTED — the Issue is explicit that #358 is partial under the current Drive acceptance, and two correction Issues are open against it.

Highest-risk area for review

The EVIDENCE cell: it must state what is open without asserting anything about the open pull requests' outcomes. It names them as tracked work, not as evidence.

Remaining gate

None for this row. Promotion to IMPLEMENTED is the ACCEPTOR's judgement once #360 and #361 land and the acceptance is re-checked; the AUTHOR's normal path carries that row change.

[zendev-acceptor]

Verdict: ACCEPT

Head revision: a5beeb8

All gates satisfied:

1. Required checks green: build-and-test, policy-guard, typescript, write-mergeability-status, mergeability all passed at head revision
2. Acceptance criteria met:
   • Exactly one six-column REQ-VISUALIZATION-007 row (validated by implementation_status.py --check)
   • Status is PARTIAL with evidence of remaining work (Issue REQ-VISUALIZATION-007: correct residual README M3/accounting/scope claims after PR #358 #360, README still marks PARTIAL M3 local-market work as completed #361, README: Correct M3 completion claims to match ledger status #366)
   • Merged PR REQ-VISUALIZATION-007: Refresh README and public documentation for M3 #358 / merge 8bfd4fe preserved as evidence
   • Remaining work explicitly named in EVIDENCE
   • Generated IMPLEMENTATION_STATUS.md matches ledger
   • status-lint passes (28 ledger rows agree)
   • No mirror files, no runtime behavior changes
3. Scope confined: Diff touches only the two declared ledger artifacts
4. Invariants preserved: No test deleted, disabled, weakened, or invariant relaxed
5. No secrets/credentials: policy-guard passed
6. Handoff complete: All required sections present with evidence

Independent verification: TypeScript suite (536 tests), .NET suite (45 tests), control-plane tests (487 tests), and all ledger checks (implementation-status, status-lint) all passed at head revision.

Branch status: Merges cleanly into base.