Add end-to-end security and regression test matrix #970

Closed
opened 2026-10-27 13:38:30 +00:00 by sam · 0 comments
Owner

Scope

Build the verification layer for remote secret input across the capability core, engine adapter, Telegram/mobile flow, and cleanup paths. Include automated redaction assertions and tests that inspect all emitted logs/events/transcripts for accidental secret leakage.

Add an integration test using a fake writable engine and a fake mobile channel, plus focused tests for real adapter boundaries where practical.

Acceptance criteria

  • End-to-end test proves a secret submitted from the mobile flow reaches only the selected writable engine and is not returned to the user or model.
  • Tests cover authorization, expiry, cancellation, replay, duplicate/concurrent submission, restart, backend failure, and delivery failure.
  • A deliberately distinctive sentinel secret is asserted absent from logs, errors, events, chat persistence, and test output.
  • Existing secret resolution, engine plugin, and channel tests continue to pass.
  • The normal project gate passes with race-sensitive session tests enabled.

Close reason

Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.


Imported from beads archie-core-1786748942463-15-78823975 · GitHub #510 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18

## Scope Build the verification layer for remote secret input across the capability core, engine adapter, Telegram/mobile flow, and cleanup paths. Include automated redaction assertions and tests that inspect all emitted logs/events/transcripts for accidental secret leakage. Add an integration test using a fake writable engine and a fake mobile channel, plus focused tests for real adapter boundaries where practical. ## Acceptance criteria - End-to-end test proves a secret submitted from the mobile flow reaches only the selected writable engine and is not returned to the user or model. - Tests cover authorization, expiry, cancellation, replay, duplicate/concurrent submission, restart, backend failure, and delivery failure. - A deliberately distinctive sentinel secret is asserted absent from logs, errors, events, chat persistence, and test output. - Existing secret resolution, engine plugin, and channel tests continue to pass. - The normal project gate passes with race-sensitive session tests enabled. ### Close reason Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic. --- _Imported from beads `archie-core-1786748942463-15-78823975` · GitHub #510 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18_
sam added the hightask labels 2026-10-27 13:38:30 +00:00
sam self-assigned this 2026-10-27 13:38:30 +00:00
sam closed this issue 2026-10-27 13:38:30 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#970