fix(cli): use a valid trigger when trace push resets the attestation
Merged
JI
22d ago+1+1+0123456789-1-1-0123456789
When the trace push hook adds no AI coding session evidence, it resets the attestation. The reset call used the trigger value `trace-push`. The reset action accepts only `AttestationResetTriggerFailed` and `AttestationResetTriggerCancelled`, so the reset was not valid. The hook now uses `AttestationResetTriggerCancelled`.
AI disclosure: this change was made with help from Claude Code.