docs planning MOBILE_EXPANSION_CONTINUATION

Resume mobile expansion from the current local checkpoint

Current override 2026-10-22: maintained dev inherited PR141/142/143 and MEX-20a/b. The new authorized batch MEX-20c/d/e/f is locally tested and complete, with migration000111 and full-source acceptance. PR144 carries20b–f; next is current-head guarded delivery, then MEX-21 only on renewed implementation scope. Use current PROGRESS over the historical guidance below. Preserve the occupied primary checkout; use .worktrees/main-reconciliation. No intermediate PR/merge/CI wait; source activation remains OFF.

Current checkpoint, 2026-10-22: MEX-00–07, MEX-09, MEX-10, MEX-17/18/19, EE-00–03 and reviewed EE-11 are LOCAL_DONE / INTEGRATION_PENDING; use current PROGRESS and their linked evidence. The authorized four-unit batch is locally complete: MEX-10 ledger/report reacceptance, MEX-17 source census, MEX-18 scoped reader acceptance and MEX-19 scoped sanctions HTTP. MEX-19 remains default-off and only disables scoped company reads. MEX-08 still requires EE-19; EE-04/05 require their unmet source-admission/rights gates; MEX-20 enforcement review remains retained. Current source checkpoints do not accept source admission, later mobile journeys or production/commercial readiness. PR140, the Go1.27.3 runtime update and its wiki mirror were already integrated separately and must not be repeated.

Foundation history

The foundation MEX-00 audit and the subsequently authorized MEX-01 registration contract and MEX-02 exploration contract are LOCAL_DONE / INTEGRATION_PENDING. The earlier four-unit request selected MEX-03 baselines, EE-00 inventory, EE-01 qualification and EE-02 types/numerics, now locally complete. Qualification is not source admission: PBE rights and full-source/runtime/privacy gates remain pending. Later implementation checkpoints do not satisfy them. This file is continuation guidance, not additional execution authorization.

Starting point for the next authorized agent

1. Read applicable AGENTS, FAST_EXECUTION, current PROGRESS and DELIVERY_WORKFLOW, then the MEX-00 evidence and combined execution prompt.
2. Inspect .worktrees/mobile-expansion-plan, codex/mobile-expansion-plan and actual maintained dev/main before acting. The foundation reconciles original plans 47fded8c / 35accb9e with dev a2f8925c, preserving both histories. Do not check out the old plan base as the implementation base. Do not reset, stash, cherry-pick an already inherited change or include another agent's edits.
3. Refresh remote refs when available. The foundation's remote check failed DNS; no remote current-head/CI acceptance was established. Work on maintained dev when available; otherwise isolate and reconcile normally under ADR-020.
4. The requested MEX-10/17/18/19 batch is now locally complete and tested. The next authorized delivery step is to push maintained dev, open the protected dev→main batch PR, require current-head/base checks and merge only through the guarded workflow. MEX-08 requires EE-19, not just MEX-07; MEX-20 enforcement and EE-04/05 source admission remain held by their owning gates. Select one newly authorized bounded task at a time; no schema/UI changes before their owning dependencies, and required source gates cannot be mocked away.
5. Read the selected unit and linked rules; do not rerun the entire project for this audit. Relevant code/config/base changes invalidate affected evidence. The dependency JSON has no completion flags.

Reuse and guardrails that must survive the handoff

• One free vehicle; extra vehicles Premium. Current technical ceiling3 and existing professional feature matrix remain until an explicit amendment. Preserve old vehicles/history and expired-account data-exit rights. Registration v2 and its23 worked examples are frozen; hosted vehicles.multiple admission is implemented in MEX-07; local quota/lease acceptance remains MEX-08 after EE-19.
• Exploration v1 has54 shape and three counting examples in a separate schema without live endpoints. Reuse it for typed intent/source/clock/coverage/company filters and Android wording; actual semantics/SQL/HTTP/screens and source acceptance are still unimplemented.
• Reuse PRM cloud/ledger/metrics/subscription and Kotlin ports. Source coverage does not close Android journeys or real provider proofs.
• Keep EE capability/unit/tariff/source contracts ahead of dependent migrations and Android. PHEV is one vehicle; no fake electricity FuelProduct or zero cost. EE-02 frozen contract has46 shape and24 exact Go/Kotlin/Rust examples; numerical oracles are not the runtime EE-11 engine.
• MEX-03 actual baseline distinguishes the in-memory picker from unused global search; target the real consumer and compare pinned workloads. Host SQLite/JVM does not establish phone latency.
• Reconcile OPT commits f60bb3e2, 8de22c24, 6e8b306a before repeating that work. Their persistence/no-store and real SQLite acceptance require review; don't blindly accept their phase3 declaration. Allocate Room versions from the actual combined database. Preserve Home commit a2f8925c.
• Close missing FQ scoped-read acceptance through MEX-18; MEX-20a–f are six real-source enforcement units. Current-company association is not historical site attribution. No source-global data is suppressed for lack of association.
• D receipts/business portal stays future-only until extreme consolidation and thousands of real clients, unless expressly requested earlier for that scope. iOS, charging control/payment, provider registration and activation stay held.
• Local source implementation and commits are distinct from publication, deployment, device changes and release certification. Follow the human's active authorization; this foundation does not publish or authorize those steps.

Deliver each task with actual targeted/risk tests, evidence, concise PROGRESS and one atomic English commit. Report in Portuguese. Never convert an absent test, provider permission, source sample or live access into PASS.