Non-Functional Requirements — Retired

:::caution This page is retired Non-functional requirements now have a single, cross-version authority: requirements/nfr.md. NFRs are inherently cross-version (a coverage threshold is tightened across releases, not re-authored per release), so they are catalogued once there rather than restated per version. This page's four original entries map as:

• REQ-NFN-01 (performance), REQ-NFN-02 (modularity), REQ-NFN-03 (test coverage) — unchanged ids, now in nfr.md with an explicit Introduced version and (for coverage) a correction to the actual CI-enforced gate value.
• REQ-NFN-04 (Pydantic v2 / Jinja2) — split into REQ-NFN-04a (Pydantic for the IR, v1.0), REQ-NFN-04b (Pydantic for translation caches, retargeted to v4.0+ since translation itself is v4.0+ scope), and REQ-NFN-04c (Jinja2, v1.0).

nfr.md also adds a fifth category, Operability (REQ-NFN-05..REQ-NFN-10), backfilled from RUNBOOK.md and closed incident records — reliability properties (stale-lock recovery, golden-master fixture protection, self-hosted CI resilience, temp-directory cleanup, credential hygiene, the Markdown quality gate) that were already engineered but never had a formal requirement id. :::