Rebuild operator UI around product environments

[cbusillo]

Goal

Replace the current transitional Launchplane UI with a product operations surface after the product/environment API contract lands.

Direction

Do not refine the current context-picker/product-config mental model into the target UI. Reuse only pieces that fit the new model: session/auth client, API wrapper, status/evidence formatting, and theme basics.

Depends on completed backend/API plan #152 and completed backend readiness plan #161.

UI scope

• Start on product list / product overview, not a raw context picker.
• Show products such as SellYourOutboard, VeriReel, Odoo CM, and Odoo OPW.
• Nest testing, prod, and previews under each product.
• Group runtime settings and secrets by product/environment.
• Show promotion dry-run and workflow dispatch with action availability reasons.
• Put raw records, contexts, and provider details behind advanced diagnostics.
• Browser-validate desktop and narrow/mobile widths.

Done when

• The primary UI no longer exposes legacy context names as the picker model.
• Product/environment state comes from the API built in Finish product/environment API before UI rebuild #152.
• Secret values are never revealed and submitted secret values are cleared immediately.
• Signed-in browser validation proves SYO dry-run promotion and workflow dispatch with no prod mutation on dry-run.

Current Status

State: Product-first operator UI rebuild has a deployed selected-lane readiness fix. PR #434 scopes expected config rows and summary counts to the active stable environment so an unrelated lane cannot make the selected lane appear blocked.
Next action: Validate the signed-in SellYourOutboard dry-run and workflow dry-run path against the deployed service, then decide whether #153 is close enough to mark ready or needs one final diagnostics/activity slice.
Blocked by: Live SYO validation still depends on signed-in browser/session access and product workflow availability.
Last verified: 2026-05-08 after PR #434 merge: pnpm --dir frontend validate, PR CI/Security/CodeQL, post-merge CI/Security/CodeQL, Deploy Launchplane run 25531169853, and live health trace launchplane_req_2289b1ede9e44daca1d2ef60bd580acf.

Decisions

• The current transitional UI is not the target and should not receive further product workflow polish.
• UI rewrite should restart from a fresh design pass with Claude Design and Codex Desktop, with Code helping implementation and validation.
• Product/environment API behavior must be proven before design starts so the new UI models the right operations.

Relationships

• Unblocked by completed Prove backend/API product workflows before UI rewrite #241.
• Restart the operator UI from Claude Design/Codex Desktop; do not continue old UI implementation work.
• Retire file-backed state compatibility paths #163 remains non-blocking transition debt; the new UI must use service/read-model APIs and must not model file-backed state as canonical.
• Absorb remaining product-repo orchestration into Launchplane drivers #164 is related for broader Odoo/product-repo orchestration, not a blocker for the first generic-web/SYO UI unless scope expands.

Open Questions

• Is the first UI slice strictly generic-web/SYO, or should it include any Odoo/tenant operations? If Odoo is included, Absorb remaining product-repo orchestration into Launchplane drivers #164 and related tenant/devkit blockers must be resolved or explicitly deferred.
• Should Add SellYourOutboard prod backup gate after initial launch #100 SellYourOutboard prod backup gate be required before showing prod promotion controls in the rebuilt UI, or should the first UI expose dry-run/proof surfaces only until that gate exists?
• Should Add supported authz policy mutation and reload operator workflow #83 authz policy mutation/reload be included in the first operator UI, or remain operator/API maintenance outside the initial product-environment UI?