This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
# Phase 1.0BA: offline AV target-profile and callsite audit
|
||||
|
||||
Status: `EXACT_CALLSITE_AND_PROFILE_DELTA_SOURCE_PATCH_ALLOWED_NO_BUILD`
|
||||
|
||||
Date: 2026-07-29
|
||||
|
||||
The remote-bound AZ commit leaves one exact integration point in `main`: after
|
||||
`rarch_main` returns and S15 is set, but before `_Exit`. On the normal PS5 loop
|
||||
return, `rarch_main` has already called `main_exit`; the PS5 frontend deinit
|
||||
then removes its SDL, frontend and platform initialization markers. Early
|
||||
initialization returns that bypass `main_exit` retain initialized bits and the
|
||||
AZ predicate therefore rejects D14.
|
||||
|
||||
The smallest profile is a derivative of `write-diag`: it retains the
|
||||
contentless `-v` startup correction, write firewall, D13 operation evidence,
|
||||
bounded runtime, inherited stdout, SDL diagnostic overlay and frame-zero
|
||||
source. The only new target define is `CHIMERA_PS5_AV_DIAG`; its stream magic
|
||||
takes precedence over the inherited J selection. Launcher identity remains
|
||||
outside the payload so both future launch arms use one byte-exact ELF.
|
||||
|
||||
The next source commit may add the call and a distinct `launch-canary` profile,
|
||||
plus host/static tests. This audit does not permit a cross-build, ELF, runner
|
||||
activation, connection, transfer, execution or PS5 action. A subsequent exact
|
||||
source audit must authorize any artifact build separately.
|
||||
Reference in New Issue
Block a user