oficina / suite Public

Track active fresh-auth and Docs linking design reviews

Paul Campbell pushed by paul@keymail.dev 1 month ago 601d7e5f6315ef4f92245f32895c2767cdb95a4f parent 7c70687

1 file changed, +8 −0

implementation/overnight-2026-09-07.md +8 −0

No CI script — run details

CI log

amadan: no CI script — add an executable .amadan/ci or a `ci` target to the Makefile

diff --git a/implementation/overnight-2026-09-07.md b/implementation/overnight-2026-09-07.md

index a819bf5..62950fd 100644

--- a/implementation/overnight-2026-09-07.md

+++ b/implementation/overnight-2026-09-07.md

@@ -719,3 +719,11 @@ Full review is retained there and posted to suite discussion 5.

- Fable5 APPROVE for encoded config delta and separate actual canary evidence review. Full actual CI success checked. Home branch merged normally through Amadan as0dc863c. Shared Home checkout remains the owner's domain/oficina-works branch; fetched remote but did not switch or overwrite it.

- Eight live Chromium/WebKit JS/width cases passed Home→credential navigation with real secure browser-bound cookies and exact deployment versions. Eight live HTTPS consumer tests passed foreign-origin, expired, wrong-nonce and replay refusal, eight parallel callbacks with one winner, synthetic identity session creation, signout CSRF and revocation. These do not assert live email authentication; actual-handler local browser flow and email/recovery integration cover that path separately. User notified with https://overnight-home.bds.oncarlos.com/ and the placeholder signed-in destination. Team chooser and Docs return remain unimplemented.

- Asked user asynchronously for the first real team's name and URL label; no answer yet. This is needed for the real alias/bootstrap, not authorization to continue implementation. Docs analysis confirms existing people.id owns content while verified email drives legacy sessions/grants; explicit fresh double-auth linking must retain that ID. Rastrillo auth exposes SessionFrom/RequireFreshSession, but Home's assertion endpoint still needs an explicit max-age reauthentication continuation before safe roster editing/account linking. Do not mint fresh auth_time from a standing session. Original full team-entry acceptance remains outstanding.

+## Fresh authentication and existing-account linking, 8 September continuation

+- Previous goal turn classified as progress: enabled and verified Home exchange deployment, independent code/CI/canary approval and Home merge0dc863c. This continuation preserves the full suite objective and the user's team-entry priority.

+- Home fresh-auth design branch feat/home-fresh-assertion at4b184e7, worktree home/.claude/worktrees/overnight-home-fresh; implementation/fresh-assertion.md. Amadan Home discussion21/task21; original owner coordination updated in discussion9. max_age=300 requests actual email/second-factor authentication when stale, binds an existing subject and preserves actual AuthTime. Receiver-side freshness remains mandatory. Found Rastrillo0.23 sessions.Fresh accepts future timestamps by itself; design explicitly adds a future-time refusal. No code implementation yet, pending required design review.

+- First Fable design attempt fb470be ended permission_denied trying to read module sources; its final text is not a verdict. Authoritative terminal receipt /tmp/oficina-home-fresh-review/design-exit.json. Corrected4b184e7 review supplies those external source excerpts directly and uses read-only worktree access. Existing active service oficina-home-fresh-design-r2-20260908.service, PID3376787, actual active/running revalidated. Output /tmp/oficina-home-fresh-review/design-r2-review.ndjson, final receipt design-r2-exit.json when finished. Do not restart on observation timeout or read reasoning deltas as approval.

+- Docs draft design/home-account-link at4cb40cb, worktree docs/.claude/worktrees/overnight-home-link-design, implementation/home-account-link.md; Amadan Docs discussion46. Existing IDs/grants/content remain unchanged; explicit fresh double-auth plus atomic bounded sealed pending-link rows and unique identity mappings. New Home-only principals require a separate data-model migration, not fake email. Reuse/extract the existing purpose sealer with compatibility tests before Docs consumption. Draft is NOT approved for implementation.

+- Docs independent Fable design review is also confirmed running: oficina-docs-home-link-design-review-20260908.service, PID3400521. Output /tmp/oficina-docs-home-link-review/review.ndjson, exit.json when terminal. Both reviews use configured claude-fable-5 via Command Code; no finer model version claimed. Read only final result blocks, not reasoning deltas. Finish Home design corrections then implement/test/review/deploy fresh-auth before linking. No new deployment this continuation; Home preview stays eaefda9. Team-name/label question still unanswered, but does not block these implementation prerequisites.