docs: compile-check skill no longer says a skipped dependent is compiled in full next

Merged
HA
4d ago
+15-14

Summary

  • The compile-check skill no longer tells agents that the next body edit after a skipped dependent is compiled in full.

User Impact

  • Before: the skill said the first body edit after a run that picked an assembly up only because a reference changed is compiled in full, "whether it compiled or skipped the assembly". Since a skipped dependent now keeps its records, baseline and saved generator output, that edit is checked on the changed files only, so the skill overstated the cost.
  • After: the skill names only the case that still compiles in full, a dependent that was compiled because an assembly it references changed.

Changes

  • Packages/src/Editor/CliOnlyTools~/CompileCheck/Skill/SKILL.md: the clause is narrowed to "a run that compiled the assembly only because an assembly it references changed".
  • The generated copies under .claude/skills/ and .agents/skills/ were regenerated with uloop skills install --claude --agents and match the source.
  • resultstore/baseline.go: the comment on a missing manifest no longer says a skip removes the records; they are removed only when the unit's next compile starts (the sole caller of Forget is the start of CompileUnit). Comment only.
  • docs/compile-check.md already describes both cases correctly and is unchanged. ADR 0017 mentions skipped dependents only in its measurement context and in its existing amendment, so it is unchanged too.

Verification

  • go test of compilecheck and compilecheck/resultstore: pass. gofmt -l . empty.
  • go run ./cmd/check-skill-size (in cli/release-automation): no SKILL.md over the limit (this one is 7,946 bytes).
  • scripts/sync-tool-docs.sh --check: the catalog matches.
  • cmp of the source against both generated copies: identical.