4.0 KiB
IM10 confirmation, date and native discovery follow-up
Application source 5a880a6ac711db53cdcab01146542f94694a6275 adds the bounded fixes below. Native discovery caller/evidence integration is df8f4dbbd33dc9001ae9dd4965b5d6a1b0e55748. This report records development verification. Final A3 Gate F remains open.
Confirmation focus
The real mobile saved-search deletion journey reproduced Cancel losing initial focus when confirmation opens above the filter Drawer. The active element was the confirmation's presentation container. Shared ConfirmProvider now recovers Cancel on opening-transition completion only while focus remains on that exact container. Deliberate focus already moved inside the dialog is preserved. Focus enforcement, cancellation, restoration and confirmed writes retain their existing owners.
The deterministic new case failed before the fix while three existing confirmation cases passed. The final selected confirmation/discovery run passed 34 cases, including the prior deliberate-focus transition regression. Raw red/green/type/lint receipts are in evidence/im10-followup-2026-11-11/.
Calendar-day inputs
Add/Edit picker wrappers now parse literal dates as local calendar days and format the selected local day. The seven controls retain their request and revision contracts. Add's initial and successful-reset default now uses local today. Existing reopening draft retention remains intact. Calendar-day report records the actual component callbacks and exact payloads.
Seven component cases passed separately in Los Angeles, Oslo and Kiritimati processes. They include EN/NB, all seven controls, null/invalid callbacks, exact creation/save payloads, revision7 and two fixed UTC clocks around midnight. The previous five cases and nearby suite overlap these results. These are seven cases executed in three environments. Actual MUI date-widget browser interaction and native devices remain unexecuted for this date package.
Integrated checks and native browser evidence
- 96 selected frontend tests in 11 suites passed together on
5a880a6a. Full application lint and export/build with TypeScript passed. Earlier 67, 34 and nearby date counts overlap this combined run. - Both complete existing native discovery specs passed together, 11 tests with zero skips/retries/flaky outcomes, on
ec57a24dplus the exact confirmation fix. The separate date package was not included in that browser source. Its controls are outside those saved-search journeys. Native reconciliation preserves the source hashes, failed/intermediate receipts and final combined native JSON/list. - Native JSON embeds all 31 screenshots and 27 accessibility-audit attachments. Root independently inspected the final counters and screenshot bodies, verified all 20 compressed/raw receipt hashes and four raw working-source hashes, and matched those sources to Git after LF normalization. Native owner reads/writes/foreign denials remain actual disposable SQLite API calls; provider-shaped search/run results retain their documented fixtures.
- The earlier controlled drawer36/108 and saved16/48 matrices remain their own source-bound receipts. They were not repeated by this native package. Earlier page-query/rules tests remain separately scoped.
Remaining qualifications
Legacy Edit timestamp loading and Company/Jobs date display still need a qualified date-versus-timestamp contract. The current fix preserves legacy parsing/loading and does not rewrite persisted records or reconstruct timezone/precision metadata. These findings are tracked in the date report.
Complete route/visual consistency review, affected broader regression, human/device/native-language checks and final A3 review remain open. Provider/model activation, integrated security, actual recovery, hosted/production and final release qualifications retain their separate gates. Rollback reverts the confirmation/date source commits and reruns affected checks before publication.