govkit-genai-preflightlisted

# LLM Application Preflight Run after `/govkit-architecture-preflight` for a model-backed feature. Determine the feature name from the user's request; if it is not provided, ask before proceeding. ## Required extension Confirm `extensions/llm-application/manifest.yaml` exists. If it is missing, stop and report: ```bash govkit extension add llm-application --target . ``` Do not reconstruct the contracts from agent knowledge. ## 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` Extension contracts: - `extensions/llm-application/docs/backend/architecture/LLM_GATEWAY_CONTRACT.md` - `extensions/llm-application/docs/backend/architecture/LLM_OBSERVABILITY_CONTRACT.md` - `extensions/llm-application/docs/backend/architecture/MODEL_GUARDRAILS_CONTRACT.md` - `extensions/llm-application/docs/backend/architecture/LLM_EVALUATION_CONTRACT.md` Also read `docs/backend/architecture/TECH_STACK.md` and applicable ADRs for selected implementation products. Product configuration never overrides an extension contract. ## Validation checklist ### 1. Gateway boundary (Section 10) - Identify the typed outbound model gateway port and adapter boundary - Identify logical model capabilities or aliases; reject provider identifiers in domain code - Record routing, capability, fallback, retry, timeout, cancellation, streaming, and de