[codex] fix personal-ops local portfolio mapping#139
Merged
Conversation
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
Updates
config/notion-project-map.jsonsopersonal-opspoints at the live Local Portfolio Projects row instead of the older Project Portfolio scoring row.Why
The bridge-sync cleanup surfaced that the existing
personal-opsmap used page35bc21f1-caf0-81cb-9426-dd264ef668b2, which fetches from the olderProject Portfoliodata source. Build Log receipt routing expects the Local Portfolio Projects row. Live Notion readback confirmed the currentPersonal OpsLocal Portfolio page is332c21f1-caf0-810d-bf15-e5486454ff81.Review Of What Was Built
personal-opsto Local Portfolio page332c21f1-caf0-810d-bf15-e5486454ff81.harness-scorecard,peer-agent-tools, andoperator-os-docsunmapped because live Notion checks did not find an exact safe Local Portfolio target for those identities.Cleanup Review
No removals. This avoids a future bad receipt relation into the older scoring/project database while preserving the existing no-target policy holds for unrelated project families.
Verification Summary
332c21f1-caf0-810d-bf15-e5486454ff81is titledPersonal Opsundercollection://7858b551-4ce9-4bc3-ad1d-07b187d7117bLocal Portfolio Projects.35bc21f1-caf0-81cb-9426-dd264ef668b2is under oldcollection://35e04e4d-bcd8-45c0-b783-238edef210f7Project Portfolio.jq -e '."personal-ops".localProjectId == "332c21f1-caf0-810d-bf15-e5486454ff81" and .SecondBrain.localProjectId == "362c21f1-caf0-8147-8bbf-fa0fd3ae1480"' config/notion-project-map.jsonuv run pytest tests/test_project_registry.py-> 14 passedsupp:personal-ops.notion_local_page_idresolves to332c21f1-caf0-810d-bf15-e5486454ff81;harness-scorecard,peer-agent-tools, andoperator-os-docsremain null.actionable_unprocessed_shipped_count=0,processed_shipped_without_receipt_count=0.Found: 21,Written: 0,Skipped: 21,Failed: 0.Shipped Summary
This branch corrects future bridge/Notion receipt routing for
personal-opswithout widening project mapping for ambiguous no-target rows.Next Phase
Decide whether active infrastructure projects like
harness-scorecardandpeer-agent-toolsdeserve new Local Portfolio rows. Do not create rows automatically from bridge-sync; require an explicit operator/project routing decision.Remaining Roadmap