Consume verified Notion snapshot context

[saagpatel]

What

Allow receipt-backed portfolio generation to consume an explicitly configured Notion snapshot when the direct Notion API path is unavailable.

Why

The scheduled producer had a fresh schema-v2 snapshot but still carried forward stale Notion context because portfolio truth only attempted the direct API loader.

Review Of What Was Built

• Accept GHRA_NOTION_SNAPSHOT_PATH as an explicit producer input.
• Fail closed unless schema, freshness, row count, live-read receipt, authority receipt, and content hash verify.
• Map snapshot project fields into the existing advisory context contract.
• Preserve the direct API path as first preference.

Cleanup Review

No generated outputs, schemas, or unrelated producer behavior changed. Stale or unverified snapshots remain no-write/unavailable inputs.

Verification Summary

• uv run pytest -q tests/test_portfolio_truth.py tests/test_project_registry.py tests/test_operator_os_seam_linter.py — 129 passed.
• uv run ruff check . — passed.
• git diff --check — passed.

Shipped Summary

The branch can use a fresh, independently verified Notion snapshot without silently treating arbitrary local JSON as live context.

Next Phase

Wire the canonical scheduled producer to the explicit snapshot path, regenerate from the merged commit, and verify inputs.notion.mode=live with no carry-forward.

Remaining Roadmap

Reconcile BridgeDB, close the three authorized SHIPPED rows, then rotate and verify the recovery anchor.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 55b2e55976

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".