ab3eaa7c68
The comment said every audit read keys on a running or an authenticated run. That claim was false. claimQueuedRun cancels a queued run when an active subtree pause hold holds the issue, and it writes an activity log event for that cancelled run. The audit feed reads that activity log and can show the cancelled run. State the fallback order the audit feed uses when it finds no responsible user on the cancelled run: issue, then agent API key, then company default. Co-authored-by: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| CHANGELOG.md | ||
| package.json | ||
| tsconfig.json | ||
| vitest.config.ts | ||