[codex] map cost-tracker to Notion project

[saagpatel]

What

Adds the cost-tracker canonical key to config/notion-project-map.json with the live Local Portfolio page ID.

Why

The BridgeDB shipped-sync backlog had a cost-tracker row that was previously classified as no_durable_target because the registry could not route it to a durable Notion Local Portfolio page. Live Notion verification found the canonical page, so the registry map should carry that truth.

Review Of What Was Built

• Maps cost-tracker to Local Portfolio page 378c21f1-caf0-8162-8bc1-eed47cbe9ca3.
• Keeps the PR scoped to the registry map only.
• Leaves the broader local portfolio-catalog reconciliation work out of this branch.

Cleanup Review

No cleanup or removals in this PR. The intentional cleanup was scope control: this branch excludes the unrelated config/portfolio-catalog.yaml working-set changes present in the local quarantine branch.

Verification Summary

• python -m json.tool config/notion-project-map.json >/dev/null passed.
• uv run pytest tests/test_project_registry.py passed: 14 tests.
• Regenerated local output/project-registry.json shows cost-tracker with notion_local_page_id set to 378c21f1-caf0-8162-8bc1-eed47cbe9ca3.
• BridgeDB readback showed the repaired cost-tracker row as Notion-sync ready before live sync.
• Notion bridge sync then wrote the cost-tracker Build Log receipt and BridgeDB health showed actionable shipped backlog at 0.

Shipped Summary

This branch makes cost-tracker receipt-ready through the canonical project registry instead of relying on stale no-target disposition state.

Next Phase

Decide durable routing for the remaining no-target project keys: fable-second-sprint, harness-scorecard, peer-agent-tools, and operator-os-docs. Those need owner/product decisions or explicit Notion row creation, not automatic mapping.

Remaining Roadmap

• Merge this registry map fix after CI passes.
• Keep PR fix(deps): bump starlette 1.2.1 -> 1.3.1 (GHSA-82w8-qh3p-5jfq) #122 in Notion as the sync behavior fix for repaired no-target dispositions.
• Resolve the remaining unmapped project keys through explicit portfolio decisions.

[saagpatel]

Closing this as superseded: main now already contains the exact cost-tracker mapping in config/notion-project-map.json via the broader portfolio working-set reconcile commit. The branch stayed intentionally scoped to the map-only repair, but merging it now would add no new operating value and would only fight the updated base.