Files
T
jakub 6a667d8deb Capture current mission, AI, map and administration development
Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
2026-10-13 22:52:53 +02:00

4.0 KiB

Transfer-fixes snapshot helpers — pending qualification

These scratch helpers were generated from the reviewed archived gameplay-fixes assembly, verification and preflight helpers. Only destination identifiers changed. No checks, native process or target writes were executed by this review.

Parent source snapshot: /home/jakub/devel/escapistsrereintroduced/.build/playtest-source-2026-10-02-transfer-fixes; suite: /tmp/erri-playtest-1844; normal evidence: docs/evidence/native-2026-10-02-transfer-fixes-normal. New runtime handoff: .build/playtest-2026-10-02-transfer-fixes. Existing snapshots, ZIPs, packages, logs and evidence remain immutable.

Use commands.txt individually after reviewing each prerequisite; it is not an unattended shell script. First create the new development ZIP from the frozen root. If the parent already created that exact path, skip creation and verify it; source_bundle refuses overwrite. Preflight waits for actual passing full-suite and same-source normal evidence. No claim that either result already exists is made here.

Use host-visible process inspection, not solely restricted sandbox /proc, before every native step. Any existing game remains untouched. Tools own prefix locks, fresh canonical direct-/tmp sessions, hidden Gamescope, muted audio and cleanup. Preserve all refusals/nonzero native outcomes. No native/background launch is created by this emitter.

Assembly retains native packaging's strict failure even if emitted runtime bytes match; verification recomputes raw schema-4 startup and retains the known installed-resource failure. It requires the exact previous 17-error set (historical owner-fixes reference is intentional). If new behavior/errors differ, review actual evidence rather than adjusting expectations. No human escape, physical interception/rearming, multiplayer, FPS or release qualification follows.

Do not execute old archived config/helpers directly: they remain bound to the older 420-file byte set, older ZIP and suite. The new helper paths are all transfer-fixes/1844. Counts are derived. template-provenance.json binds templates and emitted bytes. No README/status/pointer finalizer is included: those require actual final results and a fresh concurrent-edit baseline.

Final documentation proposal (parent only)

finalize_docs.py snapshots two live docs under docs-baseline/, refuses any concurrent document drift, and by default writes only scratch previews. Verified candidate mode updates current-status and playtest-build while retaining the entire prior text and marking the old handoff historical. It links the new handoff manifest, derives counts from actual reports, and leaves all package files, source and root README untouched.

After the independent final review exists, inspect its result and pass its exact approved SHA-256:

python3 /tmp/erri-package-prep-1844/finalize_docs.py --verified --review /ABS/INDEPENDENT-REVIEW.json --review-sha256 APPROVED_SHA256

Inspect proposed-docs-candidate and docs-proposal-candidate.json; append --apply only as the parent's explicit final write step. The script revalidates frozen source, registered suite membership/exit/input hashes, normal evidence, exact candidate/runtime/source identities and packed raw evidence before that write. Keep the final review/proposal/baseline hashes in the parent archive. Independent preservation review owns original/prior-package/index verification; this small finalizer only writes the two docs.

If packaging is blocked, use --mode source-only --verified --blocker-log /ABS/PRESERVED-REFUSAL.log plus the same review arguments. That mode requires successful fresh source suite and normal-route evidence but changes current-status only: no runtime pointer advancement, no package/README mutation, no claim of a new runtime result. The parent must confirm the blocker and no pending native process in the independent review. Pending previews alone may not be applied. Rebase and review the scratch baselines if another task edits either document.