Repository navigation
fix(roadmap): restore the context-efficiency phase that #275 binds to - #277
Merged
Merged
Conversation
Two fixes for the same red main landed three minutes apart: #275 (03a0dc5) declared spec.epic enterprise-mcp/tool-exposure-benchmark on the spike, and #276 (7da00d1) reverted #166, the epic phase that work item lives in. Together they leave the spike pointing at a work item that no longer exists, so Roadmap validation fails with "EpicDefinition enterprise-mcp has no work item 'tool-exposure-benchmark'". Keep #275's direction (the spike is bound to the epic) and put the phase back by reverting #276. main then carries #166, #275 and this commit, and the validator passes. Claude-Session: https://claude.ai/code/session_01N6GXDjpJz35mmBZvk2ffw1
|
Claude finished @mashkovd's task in 12s —— View job Review of #277
The PR restores the Both work items are Verdict: approved. P1: 0, P2: 0, P3: 0. |
Antigravity (agy) review — informationalModel: gemini-3.8-flash-high · commit No significant issues found. |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
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.
Why
Two fixes for the same red
mainlanded three minutes apart from two sessions: #275 (03a0dc5, 20:44Z) declaredspec.epic: {enterprise-mcp, tool-exposure-benchmark}on the spike, and #276 (7da00d1, 20:47Z) reverted #166, the epic phase that work item lives in. Together they leave the spike pointing at a work item that no longer exists:What
Keep #275's direction (the spike is bound to the epic work item) and put the phase back by reverting #276.
mainthen carries #166, #275 and this commit.Verification
roadmap/scripts/validate.py roadmap/epics roadmap/spikespasses on this branch locally; onmain's tree it fails with the message above (both ways).validatereruns were queued against the red main).🤖 Generated with Claude Code
https://claude.ai/code/session_01N6GXDjpJz35mmBZvk2ffw1