Make destructive actions truthful when security journaling fails #498

2026-08-10T16:31:05Z

timmy commented

2026-08-10 16:31:05 +00:00

Closes #497

What changed

reserve durable pending security events before session revocation and issue closure
preserve truthful successful responses and cookie clearing when journal finalization is unavailable
expose pending/completed status and explain pending confirmation in the device activity sheet
migrate existing journals in place while retaining privacy, retention, and count bounds

Verification

focused security and frontend tests: 18 passed
full suite: 1001 passed
git diff --check, Python compilation, and node --check passed

Closes #497 ## What changed - reserve durable pending security events before session revocation and issue closure - preserve truthful successful responses and cookie clearing when journal finalization is unavailable - expose pending/completed status and explain pending confirmation in the device activity sheet - migrate existing journals in place while retaining privacy, retention, and count bounds ## Verification - focused security and frontend tests: 18 passed - full suite: 1001 passed - `git diff --check`, Python compilation, and `node --check` passed

timmy added 1 commit 2026-08-10 16:31:06 +00:00

feat: make security-journaled actions outcome truthful (Closes #497 )

CI / lint (pull_request) Successful in 1m7s

Details

CI / build-release (pull_request) Successful in 5s

Details

CI / release-candidate (pull_request) Has been skipped

Details

78d044f1af

timmy merged commit 7e5b966f77 into main

2026-08-10 16:32:40 +00:00

timmy referenced this issue from a commit

2026-08-10 16:32:42 +00:00

Merge pull request 'Make destructive actions truthful when security journaling fails' (#498) from timmy/497-truthful-security-journal into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#498