Publish Chimera GFX source

docs/retroarch/phase-1.0b-proposed-one-shot-test.md

@@ -0,0 +1,49 @@
+# Proposed Phase 1.0B one-shot test
+
+Status: proposal only. Transfer and execution are not authorized.
+
+## Preconditions for a later review
+
+- bind approval to the complete ELF SHA-256, size, source commit and manifest
+  SHA-256;
+- operator independently confirms firmware 9.60 in the PS5 UI;
+- autoload remains disabled and no live path is selected or replaced;
+- exactly one transfer and one execution are separately authorized;
+- no retry, reinstall, backup, recovery, configuration or second payload is
+  combined with the window;
+- operator accepts all risks in the device-risk assessment.
+
+## Expected visible sequence
+
+1. A software framebuffer appears with `CHIMERA RETROARCH PS5 SMOKE TEST`.
+2. Initialization can pass rapidly through `S01`-`S06`; these phases are not
+   guaranteed to receive their own visible frame.
+3. `S07` shows increasing monotonic time/frame count, VideoOut/flip index,
+   320 x 240 source with destination pitch/dimensions, XRGB8888 format code,
+   controller buttons/sticks, AudioOut counters, core state and `E000`.
+4. Holding Options for two seconds shows hold progress and requests `S08`.
+   Without input, 60,000 ms or 3,600 frames requests the same bounded path.
+5. The final visible frame can show `S08` and its shutdown reason.
+6. `S09`-`S15` run after the last present; `_Exit` ends the child. No visible
+   completion frame is promised.
+
+## Operator stop criteria
+
+Do not retry. Stop the window and record the last visible phase/error when:
+
+- no image appears;
+- framebuffer bounds are `FAIL`;
+- any error other than `E000` appears;
+- flip count stops advancing;
+- input state is implausible or Options does not progress;
+- AudioOut submit time grows unexpectedly or frames stop;
+- the screen freezes beyond 60 seconds;
+- RetroArch exits before the expected phase;
+- the jailbreak/host session disappears;
+- any write-firewall trip is shown;
+- any unexpected notification, install, autoload, network or filesystem
+  behavior is observed.
+
+If the child does not exit, the proposal permits no automated kill, retry or
+reboot command. The operator may later decide manually whether a console
+reboot is necessary, outside the authorization window.