Skip to content

🔥 The seal keeps its guarantee without guarding against links nobody plants - #76

Open
ebigunso wants to merge 3 commits into
feature/2026-09-29/evals-cleanup-fixture-testsfrom
feature/2026-09-29/evals-cleanup-seal-prune
Open

ebigunso wants to merge 3 commits into
feature/2026-09-29/evals-cleanup-fixture-testsfrom
feature/2026-09-29/evals-cleanup-seal-prune

Conversation

@ebigunso

Copy link
Copy Markdown
Owner

The seal command keeps its guarantee, and the stale prune script goes (evals value-audit cleanup Task_6).

  • Seal keeps what it promises: it never overwrites (create_new), it hashes as it streams, and it verifies. write_new and hash_file are byte-unchanged.
  • Removed: the evidence-root-must-not-be-a-link check, the regular-file check and file-name validation of our own run IDs. They guarded against planted links or a hand-edited seal.json, which nothing in the workflow produces. The one README sentence that described the removed rule goes with them.
  • scripts/qdrant_prune_collections.sh and its README section are gone. Its examples used a retired collection naming scheme, and the runner already deletes every collection it creates.

Four files, 92 fewer lines. Both canonical sealed evidence directories verify at base and tip, with all 12 evidence and register hashes reproduced independently. Tests: 411 top-level plus 2 child runs, all five seal tests kept. evals-reviewer APPROVED with no findings.

Stacked on #75.

🤖 Generated with Claude Code

…-fixture-tests' into feature/2026-09-29/evals-cleanup-seal-prune
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant