FriiDump 0.5.3.16: finalize release identity and documentation

[friidump.git] / docs / reports / FRIIDUMP_NATIVE_COMPATIBILITY_REPORTING_0.5.3.16.md

diff --git a/docs/reports/FRIIDUMP_NATIVE_COMPATIBILITY_REPORTING_0.5.3.16.md b/docs/reports/FRIIDUMP_NATIVE_COMPATIBILITY_REPORTING_0.5.3.16.md
index 5f8635593d13aad7ccc36db8949f71a3ef7e2aef..259f639ed2a7867183919531933ebfb0af6ffc38 100644 (file)
--- a/docs/reports/FRIIDUMP_NATIVE_COMPATIBILITY_REPORTING_0.5.3.16.md
+++ b/docs/reports/FRIIDUMP_NATIVE_COMPATIBILITY_REPORTING_0.5.3.16.md
@@ -2,11 +2,11 @@
 
 ## Status
 
 
 ## Status
 

-This is a source candidate for Windows and physical-drive validation. It is not
-a promoted release and does not replace `v0.5.3.15-pf1`.
+This document records the implementation and accepted validation basis for
+FriiDump 0.5.3.16-pf1. Candidate-specific reports remain historical evidence;
+the release identity is the annotated tag and its exact commit/tree.

 
 ## Scope
 
 ## Scope

-

 The change adds native `friidump-test-result.v1` generation to normal dump
 invocations. It deliberately excludes broad drive-research discovery; that
 work remains assigned to a separate future utility.
 The change adds native `friidump-test-result.v1` generation to normal dump
 invocations. It deliberately excludes broad drive-research discovery; that
 work remains assigned to a separate future utility.


@@ -103,19 +103,19 @@ The source includes fixtures for:
 The fixtures are validated against the exact Compatibility Database v1.2.0 JSON
 Schema. The database PHP semantic validator is used during package validation.
 
 The fixtures are validated against the exact Compatibility Database v1.2.0 JSON
 Schema. The database PHP semantic validator is used during package validation.
 

-## Remaining promotion gates
-
-Before a release can be promoted:
-
-1. Build with the maintained Visual Studio 2019 32-bit toolchain.
-2. Run the MSVC fixture tests.
-3. Validate no-media reporting on a real drive.
-4. Validate a complete GameCube or Wii report.
-5. Validate a controlled partial cancellation.
-6. Validate Xbox assembled-output reporting on the applicable hardware path.
-   The copied GDR-8050L reference dumper remains a special Windows-only path;
-   complete output reporting must be validated there, and Ctrl+C cancellation
-   must not be claimed for that path until its copied loops receive an explicit
-   cancellation callback.
-7. Submit generated reports to the live v1.2.0 database and confirm acceptance.
-8. Review exact report contents before assigning a release tag.
+## Accepted validation basis
+
+The release campaign completed these gates:
+
+1. Maintained Visual Studio 2019 32-bit build and fixture execution.
+2. Linux/CMake build and raw-I/O authorization preflight.
+3. Real-drive no-media and controlled-partial reporting.
+4. Complete GameCube validation with an exact known-good image hash.
+5. Original Xbox GDR-8050L game-view, XDVDFS, DMI/media-ID, native-report,
+   controlled-cancellation, hashing, and STOP UNIT validation.
+6. Exact report review and compatibility-database acceptance.
+7. Candidate publication and exact fast-forward promotion to canonical `main`.
+
+The copied Windows challenge-drive loops retain their documented cancellation
+boundary. No broader cancellation claim is inferred from the portable Linux
+path.
\ No newline at end of file