What is actually left

Chain 1Deploy — strictly ordered

The first two steps are trivial and the third is the only genuinely uncertain one, because secrets, routes, DNS and migrations have never been exercised together.

1. Align the pnpm pin agentS11.20.0 → 11.25.0 in 8 places across 5 workflows. Currently breaks every env check and both deploy workflows.
2. Merge the env-schema fix agentSAlready written. It was never a credential problem. → faloos PR #223
3. First staging deploy agentMHas never happened once. This is where unknowns surface. → faloos #118
4. Manual acceptance MohammedMStaff login, CDD approve/fail, ledger reversal, role assignment, cold load. → faloos #218
5. Promotion evidence agentMArtifact digest, migration evidence, rollback drill. → faloos #211
6. Production agentMNeeds the GitHub plan upgrade for the required-reviewer gate.

Chain 2Native & App Store — parallel, now unblocked

The first two steps are done. The app record exists on IDK UNO LTD and the build config points at it, so everything remaining here is ordinary agent work up to the device checks.

1. App Store record — DONE SCreated on the IDK UNO LTD provider: app ID 6809646079, bundle com.faloos.native. Apple registered the bundle ID automatically and renamed the listing "Faloos - native" because "Faloos" was taken — changeable before submission. → App Store Connect
2. ascAppId wired — DONE SBoth placeholders replaced with 6809646079 and pushed (23fbc18).
3. First EAS build agentMProject and build profiles already configured.
4. TestFlight external + Beta App Review MExternal testers, never the internal track.
5. Store metadata, privacy, screenshots M
6. Device acceptance MohammedSPush end-to-end, avatar lifecycle, name persistence. No simulator, ever. → faloos #218

Chain 3Product gaps — the real long pole

Of the 64 canonical v0 screens, 17 were flagged undesigned and all 17 now have final dispositions (faloos #33). Exactly one native journey is unbuilt: the social layer — friends feed, likes, counters. The only L item in this chain, and it decides submission timing more than any engineering step. It is not the only unbuilt work overall: the 22 back-office parity screens in Chain 4 are specified and largely unbuilt too. → faloos #36

Push (#37) and profile editing (#38) already have merged code; they wait on device acceptance, not development.

Chain 4Back-office parity — every screen, specified

The legacy console carried 172 unique admin routes. Roughly 40 were website CMS and a further cluster was forked-template scaffolding whose database tables were never created. Stripping those, the real operational surface is 22 specified screens. Each issue below carries a full requirements spec — purpose, legacy behaviour, data, states, actions, viewports, tokens, out of scope.

First slice in flight: an aggregate API plus five report screens, design only — nothing built or run, and it stays draft until real runtime evidence exists. → work PR #1

WaitingFive open decisions, plus one already closed

• App Store record — done, nothing neededCreated on IDK UNO as 6809646079. Optional: tell me the display name you want, since Apple auto-renamed it "Faloos - native".
• Social layer: in v1, or cut?The only unbuilt native journey — the 22 back-office parity screens are a separate body of unbuilt work. Decides submission timing.
• Palette directionCobalt, which every existing screen uses, versus the navy-and-aqua set the new reports were built in.
• Close the merchants issue?A merchant auth guard existed, but no merchants table was ever created.
• GitHub plan upgradeRequired for the production reviewer gate.
• Fee changes and unsettled paymentsA safe default is already applied: new rules affect only payments initiated afterwards.

GreenAlready done, not at risk