docs: repair Swift 6 migration ledger references

[baron]

Summary

• replace seven stale pre-rebase PR Migrate CodeMap core to Swift 6 with exact official Tree-sitter pins #580 commit references with their reachable merged-history equivalents
• remove ledger-internal item labels that conflict with the governing nine-item migration plan
• preserve the existing migration evidence and product claims

Scope

Documentation-only follow-up promised in the approving review for #580. No source, dependency, test, workflow, or runtime behavior changes.

Validation

• git diff --check
• all replacement hashes verified as ancestors of merged main
• contribution commit preflight
• contribution push preflight / repository guardrails

[baron]

Current-main refresh on exact head 5bdcfc1542e482b88d6a9e7adbab36f4c894597b: the documentation corrections remain useful, but the migration ledger has advanced substantially and this branch conflicts in that authority; historical app shards 3/4 are also red. Please recreate this as a small current-ledger doc patch, then obtain independent review. As the author, I cannot self-approve.

[morluto]

Audit disposition — docs-only merge candidate after refresh (2026-08-14)

This is appropriately narrow and I found no runtime/code blocker. Because the document’s purpose is provenance, however, every replacement hash and ancestor claim must be re-derived from the current merged history immediately before merge; these references become stale whenever the branch is rebased or predecessor PRs are integrated differently.

Please refresh onto current main, rerun the reachability checks, and consider preferring stable PR/merge references or a generated verification command alongside raw hashes. Subject to that, this should be straightforward to merge.

[morluto]

Deep-review assessment — 2026-08-14

Disposition: rebase and re-derive the evidence, then merge. This is documentation-only and the corrections are useful, but commit-hash provenance is inherently tied to the exact current history. The replacement hashes and “ancestor of merged main” claims must be regenerated after the branch is refreshed, not merely carried forward from an earlier base.

Please rebase onto current main, rerun the ancestor/reachability checks for every referenced hash, and ensure the ledger distinguishes durable architectural evidence from transient validation ticket IDs. I did not find a substantive blocker beyond staleness of the evidence itself.