cesnimdaP7-09 — Settings, Connections and data lifecycle
Follow the exact Phase 6 handoff and implementation plan. P7-08 is implemented CONDITIONAL GO and normally pushed as c5176e3251c869e13284b994b59b2f7aa9220eb1. Direct verification at 2026-10-17T02:03:53.815275 UTC proves clean HEAD = origin = live development; local/origin/live main remains 27657f31131cd95d42f0e1290853ec9c9b3959a4. The exact receipt is .artifacts/phase7/p7-08/operations-push-receipt.json.
Approved boundaries and preservation
| Boundary | Existing owners / required preservation |
|---|---|
| Preferences and Connections | Existing Settings tabs/mobile selector/panel associations, parent Rules draft session, local theme/table preferences, account language owner, notification preference, Profile/security links and mailbox-provider owners |
| Data/privacy/plan/backup | Existing independent General subcards, privacy, usage/entitlement, import/export and backup/deletion owners; preserve formats, counts, recent-auth and server availability/admission |
An independently reviewable OAuth sender repair precedes presentation because two live callback listeners accept uncorrelated messages. It hardens the existing client handshake; it does not add a phase, provider, backend protocol, grant or route. Preferences/Connections presentation follows its verified publication, then data/privacy/plan/backup. Do not redo accepted Settings navigation, Rules ownership or P7-01 security presentation.
Keep Rules' six fields, saved baseline, validation, submitted-snapshot acknowledgement, internal-tab draft retention and explicit discard. Notification preferences are a separate one-boolean account save scope; in-app reminders and email delivery remain distinct. Preserve local preferences versus server-owned settings, dirty retry/discard behavior, explicit writes and account/session disposal.
No billing, deletion, restore, provider sync/send/grant, worker/model or other withheld capability is activated. Actual provider interoperation and destructive operations retain separate evidence/authority requirements.
Fresh entry evidence
Fresh frontend 23 cases / 3 suites PASS, 2026-10-17 02:05:04.985979–02:05:19.337394 UTC, p709-entry-20261017T020504Z: Settings14, Connections3 and job-correspondence Gmail import6. The contemporaneous 15-input snapshot .artifacts/phase7/p7-09/entry/source.json and post.json prove held bytes matching committed c5176e3 canonical source; its capture is not represented as occurring before the command started.
Fresh unchanged-binary backend 40/40 PASS, 02:05:30.082119–02:05:33.187997 UTC, p709-oauth-entry-20261017T020530Z, covers ExternalOrigin/Gmail/Microsoft controller cases using --no-build. This is finite existing server-contract evidence, not new tests, a Release rebuild, real OAuth or production acceptance. The portable entry records raw reports, commands and source/runtime identities.
Entry inventories are frontend 791/95, browser 323, backend 1,054, derived from completed bounded additions. Latest whole frontend573/89, backend1,033 and sidecar49 remain inherited until P7-12. Do not substitute affected subsets for an integrated run.
Findings to validate in the presentation boundaries
Notification reads depend on locale callbacks and can replace an unsaved choice; failed initial reads lack GET recovery, state-only saves permit duplicates, and late acknowledgements replace newer edits. Provider status failures currently resemble disconnection. Privacy/data lifecycle owners require truthful read/retry/pending states and disposal checks; partial import must report completed writes honestly without inventing transactions or resume semantics. These are bounded source findings, not completed repairs.
All 57 groups remain 56 PARTIAL / C11 DEFERRED, with 33 current routes. RD11 language, RD12 notification and RD13 Rules failures remain independently diagnosed; successful reruns do not close them. F20/RD21, other reliability/scaling debt, human screen-reader, physical touch/software keyboard, real zoom and production fonts/photos/print remain qualified. P5-13 is withheld; followMode is deferred. Production remains NO-GO, main is unchanged and Phase 8 implementation has not started.
The separate sender repair is published asdac2927, directly verified clean08:27:48 UTC; its39/3, native9, type/lint/build/hygiene and all qualifications remain recorded. The first Preferences/Connections boundary now has final91/6, backend52, native17 and gates PASS, all18 new PNGs reviewed and qualified54 axe scans0/284. Finite results retain precise source/run scopes and failures. Derived inventories become824/95 frontend and331 browser; backend1054 unchanged. First-boundary final hygiene PASS and normal e7dba9a publication directly verified08:50:42UTC; data/privacy/plan/backup follows, beginning with the separately bounded import compatibility repair. Neither the second boundary nor allP7-09 is accepted yet.
Import prerequisite completion — 20 October 2026
The import compatibility boundary is implemented CONDITIONAL GO: fresh full frontend 837/97, full backend 1057, native 25 and type/lint/build gates pass; 11 all-enabled scans have zero violations with contextual incompletes retained. The independent company contract repair is published as 5addcde1e22e9625d1b39df037a05b24c69c9cde, remote verified 07:16:14 UTC. Import's 13 new frontend cases/two suites and four browser cases derive inventory 837/97 and 335 respectively. These do not claim a complete 335-case browser acceptance.
Remaining data presentation completion — 20 October 2026
Privacy, usage and backup now have 47 affected frontend cases/six suites, 22 existing backend contracts, final native Settings nine, import four, CSV one and ordinary P2-D01 one PASS. Types/lint/build pass; fresh Rules/Settings eight-case consumer completion and final hygiene/publication are recorded before exit. Quick Capture's manual code remains accessible and is verified rather than rebuilt. The 37 final axe scans report zero violations and 141 contextually triaged incomplete nodes; six actual final PNGs were inspected. Inventory becomes frontend 855/99, browser 339, backend 1057; fresh whole integrated acceptance remains P7-12.
Final Rules/Settings consumer eight PASS at 07:57:22 UTC, bringing the final export's focused native total to 23/23, zero skipped/flaky/retries. Export TUs6Z9wfC6aEYGOeW_UZ- and all observed source identities match the final portable evidence.
P7-09 implemented acceptance: CONDITIONAL GO, publication pending. The two approved presentation boundaries and independent sender/import/company repairs are complete within their bounded scope. All 57-group/manual/provider/output/reliability/production qualifications remain. P5-13 is withheld and followMode deferred. Owner-authorized release continuation is separate; current main cc79771 has a queued corrected release run, with no deployment success claimed. P7-10 Users, Audit and System follows in three separate commits after publication.