GPT-5.3 Codex AI Chat Assistant

Goal: route launch examples through reviewed prompt templates. Required changes: add example aggregation, update pages, update audits and docs. Out of scope: changing provider config, billing params, runtime forms, or prompt database storage. Compatibility: keep the old path only until reviewed coverage is complete. Acceptance: all launch example surfaces prefer reviewed prompt examples and typecheck passes.

Order: audit current config, compare generated facts, then update seed script. Contract: model slug, category, and provider ID must stay stable. Verification: parity check before runtime change. Rollback boundary: config generation can revert independently from UI content. Risk: changing display fields may affect SEO pages.

Touched files: prompt template source and locale files. Invariants: no code path or route behavior changed. Known risk: new pages increase static prompt count. Verification: prompts:check and SEO title audit. Next owner decision: whether to run full build before merge.

Auth question: who can access reused prompts and uploaded references. Storage question: where reference assets live and when they expire. User data question: whether prompts can contain private customer data. Abuse path: public sharing could expose private media. Review owner: security and product need retention rules before launch.