Repository navigation
The return of the Plan agent repaired without a word to the developer - #79
Merged
Merged
Conversation
`/surface-plan` writes the return of the `Plan` agent "as it is". Twice in the six runs of the first campaign of the evaluations the return could not be written so: it arrived once with `<` and `>` escaped, which the state script would not have read as slice markers, and once with absolute paths, which the plan folder must not hold. The command repaired both, rightly, then told the developer of a "deviation" on a document they never read (#70). Refs #70
This was referenced Oct 3, 2026
PierreMardon
added a commit
that referenced
this pull request
Oct 3, 2026
The report of the second campaign of the evaluations, kept for the next one to be compared with: `evals/reports/2026-10-03-e830bc236e9b/`. It measures the chain after the four first fixes drawn from the first campaign (#78, #79, #80, #81), on `01-overdue-list` and `03-overdue-reminders`, three runs each: 67 sessions, 17.07 USD at list price. - `report.md` and `summary.json` of the campaign, as `report --against evals/reports/2026-10-03-6bf7c06609a6/summary.json --keep` wrote them. Nothing else changes. Refs #77
This was referenced Oct 3, 2026
Closed
Closed
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.
/surface-planwrites the return of thePlanagent "as it is". Twice in the six runs of the first campaign of the evaluations the return could not be written so: it arrived once with<and>escaped, which the state script would not have read as slice markers, and once with absolute paths, which the plan folder must not hold. The command repaired both, rightly, then told the developer of a "deviation" on a document they never read (#70).What was done
skills/surface-plan/SKILL.mdnames two repairs that are not a rework and are not reported: a return that arrived escaped is written with its characters, every entity once; a path of the machine becomes its path from the root of the repository, or a neutral form when it lies outside it.templates/plan.md, the mandate of the agent, asks for paths from the root of the repository, where it only forbade the paths of a machine.ARCHITECTURE.mdsays the same of thePlanagent.Tests
The test of step 6 holds the two repairs and the sentence of the template. The lint and the prompt tests pass locally; the CI runs every gate.
Not checked yet
No real session was run on this change. Why the return arrived escaped once is not explained: the repair makes it harmless, it does not prevent it. The next campaign of the evaluations reads the hand overs for these reports.
Refs #70, #77