docs(arch): realism leads the quality list; performance moves to the end

Owner decision: prioritise realism, keep the performance target but put it last.

- Quality goals reordered (01 + combined architecture.md): 1 visual realism,
  2 geographic fidelity, 3 walkability/usability, 4 reproducibility/portability,
  5 provenance, 6 performance efficiency.
- Quality requirements (10 + combined) reordered to match, with two new realism
  requirements (façade reads like the photographs; placement within ~1 m) and the
  quality scenarios renumbered so QS-1 is the reference comparison and QS-9 the
  frame rate.
- Both documents carry the same guard so the order cannot become an excuse:
  performance is a floor, not a preference - 60 FPS at 1440p without frame
  generation must be met at every release; if realism cannot fit, the realism scope
  is cut deliberately and recorded, never the frame rate. Walkability outranks
  realism in one direction: a block you fall through is not a demo.
- Solution strategy and 'quality achievement' now lead with realism and describe
  performance as a budget rather than a driver.
- Docs/release-checks.md: the performance check is the last check, with that reason
  stated; ROADMAP gains a 'Quality priority' section; AGENTS.md gains the tie-break
  rule beside the existing scope-cutting rule.

Docs/release-checks.md

@@ -13,15 +13,6 @@ Record results in the table at the end of this file, with the date, the exact bu
 3. **Licensing.** Every new asset has provenance in `THIRD_PARTY_NOTICES.md`, or is recorded as unresolved and kept out of the build.
 4. **Version discipline.** Patch releases contain fixes, optimisation, docs, or tuning only — no new scope.
 
-## Performance check
-
-Measured at 1440p on the development workstation: Bazzite, Ryzen 7 7700X, 64 GB RAM, RTX 5070 Ti 16 GB.
-
-- Record the quality preset, the exact upscaling state (off, DLSS/TSR/FXAA and mode), and the engine version.
-- Report frame rate without frame generation and with frame generation, separately.
-- Target: 60 FPS at 1440p without frame generation.
-- Capture a frame-time graph over a fixed traversal route, not a single sample. State the route.
-
 ## `0.1.0` checks
 
 1. Player traverses both the south-side frontage and the north-side frontage of the demo without falling through geometry, including the designated crossing. Walk the route twice: once normally, once with collision debug visualisation enabled.
@@ -32,6 +23,17 @@ Measured at 1440p on the development workstation: Bazzite, Ryzen 7 7700X, 64 GB
 6. Linux build packaged and launched; controls documented in `Docs/` and shown in-game.
 7. Tag `v0.1.0`, write the `CHANGELOG.md` entry, then remove the completed section from `TODO.md` (its goal stays in `ROADMAP.md`).
 
+## Performance check (last)
+
+Performance is the **last** check on purpose: realism leads the design and the frame budget only decides how much of it fits. It is still a floor — a release is not tagged below 60 FPS at 1440p without the owner's explicit approval.
+
+Measured at 1440p on the development workstation: Bazzite, Ryzen 7 7700X, 64 GB RAM, RTX 5070 Ti 16 GB.
+
+- Record the quality preset, the exact upscaling state (off, DLSS/TSR/FXAA and mode), and the engine version.
+- Report frame rate without frame generation and with frame generation, separately.
+- Target: 60 FPS at 1440p without frame generation.
+- Capture a frame-time graph over a fixed traversal route, not a single sample. State the route.
+
 ## Check-record template
 
 | Version | Check | Result | Evidence | Date |