amadan
Prioritize Home team-aware entry and record routing gaps
1 file changed,
+9
−0
implementation/overnight-2026-09-07.md+9 −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 df00c96..4eb24a1 100644 |
| --- a/implementation/overnight-2026-09-07.md |
| +++ b/implementation/overnight-2026-09-07.md |
| @@ -695,3 +695,12 @@ Full review is retained there and posted to suite discussion 5. |
| - Sheets theme003/reconcilea75 lacked d35 atomic batching and0010 content_version. Root created fix/visible-release-integration, mergingd35 into003 without conflicts and correcting Fable's binding theme-copy instructions. Exact20c269129733dcd57f5d1c4f03bcccd5f5f4ff2f has full local/race and actual CI green, Fable APPROVE, and a passing local Chromium editor chrome drive (menus/formats/formula, width reload, real XLSX download, light/dark,320/768, read-only viewer). First driver run failed on hardcoded port8799 despite SHEETS_PORT; second fresh synthetic run copied only that port to18879, without changing assertions or app. Evidence /tmp/oficina-sheets-visible-review and /tmp/oficina-sheets-visible-browser-r2. Local processes stopped. |
| - DEPLOYED Sheets preview20c2691 at08:03 Dublin, built by make release, ARM64 SHA b397e85e191e7f4d70232dbd303b4bbdc3721c013a1557f37a2084dcaea640a4. Actual API body/header match, four live signin browser cases pass. Platform watcher checked header only; one exact host/environment restart followed actual old-body/new-header evidence. Receipt /tmp/oficina-sheets-visible-release/verified.json. DB and separate keys preserved. User notified with create/rename/import/paste/theme checks; no multi-tab import claim. Production untouched. |
| - Sheets preview now allows Paul's known address and inherits normal app mail settings: removed ONLY the named environment's placeholder CARLOS_SMTP_HOST/FROM/PORT. No email sent by root. IMPORTANT: prior fixture-only zero-mail assumptions are no longer true. Do not run old privileged fixture writer against this environment under stale SMTP assertions. Docs and Sheets full live authenticated browser checks remain pending; user can now try both. |
| + |
| +## Priority change: team-aware app entry |
| + |
| +- User asks to drop app rollout work in favour of docs.oficina.works → Home sign-in → team choice if needed → team's Docs. Acceptable alternative URL docs.oficina.works/<team-id>. Pause further feature deployments while defining this boundary; leave existing instances and previews intact. |
| +- Verified prior Home ruling16 (2026-09-03) and Docs design§9.2 choose <team>.<app>.oficina.works, credential originid.oficina.works and directoryoficina.works. The two bare app hosts currently alias existing bds instances; they are not team-aware gateways. |
| +- Fetched platform origin/maindcf0cad: path routing exists (internal/edge/edge.go lookupUpstreamPath; internal/domains/claims.go SetClaimPaths). It selects existing routes by first segment, preserves original path and Host, falls back to front host route on prefix miss, and current aliases.go requires target on the same box. No session-aware team router demonstrated. Do not infer a complete fleet-wide gateway from path routing alone. |
| +- Fetched rastrillo origin/main2c3ae78: identity-assertions design exists but still NOT RULED and no assertion code package. Home candidate9b77ec8 has credential sign-in but directory/team/consumer handoff not implemented. Earlier Fable assertion recommendation permits a bounded core implementation after resolving wire/transport contract; it does not require waiting for all SAML work. Re-read full review before adopting its advice. |
| +- Common next slice across URL choices: shared signer/verifier and browser-bound/replay-protected app exchange; authoritative Home team membership and instance registry; app entry redirect, one-team auto-select/multi-team chooser on directory origin; Docs consumer with audience tied to actual team instance; two-team isolation, stable deep links, switch/signout/expiry tests. Preserve separate team DBs and existing production identity/data while migrating. |
| +- Options to present: generic entry with redirect to team subdomain (smallest change, current isolation); path-prefixed common host (user-acceptable, needs base-path support, browser-storage/session partitioning and platform cross-box decision); cookie-selected common host (largest trusted gateway change, must avoid global team-cookie switching existing tabs/deep links). |