Clarify OPERANT registry mapping#126
Merged
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
1 participant
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
Adds explicit registry aliases and catalog metadata for the OPERANT mapping cleanup.
Why
The local checkout remains
operant-public, but the canonical operating project is OPERANT /saagpatel/operant.operant-mcpis a shipped distribution slice, not a separate active portfolio project.Review Of What Was Built
operant-mcp -> operant-publicto registry overrides.OPERANT -> operant-publicto Notion title aliases.operant-publiccatalog contract documenting the canonical OPERANT project and MCP slice relationship.Cleanup Review
Kept the change scoped to registry/catalog config only. No Notion, BridgeDB, dashboards, memory notes, or broad docs were changed.
Verification Summary
python3 -m json.tool config/project-registry-overrides.json >/dev/nullconfig/portfolio-catalog.yamluv run pytest -q tests/test_project_registry.py tests/test_portfolio_catalog.py tests/test_portfolio_truth.py-> 82 passed, 1 existing legacy CLI warninguv run python -m src.cli report saagpatel --portfolio-truthrefused to publish without live Notion context, as designeduv run python -m src.cli report saagpatel --portfolio-truth --portfolio-truth-allow-empty-notionsucceeded with 132 carried-forward Notion rowsOPERANT,operant-mcp, andoperant-publicresolve tooperant-publicoutput/portfolio-truth-latest.jsonand/Users/d/Projects/project-registry.mdShipped Summary
The GithubRepoAuditor registry can now reconcile OPERANT and operant-mcp references back to the existing
operant-publiclocal repo key without creating a phantom second project.Next Phase
Refresh any downstream local portfolio views from the generated truth snapshot when needed. Main risk is that a future full checkout rename from
operant-publictooperantwould need a separate, broader path migration.Remaining Roadmap
No additional OPERANT registry cleanup is required for this narrow slice.