Persist operator project Notion mappings#195
Merged
Merged
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1824e30eb9
ℹ️ 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".
saagpatel
force-pushed
the
codex/durable-notion-ghra-mappings-20260719
branch
from
July 20, 2026 07:24
16726fd to
50cbc70
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Enroll operator-scripts as an out-of-tree supplementary repository and map both operator-scripts and operating-memory-os to their canonical Local Portfolio page IDs.
Why
Receipt-backed BridgeDB syncs should survive clean producer-evidence regeneration without temporary worktrees or generated-file edits.
Review Of What Was Built
Cleanup Review
No generated project-registry files were edited. No unrelated portfolio entries changed.
Verification Summary
uv run pytest -q tests/test_project_registry.py tests/test_notion_export.py— 38 passed.Shipped Summary
A clean producer checkout can regenerate the canonical mappings from tracked source.
Next Phase
Merge, regenerate portfolio truth from the fresh live Notion snapshot, and reconcile BridgeDB canonical keys.
Remaining Roadmap
Refresh and verify the BridgeDB recovery anchor.