Skip to content

Fix verify passing where canaryhook was never initialized - #16

Merged
raj-khan merged 1 commit into
mainfrom
verify-needs-init
Oct 23, 2026
Merged

raj-khan merged 1 commit into
mainfrom
verify-needs-init

Conversation

@raj-khan

Copy link
Copy Markdown
Contributor

The decoys and .canaryhook/ are gitignored, so a CI checkout has no record and npx canaryhook verify always printed "No canary trips." The documented CI step could never fail.

  • verify now exits 1 with "not initialized" when there is no .canaryhook/canaries.json. --json adds initialized.
  • The README CI section shows the workflow that works: init before the agent step, verify after.

The decoys and .canaryhook/ are gitignored, so a CI checkout had no record and verify always reported no trips. It now fails when there is nothing to verify, and the README shows init before the agent step.
@raj-khan
raj-khan merged commit f5be565 into main Oct 23, 2026
1 check passed
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