Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,8 +91,15 @@ run delivered two emails and rejected the superseded code at 19:44:55 WAT on
out waiting for code entry; one-hour expiry remains unverified. All five authorized
boundary emails are used. On 4 November, key 9D8D was revoked (401 verified), the
hook/runtime/secrets removed and ledger login disabled with password removed;
thirteen replay tombstones remain.
All six services are healthy. API and worker run
thirteen replay tombstones remained at that checkpoint. A separately authorized
one-email expiry run on 4 November received direct owner entry and reached its
automatic submission after 3,665 seconds, but failed while waiting for the expected
rejection message. Neither rejection nor post-submission sign-in was established;
one-hour expiry remains unverified. All six authorized boundary emails are used.
Before this run's long wait, key Z123 was revoked (401 verified), the hook and
temporary runtime/secrets removed, and ledger login/password disabled. Fourteen
replay tombstones remain. See the acceptance report for the failed assertion.
All six services were healthy at that cleanup checkpoint. API and worker run
`db93880e924ac679e24b8cb40abef4ff77e57beb` (separately released PR #62); the pilot
preserved this version. Dashboard remains `328f5ad`, admin `cd3d3ff`,
marketing/developers `1829289`. No new paid infrastructure was added.
Expand Down
11 changes: 9 additions & 2 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,15 @@ run delivered two emails and rejected the superseded code at 19:44:55 WAT on
out waiting for code entry; one-hour expiry remains unverified. All five authorized
boundary emails are used. On 4 November, key 9D8D was revoked (401 verified), the
hook/runtime/secrets removed and ledger login disabled with password removed;
thirteen replay tombstones remain.
All six services are healthy. API and worker run
thirteen replay tombstones remained at that checkpoint. A separately authorized
one-email expiry run on 4 November received direct owner entry and reached its
automatic submission after 3,665 seconds, but failed while waiting for the expected
rejection message. Neither rejection nor post-submission sign-in was established;
one-hour expiry remains unverified. All six authorized boundary emails are used.
Before this run's long wait, key Z123 was revoked (401 verified), the hook and
temporary runtime/secrets removed, and ledger login/password disabled. Fourteen
replay tombstones remain. See the acceptance report for the failed assertion.
All six services were healthy at that cleanup checkpoint. API and worker run
`db93880e924ac679e24b8cb40abef4ff77e57beb` (separately released PR #62); the pilot
preserved this version. Dashboard remains `328f5ad`, admin `cd3d3ff`,
marketing/developers `1829289`. No new paid infrastructure was added.
Expand Down
6 changes: 3 additions & 3 deletions docs/deploy-runbook.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,10 @@ Superseded-code rejection passed on 3 November; one-hour expiry remains unverifi
Native changes remain local, not a distributed release. See the
[session and cleanup evidence](sprout-session-acceptance-2026-11-02.md).

The latest pilot is retired: Supabase hook Disabled, QA key 9D8D revoked and
The latest pilot is retired: Supabase hook Disabled, QA key Z123 revoked and
rejected with HTTP 401, auth admission and optional hook/vault runtime/network
removed, temporary secrets deleted. The restricted ledger role is NOLOGIN with
password removed; thirteen replay tombstones remain. Original core configuration
password removed; fourteen replay tombstones remain. Original core configuration
and proxy are restored. No additional paid AWS service was provisioned.
Default Supabase fallback is link-only and incompatible with native code entry.

Expand All @@ -27,7 +27,7 @@ needs fresh scoped credentials/configuration and the preflight in the
[Sprout validation report](sprout-pilot-validation-2026-10-25.md). Before rolling
back to older code, keep auth admission disabled and preserve replay metadata.
Latest pre-pilot host configuration backups remain root-only in
`.sync-backup-20261103-evening`; never print their contents.
`.sync-backup-20261104-expiry`; never print their contents.

## Previous production (October 16, 2026)

Expand Down
37 changes: 37 additions & 0 deletions docs/sprout-session-acceptance-2026-11-02.md
Original file line number Diff line number Diff line change
Expand Up @@ -269,3 +269,40 @@ automatically submits after 3,665 seconds. It has not run live and needs a new
one-email allowance. Temporary sender access should be retired after delivery,
before the long wait. This is a rejection-after-expiry check, not a measurement
of the exact instant at which Supabase invalidates a credential.

## Expiry-only result — 4 November

The owner approved one additional email and entered its code directly at the
start, without submitting. Message `msg_hrusnk2yta6wzh94lhple7l2` was created at
07:10:29.512 UTC / 08:10:29 WAT and has provider delivery evidence; retained HTML,
text and content hash are null. This consumed the new allowance: six boundary
emails authorized and used in total, none remaining.

The runner recorded `EXPIRY_CODE_ENTRY_READY` at 07:10:31 UTC, detected the
Continue button enabled and scheduled submission for 08:11:32 UTC / 09:11:32 WAT,
3,665 seconds after its request start. It passed the pre-submission signed-out and
Continue-enabled assertions and reached the tap. It then failed at
`HabitFlowTests.swift:36`, waiting 20 seconds for the expected “That code didn’t
work” message. The later signed-out assertion and `EXPIRY_CODE_REJECTED` marker
were not reached. `Expiry.xcresult` records one test, one failure, zero passes or
skips. **This establishes neither expired-code rejection nor post-submission
sign-in.** The underlying response is not established by these safe summaries;
do not classify this as a provider expiry defect or a successful sign-in. No
code, credential, mail body or UI attachment was retrieved for the follow-up.

Before the long wait, the sender was fully retired: hook Disabled, key Z123
revoked and HTTP 401 verified, original core configuration restored, optional
hook/vault runtime/network and secrets removed, local ciphertext transfer files
removed. A browser revocation timeout was resolved by revoking only the matching
key through the authorized database path (hash, workspace, name and suffix
checked). Ledger NOLOGIN/password removed; fourteen replay tombstones retained.
All six services were healthy with zero restarts and unchanged versions; public
checks passed. Cleanup SSM `0da5169e-a926-4d0b-a608-877b528d61f3`; final health
`73358d22-b2c7-4a1c-a433-a15426b1459f`; delivery audit
`2d70aee6-5446-47bf-8b71-3d659837f644`.

Evidence is in `.cache/rootmail-acceptance/20261104/expiry-only/`: safe `EXPIRY_`
markers in `expiry.log`, `Expiry.xcresult` test-results summary and
`hook-disabled.png`. The scheduled follow-up collected the failed result; it did
not rerun the test or enable any access. One-hour expiry and the other broader
rollout/account gates remain open. Native changes remain local and undistributed.
10 changes: 8 additions & 2 deletions docs/supabase-rollout-acceptance-2026-10-27.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,8 @@ the successful request evidence.
resolution passed on 3 November. Discarded-acknowledgement recovery after a real
hosted commit also passed, with an independent Mac read and no duplicate revision.
- Immediate superseded-code rejection passed on 3 November. Verify controlled
one-hour expiry; the combined runner timed out before submitting that code.
one-hour expiry; the later expiry-only run reached submission but failed to
observe the expected rejection message. Neither acceptance nor rejection is proven.
- Complete account deletion/retention acceptance using disposable data/accounts,
including ownership and prevention of resurrection. Never delete the owner account.
- Have an independent customer complete installation, and obtain applicable
Expand All @@ -74,7 +75,12 @@ provider-delivered two emails and rejected the superseded code at 19:44:55 WAT o
claimed. Five boundary emails were authorized and used, with none remaining.
Cleanup on 4 November verified key 9D8D rejected with 401, hook Disabled,
auth admission/runtime/secrets removed, and ledger NOLOGIN/password removed;
thirteen replay tombstones remain. Replacement-code acceptance passed earlier;
thirteen replay tombstones remained. The next authorized one-email expiry run
reached automatic submission after 3,665 seconds but failed its expected-error
assertion; expiry remains unverified. Its sender was retired before the wait:
key Z123 rejected with 401, hook/runtime/secrets removed, ledger NOLOGIN/password
removed; fourteen replay tombstones remain. All six boundary emails are used.
Replacement-code acceptance passed earlier;
Supabase HTTP 429 had blocked a separate request before the hook.
All six services are healthy; API/worker run the separately
released `db93880`, preserved throughout this pilot. No additional paid resource
Expand Down
Loading