X-Git-Url: https://git.jtryba.com/browse/friidump.git/blobdiff_plain/d44030dfa440b1967ec7dcd3ccfe46fb69934486..3faddd693c9198081778561c683f21c7904c7376:/friidump-handoff.md?ds=sidebyside

diff --git a/friidump-handoff.md b/friidump-handoff.md
index 93f3c75..5e5ddec 100644
--- a/friidump-handoff.md
+++ b/friidump-handoff.md
@@ -1,101 +1,33 @@
-
-# FriiDump / GC-Wii Work Handoff
-
-**Purpose:** Continue the current FriiDump + Project Frankenstein GameCube/Wii support work without requiring the user to re-explain project context.
-
-## Scope
-
-This is **not** a project specification. It is a handoff for the next engineering agent.
-
-## Current Objective
-
-Use Project Frankenstein Stage5B firmware analysis to improve FriiDump's HLDS GameCube/Wii support, then validate every supported profile on real hardware.
-
-The workflow is:
-
-1. Recover parser information from firmware (Stage5B).
-2. Integrate into FriiDump.
-3. Validate on owned hardware.
-4. Feed results back into the analyzer.
-
-## 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.
+# FriiDump 0.5.3.16-pf1 Release Handoff
+
+## Accepted implementation authority
+
+- Promoted main commit:
+  `29417fff9ebac65b1cf60ea8951c687696302c55`
+- Promoted implementation tree:
+  `d9a03be5b4ca5a5d2c5f5a14400a9ba3488c56db`
+- Candidate branch:
+  `candidate/v0.5.3.16-pf1-candidate21`
+
+Candidate21 closed the Linux GDR-8050L DMI boundary by placing READ DVD
+STRUCTURE Format in CDB byte 7. Physical validation captured media ID
+`TQ00501A`, established both game-view transitions, read XDVDFS metadata,
+produced a controlled partial output with hashes and an atomic native report,
+and completed STOP UNIT.
+
+## Release-finalization boundary
+
+The release-finalization commit changes only release identity, active
+documentation, and the generic Linux capability helper's expected release
+version/default build path. Candidate-specific validation scripts remain
+unchanged as exact historical evidence.
+
+## Remaining release gates
+
+1. Review and accept the release-finalization commit.
+2. Build and test Windows and Linux from the exact finalization commit.
+3. Create one annotated tag `v0.5.3.16-pf1`.
+4. Push only that tag.
+5. Verify private/public tag object, peeled commit, tree, dispatcher, and exact
+   artifacts.
+6. Retire the candidate branch in a separate gate after release acceptance.
\ No newline at end of file