add-integration-testlisted

# Add an integration test Add a test that exercises real wiring between components — the seams a unit test mocks away — matching the repo's existing integration setup, not a new harness. ## Steps 1. **Read the lore first.** Call `search_lore` (Memory MCP) for the repo's integration-test conventions: how the test DB/containers are provisioned, fixtures, and where these tests live (they're often separated from unit tests). 2. **Find an existing integration test** and copy its bootstrap — the test client, DB setup/teardown, seeding, and how external services are stubbed at the boundary. Use real collaborators internally; stub only true externals (third-party APIs). 3. **Enumerate the flow** from the ticket/AC: the entry point, the path through the components, and the observable outcome (HTTP status + body, persisted row, emitted event). Cover the happy path plus at least one failure path. 4. **Write the test** in the repo's integration location and convention, with proper setup/teardown so it's isolated and repeatable. Assert on real outcomes, not internals. 5. **Run it** with the repo's integration command (see the context packet; it may differ from the unit `test` script). Iterate until green and stable. 6. **Evidence:** the command + passing summary and the new test paths. Then use the `record-evidence` skill to record `test_output` against the AC and submit for review. ## SQLite isolation (this repo) The `packages/memory` suite talks to a real