plan

# Plan Generate a complete plan for feature implementation with thorough research. The plan must contain enough context for an AI agent to implement the feature in a single pass. Codex is the primary planner in this workflow. If you also have a separate Claude workflow available, treat it as an optional second-opinion lane rather than the source of truth. ## Step 1: Mandatory Repo Audit Do not start drafting until you have verified the current repo shape for the feature area. ### Verify These Facts In-Repo - Primary entrypoint(s) and integration surfaces relevant to this feature - Exact module names and singular/plural usage - Validator/controller/service directory layout in the affected area - Actual data-model/schema/type source of truth used by this codebase - Existing user-facing or operator-facing surface(s) this feature extends - Shared type/export hubs if cross-app types are needed - Actual validation/build/typecheck workflow used by this repo ### Repo Audit Rules - Do not assume any specific stack or layout. Discover the actual routing, validation, schema, frontend, and build patterns used by the current repo. - Every existing file path cited in the final plan must have been opened in this session. - Mark every path in the final plan as either `existing` or `new`. - Never cite a line number unless it was verified in the current checkout. - Never let template/example paths leak into the final plan. - If the brief or user request conflicts with repo reality, a...