Agent Release Readiness Ledger

Agent Release Readiness Ledger

This is the human/MkDocs wrapper for agent-release-readiness.json. The JSON file is the canonical machine-readable ledger for tracked mission fixes, generated-target propagation and Arma 2 OA smoke gates.

Use this before release notes, generated mission propagation or any claim that a source fix is complete outside the Chernarus source mission.

What It Tracks

Section	Meaning
toolingGate	LoadoutManager root-discovery rule, skip-zip option and current local checkout status.
sourceOnlyFixes	Compatibility key for tracked fixes; entries now record source, Vanilla and smoke status independently.
patchReadyNotSourcePatched	Playbooks that are ready for implementation but are not current source patches.
releaseGate	Minimum validation needed before a lane can be called release-complete.

Current Canonical Flow

Current fetched master for the July 2 PR #122 release pass is origin/master@bd48a6dbe673ae47a88053dafdf948a29cb8dfe0; PR #122 head is 7b94b3c9124896797017a5a13e28fc482dee3ebb. Treat PR #122 as source-backed and runtime/RPT-pending until the release evidence packet is attached.

1. Read Source fix propagation queue for the human explanation.
2. Load agent-release-readiness.json for machine status.
3. Run LoadoutManager from a checkout where branch-specific root discovery succeeds. Current PR #122 and fetched origin/master@bd48a6dbe673ae47a88053dafdf948a29cb8dfe0 accept either an a2waspwarfare ancestor or the documented repo markers; direct current Miksuu b8389e74 and origin/perf/quick-wins@0076040f still need the ancestor.
4. Inspect generated diffs.
5. Record Arma 2 OA smoke in the owning page and machine files.

Continue Reading

Previous: Source fix propagation queue | Next: Testing workflow

Main map: Home | Machine ledger: agent-release-readiness.json | Progress: Progress dashboard