Publish Chimera GFX source
phase0-ci / build-and-audit (push) Successful in 2m14s

This commit is contained in:
Chimera GFX release export
2026-09-03 03:27:14 +02:00
commit a6037502d7
828 changed files with 100454 additions and 0 deletions
@@ -0,0 +1,40 @@
# Phase 1.0DB: post-CZ differential analysis
Status: `RAW_CONTEXT_FAILURE_CONFIRMED_CAUSAL_BIGAPP_COMPARISON_NOT_READY`
The consumed CZ run is a valid raw-elfldr baseline, but not a successful AV
run. It reached RetroArch and SDL video initialization, then
`sceVideoOutOpen(0xff, 0, 0, NULL)` returned signed `-2144796663`
(`0x80290009`). D06 and D07 were not reached. D04 returned `-1`, remote EOF
followed, and the distinct cleanup terminal D14 was absent.
## Comparison with Phase 1.0O
O and CZ both used the raw SceSpZeroConf-based elfldr constructor, but they did
not use identical artifact bytes and their runtime state was not captured as
identical. O obtained positive handle `1309671680`, registered buffers with
result `0`, then failed the first flip with `-1`. CZ failed earlier at open.
The difference therefore cannot identify a root cause or be attributed to the
new D14 path. Public evidence does not bind `0x80290009` to a stable semantic
name, so this repository records the raw value only.
What the pair does prove is narrower: raw elfldr can reach the video path, but
it has not produced a usable, repeatable VideoOut/presentation lifecycle. A
third raw attempt would neither isolate the launch-context variable nor be
authorized.
## BigApp decision
Official shsrv v0.7 remains the source-proven comparison arm because it
replaces a SystemService-launched BigApp rather than SceSpZeroConf. It has not
been tested by Chimera and is not safe to invoke directly: it requires a
device-resident ELF, can terminate the active BigApp, has unbounded waits and
uses kernel/ptrace and root/jail mutations. Its deployed identity and live
result channel remain unproven.
A causal comparison requires the exact unchanged CZ artifact, a bounded
BigApp launcher with no persistent writes or remounts, explicit app-termination
scope, bounded cleanup and a separately approved one-shot result channel.
Those prerequisites do not currently coexist in an artifact. No shsrv
connection, hbldr command, staging, execution, retry or other device action is
authorized by this analysis.