X-Git-Url: https://git.jtryba.com/browse/friidump.git/blobdiff_plain/d44030dfa440b1967ec7dcd3ccfe46fb69934486..29417fff9ebac65b1cf60ea8951c687696302c55:/friidump-handoff.md

diff --git a/friidump-handoff.md b/friidump-handoff.md
index 93f3c75..4be8970 100644
--- a/friidump-handoff.md
+++ b/friidump-handoff.md
@@ -1,101 +1,37 @@
+# FriiDump Candidate21 Handoff
 
-# FriiDump / GC-Wii Work Handoff
+Candidate20 established the Linux Xbox game view twice on the USB
+`HL-DT-ST DVD-ROM GDR8050L 0012`, read Red Faction II XDVDFS data, captured the
+32-sector game lead-in, produced a 482,115,584-byte controlled partial image,
+hashed it, wrote an atomic native report, and completed STOP UNIT.
 
-**Purpose:** Continue the current FriiDump + Project Frankenstein GameCube/Wii support work without requiring the user to re-explain project context.
+Candidate20 evidence SHA-256:
 
-## Scope
+`f82ceb50ca7e41d3a9c962557b2dadb47276c767da756721bb9e4337572742d2`
 
-This is **not** a project specification. It is a handoff for the next engineering agent.
+Two acceptance findings remained:
 
-## Current Objective
+1. Step 9 sticky descrambling returned CHECK CONDITION `05/81/00`, but both
+   final capacity checks reported 3,431,264 sectors and XDVDFS data was
+   readable. The transport result remains logged as FAIL, while the live
+   acceptance policy treats it as non-blocking when game-view proof succeeds,
+   matching the copied Windows path's outcome-based authority.
+2. Media ID was empty. The portable READ DVD STRUCTURE helper placed Format in
+   CDB byte 11 instead of byte 7. The copied Windows `GetMediaID()` path uses
+   byte 7. Candidate21 corrects this boundary and adds persistent
+   `[XBOX-DVD-STRUCTURE]` PFI/DMI diagnostics.
 
-Use Project Frankenstein Stage5B firmware analysis to improve FriiDump's HLDS GameCube/Wii support, then validate every supported profile on real hardware.
+Candidate21 does not add RecoveryKick or any generic recovery/authentication
+sequence.
 
-The workflow is:
+Validation order:
 
-1. Recover parser information from firmware (Stage5B).
-2. Integrate into FriiDump.
-3. Validate on owned hardware.
-4. Feed results back into the analyzer.
+```bash
+bash ./validation/friidump-v0.5.3.16-pf1-candidate21-linux-live-validation.sh build
+bash ./validation/friidump-v0.5.3.16-pf1-candidate21-linux-live-validation.sh capability
+```
 
-## Major accomplishments
-
-- Added analyzer-derived HLDS profile support.
-- Added media preflight before vendor seed retrieval.
-- Added STOP UNIT after successful dumps.
-- Added profile reporting.
-- Added live INQUIRY alias support.
-- Validated multiple GDR-8163B firmware revisions on real hardware.
-- Validated GCC-4244 B101 and B103 on real hardware.
-- Validated GCC-4243N A102 on real hardware.
-- Captured canonical firmware dumps for GCC-4243N A102 and GCC-4244 B101.
-
-## Important engineering observations
-
-- Trust live firmware/INQUIRY over stickers.
-- Preserve firmware provenance.
-- Prefer exact Stage5B-derived parser profiles over legacy Type3 fallbacks.
-- Hardware validates analyzer discoveries.
-
-## Current hardware validation status
-
-### Validated
-
-**GDR-8163B**
-- 0B30
-- 0D20
-- 0E15
-- 0L20
-- 0L23
-- 0L30
-- 0M26
-
-**GCC-4244**
-- B101
-- B103
-
-**GCC-4243N**
-- A102
-
-## Firmware dumps completed
-
-- GCC-4243N A102 (canonical)
-- GCC-4244 B101 (canonical)
-
-These should be analyzed by Stage5B to determine whether new promoted parser profiles or aliases are appropriate.
-
-## Owned hardware inventory (validation targets)
-
-- GDR-8163B x15
-- GDR-8081N x3
-- GCC-4241N x5
-- GCC-4243N x5
-- GCC-4244N x9
-- GCC-4160N x3
-- GWA-4164B x1
-- GSA-H73N x1
-- GH22NS30 x1
-
-Do **not** ask the user to test drives outside this inventory.
-
-## Immediate next work
-
-1. Analyze GCC-4243N A102 firmware.
-2. Analyze GCC-4244 B101 firmware.
-3. Update FriiDump with any new aliases/promoted profiles.
-4. Continue owned-hardware validation in this order:
-   - GCC-4241N
-   - GCC-4160N
-   - GWA-4164B
-   - GSA-H73N
-   - GH22NS30
-
-GDR-8081N remains a separate research effort and should not be modified until its firmware evidence supports doing so.
-
-## Notes for the next agent
-
-- Avoid re-implementing already completed features (media preflight, STOP UNIT, profile reporting).
-- Use analyzer results as the primary source of truth.
-- Prefer evidence over assumptions.
-- When suggesting validation work, consult the user's current hardware inventory first.
-- The long-term architectural document is PFES; this file is only a transition handoff.
+Windows MSVC validation is required before the final physical Linux Xbox smoke.
+The final smoke must report media ID `TQ00501A`, successful DMI capture, both
+game-view transitions, controlled cancellation, hashes, native report, and
+STOP UNIT.