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 was previously recorded at origin/feat/qol-polish-pack@e47366be8bbfc53ffe667aeec42ec33cf3516c7d, was observed on 2026-07-01 at 722f5d05705b93503d18d079575a5f4815dca8f6 after an HC registry guard commit, then at 6176c70aa34ea4040876e7a3e3e329d17cdcff33 with HC civilian-registry hardening plus scanner -RequireHcRegistry, then at 3694c068639db015de52e1f7d9f433859010522c with HC/client PV handler guards, then at f5c41461508e117d13d0b6172cbd66698091a8eb with parenthesized SQF count guards, and is currently observed at bfdd9b2a9c4a19023f42d36053abeb5bd1e27a6f with a hard startup-banner requirement in the older Tools/Monitor release scanner. 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.

2026-06-30 Release Command-Center Static Gate

Local branch codex/release-command-center-20260630@e590126f53 is recorded as release-branch-local, static-verified, package-provenance-verified-local, handoff-packet-ready-local, runtime-rpt-packet-matrix-local, runtime-run-ledger-local, archive-sha-runtime-gate-local, windowed-rpt-scorer-local, startup-banner-rpt-gate-local, hc-registry-rpt-gate-local, hc-client-pv-guard-local, sqf-count-guard-local, runtime-pending, source-propagated Chernarus+Takistan, and not-deployed.

What is safe to say now:

• The branch has a generated release RPT marker shape: WASPRELEASE|v1|candidate=release-command-center-20260630|git=<short-head>|terrain=<terrain>.
• The remote HC registry guard on origin/feat/qol-polish-pack@722f5d057, the PR #122 scanner gate at 6176c70aa34ea4040876e7a3e3e329d17cdcff33, the release/static head 94c6ab30a220337a04280ddf9967b9da801bf4c6, PR #122 HC/client PV guard head 3694c068639db015de52e1f7d9f433859010522c, PR #122 count-guard head f5c41461508e117d13d0b6172cbd66698091a8eb, and PR #122 startup-banner scanner head bfdd9b2a9c4a19023f42d36053abeb5bd1e27a6f were reviewed on 2026-07-01. The release branch did not raw-cherry-pick the older Tools/Monitor scanner because the current release scorer/log schema differs; it adapted the HC evidence idea and startup-banner hard gate into Tools/PrTestHarness, adapted the later PV handler guards, and cherry-picked the count guard parenthesization directly into both maintained terrains.
• Tools/LoadoutManager generated the ignored Chernarus and Takistan version.sqf files with terrain-specific marker values after the e590126f53 commit.
• initJIPCompatible.sqf logs the marker plus a MISSINIT terrain/session line.
• Client/Functions/Client_FNC_Special.sqf guards upgrade-completion cache clears when WFBE_Client_Logic is nil or objNull, and LoadoutManager propagated that source change to maintained Vanilla Takistan.
• Client_HandlePVF.sqf, HandleSpecial.sqf, and LocalizeMessage.sqf guard HC/client-only PV dispatch surfaces from non-array parameter count, missing WFBE_CL_FNC_EndGame, and missing GroupChatMessage errors in both maintained terrains.
• Thirty maintained mission files now parenthesize SQF count guard comparisons in both Chernarus and Takistan, reducing ambiguity and potential runtime RPT noise in client, common, server patrol/delegation, and NEURO paths.
• Tools/PrTestHarness/Rpt/Test-WaspRuntimeRptPacket.ps1 is the first runtime evidence gate. It requires exactly ten role files, chernarus/{server,HC1,HC2,start-client,late-JIP}.rpt and takistan/{server,HC1,HC2,start-client,late-JIP}.rpt, checks terrain markers/world names, rejects extra/missing RPTs and duplicate copied paths, and validates a release-run-ledger.json run ledger with per-terrain launch times, command lines, PIDs, original source RPT paths, copied packet paths and, when -ExpectedArchiveSha256 is supplied, the approved _MISSIONS.7z SHA256. Public checker output hashes original source RPT paths and duplicate command lines instead of emitting them.
• Tools/PrTestHarness/Rpt/Test-WaspReleaseRptEvidence.ps1 scores current-mission RPT windows and gates generic stop-condition errors without emitting raw RPT lines; the e590126f53 scorer also requires at least two non-zero-owner CIV HCSIDE|v1|connect|... rows, fails on connect-skip or non-CIV HC connect rows, and fails if any scored file lacks the startup ## Mission Name banner. The scorer and Tools/Monitor/Get-WindowedRpt.ps1 keep the startup banner immediately above the latest MISSINIT, so the WASPRELEASE marker remains inside the current scored window.
• Tools/PrTestHarness/Rpt/New-WaspReleaseRptSummary.ps1 writes redaction-safe JSON and Markdown summaries from release RPT scorer output.
• Tools/PrTestHarness/Package/Test-WaspReleasePackage.ps1 writes redaction-safe JSON and Markdown package provenance for _MISSIONS.7z: archive roots, required files, generated markers and per-required-file hashes.
• Tools/PrTestHarness/Release/New-WaspReleaseHandoff.ps1 writes redaction-safe JSON and Markdown release handoff packets with exact runtime markers, the runtime run-ledger template, scorer commands, deploy approval checks and rollback checks; it also re-hashes the local archive and fails handoff readiness if the archive path, length, SHA256 or release git no longer matches the package manifest and current HEAD.
• Local static/package gates passed: LoadoutManager RELEASE packaging, package provenance validation, release handoff packet generation, runtime packet matrix synthetic pass/fail fixtures, archive-SHA run-ledger pass/fail fixtures, duplicate-process redaction fixture, scorer windowing smoke, startup-banner scorer pass/fail fixtures, HC registry scorer synthetic fixtures, runtime run-ledger validator synthetic pass/fail fixtures, git diff --check, static smoke, and BugHunt HIGH. The local package manifest for e590126f53 recorded _MISSIONS.7z as 1,882 entries, 7,164,415 bytes, SHA256 370829262B778B33D484EF8E12FC122FCA102BAFC7F29093FBE844D1A1CC1C4E, with only Chernarus and Takistan mission folders at archive root.

