Map held shipped projects to Local Portfolio

[saagpatel]

What

Adds Local Portfolio mapping entries for two held shipped-event project keys:

• fable-second-sprint -> 393c21f1-caf0-8139-b728-ff2829299920
• operator-os-docs -> 393c21f1-caf0-8157-8769-e40cdefda078

Why

These projects now have verified Local Portfolio rows, so bridge shipped-event sync can resolve their durable Notion targets instead of leaving their shipped events held.

Review Of What Was Built

• Created canonical project-map entries for both project keys.
• Kept the change scoped to config/notion-project-map.json only.

Cleanup Review

No cleanup or removals in this patch. The generated registry was validated locally but not committed as churn.

Verification Summary

• python3 -m json.tool config/notion-project-map.json
• uv run pytest tests/test_project_registry.py tests/test_notion_export.py -> 33 passed
• Local registry render confirmed both page IDs resolve for fable-second-sprint and operator-os-docs.

Shipped Summary

The branch teaches GithubRepoAuditor's Notion export/project registry about the two newly mapped Local Portfolio rows.

Next Phase

After merge, rerender local registry state and run Notion bridge shipped-sync so the held shipped events receive durable Build Log receipts.

Remaining Roadmap

• Verify the shipped-event queue drains to zero after live sync.
• Re-check bridge health after receipts are written.