docs(status): record the RSP-category Phase 2 criterion as met

[doublegate]

Motivation

docs/STATUS.md is the single source of truth, and it fell out of date after
the RSP work in #41–#44. It still listed the RSP vector unit as a stub ("COP2
retires inertly") and reported 250 suite-wide failures (now 93).

Changes (docs-only)

• Both n64-systemtest readiness tables now carry the RSP-category criterion as
  MET — 0 RSP-prefixed failures, down from ~413 at Phase 1 close.
• The RSP vector unit (full VU ISA, load/store, reserved opcodes) and the DPC
  command registers are marked implemented.
• BREAK semantics note updated (halts in a taken branch's delay slot).
• An explicit Phase 2 status: one of two exit criteria met; v0.3.0 is not
  cut until the microcode / RDP-command-list criterion also holds.
• Suite-wide count corrected 250 → 93 with the current category breakdown.

Verification

The MET claims are the committed #[ignore]d n64-systemtest runner, not a
self-assessment. RSP-category zero was confirmed by dumping every remaining
failure and checking none are RSP-prefixed.

markdownlint green.

🤖 Generated with Claude Code

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 60c51091-4fa6-42ef-8c7c-838f66404ace

📥 Commits

Reviewing files that changed from the base of the PR and between 177ffff and df6680e.

📒 Files selected for processing (1)

• docs/STATUS.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated project status: Phase 1 marked complete; Phase 2 RSP exit criterion confirmed met with 0 RSP-prefixed failures.
  • Refreshed n64-systemtest accuracy-gate results, including updated CPU/COP0/TLB/COP1 and Phase 2 RSP figures.
  • Revised test-ROM gate execution details to reflect three gates producing real results today; updated roadmap (RSP vector unit implemented, RDP DPC command registers implemented; RDP rasteriser still stubbed).

Walkthrough

Updates docs/STATUS.md with completed Phase 1 and RSP Phase 2 criteria, implemented RSP/DPC roadmap entries, three active test gates, and revised n64-systemtest accuracy results.

Changes

Status documentation

Layer / File(s)	Summary
Milestones and implementation roadmap docs/STATUS.md	Phase 1 and the RSP Phase 2 criterion are marked complete; RSP vector-unit and DPC register entries are marked implemented, while RDP rasterisation remains stubbed.
Test corpus and accuracy gates docs/STATUS.md	Three gates now report real results, and the n64-systemtest tables record zero failures for CPU/COP0/TLB/COP1 and RSP-prefixed tests.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• doublegate/RustyN64#28: Documents COP1 progress and the resulting n64-systemtest failure counts.
• doublegate/RustyN64#29: Updates Phase 1 status and n64-systemtest failure results after VR4300 FPU changes.
• doublegate/RustyN64#40: Defines the Phase 2 RSP exit criteria reflected by the updated status documentation.

🚥 Pre-merge checks | ✅ 9 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Changelog Entry For User-Visible Changes	⚠️ Warning	FAIL: this user-visible docs update has no corresponding [Unreleased] entry in CHANGELOG.md.	Add an [Unreleased] changelog bullet for the STATUS.md changes (RSP MET, Phase 2 update, count corrections).

✅ Passed checks (9 passed)

Check name	Status	Explanation
Title check	✅ Passed	Uses Conventional Commits form, stays under 72 characters, and matches the docs-only status update.
Description check	✅ Passed	The description aligns with the STATUS.md documentation updates and the RSP Phase 2 criterion change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Oracle Number Is Stated	✅ Passed	PASS: docs/STATUS.md states the current oracle figure (0 RSP-prefixed failures, suite-wide 93), and the PR is docs-only, which this check exempts.
Docs-As-Spec Sync	✅ Passed	Only docs/STATUS.md changed; no chip-crate source files are in the diff, and the PR body says the change is docs-only.
Measured, Never Tuned	✅ Passed	The only new numerals are failure counts (413→93); no new hardware constant or timing value was added, and existing clocks are already ADR/ledger-anchored.
Unsafe Stays Out Of The Chip Crates	✅ Passed	PR diff touches only docs/STATUS.md; all chip crates and rustyn64-core still have #![forbid(unsafe_code)], and no unsafe blocks/fns/impls were found in Rust code.

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/STATUS.md`:
- Around line 114-116: Update the three status rows in the documentation table
to include provenance for each hardware-behavior claim: cite authoritative
manual sections or accuracy-ledger entries and name regression tests covering
BREAK delay-slot behavior, reserved VU operations, and DPC START_VALID
double-latching/FREEZE semantics. Ensure undocumented behavior has both a cited
source and a test that fails if the behavior changes.
- Around line 13-28: Update the stale “not executable” status claims in
docs/STATUS.md, especially the statements around the n64-systemtest count and
runner output, to reflect the now-available real gate results shown in the
current status section. Remove or revise the conflicting Sprint 2 and “never
reports a real number” wording so the document consistently presents Phase 1 as
complete and treats docs/STATUS.md as the authoritative source.
- Around line 13-14: Add the RSP test started/completed count to the Phase 2 RSP
status entry at docs/STATUS.md lines 13-14, alongside the existing zero-failure
evidence. Apply the same count update to the corresponding RSP entry at
docs/STATUS.md lines 195-196, preserving the existing phase status and test
command.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d9813086-af98-4dc1-97b5-2813ebef7cd7

📥 Commits

Reviewing files that changed from the base of the PR and between b13dd53 and 376dfe3.

📒 Files selected for processing (1)

• docs/STATUS.md

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/STATUS.md`:
- Line 14: Update the n64-systemtest status entry to remove the ambiguous “was
~413 at Phase 1 close” parenthetical or explicitly qualify ~413 as the
suite-wide failure count. Preserve the existing RSP category result and use
docs/STATUS.md as the authoritative wording for historical counts.
- Around line 99-106: Update the opening sentence in the status section to say
“Three gates execute real results today,” distinguishing executable gates from
corpus entries while preserving the existing details about basic.z64,
n64-systemtest, and golden-log.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d529a565-d1e8-46c4-95be-9d9f3015085a

📥 Commits

Reviewing files that changed from the base of the PR and between 376dfe3 and 177ffff.

📒 Files selected for processing (1)

• docs/STATUS.md