chore: track audit-runs summary artifacts (md/csv/diff/txt/json/etc)

Snapshot of every non-log artifact under audit-runs/ from audits 003
through 058: findings.md per audit, comparison CSVs, probe diffs,
schema docs, register-dump txts, lr-trace JSONL streams, the saved
canary patch diffs, etc. ~284 files / ~52 MB total.

Excluded (per .gitignore): probe stdout/stderr/log streams (the raw
firehose), guest-memory dumps under audit-026/027/029 (4.5 GB of
.bin files; *.bin pattern added to .gitignore this commit).

Also adds the orphan audit-058-sub825070F0-activation directory that
a subagent accidentally created at project-root instead of
under xenia-rs/audit-runs/; relocated to its proper home.

Purpose: cross-machine continuity. With these summaries committed,
a fresh clone gives the next session the full per-audit context
(findings + tables + cascade predictions) without dependence on
local-only working tree.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
MechaCat02
2026-05-10 21:36:41 +02:00
parent 609f586ed8
commit 8e709b0a24
284 changed files with 677656 additions and 0 deletions

View File

@@ -0,0 +1,25 @@
# AUDIT-040 canary patch — extends audit-030 TrapLogLR helper to log
# r3..r10 + r28..r31 plus a 32-byte memdump from r4 and r5 (the two source
# pointers passed into sub_8244FC90). Total +56 LOC across 4 files. Applied
# 2026-05-09 then reverted at session close; `git status` clean afterwards.
#
# Files changed:
# src/xenia/cpu/backend/x64/x64_emitter.cc (+43) TrapLogLR + dump_bytes
# src/xenia/cpu/cpu_flags.cc (+5) log_lr_on_pc cvar
# src/xenia/cpu/cpu_flags.h (+2) DECLARE_uint64
# src/xenia/cpu/ppc/ppc_hir_builder.cc (+6) Trap(100) emit on PC match
#
# Build: cd build/ && ninja -f build-Debug.ninja xenia_canary
#
# The TrapLogLR helper now reads:
# ctx->r[3..10], ctx->r[28..31], ctx->lr
# thread_state->memory()->TranslateVirtual<const uint8_t*>(r4) -> 32 bytes
# thread_state->memory()->TranslateVirtual<const uint8_t*>(r5) -> 32 bytes
#
# Output format:
# TRACE-PC-LR pc=8244FC90 lr=82450440 r3=BC65CD00 r4=701CF580 ... r31=701CF3C0
# TRACE-PC-LR r4* addr=701CF580 bytes=F800008C 00000000 ... (8 dwords hex)
# TRACE-PC-LR r5* addr=BC79C960 bytes=820B57D0 FFFFFFFF ... (8 dwords hex)
#
# Reusable for other ctor-input investigations: change --log_lr_on_pc value;
# reinterpret r4*/r5* dumps based on the target function's argument convention.