Files
SeedPass/scripts
thePR0M3TH3ANandClaude Opus 5 cf18ab8091 test: close the gaps mutation testing found in approvals, sinks, and a flaky test
Approvals scored 58%. Five survivors, all genuine:

  - `ttlSeconds` and `uses` validation was unguarded by any test. An approval
    issued with ttl 0 is expired the instant it exists; one with uses 0 can
    never be consumed. Either would look like a granted authorization to
    whoever asked for it and silently authorize nothing — the confusing
    failure rather than the safe one.
  - The expiry boundary (`<=` vs `<`) was unpinned. It now asserts that an
    approval expiring exactly now is refused, and that one millisecond earlier
    it still works, so the boundary is where it claims to be rather than
    approximately there. Python uses `<=`, so this is parity as well as the
    safer direction.

Approvals now 100%.

Sinks scored 67%. The survivor turned `&&` into `||` in the command-spec
parser, which makes a multi-element spec whose FIRST element contains
whitespace get tokenized — silently discarding every element after it. Losing
an argument changes which command runs, and dropping a `--dry-run` or a target
path is exactly the kind of silent change that matters for a sink being handed
a secret. Sinks now 100%.

Separately, the full suite caught a flaky test of my own: the recovery-split
tamper check rewrote the payload's tail and, depending on the payload's
padding, sometimes reproduced the original string exactly — asserting nothing.
It only failed when a randomized share happened to end the wrong way. Now it
flips a character and asserts the result actually differs before expecting the
throw, plus a second case that tampers at four positions rather than trusting
one. Five consecutive runs are clean.

The agent's mapping was also wrong: agent.ts holds the high-risk session, whose
tests live in highRisk.test.ts, so leaving that suite out scored the agent at
38% and blamed the code for a gap that was really a gap in the harness.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01Vtx94nXDmNgXEeThUZP4QN
2026-08-19 13:41:55 -04:00
..
2025-07-19 19:11:59 -04:00
2025-07-11 10:41:33 -04:00