Repository navigation
feat(code-context): the Round sets what to return; journeys carry nav_path (0.2.15) - #37
Merged
Merged
Conversation
… tier A journey declaration may carry navPath (1-6 navigation labels, area to leaf) and order (the leaf's position within its parent). The helper validates both, checks each label for local provenance, and emits nav_path / order only when present, so an older-style candidate produces the same payload as before. validate-submission warns when a journey name does not end with its navPath leaf. record-round no longer prints the investigation tier or a time budget, and the Round file no longer keeps them: the Round's questions and its journey-map instructions define what to return. The Round file now keeps the server's journey-map instructions (how, maySkip) so the agent can read them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ry navPath Remove the quick/full tier rules from the answer skill. The Round's open questions (text and answer expectation) and its journey-map instructions now define what to return and how deep to go; the sibling enumeration, family sweep, test-state sweep and coverage check run when a question asks for them, not by tier. Describe navPath / order and the one-journey-per-leaf shape as the format of what the contract asks for. Direct submission flow is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Today's Doable server forbids unknown journey keys, so a journey carrying nav_path or order is rejected with 422 by any server that predates the contract change. Send them only when the Round's journey-map instructions mention nav_path; otherwise keep validating them locally, drop them from the payload, and have validate-submission say so. The journey name is sent unchanged either way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Doable now says on every Round what it already has and is about to write; the agent judges the scope by it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… name A first draft sent nav_path/order. Every reader of a stored round (orchestration's and the platform's pinned test_spec, a rolled-back trd) refuses extra journey keys, so the path stays in name and the order in the list. Keys an agent adds from older guidance are not sent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
alphali
force-pushed
the
claude/context-contract
branch
from
October 17, 2026 16:10
a08314d to
79dca33
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.
Stacked on #36 (0.2.14, direct submit). Server side: getdoable/trd#618, whose Change Set is
docs/change-sets/code-context-contract.yamlin trd.Change
What to return comes from the Round.
situation, its questions' answer expectations and itsjourneyMapinstructions define what to return and how deep to go.Helper:
name(labels joined with " › ") and the order in the list. Keys an agent adds from older guidance (navPath,order) are not sent. A first draft of this PR sentnav_path/order; orchestration's pinned test_spec refused such rounds (see getdoable/trd#618).how/maySkiptext and the Round'ssituation, and prints the situation.Docs:
answer-contract.md, TESTING scenarios 26, 27 and 30, and CHANGELOG are updated.Tests
npm test: release verifierdoable-code-context@0.2.15, workflow check, node tests 6/6.navPath/orderis sent with the stored keys only, name unchanged;Not merged. It waits for #36 and the trd deploy (deploy order: trd, then this release).
🤖 Generated with Claude Code