Repository navigation
docs(agents): fix the stale pointers in the agent context files - #906
Merged
JSdotNet merged 1 commit intoOct 1, 2026
Merged
Conversation
The harness README and the Storybook csproj comment pointed at the pre-ADR-0016 .design folder; they now name .devbook/design/. The README table gains the Backlog.AzureFoundry.TestService row, and its opening no longer calls every harness a Blazor Server host. CLAUDE.md named two of backlog-tools' four skills; it now names all four with their invocation mode, and lists the two missing SKILL.md paths. One sentence, repeated in .agents/rules/context-loading.md, routes plugins/, tools/, build/, .github/ and .claude/ through delivery:flow-code, as the gate table's tooling row already implied. AgentContextPointerTests guards each of these. Item 1 of the issue was already obsolete (orch-context.md was deleted in 3921e82). Item 4, keep or delete the vendored Aspire skills and the orphan design doc, is left for a person. Refs #763 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 30, 2026
JSdotNet
marked this pull request as ready for review
October 1, 2026 05:51
JSdotNet
deleted the
schedule/issue-sweep/2026-10-01/763-agent-context-pointers
branch
October 1, 2026 05:51
This was referenced Oct 1, 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.
Refs #763 — this PR deliberately does not close it. Item 4 of the issue needs a decision from a person (see below), so the issue should stay open after this merges.
Summary
This corrects the stale pointers the 2026-09-27 review found in the agent context files. It covers items 2 and 3 of #763 and adds a guard test for them. Item 1 was already done on main:
.claude/orch-context.mdwas deleted in 3921e82.Changes
src/Harness/README.md..devbook/design/", embedded by the Storybook csproj. The README used to point at the pre-ADR-0016.designfolder.Backlog.AzureFoundry.TestServicerow (Aspire resourceazure-foundry-test). That service is the minimal-API stand-in the desktop harness uses for Azure Foundry chat-completions and Cost Management.Backlog.UI.Storybook.csproj. The comment that still said ".designchapters" is corrected. The build is unchanged.CLAUDE.md.backlog-toolsskills with their invocation mode.backlog-import-planandbacklog-import-inboxare user-invoked and one-shot.backlog-run-plan-itemis model-invoked and runs through the gate.backlog-answer-notesis model-invoked, writes onlyannotationfences throughannotations.mjs, and never pushes.CLAUDE.mdand.agents/rules/context-loading.md. Both gain the same sentence routingplugins/,tools/,build/,.github/and.claude/throughdelivery:flow-code, as the tooling row of the gate table already implied.context-loading.mdsays to keep the two copies in step.tests/Backlog.ArchitectureTests/AgentContextPointerTests.cs. Five guards:.designin the harness filessrc/Harness/project has a README rowCLAUDE.mdorch-context,pr-jsdotnet,github-app.yml,src/Shared/)Acceptance criteria
.designin the harness README, and it names.devbook/design/AgentContextPointerTests.No_harness_file_points_at_the_pre_devbook_design_folder. The positive wording was checked by reading.…The_harness_readme_table_lists_every_project_under_src_harnessCLAUDE.mdnames all four skills, and "Neither of its skills" is gone…Claude_md_names_every_backlog_tools_skill. Each invocation mode was checked against its SKILL.md frontmatter by reading.backlog-import-inboxandbacklog-answer-notespaths…Claude_md_names_every_backlog_tools_skillCLAUDE.md, and the same one incontext-loading.md…Both_gate_copies_route_the_folders_outside_src_and_tests_through_flow_code.devbook/, and the Aspire skills and design doc are untouched…No_agent_context_file_names_a_known_dead_pointer. This already passed before the change and guards against a regression.Testing
dotnet build Backlog.sln: 0 warnings, 0 errors. The build was incremental.dotnet test Backlog.sln: 10,310 total, 10,309 passed, 1 skipped (the EndToEnd placeholder), 0 failed. Zero repair attempts were needed.Backlog.ArchitectureTestswas re-run: 247 passed.node .devbook/_tools/devbook-meta/build.mjs --checkpasses.node tools/devbook/check-metadata.mjschecked 149 files: 0 blocking, 287 advisory, which is the existing baseline.Review
Two review lenses raised three minor findings. The sweep fixed all three before committing.
CLAUDE.md(raised twice): the draft saidbacklog-answer-notes"does not go throughdelivery:flow-spec". No source supports that. It would have created a gate exemption for writes under.devbook/, so the clause was removed. The sentence now describes only what the skill does.src/Harness/README.md:24: "Backlog.UI.Storybookis the odd one out: it hosts no app UI" contradicted the new TestService row, which also hosts no UI. The sentence is now scoped: "Among the Blazor hosts, …".No findings are left open.
What could not be proved
Read this section first. It is what personal validation has to cover.
.devbook/, Aspire skills and design doc) is a property of the diff. Criterion 8 (the checks and build stay green) was verified by running them.CLAUDE.mdnow describes whatbacklog-answer-notesdoes, but deliberately says nothing about whether it routes throughdelivery:flow-spec. Only the gate owner can decide that.AgentContextPointerTestsasserts on the text of these files. A later rewording of the same facts will need the test updated alongside it.Assumptions
.claude/counts as tooling and routes throughflow-code. Thedevbook-*rule trios under it stay owned bydevbook:update.Program.csroutes and from AppHost lines 143–145, wheredesktop-web-harnessreferences it.Left for a person (item 4 of #763)
.agents/skills/aspire*skills (928 lines): they have no wrapper and nothing references them. Either wrap them under.claude/skills/and reference them from a rule, or delete them..claude/design/multi-account-settings.md: either move it into.devbook/arc42/as a proposal throughdelivery:flow-spec, or delete it.backlog-answer-notesand the gate: say whether its annotation-only writes under.devbook/go throughflow-spec, and put the answer in both gate copies.Related
Merge order: no open PR touches
CLAUDE.md,.agents/rules/context-loading.mdorsrc/Harness/README.md. #902 and #904 from this sweep do not overlap.Checklist
This pull request was opened as a draft by an unattended run of
delivery-schedule:schedule-issue-sweep(delivery-schedule@1.13.0) on 2026-10-01. Nothing is ready for review until a person says so.🤖 Generated with Claude Code