feat(hooks): log CAT-UNVERIFIED tags instead of treating them as evidence

[EdbertChan]

Summary

Claude can say "I could not check this" in a reply. Until now that was free.

Nothing wrote the claim down. It vanished the moment the reply was sent.

This logs those claims per session. Any still open are listed again the next
time the user types.

A claim closes once a later reply runs a real check and stops repeating it.

The written rule already said a hedge means go and check. The tools said the
opposite: the tag silenced every evidence gate.

Review Claim

Well-formed unverified-claim tags are recorded per session and re-surfaced on
the next prompt until a later turn verifies them.

Review Lane

behavior

Review Unit

engine-runtime

Safety Invariant

The new hook writes only its own ledger file under
~/.cache/catstack-unverified-ledger/ and prints text. It blocks no turn, edits
no repo file, and no other hook reads its output, so a bug here cannot change
what any existing gate decides.

Slice Rationale

Recording is separable from enforcing. This slice makes the claims visible
without changing whether a turn may end; the stacked follow-up adds the
refusal. Landing both together would mix a new data path and a new block into
one review.

Non-goals

• Does not change diu-stop, hedge-runs-prove-it, or prove-it-ship-gate.
• Does not change what counts as a well-formed tag; _markers/markers.py is untouched.
• Does not refuse or block any turn. That is the stacked follow-up.
• Does not report malformed tags, which diu-stop already rejects.

Test Plan

Test Plan

• cd engine/hooks/unverified-tag-ledger && python3 -m unittest discover -s tests
• python3 engine/skills/make-pr/scripts/preflight.py --base origin/main
• python3 scripts/check_hook_test_coverage.py engine/hooks/unverified-tag-ledger
• python3 scripts/check_no_new_comments.py
• python3 scripts/check_ecosystem_boundaries.py

Observed on this branch:

Ran 17 tests in 0.021s
OK

unit    engine-runtime: 8 file(s)
gate    python3 scripts/check_hook_test_coverage.py engine/hooks/unverified-tag-ledger
        check_hook_test_coverage: OK (1 hook(s) checked)
ok      preflight passed

Fixture vs live: unit and fixture only. The hook is not installed on this
machine, so the refusal has never fired inside a real session:

$ ls -la ~/.claude/hooks/unverified-tag-ledger
ls: /Users/edbertchan/.claude/hooks/unverified-tag-ledger: No such file or directory
$ ls -d ~/.cache/catstack-unverified-ledger
ls: /Users/edbertchan/.cache/catstack-unverified-ledger: No such file or directory

Revert Plan

Revert Plan

• Safe to revert? Yes
• Revert command: git revert <sha>, then bash install.sh to drop the symlink
• Post-revert steps: optionally rm -rf ~/.cache/catstack-unverified-ledger
• Data migration? No

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_fa800cfd-771d-4e04-9bfc-6c1dcf3f2767)

[EdbertChan]

This pull request is part of a Mergify stack:

#	Pull Request	Link
1	feat(hooks): log CAT-UNVERIFIED tags instead of treating them as evidence	#464	👈
2	feat(hooks): refuse a CAT-UNVERIFIED tag from a turn that ran no check	#468
3	fix(hooks): wire unverified-tag-ledger into settings and declare its subagent opt-out	#474

[EdbertChan]

Revision history

#	Type	Changes	Reason	Date
1	initial	9270245		2026-09-12 03:11 UTC
2	rebase	9270245 → 44d7c23 (rebase only)		2026-09-12 03:11 UTC

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_d6d57674-f31f-45b0-acf9-31fbd4bf623f)

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request