genai-preflightlisted

# GenAI Preflight Run after `/architecture-preflight` to validate GenAI-specific architecture decisions for a feature. Determine the feature name from the user's request; if it is not provided, ask before proceeding. ## Inputs to read Feature specs: - `features/<feature_name>/nfrs.md` - `features/<feature_name>/acceptance.feature` - `features/<feature_name>/eval_criteria.yaml` - `features/<feature_name>/architecture_preflight.md` (sections 1-9 should already be complete) L5 Contracts: - `docs/backend/architecture/LLM_GATEWAY_CONTRACT.md` - `docs/backend/architecture/OBSERVABILITY_LLM_CONTRACT.md` - `docs/backend/architecture/GUARDRAILS_CONTRACT.md` - `docs/backend/architecture/EVALUATION_LLM_CONTRACT.md` ## Validation Checklist For each item, validate and document the finding: ### 1. LLM Gateway (Section 10) - Confirm LiteLLM is configured as the sole gateway - Identify model alias(es) to be used - Confirm fallback chain is defined (or justify single-provider) - Confirm cost budget is documented in nfrs.md under "LLM Cost" - Check for prohibited direct provider SDK imports ### 2. Observability (Section 11) - Confirm OpenLLMetry instrumentation is planned - Confirm Langfuse trace export is configured - Determine if prompt versioning in Langfuse applies - Confirm environment matrix alignment ### 3. Guardrails (Section 12) - Determine guardrail mode: `nemo`, `guardrails-ai`, `both`, or `none` - If `none`, confirm justification exists (non-user-facing feature) - If `nemo