What is not proven yet:

• Runtime AICOM, HC delegation, JIP, town cleanup, WDDM/static defense, artillery, and supply behavior.
• Server deployment, rollback proof and dedicated-server runtime proof.
• cmdcon30 WEST AI-commander founding resolution.

Release gate: collect a fresh, sanitized Chernarus and Takistan dedicated-server evidence packet, validate the exact role matrix first, then run the token scorer before stronger wording:

& .\Tools\PrTestHarness\Rpt\Test-WaspRuntimeRptPacket.ps1 `
  -RptRoot "<release-candidate-rpts>" `
  -ExpectedGit e590126f53 `
  -ExpectedArchiveSha256 370829262B778B33D484EF8E12FC122FCA102BAFC7F29093FBE844D1A1CC1C4E `
  -RunLedgerPath "<release-candidate-rpts>\release-run-ledger.json"

$expectedReleaseMarkers = @(
  "WASPRELEASE|v1|candidate=release-command-center-20260630|git=e590126f53|terrain=chernarus",
  "WASPRELEASE|v1|candidate=release-command-center-20260630|git=e590126f53|terrain=takistan"
)

& .\Tools\PrTestHarness\Rpt\Test-WaspReleaseRptEvidence.ps1 `
  -RptDirectory "<release-candidate-rpts>" -Recurse `
  -ExpectedMarker $expectedReleaseMarkers

For a wiki/release-safe packet, run the summary wrapper after collecting the same fresh RPTs:

& .\Tools\PrTestHarness\Rpt\New-WaspReleaseRptSummary.ps1 `
  -RptDirectory "<release-candidate-rpts>" -Recurse `
  -ExpectedMarker $expectedReleaseMarkers `
  -OutDirectory "<release-candidate-rpts>\summary" -Force

Continue Reading

Previous: Source fix propagation queue | Next: Testing workflow

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