The user requested an explicit handoff when a project/profile becomes a good foundation for a new product. Assess each selected native/backend profile independently and report milestone changes during development handoffs. CLI 0.26.0 adds scoped inbox file destinations to the ready local Files + Inbox starters. Fresh Go and Rust both-platform copies each pass 52 iOS cases, 67 Kotlin host cases, 11 device storage cases and both media process stages. Open resolves current authorized metadata and explicit verified preview without marking read; a target deleted by an independent client yields its real backend 404. Every exact-lease rebind clears the route. Read the current evidence and limits. CLI 0.25.0 adds durable manual Files recovery to the ready local Files-only and combined starters. Final generated Swift/Kotlin workflows pass against Go and Rust: 45/49 focused iOS cases; 62 host, 11 device storage cases and six killed- process Files stages per Kotlin backend. Accepted uploads/deletes now persist before HTTP and restore without replay. Unreadable state is preserved and blocks new changes. Read the exact matrix and host limits. CLI 0.24.0 maintains that local readiness and adds explicit Files recovery review. Focused generated workflows pass on Swift/Kotlin against Go/Rust: 40 Go Files-only / 44 Rust combined iOS cases; 56 host, seven storage and two Files screen stages per Kotlin backend. The canonical feature sources are shared across Files-only/combined inventories. Keep preserves intent; Forget releases local bytes/key without proving rollback/cleanup, then requires a fresh read. Read current evidence and startup limits. CLI 0.23.0 adds connected starter ready Files + Inbox combinations for Swift and Kotlin with either Go or Rust. Independent generated upload-to-notice, preference uncertainty, account isolation and restoration pass. Go additionally passes the full combined iOS/Android regression suites. Read the combined guide. CLI 0.22.0 adds connected starter ready Daily Files selections for Swift and Kotlin with either backend. Independent native gallery import, receipt recovery, verified preview, account isolation and process restoration pass; pending transfer bytes remain explicitly ephemeral. Go also passes the full iOS and Android connected workflows. Read Files construction/evidence. CLI 0.21.0 adds connected starter ready inbox selections for Swift/Kotlin with either Go or Rust. Fresh generated products pass actual account inbox interaction, committed lost-reply readback and process restoration; Rust also passes the full existing connected suite with the added capability. Read inbox construction/evidence.
Last assessment: 2026-10-19. Rust adds an independently running runtime/Health foundation, injectable clock/IDs and bounded JSON/version/key helpers with shared Go conformance checks. The explicit core memory Identity profile now passes its own Go/Rust session acceptance. Account now passes bootstrap, owner pages/selection and strong-CAS rename through versioned credential seams. Committed memory events now reach independent Audit, with replay/retry/readiness/shutdown evidence. The core PostgreSQL profile now passes owned transactions, explicit migrations, restart/replay and Go↔Rust account/session/Audit handoff acceptance. Notes now passes scoped CRUD, immutable command receipts and replay after deletion in memory/PostgreSQL and across Go/Rust restarts. Recovery now passes verified contact/reset/change flows, local TLS/STARTTLS, atomic rollback and killed-process Go/Rust challenge handoff. Private SMTP is explicit; anonymous reset admission is bounded and ephemeral. Files now passes scoped metadata/receipts/bytes/Audit conformance, PostgreSQL rollback and killed-upload Go/Rust handoff using a retained private directory. In-app Notifications now passes event/fingerprint/HTTP conformance, coherent scoped inbox/read/settings behavior and killed pending-delivery handoff across Go/Rust. Rust now passes standalone CLI extraction through 0.19.0. CLI 0.20.0 adds an explicit rust-connected selection, sharing native composition with Go-connected. Independent Swift/Kotlin host and actual screen/process acceptance pass; both Daily profiles are connected starter ready for the tested local baseline. Optional Rust APNs/FCM adapters now pass local TLS/JWT/cache tests and guarded manual preview in memory/separate PostgreSQL owners; compiled selection stays off by default. Retained jobs/recovery now pass shared rules, PostgreSQL rollback, SIGKILL and Rust→Go→Rust worker/outcome/lineage handoff. Live delivery remains separate. Rust Realtime now passes bounded/coalesced live Notes, native bearer admission, credential rechecks, capacity release and owned socket shutdown with memory and disposable PostgreSQL stores. Rust CLI has separate independent acceptance below; connected native Rust selection remains separate. Rust operations now has explicit proxy/private metrics, a non-root/read-only release image and actual local Caddy/WebSocket/SMTP plus paired backup/restore acceptance. CLI 0.19.0 now repeats these checks in renamed generated output. Public TLS/hosting remains separate. Rust-connected native evidence is recorded in its own construction guide. Daily + go-connected has independent Swift/Kotlin CLI 0.18.0 owner workspace create/rename and explicit conflict/uncertainty review, alongside registration, scoped caching, verification/reset/change forms and live Notes reads. Secure restore and durable pending-command acceptance remain required and pass. Go retains its separate 0.14.0 PostgreSQL/Docker recovery baseline. Cold offline sign-in, automatic sync, additional feature selections and live provider/release-device acceptance remain separate.
Recovery follow-up: construction/evidence records
CLI 0.11.0 output at
/private/tmp/mobile-push-recovery-starter-2QauZT/recovery-verified, module
github.com/example/recovery-verified/backend. It passes its own check/race/smoke,
disposable PostgreSQL upgrade/rollback/reopen/recovery and generated Make-runner
acceptance. Current owners can cancel before sending or explicitly replace an
eligible terminal job; uncertain sources require duplicate-risk acknowledgement.
Standalone Go readiness is preserved, without promoting native connected profiles.
Queue follow-up: construction/evidence records CLI 0.10.0
output at /private/tmp/mobile-push-jobs-starter-SNkXAO/verified-api, module
github.com/example/verified-api/backend. Source and output pass check/race/smoke,
disposable PostgreSQL queue/rollback/SIGKILL recovery and generated runner checks.
The worker is opt-in, retries preflight only and retains unknown sends without
automatic resend. This preserves Go standalone readiness; native connected
profiles and live delivery remain separate.
Go provider follow-up: setup/evidence records
source and independent output checks for CLI 0.9.0 at
/private/tmp/mobile-provider-verified-9jtwolsv/push-api, module
github.com/example/push-api/backend. Source and output pass check/race/smoke and
their own disposable PostgreSQL 14.24 suite. Local TLS tests verify provider
protocols; real Identity HTTP checks verify preview ownership/proof/version and
conditional retirement. The generated runner acceptance passes real
auth/account/data/inbox/installation flows. Provider selection remains off by
default, with no live cloud credentials or device-delivery evidence. Native
readiness levels are unchanged.
| Level | Meaning |
|---|---|
| Foundation candidate | Reusable boundaries and selected behaviors work in the reference application; extraction is worth starting. |
| Standalone starter ready | A clean, renamed product has been generated outside this checkout, builds/runs independently and passes the checks for its selected capabilities. |
| Connected starter ready | A standalone starter additionally exercises a real chosen backend's sign-in, renewal, account isolation and remote data behavior. |
A local-only product can reach standalone readiness without authentication, remote synchronization, every catalog component or every backend. GPU capability is optional; device performance claims require separate measured evidence. Readiness applies to the selected profile and tested behavior, not a blanket production guarantee for the whole catalog.
| Profile | Current state | What remains before recommending generated products |
|---|---|---|
| Swift Daily + connected + Files + Inbox (Go/Rust) | Connected starter ready through CLI 0.26.0. Each backend passes 52 focused iOS cases, including current file lookup, verified preview and actual removed-target handling from inbox navigation. Earlier full/durable recovery evidence remains versioned. | Manual Files recovery and in-app notice destinations are ready for the tested local baseline. OS notification routing, deep links, background transfers, retention and public release remain separate. Read current evidence. |
| Kotlin Daily + connected + Files + Inbox (Go/Rust) | Connected starter ready through CLI 0.26.0: 67 host, 11 storage cases and both media process stages per backend, including read-only notice destinations. Earlier six-stage Files recovery remains historical evidence. | Accepted Files input survives app force-stop with explicit retry/review. OS push/deep links, background sync, native workflows across backend PostgreSQL restarts and public release remain separate. Read evidence. |
| Swift Daily + connected + Files (Go/Rust) | Connected starter ready through CLI 0.25.0. Go Files-only passes 45 iOS cases; identical feature sources pass Rust combined recovery. Explicit Files-only Go/Rust closures remain copy-checked. | Durable manual recovery is ready for the tested local media pattern. Add background/OS transfers, retention/orphan sweep and release deployment deliberately. Read the exact matrix. |
| Kotlin Daily + connected + Files (Go/Rust) | Connected starter ready through CLI 0.25.0. The canonical feature passes 62 host, 11 storage and six process stages per backend in combined copies; explicit Files-only closures remain copy-checked. | Process restoration now recovers accepted transfer bytes/commands, with no automatic resend. Background/OS transfer, queues, retention and public release remain separate. Read the exact matrix. |
| Swift local UI / Daily | Standalone starter ready through mobile-foundry 0.1.0; product-owned configuration/screens and UI → Query → Kernel closure. | Ready for local UI products. Add deliberate feature capabilities and release branding/signing as needed. |
| Kotlin local UI / Daily | Standalone starter ready through mobile-foundry 0.1.0; product-owned resources/screens and product-only module settings. | Ready for local UI products. Add deliberate feature capabilities and release branding/signing as needed. |
| Swift Daily + local-data | Standalone starter ready through mobile-foundry 0.2.0; local Services/Data and injected CRUD/live-reader exemplar. | Ready for local stored-data products. Replace the Notes domain and supply release branding/signing as needed. |
| Kotlin Daily + local-data | Standalone starter ready through mobile-foundry 0.2.0; local module overlays and native SQLite/observation. | Ready for local stored-data products. Remote/account/sync behavior needs separate capabilities. |
| Swift Workspace | Standalone starter ready through mobile-foundry 0.3.0; app-owned adaptive list/detail. | Ready for UI products; replace placeholder projects and add feature capabilities/signing deliberately. |
| Swift Browse | Standalone starter ready through mobile-foundry 0.3.0; retained local search and detail/back. | Ready for UI products; replace placeholder collections and add chosen providers later. |
| Kotlin Workspace | Standalone starter ready through mobile-foundry 0.3.0; native Back, saveable state and adaptive panes. | Ready for UI products; durable records and deep navigation need separate capabilities. |
| Kotlin Browse | Standalone starter ready through mobile-foundry 0.3.0; saveable search/detail and native Back. | Ready for UI products; collection persistence/provider operations are separate capabilities. |
| Swift Daily + go-connected + Go | Connected starter ready through CLI 0.18.0: independent native sign-in/accounts, Notes/receipts, renewal, Keychain/process and pending-journal recovery, verification/reset/change forms, foreground live reads, read-only saved first pages, native registration/explicit sign-in and owner workspace create/rename with explicit recovery. | Ready to start connected Notes-shaped products. Add contact-change/invitation policy, offline startup/automatic sync, deployment/signing and selected additional native features deliberately. |
| Kotlin Daily + go-connected + Go | Connected starter ready through CLI 0.18.0: independent sign-in/account isolation/Notes, renewal, recreation, killed-process Keystore/pending recovery, verification/reset/change forms, foreground live reads, read-only saved first pages, native registration/explicit sign-in and owner workspace create/rename with explicit recovery. | Ready to start connected Notes-shaped products. Native queues/background sync, other provider adapters, release/device checks and additional features remain separate. |
| Swift Daily + rust-connected + Rust | Connected starter ready through CLI 0.20.0: shared native ports/composition, real Rust-backed host workflows and 36 generated iOS tests with secure/pending/cache relaunch recovery, identity/live forms and workspace conflict/uncertainty review. | Ready to start the tested session/accounts/Notes-shaped products. Connected PostgreSQL restart, public deployment/release devices, additional native features and automatic sync remain separate. Read evidence. |
| Kotlin Daily + rust-connected + Rust | Connected starter ready through CLI 0.20.0: shared native ports/composition, 41 selected host tests, seven native storage tests and ten actual screen stages, including killed-process Keystore/pending/cache recovery and identity/workspace uncertainty flows. | Ready to start the tested session/accounts/Notes-shaped products. Connected PostgreSQL restart, deployment/release devices, native Files/inbox/push/queues and automatic sync remain separate. Read evidence. |
| Swift Daily + connected + inbox (Go/Rust) | Connected starter ready through CLI 0.21.0: exact-lease Activity inbox, server unread count, filter/paging, read/settings uncertainty and app relaunch. Fresh Go inbox and Rust full suites pass 36/41 iOS cases. | Ready for the selected local account inbox pattern. Generated native Files, OS push, offline inbox, richer types and connected database restart remain separate. Read evidence. |
| Kotlin Daily + connected + inbox (Go/Rust) | Connected starter ready through CLI 0.21.0: 47 host cases per backend, seven storage cases and two Go/twelve Rust screen stages, including uncertainty readback, Activity recreation and killed-process restore. | Ready for the selected local account inbox pattern. Add Files/push/background work and product retention deliberately. Read evidence. |
| Swift/Kotlin Physics | Catalog capability verified: pure 2D modules, native court/control consumers, five numeric cases per platform and five total native interactions. | Register a deliberate CLI feature combination and independently verify generated output before recommending physics-enabled starters. |
| Swift/Kotlin Go session | Catalog integration verified: deployment-bound authority, real HTTP/account scope, rotation checkpoints, discovery/switching and actual native-vault workflows. | Daily + go-connected supplies independent generated acceptance separately below. Other shells and providers remain separate selections; route restoration alone still does not establish process recovery. |
| Swift/Kotlin Go remote data | Connected foundation candidate: account-scoped Notes, Files and Notifications verified against Go through URLSession/OkHttp; catalog owners build and pass recovery/replacement tests. Inbox read/settings recover through authoritative refresh. | Daily + go-connected selects remote Notes. Optional Files and inbox now have separate generated acceptance above. Multi-item queues and system push remain separate; catalog host/state tests do not establish those product workflows. |
| Swift/Kotlin system notifications | Catalog capability verified: explicit OS permission/settings, local previews and bounded app-owned open navigation. iOS warm/cold opens and Android real content PendingIntent/recreation checks pass. | Live provider integration/sending, remote scoped destinations, Android cold process acceptance and independent CLI selection remain separate. |
| Swift/Kotlin remote previews | Catalog capability verified: strict provider-payload admission, foreground receipt without navigation and generic tap routing; Apple simulator warm/cold opens and Android actual PendingIntent/launcher/recreation checks pass. | Verify live signed-device APNs/FCM delivery and Android killed-process FCM entry. Account-scoped destinations and independently generated connected profiles remain separate. Read construction/evidence. |
| Swift/Kotlin provider tokens | Catalog foundation candidate: swappable collection ports, app-only APNs/FCM adapters, process-local rotation and explicit registry handoff; host/native adapter and default missing-setup UI checks pass. | Configure signing/Firebase and verify actual issued tokens on devices. Sending, remote opens, FID sender semantics and generated connected CLI selection remain separate. Read setup/evidence. |
| Swift/Kotlin installation registry | Catalog foundation verified: secure app/deployment proof vaults, exact-lease registry ports, guarded explicit registration and readback; native Keychain/Keystore and real Go HTTP handoff/renewal/retirement checks pass. | Live provider token acquisition/configuration, sending, remote scoped routes and independently generated connected combinations remain separate. |
| Go push dispatch/providers | Foundation candidate: exact-session dispatch and conditional retirement plus real APNs/FCM adapters and opt-in guarded manual preview. Local TLS, memory/PostgreSQL HTTP and independently extracted checks pass. | Configure private provider credentials and verify cloud acceptance/device delivery. Durable queues, fanout, retry receipts and native remote opens remain separate. |
| Go queued previews/recovery | Foundation candidate: immutable jobs, fenced claims, guarded enqueue/status/cancel/replacement, bounded preflight backoff and retained uncertainty verified in memory/PostgreSQL and an independent copy. | Live provider acceptance, fanout, provider-result retry classification, retention/erasure/cross-session administration and native queue UI remain separate. |
| Go backend | Standalone starter ready through CLI 0.14.0: independently generated API, account-scoped WebSocket hints, core identity lifecycle, existing auth/data/inbox/installation/provider/job seams, race/PostgreSQL recovery and Docker/email/backup/restore acceptance. | Ready to start Go APIs with the tested portable baseline. Configure real hosting/SMTP and chosen product policy. Daily selects native socket/recovery UI through its separate acceptance. Richer roles/auth, multi-replica fanout and external delivery need deliberate extensions. |
| Rust backend | Standalone starter ready through CLI 0.19.0: independent renamed package/lock, 24 crates/30 fixtures, memory APIs, PostgreSQL rollback/SIGKILL/restart and freshly built Docker/Caddy/SMTP/metrics/backup recovery. | Ready to start standalone Rust APIs with the tested local baseline. Connected native Rust has its own row/acceptance; public TLS/hosting, external delivery, product policy and explicit routing/network gaps remain separate. Read construction/evidence. |
| Supabase integration | Local development stack present; native provider adapters/policies unconnected. | Real auth/account/remote Notes adapters and policies, then connected starter verification. |
| Firebase auth/data integration | Local emulator setup present; native auth/data adapters and rules unconnected. FCM token adapters are assessed separately above. | Real auth/account/remote data adapters and rules, then connected starter verification. |
Native runtime evidence is recorded in the
Swift handoff
and Kotlin handoff,
including references to the earlier local foundation slices.
Local provider infrastructure alone does not establish a connected mobile starter.
The Daily inventory records source/test
closure, identity edit locations, exclusions and the product-only Kotlin settings
overlay. make starter-check shares the CLI's profile validator and remains
read-only. make cli-test checks generation safety. Independent native acceptance
provides the additional runtime evidence recorded below.
Clean-entry evidence, 2026-10-10: both native products build; two hosted iOS
checks and two actual Android Activity checks pass for Daily navigation, theme
retention and product-owned runtime metadata. make starter-check passes, plus
four negative inventory probes covering missing dependencies/fixtures and an
escaping path. See the Swift product handoff
and Kotlin product handoff.
Those initial runs used this checkout and did not establish standalone readiness.
CLI 0.18.0's untouched workspaces-ready output at
/private/tmp/mobile-workspaces-final-2e2xbabf/workspaces-ready, identity
com.example.workspacesready, module
github.com/example/workspaces-ready/backend, passes its own full connected
acceptance with exit 0. 36 iOS checks and all ten Android UI stages pass with
zero failures/skips, on iPhone 17 Pro/iOS 26.2 and Pixel 9 Pro/Android 15.
Selected host checks pass: Swift Session 11 / Services 3 / Data 7; Kotlin Session
11 / Services 3 / product state 27. Seven Android SQLite instrumentation cases
also pass. All 51 selected source/overlay/fixture hashes remain unchanged and
match the checkout after execution.
Actual forms create without switching, select explicitly, retain Notes under stable account IDs, rename with a strong version, refuse a competing rename, read back a committed rename with a lost reply and explicitly review a committed create with a lost reply. Proxies verify exact strong preconditions, one attempt per named Account operation and no implicit replay. The state suites require a new review after every uncertain create, reject stale-lease results and preserve original-owner uncertainty. Secure selected-account and pending Notes process restoration, registration, identity recovery, live reads and cached outage recovery still pass in the same generated apps.
Reports: .cache/connected-ios/Results/connected-1792269824439184000.xcresult,
.cache/connected-android and Gradle test-results inside the generated output;
runner log /private/tmp/mobile-workspaces-ready-final.log. Host and UI fixtures
use separate owned API processes, preserving production guards. The generated
source files were not patched after extraction. CLI's 32 cases, inventory and
notes checks pass separately. Read construction, setup and learning order.
This preserves connected Daily starter readiness. Account warnings remain process-local; Account has no command receipts, automatic replay, invitations, membership, roles or deletion workflow. Source-only/catalog behavior, other provider/shell selections, offline startup and release/device delivery keep separate acceptance requirements.
CLI 0.17.0's untouched registration-verified output at
/private/tmp/mobile-registration-verified-yz2nc6d9/registration-verified, identity
com.example.registrationverified, module
github.com/example/registration-verified/backend, passes its own full connected
acceptance. 29 iOS checks, eight Android UI stages, seven selected SQLite tests
per platform and 21 Android product-state cases pass with zero failures/skips
on iPhone 17 Pro/iOS 26.2 and Pixel 9 Pro/Android 15. Four boundary cases per
platform and actual Go port checks also pass.
Real forms register unseeded users and require explicit sign-in. Newly issued credentials restore Personal/Notes after process termination. Duplicate input cannot change the original password. A committed registration reply is lost; proxy counters establish one attempt/commit and recovery through explicit sign-in. Original identity/socket/mail, cached reads and pending one-commit recovery still pass. Read scope, learning findings and evidence.
Both connected Daily profiles remain ready with this selected scope. Registration is separate from authenticated access and Personal bootstrap. Contact change, invitation/role/approval policy, account deletion, MFA/OIDC/passkeys and release/ physical-device acceptance remain additional product capabilities. Earlier dated evidence below retains its original scope.
CLI 0.16.0's untouched read-cache-final output at
/private/tmp/mobile-read-cache-final-pomd2psd/read-cache-final, identity
com.example.readcachefinal, module github.com/example/read-cache-final/backend,
passes its own complete connected driver. 22 iOS checks, six Android UI stages,
seven SQLite cases per platform and fifteen Kotlin product-state cases pass with
zero failures/skips on iPhone 17 Pro/iOS 26.2 and Pixel 9 Pro/Android 15.
The owned read outage proves saved first-page rendering after process restart,
read-only gating, account isolation, explicit removal and fresh recovery. Existing
identity/socket/mail and original pending-command/one-commit checks still pass.
Read scope, learning findings and actual evidence.
Both Daily + go-connected profiles remain connected starter ready with this selected capability. Cache content requires a current authenticated binding; cold restore still requires the API. Automatic sync, offline writes, multi-command queues, additional feature selections and release/device acceptance remain separate. Earlier dated evidence below retains its original scope.
CLI 0.15.0's untouched native-foundations output at
/private/tmp/mobile-native-foundations-2o0f4kjn/native-foundations, identity
com.example.nativefoundations, module github.com/example/native-foundations/backend,
passes its own complete connected driver. Thirteen iOS checks on iPhone 17 Pro/iOS
26.2 and four Android stages on Pixel 9 Pro/Android 15 execute without failures or
skips. Real SMTP capture and native HTTP/sockets establish verification/reset/change,
revoked access and external-write live reads. Prior pending command/process recovery
assertions remain required and pass. Seven Android state tests and source/CLI checks
pass separately. Read scope, findings and evidence.
Swift and Kotlin Daily + go-connected remain connected starter ready, now including this selected scope. External SMTP delivery, production deployment, other shells, registration/contact changes, multi-item sync and additional native selections remain separate. Earlier dated evidence below retains its original scope.
Backend 0.14.0 evidence: the unmodified independent service-ready output at
/private/tmp/mobile-backend-complete-mjdo0i5l/service-ready, module
github.com/example/service-ready/backend, passes its own check/race/smoke,
disposable PostgreSQL 18.6 and freshly built container operations acceptance.
Read the complete scope and observed run.
Local SMTP capture and tested restore establish the portable backend baseline;
no cloud rollout or new native screen acceptance is inferred.
CLI 0.13.0 adds one native journal slot per original deployment/principal/account. Stage commits before HTTP; settlement commits the matching receipt before clearing pending. Recovery stays explicit and unreadable stores block new writes.
Final independent output is
/private/tmp/mobile-pending-starter-4hc0bs4d/recovery-verified, identity
com.example.recoveryverified, module github.com/example/recovery-verified/backend.
Its copied driver passes real API and screen scenarios on iPhone 17 Pro/iOS 26.2
and Pixel_9_Pro/Android 15. Both retain original command IDs through process restart,
recover a withheld committed receipt, keep an unforwarded change pending after
receipt 404 and explicitly retry identical input. The proxy checks one commit per
scenario. iOS executes one UI case and Android three install-once instrumentation
stages, each without failure/skip. Native storage, owner, CLI and fixture checks
are recorded in pending evidence.
Daily + go-connected remains connected starter ready for Swift and Kotlin. This adds durable manual recovery, not offline auth/reads, a multi-item outbox, automatic sync, merging, erasure or a migration framework. Catalog gallery owners remain transient. Existing local-only and backend-ready profiles are unchanged.
CLI 0.12.0 registers --with go-connected --backend go only for Daily, on Swift,
Kotlin or both. API co-location alone preserves the local shell. The selection
copies HTTP/Session and narrow remote Notes Services, app-owned connection/screens,
secure vault composition and its own acceptance driver. The public endpoint is
strictly admitted, configured in app source and recorded in provenance; no user
account, provider credential or live worker is provisioned.
Final independent output is /private/tmp/mobile-connected-starter-z3ieecjs/launch-ready,
module github.com/example/launch-ready/backend, installed identity
com.example.launchready. Its own connected driver passes on iPhone 17 Pro/iOS
26.2 and Pixel_9_Pro/Android 15. Seven hosted iOS, two Android entry and both Android
write/restore stages pass without failures/skips. Ordinary Android units have
64 passes and two expected external-API skips; the owned driver separately runs
the real API methods. All 32 CLI cases, generated Go check/race/smoke, starter
inventory and documentation checks pass. Detailed evidence and limits are recorded
in connected construction. Actual native
workflows verify sign-in, Personal bootstrap, owned workspace selection, renewal,
remote Notes CRUD, account isolation and sign-out. iOS terminates/relaunches the
application and restores the selected workspace through Keychain. Android installs
once, uses two non-skipped instrumentation runs separated by force-stop, and
restores through the actual Keystore record; Activity recreation is separate.
This establishes a starting point for connected products with the selected scope. The shell uses one iOS scene and one Android task entry. Production registration/ recovery, roles, multi-item native pending queues, merge/sync, Files/inbox/push product selection, multiwindow coordination and release deployment/signing remain deliberate extensions. Server restart durability requires the existing PostgreSQL setup.
CLI 0.7.0 selects installation metadata under Notifications, credential v2 beside
compatible v1, and the immutable 0002 migration. Independent output
/private/tmp/mobile-installations-starter-d1q94emj/device-api, using module
github.com/example/device-api/backend, passes its own formatting/import/vet/build,
full race suite, process smoke and disposable PostgreSQL 14.24 migration/rollback/
SIGKILL recovery. Its generated root Make runner passes real HTTP proof refusal,
explicit cross-principal rebinding, old-session cleanup refusal and settled
unregister, alongside the existing auth/data/inbox/renewal/sign-out workflows.
Source conformance covers twelve-way same-ID create contention, private proof, token rotation/CAS, late cleanup/revocation, pre-registration tombstones, target uniqueness/expiry reclamation and cancellation. Forced installation, tombstone and inbox writes all roll back retirement. A compiled process retains registration through SIGKILL, then recovers blocked revocation after another kill and verifies raw-token erasure. Capability tests retain v1's exact shape and enforce v2 edge caller policy. All 28 CLI cases and starter inventory checks pass.
No native code changes or native readiness promotion are claimed from this backend batch. Secure installation storage, OS tokens, offline unlink, provider queues/ delivery and production retention remain separate. Read construction and limits and the learning walkthrough.
Both catalogs now bind NotificationInboxRepository on the exact current session lease. Go identity and accounts includes Account inbox with server unread count, unread filtering, paging, first-read acknowledgement, media preference and a reference detail sheet. It retains at most 200 rows. Unconfirmed mutations require full successful refresh before another change, with no auto-replay on renewal.
The shared page corpus covers scope/type/category, duplicates, missing read_at, impossible/normalized dates, count bounds and unread/cursor consistency. Two inbox service tests pass per platform. Real Go URLSession/OkHttp acceptance creates an upload-ready item, drops read and preference acknowledgements after commit, reads current state and checks another account's empty/default inbox.
Two owner tests pass per platform for uncertainty/readback and late old-account completion. iOS execution is confirmed in .cache/ios/Logs/Test/Test-FoundryCatalog-2026.10.17_12-29-08-+0300.xcresult on iPhone 17 Pro/iOS 26.2: passed 2, failed/skipped 0. Android unit XML likewise reports 2 with no failures/skips; its debug APK builds. These checks build the connected views but do not perform inbox gestures against a real API. Existing component interaction evidence remains separate. No connected CLI profile is promoted.
Read setup and the learning pattern. Native starter readiness and Go CLI 0.6.0 selection remain unchanged; generated connected inboxes, Realtime, native installation/token integration and cloud push need their own slices. Backend installation metadata is recorded above.
CLI 0.6.0 includes Notifications in the full Go selection. Independent output
/private/tmp/mobile-notifications-starter-fwo4ysh0/inbox-api, with module
github.com/example/inbox-api/backend, passes its own formatting/import/vet/build,
race suite, memory process smoke, disposable PostgreSQL 14.24 migration/transaction/
SIGKILL recovery and generated Make-runner authentication/account/Notes/Files/
Notifications acceptance. Its upload completion produces one in-app item; the
runner reads it, acknowledges it and changes the media preference.
The final copy in the same parent, inbox-final, uses
github.com/example/inbox-final/backend. It includes the new cursor/HEAD test
and finished generated setup guide; its own check target, focused race acceptance
and generated Make-runner probe pass. The earlier inbox-api copy supplies the full
independent PostgreSQL evidence for the same runtime/migration implementation.
Source conformance checks twelve-way duplicate delivery, conflicting source identity, scope isolation, suppressed replay and preference races. Forced item, inbox and scope failures roll back all notification effects. Process checks block Notifications while Files commits, kill the API, then recover delivery; another restart preserves one item, first-read timestamp and preference. The source also checks scoped/filter-bound cursors and HEAD. All 28 CLI cases and starter inventory checks pass. Native connected catalog and backend installation evidence are recorded above. Cloud push, Realtime and retention remain pending. Read the setup and learning path.
CLI 0.5.0 includes Files in the full Go backend. The independent media-final
output under /private/tmp/mobile-files-starter-hk73dwex uses
github.com/example/media-final/backend and passes formatting/import/vet/build,
race/smoke, disposable PostgreSQL 14.24 and API crash recovery, plus its generated
Make-runner auth/Files upload/download/deletion/receipt workflow. The short-module
media-api output passes memory/race and runner checks too. Private local object
storage is ignored by generated git configuration and must be retained with the DB.
Both native catalogs build and their real HTTP Files adapters pass URLSession/ OkHttp receipt recovery; each platform's two owner tests pass. These catalog screens are not part of generated native/Go auth/media composition. Cloud object storage, background transfer, long-term cleanup and physical-device performance remain separate work. Read Files construction.
CLI 0.4.0 registers Go. --platform none --backend go generates an API-only
project; adding Go to a native profile co-locates an independent API. This first
selection includes Health, Identity, Account, Audit and Notes. No native auth/data
integration or backend module subset is implicit.
Fresh outputs outside this checkout at /private/tmp/go-starter-acceptance-q7d088qa:
| Output | Identity | Observed evidence |
|---|---|---|
| canopy-api | github.com/example/canopy-api/backend | Go formatting/import policy/vet/build/race and smoke; real generated Make-runner auth/account/Notes/CAS/receipts/renewal/sign-out; full disposable PostgreSQL suite and API crash recovery. |
| canopy-combined | a.example/canopy/backend; com.example.canopycombined | Both native local-data apps build; renamed Go formatting/import/vet/build/race checks pass alongside native output. |
| ready-api | example.com/ready-api/backend | Final registered inventory; Go checks/race/smoke and generated runner acceptance pass. |
28 CLI cases pass with zero failures, including six backend-focused cases. The source/fixture/migration/import closure is copied, module/path policy rewritten, source kept unchanged and output contains no required checkout references. Project Compose names/volumes are independent; Compose configuration validates. PostgreSQL execution used isolated local 14.24 because Docker's VM storage is read-only; the pinned 18.6 Compose runtime was not started. Dependencies/toolchains used installed caches; cold installation and release deployment remain separate.
The short a.example module exposed import-order drift after renaming. Sorting ordinary import groups in the generator fixed formatting without requiring Go at initialization. Co-located native builds do not establish auth/data wiring or new native device behavior. Earlier standalone native local-data evidence is unchanged. Read Go construction and verification reasoning.
CLI 0.3.0 adds native-workspace and native-browse for Swift, Kotlin or both.
Daily remains the default; local-data remains a Daily-only registered combination.
The new inventories select only their own product navigation/state/screens/tests
and UI/Query/Kernel. Go, session/HTTP and graphics selection remain future work.
Fresh outputs were generated outside the checkout under
/private/var/folders/_t/3ghz_tk90d53wy21s4tb20h80000gn/T/mobile-shells-r1k8eu9q.
Observed acceptance completed 2026-10-11:
| Profile / output | Identity | Native evidence |
|---|---|---|
| Workspace / Swift-only | com.example.workspacereadyswift / Workspace Ready | Simulator build; three iOS cases on iPad Pro 11-inch (M5). |
| Workspace / Kotlin-only | com.example.workspacereadykotlin / Workspace Ready | Debug build; four actual Android cases and twenty shared unit cases. |
| Workspace / both | com.example.workspacereadyboth / Workspace Lab | Both native builds; three iPhone cases and four Android cases. |
| Browse / Swift-only | com.example.browsereadyswift / Browse Ready | Simulator build; three iPhone cases. |
| Browse / Kotlin-only | com.example.browsereadykotlin / Browse Ready | Debug build; three actual Android cases. |
| Browse / both | com.example.browsereadyboth / Browse Lab | Both native builds; three iPhone cases and three Android cases. |
All listed native results have zero failures/errors/skips. iOS has two hosted identity/state cases plus one actual UI workflow per output. Workspace verifies selection, compact Back, material retention, rotation and expanded iPad list/detail. Android additionally checks Activity recreation, bounded 800→390dp reflow and font scale 1.5 fallback without losing selected identity. Browse verifies native search, filtering, empty results, clear, detail/back and retained search/material; Android includes recreation and system Back. Product labels/IDs were configured independently, and generated guides contain no source-checkout references.
Copied Swift Kernel/Query/UI checks pass 7/3/9 (nineteen total), and Kotlin checks pass 9/3/8 (twenty total). Twenty-two CLI cases pass, including all six new shell/ platform copies, source isolation, required overlay drift, Daily default and incompatible local-data refusal. Inspected Android list/detail captures and exported iPhone/iPad navigation captures show the chosen products and layouts. Artifacts/results/logs remain in the temporary acceptance parent above.
The first Android expanded assertion matched the project title in both panes; scoping it to detail corrected that locator. SwiftUI exposes a full labeled switch row; tapping its trailing control corrected a center hit. Container identifiers also masked a Back identifier and were removed from layout wrappers. A host launch wait stalled Android's shell and Xcode's temporary manifest before execution; a sample showed dyld startup. Retried jobs with bounded tool PATH completed. These observations do not establish a product performance budget.
Observed tools: Xcode 26.2 / Swift 6.2.3 / XcodeGen 2.46.0, iOS 26.2; Gradle 9.1.0 / AGP 9.0.1 / Kotlin 2.3.20 / Compose BOM 2026.03.01, launcher JDK 21.0.6 / compilation 17, API36_Test / Android 16. UI-only placeholders do not claim durable records/settings, deep links, provider integration or release/ physical-device validation. The unchanged library closure retains the earlier first-feature service/query/mutation evidence below. Read shared step 25/native step 49 and shell behavior.
CLI 0.2.0 adds --with local-data to the existing native-daily profile, for Swift,
Kotlin or both. Omission retains UI-only scope. The registry selects a complete
combination inventory, not
an implicit overlay merge. Local manifests select the original guest Services/
Data code without HTTP/session/account dependencies. No backend is selected.
Generated outside the checkout under /private/tmp/mobile-local-data-k1y9qusq:
| Combination | Product identity | Observed checks |
|---|---|---|
| Both | Field Ready / com.example.fieldready | Both native builds; eight iOS cases; 26 Android unit and eleven Android device cases. |
| Swift-only | Swift Ready / com.example.swiftready | Independent native build; all eight iOS cases pass. |
| Kotlin-only | Kotlin Ready / com.example.kotlinready | Independent native build; 26 unit and eleven device cases pass. |
iOS has seven hosted cases plus one actual UI workflow. It validates an empty title, creates/edits, cancels deletion, terminates/relaunches the app, reads the persisted record/current count and confirms deletion. Hosted cases cover Memory/ SQLite parity, guarded admission, late commits, post-commit read failure and terminal owners. Android has three product UI cases and eight real Data cases for SQLite CRUD, corruption/version refusal and cross-instance observation. Product tests exercise validation, form actions, canceled/confirmed deletion, live counts and Activity recreation. Results report zero failures/errors/skips. UI form checks use unique records and preserve the existing collection.
Separate Android process evidence: a note was entered through native controls,
then the process was force-stopped; PID absence was verified before launching
the app again. Library displayed Process rerun persisted and its live count.
No reinstall/data clearing occurred between that write and relaunch. The inspected
capture is android-process-relaunch.png under the acceptance parent. iOS's
exported relaunch screenshot was inspected as well. The temporary emulator first
displayed a System UI timeout; its am_anr event identified com.android.systemui
startup at 22:36:58, not the product. Wait cleared it; the later app check passed.
This is emulator evidence, not a physical-device performance assessment.
Selected Swift package checks pass: Kernel 7 / Query 3 / UI 9 / Services 2 / Data 9 (30 total). Android library checks are Kernel 9 / Query 3 / UI 8 / Services 2, plus four product state-owner checks (26 total). Full reference Services checks also pass on both platforms, eleven each, after HTTP Notes source separation. Nineteen CLI checks pass, including base/local platform selections, effective overlay graph drift, required source/fixture exclusions, refusals and cleanup. Source/configuration audits find no required checkout paths in all three outputs. Built plist/APK labels/identifiers and native metadata checks confirm branding.
Observed tools remain Xcode 26.2 / Swift 6.2.3 / XcodeGen 2.46.0, Gradle 9.1.0 / AGP 9.0.1 / Kotlin 2.3.20, launcher JDK 21 with compilation 17. Runtime is iOS 26.2 and Android 16/API36_Test. The tests use installed toolchains/dependency caches; fully cold dependency installation, old OS/device coverage, accessibility, release signing, account migration, backend and synchronization remain separate. Read shared step 24/native step 48 for ownership and verification reasoning.
CLI version 0.1.0, Python 3.14.8, 2026-10-10. Generated from an unrelated working
directory into /private/tmp/mobile-foundry-cli.nQJrnN; output has its own guides,
build files, wrapper, fixtures and source provenance, with no source-checkout links.
| Combination | Product | Observed output checks |
|---|---|---|
| Swift-only | Swift Sprout / com.example.swiftsprout | Simulator build, two hosted native entry cases, installed launch and inspected capture. |
| Kotlin-only | Kotlin Sprout / com.example.kotlinsprout | Debug build, two real Activity cases, installed launch and inspected capture; fresh build with no task-cache reuse also passes. |
| Both | Orbit Lab / com.example.orbitlab | Both native builds, three hosted iOS cases and three real Android cases after adding the temporary service/query/mutation probe; both launches inspected. |
The combined output's selected library checks pass using copied fixtures: Swift
Kernel 7 / Query 3 / UI 9; Kotlin Kernel 9 / Query 3 / UI 8. Native results report
zero failures/skips; Android XML also reports zero errors. Built plist/APK identity
and label match CLI inputs. Source/configuration audit finds no required paths
back to the checkout. Gradle cache hits initially retained old source locations
in build reports; these are generated artifacts, not copied source/build inputs.
The Kotlin-only fresh build executed all 58 tasks with --no-build-cache --rerun-tasks.
The feature probe is added only to temporary output: an injected memory service returns Kernel results, a state owner settles Query/ Mutation snapshots and Today renders the counter. Android exercises real action taps; Swift checks service sharing/isolation and separately hosts native entry controls. Swift imports require explicit package link products; Kotlin uses an explicit product.R import. No foundation library changes were required.
Thirteen CLI checks pass for combinations, branding, alternate source/cwd, destination/source preservation, exclusions, refusals, failure/interrupt cleanup, installation and doctor behavior. The actual command is installed in ~/.local/bin; add that directory to PATH. Xcode 26.2 / Swift 6.2.3 / XcodeGen 2.46.0 and Android Studio launcher JDK 21.0.6 / compilation toolchain 17 / Gradle 9.1.0 / API 36 are the observed tools. iOS runtime is 26.2; Android runtime is 16. Older OS/device, release archive/signing, full accessibility, real providers and GPU budgets are outside this local UI gate. Canvas/Setup and other capabilities remain extraction candidates. Read native learning step 47 and shared step 23 for implementation/evidence.
Before announcing a profile as ready, record an actual generated-product run:
- Generate into a new temporary destination outside this repository. Include selected native modules plus their dependency closure, required resources, contracts/fixtures, wrappers and setup tooling. No references back to this checkout or its parent directories may be required by the resulting app.
- Apply product display name, iOS bundle identifiers, Android application identity and product configuration. Signing/team settings and credential namespaces must be deliberate product inputs. Preserve the reusable component names.
- Start with a small product shell. Keep kitchen-sink screens, Notes/session fixtures and graphics demos as explicit examples/capabilities rather than requiring their full gallery in every product.
- Follow the generated setup guide, build and launch each selected native app, and run its capability checks using included fixtures. Add a small product feature through the existing service/query/mutation seams to verify usability.
- Verify required dependency/resource selection, safe destination refusal, failure cleanup, source preservation and exclusion of caches, local secrets, developer signing files and machine-specific SDK settings. Record generator version, source provenance, selected profiles and actual evidence.
The first profile is local native UI with no backend; data/session/graphics can be explicit later capabilities. Swift-only, Kotlin-only and both-platform output can be admitted as each is verified. Connected provider profiles come afterward; durable outbox/sync is a further capability with its own acceptance scenarios.
Bento provides the useful precedent: explicit starter registration, list/init commands, independent source copies, product metadata and generated setup guides. Its current native support must be designed separately: the existing Bento CLI registers Node/Go starters, and its mobile profile is Expo rather than Swift/Kotlin.
The implemented mobile-foundry CLI uses Python standard library
and provides list/init/doctor. It selects Swift/Kotlin/both and product identity
from registered Daily/Workspace/Browse profiles. Backend none remains default;
Go is independently verified and available, including backend-only output.
Local-data is an optional registered
capability for Daily; other capabilities and Canvas/Setup require later extraction/acceptance.
Template overlays belong in templates;
reusable source stays in native modules. Connected native provider profiles follow
their own implementation and acceptance after the standalone Go extraction.
The five shell variations remain app-owned examples. Daily now has separate clean entries: Swift and Kotlin. Swift-only, Kotlin-only and combined Daily copies passed the independent gates above, with and without local-data. Workspace/Browse select distinct UI-only overlays with their own independent acceptance gate. Next candidates are Canvas/Setup or session/HTTP/graphics selection. See standalone verification reasoning and template ownership.