Repository navigation
fix(odd): pass the user's spec by reference so handoffs stop losing requirements - #1718
Merged
Merged
Conversation
… by reference Handoffs paraphrased the user's request, the feature document summarized it, and verify never saw it (gentle-shell#1713). The document now has a fixed Specs/Tasks/Log order with verbatim quotes, handoffs reference it, verify returns a verdict per spec, and user-reported failures are reproduced first. The compact contract lives in the always-on ODD steps because the lazy assets were never read in the failing run.
Writer-surface rejections now name the offending line and ask for the same task unchanged, generic writer continuations inherit the surfaces their launch was admitted with, and unknown task ids list recent ids. Each of these failures made the orchestrator resend shorter, re-summarized handoffs that dropped requirements (gentle-shell#1713).
Inherited writer surfaces are always backticked so quoted-only entries round-trip, rejections tell invalid paths apart from prose, every rejection is asserted exactly, and the subagent_continue wiring is proven end to end (review follow-ups for gentle-shell#1713).
An unquoted surface entry with whitespace that is valid when quoted now gets both repairs (backticks or move prose) instead of prose-only advice, which could narrow the writer's scope. Unknown task ids no longer require a context, and inheritance reuses the canonical heading matcher.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (14)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Oct 3, 2026
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.
Closes #1713
Type
type:bug)Summary
## Specs(verbatim user strings, errors, and examples) →## Tasks(one line each) →## Log(whereL1is the original request verbatim) order. A requirement change rewrites only the affectedS#and reopens only its task.S#and runs the spec's examples on isolated state, and user-reported failures are reproduced before being dismissed. The compact contract lives in the always-on ODD steps, because the lazy assets were never read in the failing benchmark run.Changes
extensions/gentle-ai.tsS#verify, reproduce-firstassets/orchestrator-memory.mdassets/orchestrator-delegation.mdassets/agents/gentle-ai-{worker,verify,explore}.md## Log(verify reads all of it); report coveredS#; verify gives a verdict perS#lib/bounded-writer-admission.tsinheritAllowedEditSurfacesfor generic writer continuations; one heading matcherextensions/gentle-agents.tssubagent_continueinherits surfaces; unknown task ids list recent ids, context-safetests/*odd/tasks/spec-by-reference-handoffs.mdTest plan
npm run typecheck: no regressions (186 recorded diagnostics, baseline unchanged).npm test: all stages passed (unit tests, provider contract, runtime harness).writer-edit-surface-scope15/15,bounded-writer-admission8/8,gentle-agents191/191, prompt-contract files 589/589.review-44982330792543f8) returned no findings.Follow-up
internal/components/agentguidance/routing.go) and regeneratefixtures/odd-routing-canonical.md, so that other runtimes get the same contract.Checklist
status:approved)type:*labelCo-Authored-BytrailersSummary by CodeRabbit