Repository navigation
coverage: 3 dangling seals point into an agent worktree path (claude/worktrees/agent-a008408b9580a5586) #6912
Description
The non-required coverage check ("Every seal still describes its spec") fails on unrelated PRs, e.g. run 37477685062 on #6880, with FAIL: 3 seal(s) newly do not hold.
All three are marked [dangling] and resolve to a leaked agent worktree path instead of the repo tree:
- claude/worktrees/agent-a008408b9580a5586/specs/isa/t27a.t27
- claude/worktrees/agent-a008408b9580a5586/specs/isa/ternary_encoding.t27
- claude/worktrees/agent-a008408b9580a5586/specs/compiler/theory/isa_round_trip.t27
Expected: seals reference specs/... relative to the repo root. Fix: re-seal these three specs from a normal checkout (t27c seal --save) and drop the worktree-path seal files; consider a gate that rejects seal paths containing claude/worktrees/.
🤖 Generated with Claude Code
Activity
gHashTag commentedon Oct 6, 2026
Already fixed on master by #6862 (75cf4e5): the three seals now carry repo-relative spec_path.
tools/check_seal_coverage.pyon master: OK, none of the three listed. The failing run 37477685062 predated the fix.Follow-up idea, not built: a gate rejecting seal paths that start with
/or containclaude/worktrees/(would need to be a .t27 spec under the t27-only rule).