Current Source Status Snapshot

Current Source Status Snapshot

This page is the fast guardrail for stale "patched", "propagated" and "release-ready" wording.

The original snapshot was created on 2026-06-02 after several false current-status pulses. Since then, multiple branches and wiki batches have moved. Treat this page as a branch-aware routing page, not as proof that a gameplay fix is currently shipped.

Rule For Agents

Before saying a fix is live, prove all of these:

1. Name the branch or commit checked.
2. Check source Chernarus under Missions/[55-2hc]warfarev2_073v48co.chernarus/.
3. Check maintained Vanilla Takistan under Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan/ when propagation matters.
4. Separate origin/master, docs/source branches, release branches and PR branches.
5. Keep Arma 2 OA runtime smoke separate from static source evidence.

If any item is missing, use patch-ready, branch-local, propagated-smoke-pending or source-unverified, not shipped.

2026-06-24 post-B751b guardrail: current stable is now origin/master@f39665d79. Rows that call origin/master@7bfcf09a9 current stable were written against the PR #88 B751 baseline; rows that call origin/master@c4c9a6479 current stable were written against the PR #87 B750 baseline; rows that call origin/master@718596d5e current stable were written against the PR #86 B749 baseline; rows that call origin/master@96148edb4 current stable were written against the PR #85 B748 baseline; older dated rows that call origin/master@f8a76de34 current stable were written before the B745/B748/B749/B75/B750/B751/B751b merge chain and should be treated as pre-merge baselines until a fresh owner pass rechecks them.

2026-07-01 release guardrail: fresh release-loop fetch has current origin/master@b4a6350ca0f90c9b0316570473c05a5e790aea96; open PR #122 was previously reviewed at origin/feat/qol-polish-pack@e47366be8bbfc53ffe667aeec42ec33cf3516c7d, later observed on 2026-07-01 at 722f5d05705b93503d18d079575a5f4815dca8f6, 6176c70aa34ea4040876e7a3e3e329d17cdcff33, 3694c068639db015de52e1f7d9f433859010522c, f5c41461508e117d13d0b6172cbd66698091a8eb, and current scanner/tooling head 4c66c3b6b1c20321163e732d6d06f5dacaeb4e5a. PR #122 is source-backed and includes Chernarus plus generated Takistan changes through mission-content head f5c41461508e117d13d0b6172cbd66698091a8eb; the newer 4c66c3b6 commit is tooling-only and hardens release RPT scanning with both-terrain windows and stronger AICOM telemetry requirements. The PR #122 parity audit reports 21/21 checked AICOM/HC files hash-identical between Chernarus and generated Takistan, but the redacted 07:53 livehost probe found active Chernarus resolving to a same-name cmdcon30aicom PBO while active Takistan still lacked a same-name active PBO/folder and had only a parked candidate. Those livehost RPT windows are baseline context only, not exact release proof. Runtime/RPT release proof is still missing, and the 07:58 proof-gap matrix remains NO-GO until exact-build both-terrain RPTs, server/client/latejoin/HC1/HC2 evidence, real HC/AICOM telemetry, scanner/package PASS and human smoke exist. Treat the PR #122 deadspawn/name-tag/JIP guard entries below as PR-branch source evidence until PR #122 is merged and exact-build SERVER_DEBUG RPT evidence is captured. Do not call PR #122 release-ready from this page alone.

2026-07-01 PR #125 identity guardrail: current checked release branch is codex/release-command-center-20260630@5face13a0a0bcb7fbf9bc56e0e64bc4af89ef8f2. _MISSIONS.7z, release-package-manifest.* and release handoff were regenerated from that head: SHA256 06A7E8C3EF1DFE9BC67306D43C5CF66AD79D26401CA87E815434B92B13A17608, 1,885 entries, 7,161,540 bytes, handoff status ready_for_runtime_collection. The latest mission-source delta adds WFBE_CO_FNC_GroupGetValue and sweeps AICOM plus command-menu non-bool group default reads, preserves the Build83/cmdcon35 reconciliation, hardens AICOM lifecycle/refund handling with pending tokens and off-map transport-object proof, clears the previously committed modded mission conflict-marker tokens, and adds the capture-stall guardrails for AllCamps waypoint chaining plus independent same-target stall age. Older 88368a9723, 84b0b79ab and intermediate package proofs are historical only. Keep release status runtime-pending and not-deployed until Chernarus and Takistan each have exact ten-file proof (server, HC1, HC2, start-client, late-JIP) with matching ExpectedGit, package archive SHA, packet manifest, run ledger and summary. The app heartbeat wasp-release-readiness-auto-resume is active every 30 minutes and must keep collision checks plus explicit no-runtime/no-SSH/no-deploy approval boundaries.

2026-06-30 Release Command-Center Static Intake

codex/release-command-center-20260630@5face13a0a0bcb7fbf9bc56e0e64bc4af89ef8f2 is the current draft PR #125 release-candidate integration branch, not current origin/master, not a public deployment, and not final release evidence. Safe labels for this branch are release-branch-local, static-verified, package-provenance-verified-local, git-tracked-payload-gate-local, handoff-packet-ready-local, runtime-rpt-packet-builder-local, runtime-rpt-packet-matrix-local, runtime-run-ledger-local, archive-sha-runtime-gate-local, runtime-source-map-identity-gate-local, runtime-ledger-identity-gate-local, handoff-contract-selftest-local, windowed-rpt-scorer-local, startup-banner-rpt-gate-local, hc-registry-rpt-gate-local, stronger-aicom-rpt-gate-local, per-terrain-runtime-evidence-gate-local, takistan-west-fallback-rpt-gate-local, per-terrain-token-summary-local, runtime-packet-manifest-gate-proof-local, runtime-summary-rpt-root-binding-local, summary-release-identity-proof-local, windows-powershell-final-check-local, a2-oa-command-dialect-clean-local, role-identity-rpt-gate-local, per-role-proof-rpt-gate-local, duplicate-rpt-content-gate-local, publishable-rpt-path-sanitized-local, self-contained-handoff-local, upgrade-request-authority-local, aicom-group-default-guard-local, aicom-hc-audit-telemetry-local, aicom-jip-feed-request-status-local, aicom-donation-authority-local, aicom-command-console-authority-local, hc-client-pv-guard-local, sqf-count-guard-local, runtime-pending, source-propagated Chernarus+Takistan, auto-resume-active, and not-deployed.

Static branch evidence recorded through 2026-07-01:

• Source Chernarus and maintained Vanilla Takistan carry the release-marker startup shape for 5face13a0a.
• The latest source hygiene pass removed stale B57-SOAK-PROPOSALS.md comment references from the Chernarus source and generated Takistan output after current master deleted that doc. The pass was validated as no-stale-reference cleanup, not a gameplay fix.
• Fresh 2026-07-01 remote reconciliation reviewed origin/feat/qol-polish-pack@722f5d057, PR #122 scanner head 6176c70aa34ea4040876e7a3e3e329d17cdcff33, release/static head 94c6ab30a220337a04280ddf9967b9da801bf4c6, PR #122 HC/client PV guard head 3694c068639db015de52e1f7d9f433859010522c, PR #122 count-guard head f5c41461508e117d13d0b6172cbd66698091a8eb, PR #122 scanner/tooling head 4c66c3b6b1c20321163e732d6d06f5dacaeb4e5a, and command-center AICOM fallback head 8de3c4a60300568e42f2b7343b4c72a06621e33e. The release branch did not raw-cherry-pick the older Tools/Monitor scanner shape because its scorer/log schema differs and the branch already carries owner-keyed HC CIV registration/deferred-reannounce logic; instead, the current release scorer was tightened to require actual CIV HC registry evidence, retained startup Mission Name banners in every scored file, both-terrain runtime windows, stronger no-human AICOM telemetry, and now per-terrain runtime evidence so one terrain cannot satisfy the other's semantic gates. The later HC/client PV handler guards and parenthesized SQF count guards were adapted/cherry-picked into the release branch because they are Chernarus/Takistan-propagated and reduce runtime RPT noise before evidence collection. The 8de3c4a60 AICOM fix was cherry-picked as local b4df22ede because it directly targets Takistan WEST founding starvation with a starved-infantry fallback. The 2026-07-01 round40 pass then removed an A3-only allMissionObjects sweep from the retired W10 AICOM wildcard salvage branch in both maintained terrains and reworded one help-menu line so the A2 command-dialect smoke gate is clean; the latest 5face13a0a package evidence incorporates the Build83/cmdcon35 reconciliation, guards the new AICOM execute debounce reads, resets the active AICOM executor latches, carries the cmdcon35 placement _affected private-list fix and supersedes the older round40 identity. The manually reconciled PR #122 wiki drift salvaged only still-current guardrails: 21/21 checked AICOM/HC file parity across Chernarus/generated Takistan, the redacted livehost finding that Chernarus resolves but Takistan does not, and the proof-gap matrix that stays NO-GO without exact-build both-terrain RPT/human-smoke evidence. Runtime evidence should target 5face13a0a.
• Tools/LoadoutManager generates ignored version.sqf markers as WASPRELEASE|v1|candidate=release-command-center-20260630|git=<short-head>|terrain=<terrain>.
• The generated local markers after 5face13a0a were git=5face13a0a|terrain=chernarus and git=5face13a0a|terrain=takistan.
• initJIPCompatible.sqf logs the marker plus a MISSINIT line so RPT evidence can be tied to the branch and terrain without publishing private raw log material.
• Client/Functions/Client_FNC_Special.sqf now guards upgrade-completion cache clears when WFBE_Client_Logic is nil or objNull, and the change was propagated to maintained Vanilla Takistan by Tools/LoadoutManager.
• Tools/PrTestHarness/Rpt/New-WaspRuntimeRptPacket.ps1 is the private source-map driven packet builder. It copies the exact ten source RPTs into chernarus/{server,HC1,HC2,start-client,late-JIP}.rpt and takistan/{server,HC1,HC2,start-client,late-JIP}.rpt, writes release-run-ledger.json, emits redaction-safe runtime-rpt-packet-manifest.json and can immediately call the validator. If the private source map contains release.candidate, release.git or release.archiveSha256, those values must match supplied -ExpectedCandidate, -ExpectedGit and -ExpectedArchiveSha256; otherwise the builder stops before writing a green packet.
• Tools/PrTestHarness/Rpt/Test-WaspRuntimeRptPacket.ps1 is the first runtime evidence gate and requires exactly those ten role files. It rejects missing/extra RPTs, duplicate copied paths, duplicate copied/source RPT content hashes, wrong terrain markers/world names, wrong role identity from MISSINIT, copied files older than launch, source RPT LastWriteTime values not after launch, and source/copy SHA256 mismatches; with -RequireSourceRptExists, it re-reads the source RPTs before passing. The run ledger must include source/copy paths, source LastWriteTime, source/copy SHA256, command-line, PID, terrain-start metadata, exact roleProof, client joinPhase for start/late JIP files, non-empty matching release.candidate/release.git when expected, and the approved archive SHA when -ExpectedArchiveSha256 is supplied. HC files must contain HC-local startup proof and player-client files must contain client-local startup proof. Public output uses RPT-root-relative copied labels plus path/content hashes and 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 current scorer requires at least two non-zero-owner CIV HCSIDE|v1|connect|... rows, fails the HC registry gate on HCSIDE|v1|connect-skip or non-CIV HC connect rows, fails if any scored file lacks the startup ## Mission Name banner, requires every scored file to resolve to one runtime terrain, and adds per-terrain-runtime-evidence so Chernarus and Takistan each contribute AICOM, JIP, HC, town-cleanup, WDDM/static/artillery and supply semantic proof. It also hardens no-human AICOM evidence so event proof, TEAM_FOUNDED, CMDRSTAT and at least one autonomous action/progress token (ASSAULT_DISPATCH, COMBATSTAT, FRONT, POSTURE or SNAP) must be present. It also adds the dedicated takistan-west-aicom-infantry-fallback gate, requiring Takistan per-terrain AICOMGATE|WEST|infFallback| evidence so generic founding/progress cannot mask fallback absence. The scorer and Tools/Monitor/Get-WindowedRpt.ps1 keep the startup banner immediately above the latest MISSINIT, so the release marker stays inside the scored current window.
• Client_HandlePVF.sqf, HandleSpecial.sqf, and LocalizeMessage.sqf now 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.
• Server/Functions/Server_ChangeSideSupply.sqf now centralizes the three side-supply temp PV handlers behind a payload/channel validator in both maintained terrains. It rejects malformed payloads, wrong side/channel combinations and non-scalar amounts before the existing clamp/update/publicVariable flow; treat this as direct-channel sanity hardening, not complete sender authentication.
• Server/PVFunctions/RequestUpgrade.sqf, Client/GUI/GUI_UpgradeMenu.sqf and Client/Functions/Client_FNC_Special.sqf now align the direct player upgrade path around server-owned acceptance and payment in both maintained terrains: the GUI sends requester object and team context, the server binds the request to the player-led commander team, rechecks current level/dependencies/costs/funds/supply, commits running state plus debit only after acceptance, and the client starts the upgrade-sync timer only from the accepted upgrade-started notification.
• Server/AI/Commander/AI_Commander_Execute.sqf and Common/Functions/Common_RunCommanderTeam.sqf now read AICOM group variables through the existing group helper so default commander mode, goto position, execution signature and capture-pass counters do not trip raw group getVariable default behavior. AI_Commander_PlayerArty.sqf also carries null/default guards around artillery lookup.
• 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/New-WaspReleaseRptSummary.ps1 can produce redaction-safe release-rpt-summary.json and release-rpt-summary.md packets from scorer output without raw RPT lines or absolute RPT paths; Markdown summaries now include per-terrain selected token counts and, when -RuntimePacketManifestPath is supplied, runtime packet proof. For release handoff, -RequireRuntimePacketManifest plus -ExpectedCandidate, -ExpectedGit and -ExpectedArchiveSha256 are required; the summary remains red unless runtime-rpt-packet-manifest.json has the matching release tuple, schema a2waspwarfare-runtime-rpt-packet-builder-v1, validation.requested=true, validation.overall=pass, all required packet-validator gates with status=pass, plus a matching rptRootHash, matching copied file copiedPathHash/copiedRptSha256 values and exactly the ten copied RPT files.
• Tools/PrTestHarness/Package/Test-WaspReleasePackage.ps1 validates _MISSIONS.7z archive roots, required boot files, generated release markers, per-required-file hashes, and the complete git-tracked Chernarus/Takistan mission payload against HEAD. The only allowed archive-only mission files are the two generated ignored version.sqf files.
• dotnet run -c RELEASE, Test-WaspReleasePackage.ps1, Test-WaspReleasePackage.SelfTest.ps1, Test-WaspRuntimeRptPacket.SelfTest.ps1, New-WaspRuntimeRptPacket.ps1 synthetic happy path, Test-WaspRuntimeRptPacket.ps1 synthetic pass/fail fixtures, duplicate RPT content, role-identity and per-role-proof failure fixtures, source-map release identity drift failure fixture, blank run-ledger candidate/git/archive identity fixtures, archive-SHA/source-freshness/hash run-ledger fixtures, duplicate-process redaction fixture, scorer marker-window/startup-banner/HC-registry/stronger-AICOM/per-terrain evidence fixtures, summary release-identity proof pass/fail fixtures, runtime packet manifest gate-proof plus summary root-binding pass/fail fixtures, Test-WaspReleaseHandoff.SelfTest.ps1, publishable summary/handoff path-sanitization checks and git diff --check passed in the release worktree after the package provenance guard. powershell.exe -File Tools\PrTestHarness\Run-WaspFinalCheck.ps1 now passes static smoke, Chernarus/Takistan A2/OA lint FAIL 0 / REVIEW 0 each for the cleared find "Aircraft" heuristic, and BugHunt HIGH is clean.
• The local package provenance manifest for 5face13a0a recorded _MISSIONS.7z as 1,885 entries, 7,161,540 bytes, SHA256 06A7E8C3EF1DFE9BC67306D43C5CF66AD79D26401CA87E815434B92B13A17608, with only the Chernarus and Takistan mission folders at archive root, 1,723 git-tracked mission files matched to HEAD, 1,725 archive mission files total, zero missing tracked files, zero unexpected mission files, zero hash mismatches, and only the two generated ignored version.sqf files allowed outside git.
• The local release handoff packet for 5face13a0a recorded status ready_for_runtime_collection with runtime approval, runtime evidence and deployment approval still pending, re-hashes the local archive before handoff readiness, includes the source-map packet builder and packet-matrix commands with -ExpectedArchiveSha256 06A7E8C3EF1DFE9BC67306D43C5CF66AD79D26401CA87E815434B92B13A17608 and -RequireSourceRptExists before scorer commands, writes runtime-rpt-source-map.template.json for the private source map plus runtime-run-ledger.template.json for the operator's generated release-run-ledger.json, routes the summary through -ExpectedCandidate, -ExpectedGit, -ExpectedArchiveSha256 and -RequireRuntimePacketManifest, and carries release-package-manifest.json plus sibling release-package-manifest.md in the same handoff folder. Test-WaspReleaseHandoff.SelfTest.ps1 covers the pending approval gates, copied package manifest artifacts, release-bound runtime commands and ten-record templates without touching live runtime data.
• Current source-hygiene caveat: the previous committed Modded_Missions conflict-marker tokens were cleared in this PR line, and the release package roots remain Chernarus plus Takistan only. The modded forks are still divergent/boot-incomplete maintenance targets and are not promoted by this package proof.

Claims that still require fresh stamped runtime evidence:

• Do not call AICOM, HC delegation, JIP, town cleanup, WDDM/static defense, artillery, or supply verified from this static branch alone.
• Do not call the cmdcon30/cmdcon31 WEST AI-commander founding failure fixed until a stamped dedicated-server RPT packet proves exact-build Takistan WEST fallback fire plus both sides found/tick/progress.
• Do not call this branch deployed until deployment approval, server placement, rollback path and stamped runtime evidence are recorded. The package proof above is local artifact provenance, not live-server proof.
• Public wiki summaries must stay sanitized: no raw RPT lines, UIDs, IPs, local paths, server profile paths, SSH/server usernames, or private ops commands.

2026-06-30 PR #122 Source Intake (deadspawn guard + WEST founding diagnosis)

This page was previously anchored on PR#89 / B751b (origin/master@f39665d7950ddf14cb0bbfacb7ee1e40121e93b4) and had no awareness of cmdcon28, PR#122 or cmdcon30. The PR #122 branch source under Missions/[55-2hc]warfarev2_073v48co.chernarus and generated Takistan has since moved, and the wording below supersedes any earlier statement that the PR #122 Init_Server.sqf editor-slot reaper should remain active or that the name-tag overlay uses getPosVisual. All file:line anchors here were confirmed from the PR #122 source on 2026-06-30; no live RPT artifact, package hash or generated version.sqf is imported in this docs pass, so keep this as source evidence plus audit findings, not independent release-artifact proof.

A. Player DEADSPAWN root cause + PR #122 source fix (2026-06-30) — SOURCE-BACKED, RPT-PENDING. PR#122 (the qol-polish-pack) added an editor-slot REAPER to the WFBE_EDITOR_GROUPS_TAGGED block in Server/Init/Init_Server.sqf that called deleteGroup on EMPTY west/east/resistance editor player-slot groups to reclaim group-cap headroom. But ~13/side are "overflow" slots whose placeholder unit self-deletes at load (mission.sqm init="... deleteVehicle this"), leaving an EMPTY group a human can still JIP into. The reaper's only discriminator was count(units _x)==0, so it deleted a JIP-selectable slot's group; a player joining that slot could land in the already-deleteGroup'd group with no wfbe_side, the enrollment resolver in Server/Functions/Server_OnPlayerConnected.sqf would re-arm, exhaust, and leave the player in DEADSPAWN (no team / HUD / markers). JIP / mid-match specific. Current PR #122 source removes the reaper entirely, reverting to audit-only tagging — the block logs editor-slot audit tagged ... no groups reaped and does not deleteGroup editor/player-slot groups. Three related PR #122 source fixes verified in source:

• Name-tag overlay (client, deploy-under-new-PBO required — finding C): getPosVisual is Arma-3-only and undefined in A2-OA 1.64; the PR#122 name-tag overlay used it despite an "A2-safe ... no A3 commands" claim that was false. PR #122 now uses visiblePosition in both maintained mission copies. Because this is a CLIENT-side change, it must ship under a new PBO filename for the runtime proof pass (A2-OA caches missions by filename; clients can otherwise serve stale mission code). Server-only changes take effect in place on restart.
• Disconnect retry-clear (server): WFBE_CONNECT_RETRY_<uid> was cleared only on enrollment success, so after a 3x-exhausted enrollment a re-join with the same UID could get zero fresh re-arms. PR #122 now clears it on disconnect in both maintained mission copies with missionNamespace setVariable [Format ["WFBE_CONNECT_RETRY_%1", _uid], nil].
• JIP race nil/objNull guard (client): PR #122 guards the WFBE_Client_Logic setVariable upgrade-completion writes and logs CLIENTUPGRADE|SKIP diagnostics if the client logic object is nil or objNull.

The previously reviewed PR #122 head e47366be8bbfc53ffe667aeec42ec33cf3516c7d also contains source changes for default-off AI-heli terrain guard, slope/flatness gating, corpse proximity cleanup guard, startup-banner RPT windowing, the release RPT scanner, and redacted release-evidence summary output. The later observed 722f5d05705b93503d18d079575a5f4815dca8f6 head adds an HC registry guard. Observed PR #122 head 6176c70aa34ea4040876e7a3e3e329d17cdcff33 also carries redacted scanner summaries, HC civilian-registry hardening, and the scanner -RequireHcRegistry gate. Observed PR #122 head 3694c068639db015de52e1f7d9f433859010522c adds HC/client PV handler guards for non-array PVF parameters and missing client-only chat/endgame functions. Observed PR #122 mission-content head f5c41461508e117d13d0b6172cbd66698091a8eb parenthesizes SQF count guard comparisons across 30 maintained mission files. Current observed PR #122 head 4c66c3b6b1c20321163e732d6d06f5dacaeb4e5a is tooling-only relative to mission content and hardens release scanning with both-terrain windows plus stronger AICOM telemetry requirements. These are source-backed on PR #122, not runtime-proven here.

B. WEST AI-commander founding failure (cmdcon31, 2026-07-01) — source-integrated fallback, runtime-pending. The WEST side intermittently founds 0 commander teams (server SNAP str=0/teams=0 although the allocator shows ALLOC teams=14) while EAST founds normally. This is pre-existing on cmdcon28/cmdcon30 and is NOT caused by PR#122. The active release branch now carries 8de3c4a60 / local b4df22ede: when upgrade gating strips every stored-type-0 infantry template, AI_Commander_Teams.sqf admits the cheapest infantry template and logs AICOMGATE|<side>|infFallback|.... This targets Takistan WEST BIS_US template starvation at founding upgrade [0,0,0,0], where a base leader class can require upgrade tier 1. The earlier synchronized WEST leader-slot re-grab / HC registry churn remains supporting telemetry. Do NOT claim this released or fixed until exact-build RPTs show Takistan WEST AICOMGATE|WEST|infFallback, TEAM_FOUNDED, CMDRSTAT, autonomous AICOM progress, no SQF errors, and HC registry support with groupSide=civilian, register=true, zero HCSIDE|v1|connect-skip.

C. JIP deploy rule (2026-06-30) — reinforce for the PR #122 runtime pass. Client-side script changes must ship under a new PBO filename during the release proof pass: A2-OA caches missions by filename and clients can serve stale mission code, which makes correct client fixes look inert. PR #122's client-side visiblePosition name-tag fix and Client_FNC_Special.sqf JIP guard therefore need a fresh mission filename in the Chernarus/Takistan runtime evidence packet. Server-only changes take effect in place on restart. Already partly documented in JIP enrollment and client data delivery.

2026-06-24 B74.5/B74.9/B75/B750/B751/B751b Master Merge Intake

Fresh fetch-before-commit changed this lane from branch-only routing to current-master routing, then repeated fetch-before-commit checks advanced master again. PR #85 merged origin/claude/b745@dd14018111f97c8c268447a02cb49e5cd5eab679 as origin/master@96148edb4b532b25a73b5eb3122287557ea90b72 on 2026-06-24T14:23:47Z; PR #86 then merged origin/feat/b749-enrollment-bodyfix@2327e5c6aabcde4a962ea9235119d9757cceba91 as origin/master@718596d5e96d97d9a4e91a031304da09f4dd4d13 on 2026-06-24T14:49:57Z; a direct merge commit origin/master@6a34799b41e821b3f540d2ac911f02fd1f7b7b76 then merged origin/VBIED_factory_kill_rewards@756d691823f4e46ea099582b8061f01848e0c3f2 on 2026-06-24T14:56:35Z. gh pr list --head VBIED_factory_kill_rewards --state all returned [], so treat the B75 delta as direct-merge source evidence, not PR-routed review evidence. git merge-base origin/master origin/claude/b745 still returns dd1401811, git merge-base origin/master origin/feat/b749-enrollment-bodyfix returns 2327e5c6a, and git merge-base origin/master origin/VBIED_factory_kill_rewards returns 756d6918, so all three heads are contained by current master. The prior stable baseline for this lane was origin/master@f8a76de349da6f8b871d079c828436c10afb221c: f8a76de34..34f652ae4 is the broad B745/LoadoutManager merge, 226 files / +7611 / -9082; 34f652ae4..96148edb4 is the B748 settings-menu PR #85 delta, 9 files / +265 / -7; 96148edb4..718596d5e is the B749 PR #86 delta, 14 files / +308 / -21; 718596d5e..6a34799b4 is the B75 VBIED factory/structure reward delta, 2 maintained-root files / +88 / -2; full f8a76de34..6a34799b4 through B75 is 236 files / +8263 / -9103. Checked B745/B748, B749 and B75 ranges were clean under git diff --check. origin/ClaudeMDcopypastefromAgentsMD@b97214c3f29772067fd67e8b2fe9da5773a2dd59 adds only repo-local CLAUDE.md guidance; treat that file as repository content to audit, not as higher-priority agent instructions.

Current master now carries the broad maintained Vanilla/Takistan and tooling merge that was previously documented as branch-only: one root CLAUDE.md, one source-Chernarus EASA init touch, 103 Missions_Vanilla files, two Tools/LoadoutManager files and no Modded_Missions files in the f8a76de34..34f652ae4 scope. Maintained Vanilla now carries many earlier B74.5/B74.7 paths that prior docs marked source-only: primitive roster push/receiver/vote rows (Server_OnPlayerConnected.sqf:128-131, initJIPCompatible.sqf:228-260, GUI_VoteMenu.sqf:28-34, GUI_Commander_VoteMenu.sqf:26-31), the B74.6 RHUD/common nil guards (Client_UpdateRHUD.sqf _baseStructures guard, Common_GetSideStructures.sqf:7-10, Common_GetFactories.sqf:7-10, Common_GetClosestEntity.sqf:13), B74.7 connect fallback diagnostics (Server_OnPlayerConnected.sqf:25,38-45,51,55-65), 30 FPS picker (Rsc/Dialogs.hpp:3528, FPSPicker_Open.sqf:48), AICOM hard cap/veteran cap (Init_CommonConstants.sqf:159, AI_Commander_Teams.sqf:113-114,184), attack-heli cap/reaper and MHQ abort-cooldown constants (Init_CommonConstants.sqf:187,191,319), AI base-sell wiring (Init_Server.sqf:37, AI_Commander_BaseSell.sqf:1-69), EASA category function compile (Client/Module/EASA/EASA_Init.sqf:2, EASA_LoadoutCat.sqf:1) and the Ka-137 PKT default comment (EASA_Init.sqf:670). It also adds the Vanilla naval-HVT/SCUD/GUER reward payload (Init_NavalHVT.sqf:1,28,170,190,205,320,417, Support_ScudStrike.sqf:1,16,33,42,49,56,63,136, Common/Init/Init_Common.sqf:308-313).

PR #85 originally added the B748 settings menu in source Chernarus, then PR #86 propagated it into maintained Vanilla and removed the Arma-3-only allMapMarkers usage from the settings controller. Current master source Chernarus and maintained Vanilla both open WASP\actions\Settings\Settings_Open.sqf from GUI_Menu.sqf:230, wire MenuAction = 24 at Vanilla Rsc/Dialogs.hpp:1258,1266, define WFBE_SettingsMenu at Vanilla Rsc/Dialogs.hpp:3436, and run the settings controller at Settings_Open.sqf:19,75-79; source Chernarus Settings_Open.sqf:75-79 now matches the A2 OA-safe ambulance-circle teardown note. The earlier maintained-Vanilla WFBE_SettingsMenu / Settings_Open / MenuAction = 24 absence is superseded by PR #86.

PR #86 also supersedes the earlier B74.7.2 maintained-Vanilla enrollment gap. In both maintained roots, RequestJoin.sqf:95-96 stores WFBE_JIP_BODY_<uid> and logs the slot-group side stamp; Server_OnPlayerConnected.sqf:32 reads that client-provided body before scanning playableUnits; Server_OnPlayerConnected.sqf:25,38-45,51,55-65 keeps the widened/fallback lookup budget; and Server_OnPlayerConnected.sqf:78-80 retains the nil-wfbe_side retry guard. PR #86 body/title reports the change as a definitive JIP enrollment fix and an allMapMarkers A2 fix, but this docs pass did not verify live RPT logs, generated version.sqf or package contents. Do not call this merge release-ready until target-package smoke proves JIP enrollment, settings/profile behavior and LoadoutManager output in the intended source Chernarus and maintained Vanilla packages.

B75 adds maintained-root GUER VBIED factory/structure reward evidence only. Both source Chernarus and maintained Vanilla now expand Server_HandleSpecial.sqf:541 locals for structure accounting, snapshot enemy side-logic wfbe_structures in blast radius at :571-582, compute per-structure bounty/score at :624-643, record factory kills for the detonator UID at :647, log credited structures at :649 and fold the payout through the existing death-proof personal bounty path. This pass did not smoke VBIED blast attribution, factory stat increments, side-logic structure-list edge cases or duplicate/null-killer payout interactions, so keep B75 as current-master source evidence, not release-ready reward proof.

Fetch-before-commit advanced master one more time after B75: PR #87 merged origin/feat/b750-factory-aicom@605ad7326707b9422303e60ca6c286d6e0700864 as origin/master@c4c9a64790c63fe264bd1a25f84f0b3ca7b49362 on 2026-06-24T15:10:56Z. The B750 delta 6a34799b4..c4c9a6479 is 8 maintained-root files / +72 / -54 and clean under git diff --check; full f8a76de34..c4c9a6479 was 238 files / +8316 / -9138. Both source Chernarus and maintained Vanilla add the buy-list nil _c guard at Client_UIFillListBuyUnits.sqf:88-92, restore player infantry squad cap growth in GUI_Menu_BuyUnits.sqf:133 with _realSize = (10 + (_realSize * 2)) min _mbu, and replace AICOM price-weighted template draw with BI CfgVehicles cost effectiveness draw via Init_CommonConstants.sqf:215,219,225 and AI_Commander_Teams.sqf:428. Smoke buy-list rows with missing unit data, barracks-level infantry caps, commander bonus paths and AICOM squad variety/effectiveness before release-ready wording.

Current master advanced again via PR #88: origin/feat/b751-tk-aicom13-clientfixes@5aea1ce4016a862de413a198ba8bab0a1ce868c2 merged as origin/master@7bfcf09a98e8a9e6e26d8ac1b017807c1d54dee0 on 2026-06-24T15:55:53Z. The scoped B751 delta c4c9a6479..origin/master is 14 maintained-root files / +16 / -10; full f8a76de34..origin/master is now 242 files / +8330 / -9146. B751 raises the AICOM team hard cap from 8 to 13 in both roots (Init_CommonConstants.sqf:159; consumer clamps stay at AI_Commander_Teams.sqf:113-114,184) and adds GUER/JIP client-error guards in both roots: ammo/repair truck missionNamespace defaults (updateavailableactions.fsm:58-59), buy-list faction-filter nil _c guard (Client_UIFillListBuyUnits.sqf:40), seated unflip getPos _vehicle (GUI_Menu.sqf:130), tactical HQ deploy nil guard (GUI_Menu_Tactical.sqf:172), HQ-killed handler _isDeployed seed (Init_Client.sqf:812) and repair-depot cashrepaired nil guard (Action_RepairMHQDepot.sqf:7). The B751 diff does not touch Client_UI_Gear_FillCargoList.sqf or server_town.sqf; those PR-body follow-ups stay separate. git diff --check c4c9a6479..origin/master reports trailing whitespace at Client/FSM/updateavailableactions.fsm:59 in both maintained roots, so do not describe the source delta as diff-check-clean until that is repaired.

Current master then advanced via PR #89: origin/feat/tk-chernarus-slots@05ded76601ea4f0d2ed9de50a53048dd590da210 merged as origin/master@f39665d7950ddf14cb0bbfacb7ee1e40121e93b4 on 2026-06-24T16:46:54Z. The scoped B751b delta 7bfcf09a9..origin/master is 19 maintained Vanilla Takistan files / +511 / -1224 and is clean under git diff --check; all changed paths are Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan/mission.sqm plus 18 added Textures/*.paa files, with no source Chernarus, Modded, Tools or Extension payload. B751b replaces the previous Takistan 66-PLAY CDG legacy roster with 34 current slots: source check of the merged blob counts 14 WEST, 14 EAST, 4 GUER and 2 CIV headless-client entries. Takistan mission.sqm now has class Groups items=91 at :43-45, WEST slots beginning at id 7000 (:2835-2853), EAST slots through ids 7014-7028 (:3415-3468), two CIV Functionary1 HC entries (:3429-3489), GUER slots 7030-7033 (:3493-3577), and owner-module synchronizations remapped to the new slot ids at :599, :618 and :2831. The PR body reports a live B751b Takistan boot smoke with WEST/EAST team registration and no zero-divisor, but this docs pass did not import an RPT artifact, package hash or generated version.sqf proof; keep this as current-master source evidence plus PR-reported smoke until independent release artifacts are recorded.

2026-06-24 PR #84 Player-Stats Name Stack Intake

Open non-draft PR #84 / origin/feat/player-stats-names@177539ed5585acdb086c9cfdacf1e671459a686a is branch-only stack evidence, not current stable, deployed or release wording. GitHub reports feat/player-stats-names -> feat/player-stats, base e01e47e12a767c3406f8b89b7df5ea9d95260b87, clean merge state and update time 2026-06-24T12:51:37Z. Local checks confirm merge-base e01e47e12a767c3406f8b89b7df5ea9d95260b87, one commit, 6 files / +57 / -7 over the player-stats base branch, clean git diff --check origin/feat/player-stats..origin/feat/player-stats-names, and no Missions_Vanilla, Modded_Missions, Tools or Extension payload.

The stack touches only the in-repo stats producer/DiscordBot path and tests. Source Chernarus StatsFlush.sqf:24-25,44-50 caches name _x by UID and appends ~<name> after the numeric CSV/side fields. DiscordBot adds nullable name handling at StatsBatchParser.cs:5,31-40,49, applies latest-seen non-null names at StatsAccumulator.cs:21-23, and serializes [DataMember(Name = "name")] at PlayerStat.cs:22-24. Parser tests cover name suffix, absent suffix and internal ~ at StatsBatchParserTests.cs:43-69; the integration contract now asserts the name JSON key at StatsPipelineIntegrationTests.cs:77-83. Checked origin/master and base origin/feat/player-stats have no WFBE_STAT_NAME_, name DataMember, seg.Name or first-tilde parser hits in the checked stats paths.

Before promotion, run the DiscordBot tests in an environment with a .NET SDK, then run Arma RPT smoke for ordinary names plus ~ and | separator names, and record privacy/retention policy for publishing player names next to UID-keyed stats. The external website receiver described in the PR body is not present in this repo, so do not claim the website side from this source snapshot alone.

2026-06-24 PR #83 Wiki-Wins Batch Intake

Open draft PR #83 / origin/claude/wiki-wins-batch@a61823265c82eb7e35c7c74d851647c2235cf169 is branch-only evidence, not current stable or release wording. The original intake was base-relative to pre-B745/B751b origin/master@f8a76de349da6f8b871d079c828436c10afb221c: merge-base f8a76de34, 8 commits, 46 Chernarus-source files / +124 / -86, clean git diff --check f8a76de34..origin/claude/wiki-wins-batch, and no Missions_Vanilla, Modded_Missions or Tools payload in the scoped diff. After PR #85-#89 advanced current master to origin/master@f39665d7950ddf14cb0bbfacb7ee1e40121e93b4, live gh api plus the GitHub connector report PR #83 mergeable=false / dirty; local origin/master...origin/claude/wiki-wins-batch counts are 80 8. Treat the source anchors below as pre-B751b branch-intake proof, not current-merge readiness.

Keep the scope Chernarus-only until an owner decides propagation. Representative source anchors are broad: commander vote/reassignment UI (GUI_Commander_VoteMenu.sqf:36, GUI_VoteMenu.sqf:80-82, RequestNewCommander.sqf:13), HC bootstrap/fallback/watchers (Init_HC.sqf:15-16, Server_DelegateAITownHeadless.sqf:49-53, Client_DelegateTownAI.sqf:52-53, Client_DelegateAIStaticDefence.sqf:57-58), economy/service/supply (Common_ChangeSideSupply.sqf:12, Server_OnHQKilled.sqf:63-65,104-110, Client_UIFillListBuyUnits.sqf:9,39-40, GUI_Menu_Service.sqf:496,519, Server_MHQRepair.sqf:48, playerObjectsList.sqf:17, Server_OnPlayerDisconnected.sqf:128-131), IRS/countermeasure and lobby wiring (Common_RearmVehicle.sqf:38-40, Common_RearmVehicleOA.sqf:29-31, Server_BuyUnit.sqf:159-162, Rsc/Parameters.hpp:282,373), construction auto-wall scope (Init_Common.sqf:214-216, Construction_MediumSite.sqf:163, Construction_SmallSite.sqf:99,123, RequestAutoWallConstructinChange.sqf:9-11) and cleanup/dead-code anchors (mines_cleaner.sqf:17, updateScoreInternal.sqf:13, RequestOnUnitKilled.sqf:238-239, Init_Client.sqf:59,396, Init_Common.sqf:126,150).

Before promotion, rebase or split PR #83 against post-B751b master, then run Chernarus dedicated smoke across commander voting, HC-present/absent town delegation, HQ scoring/teamkill, buy/service/repair/supply paths, IRS level-2 rearm/AI buy, auto-wall side scoping, camp/mines/AntiStack cleanup, and decide whether LoadoutManager or hand propagation should carry any fixes into maintained Vanilla/Takistan. Do not describe PR #83 as shipped, propagated, release-ready, current-merge-ready or Miksuu-proven without a later target-branch record.

2026-06-24 PR #80 Vote/Paratrooper Guard Intake

Open draft PR #80 / origin/claude/trello-vote-para-guards@92101abe9f7b83bd7f658d03e4160d5f030aa3c7 is branch-only evidence, not current stable or release wording. The original intake was base-relative to pre-B745/B751b origin/master@f8a76de349da6f8b871d079c828436c10afb221c: merge-base f8a76de34, one commit, 10 maintained-root files / +148 / -14, clean git diff --check f8a76de34..origin/claude/trello-vote-para-guards, and no Modded_Missions or Tools payload. After PR #85-#89 advanced current master to origin/master@f39665d7950ddf14cb0bbfacb7ee1e40121e93b4, live gh api plus the GitHub connector still report mergeable=true / clean, but the PR base SHA remains f8a76de34; local origin/master...origin/claude/trello-vote-para-guards counts are 80 1. Treat this as clean-but-stale-base branch evidence until a post-B751b rebase/recheck and smoke pass.

The branch is intentionally narrower than PR #83 and already includes maintained Vanilla Takistan. In both maintained roots it adds random tied-player commander selection at Server_VoteForCommander.sqf:17,43-51,59, a Tactical paratrooper client gate at GUI_Menu_Tactical.sqf:373-393, a server backstop at Support_Paratroopers.sqf:40,53-54, default-on WFBE_C_PARA_RESPECT_CAP at Chernarus Init_CommonConstants.sqf:664 / Vanilla :466, and STR_WF_INFO_Para_MaxGroup at stringtable.xml:1118. Checked pre-B751b stable, B74.2, B69, adjacent B74, Miksuu and perf refs have no WFBE_C_PARA_RESPECT_CAP, STR_WF_INFO_Para_MaxGroup or _tiedTeams hits in the maintained roots. Before promotion, recheck the clean merge after post-B751b rebase/merge planning, then smoke player-candidate ties, AI/no-commander ties, normal clear winners, paratrooper client cap block with no fee/cooldown/request, server backstop rejection, WFBE_C_PARA_RESPECT_CAP = 0 legacy behavior, AI commander wildcard paradrops, and maintained Vanilla parity.

High-Risk Status Checks

Lane	What to verify before changing wording	Owning page
Commander reassignment DR-15	RequestNewCommander.sqf payload shape versus Server_AssignNewCommander.sqf unpacking, plus duplicate notification behavior.	Commander reassignment call shape
Factory queue cleanup DR-33	Client_BuildUnit.sqf queue token identity, empty-vehicle early exit and local queue decrement.	Factory queue counter token cleanup
Paratrooper marker revival	Sender, handler file and HandleParatrooperMarkerCreation client PVF registration in each maintained mission.	Paratrooper marker revival
Duplicate client Skill_Init	Number and order of Skill_Init.sqf calls before WFBE_SK_FNC_Apply.	Client skill init idempotency
Hosted server FPS loop	Dedicated/non-dedicated guard shape in both server FPS publisher scripts.	Hosted server FPS loop sleep
Supply mission command-center scan	Whether the 80-meter command-center scan is class-filtered to Base_WarfareBUAVterminal; keep the nearby-player/object scan separate.	Supply mission scan narrowing
Commander-built ARTY ownership	Whether commander-built artillery is discoverable by Tactical fire missions, and which branch shape provides it: docs/source uses a commander-team gunner handoff, while release uses replicated artillery owner markers plus a commander-team vehicle sweep.	Construction and CoIn systems
WASP marker wait cleanup	Whether the display-54 wait is throttled like the display-12 sibling.	WASP marker wait cleanup
Town AI vehicle despawn DR-45	Whether wfbe_active_vehicles cleanup checks every player occupant before deleteVehicle, and whether Chernarus fixes have been propagated to maintained Vanilla.	Town AI vehicle despawn safety
Source/Vanilla propagation	Whether Chernarus, maintained Vanilla and skipped/generated files all carry the same intended behavior.	Source fix propagation queue
AI commander branch revival	Whether feat/ai-commander is still branch-only, whether default-on behavior is accepted, and whether maintained Vanilla/smoke evidence exists.	AI commander autonomy audit
DroneStrike branch	Whether the latest drone tuning branch is the target, whether paid-support authority moved server-side, and whether generated scope/smoke exists.	PR8 and drone upstream lesson match
ReconUAV branch	Whether ReconUAV replaces the old UAV module, whether it is rebased onto latest DroneStrike tuning, and whether recall/reveal/JIP cleanup is smoked.	PR8 and drone upstream lesson match

2026-06-22 Current-Head Caveat

Fresh checks for the Town AI despawn lane found current stable origin/master@0139a346, current Miksuu master@b8389e748243, origin/perf/quick-wins@0076040f, B69 origin/claude/b69@0a1ccb4d and live origin/feat/aicom-fleet-improvements@cc5090bed4ad; current origin exposed no release/* or feat/*town* heads. This page still preserves older routing matrices, so owner pages with later source proofs supersede rows below. For DR-45, use Town AI vehicle despawn safety: current stable still lacks the crew guard, while B69 has only a Chernarus-side candidate.

Supply scan supersession from the 2026-06-22 refresh: docs/source 15563691 carries the truck-only typed scan at supplyMissionStarted.sqf:25,28,44, current stable origin/master@0139a346 carries the heli-aware typed scan at :7,55,61,83, and direct current Miksuu b8389e748243 plus perf 0076040f still broad-enumerate/post-filter at :25,28,44. Current origin exposes no live release/* head, so a96fdda2 / 7ff18c49 supply scan evidence is historical release-line proof only.

WASP marker wait supersession from the 2026-06-23 current-B74.1/B74.2 refresh: docs/source HEAD@c9df2a8b7264 is unchanged from 46840f048bd4 for checked WASP paths and still has the unslept display-54 loop in both maintained roots (Init_Client.sqf:267; global_marking_monitor.sqf:57,62,64,68-69,80). Current stable/B74.1 origin/master@f8a76de34 / origin/claude/b74.1-aicom@f8a76de34, B74.2 origin/claude/b74.2-aicom@21b62b04, B69 origin/claude/b69@8d465fce, B74 origin/claude/b74-aicom-spend@b23f557f, origin/feat/client-fps@709258e7 and live map branches already carry sleep 0.1 at global_marking_monitor.sqf:64 before findDisplay 54 at :65 in both maintained roots; stable/B74.1/B69/B74/live-map launch at Init_Client.sqf:397, B74.2 launches Chernarus at :403 and Vanilla at :397, client-fps launches Chernarus at :308 and Vanilla at :287. B74.2's checked Init_Client.sqf delta is unrelated vehicle-tint/join-ACK/intro-music drift. Current Miksuu b8389e748243, perf 0076040f8a5e and historical a96fdda2 remain old-shape, and current origin exposes no live release/*, WASP or marker rescue head.

Source-fix queue supersession from the 2026-06-23 current-stable/B74.1 refresh: current stable origin/master@f8a76de34 equals origin/claude/b74.1-aicom@f8a76de34. For the existing propagated-fix queue paths, scoped diff 0139a3468609..f8a76de34 touches only maintained-root Client/Init/Init_Client.sqf, and the B74.1 tip commit itself changes only Chernarus Common/Init/Init_CommonConstants.sqf. Current stable/B74.1 Chernarus and maintained Vanilla now use the B69/B74 Skill_Init/apply line shape (Init_Client.sqf:805,828), while the checked paratrooper registration (Init_PublicVariables.sqf:38), one guarded FPS publisher (serverFpsGUI.sqf:4, publish at :9-10, no monitor path), heli-aware typed supply scan (supplyMissionStarted.sqf:7,55,61,83), in-loop supply player-list reset (playerObjectsList.sqf:18) and marker-based commander ARTY (Construction_StationaryDefense.sqf:166-168; Common_GetTeamArtillery.sqf:41-78, side read at :56) stay on the same queue shape. Use Source fix propagation queue before reusing older 0139a346 propagated-fix anchors.

2026-06-14 Current Ref Snapshot

Checked after git fetch --all --prune: docs checkout docs/developer-wiki-index 76674ae4, stable origin/master cf2a6d6a, release origin/release/2026-06-feature-bundle a96fdda2, Miksuu b8389e74 and origin/perf/quick-wins 0076040f. Targeted rows have since been refreshed on 2026-06-22 with current branch heads where noted. Use this as a routing snapshot only; owner pages and source refs still win for detailed rationale, patch shape and smoke status.

Lane	Current source evidence	Route / caveat
Patrols v2	Current stable Chernarus and maintained Vanilla retire the old server_town_ai random-town patrol launch (server_town_ai.sqf:44,220), add Server/FSM/server_side_patrols.sqf, run patrols through Common_RunSidePatrol.sqf, maintain WFBE_ACTIVE_PATROLS through Server_HandleSpecial.sqf:215-242, and use && at server_patrols.sqf:26 in both roots.	Treat older 89ae9dad DR-57 / AI1 "patrols dead on master" wording as historical branch evidence. Canonical route: Towns/camps/capture and Source fix propagation queue.
Paratrooper marker PV	2026-06-23 refresh: docs/source HEAD@7e88d609 registers HandleParatrooperMarkerCreation at Init_PublicVariables.sqf:39 in both maintained roots; current stable/B74.1 origin/master@f8a76de34, B69 origin/claude/b69@8d465fce and B74 origin/claude/b74-aicom-spend@b23f557f register it at :38; historical a96fdda2 and 7ff18c49 register it at :34 but current origin exposes no live release/* head; current Miksuu b8389e748243 keeps sender/handler files without the checked maintained-root registration; perf carries it in Chernarus only at :40.	Branch-present in docs/source, current stable/B74.1/B69/B74 and historical release-line checked roots, but marker smoke remains required. Use Paratrooper marker revival.
Client Skill_Init	2026-06-23 refresh: docs/source HEAD@b2738971 runs one init/apply at Init_Client.sqf:547,571; current stable/B74.1 origin/master@f8a76de34 and current B69/B74 run :805,828; live origin/feat/client-fps@709258e7 keeps one-call/apply with Chernarus :613,636 and Vanilla :583,606. Previous current-stable 0139a346 line anchors :624,647 are superseded for current-stable wording. Historical release-line a96fdda2 / 7ff18c49 carries :563,586 / :564,587, but current origin exposes no live release/* head. Current Miksuu/perf and historical feat-ai still run duplicate init calls (:560,:584 or :561,:585) before apply.	Do not reuse older matrix wording that says stable still duplicates or that release evidence is a live release-head claim. Use Client skill init idempotency.
Hosted server FPS	Docs/source guards both publishers (serverFpsGUI.sqf:1, monitorServerFPS.sqf:1). Current stable/B74.1 f8a76de34, current B74.2 21b62b04, B69/B74, client-fps, ASR FPS and historical release guard only serverFpsGUI.sqf:4, publish SERVER_FPS_GUI at :9-10 and no longer carry the old monitor path. Miksuu/perf still start both FPS scripts with unguarded while {true} at line 1 and sleep only inside isDedicated.	Stable/B74-shaped refs, historical release and docs/source now have different source shapes. Smoke the target branch's publisher shape through Hosted server FPS loop sleep.
Supply command-center scan	Docs/source uses the truck-only typed terminal scan at supplyMissionStarted.sqf:25,28,44; current stable/B74.1 origin/master@f8a76de34 uses the heli-aware typed terminal scan at :7,55,61,83; historical release a96fdda2 uses :7,53,59,81; Miksuu/perf still use broad nearestObjects [..., [], 80] at :28 plus a post-filter.	Keep truck, heli and nearby-player scan claims on the supply owner pages: Supply mission architecture and Supply mission scan narrowing.
Supply player-list index	Docs/source moves _i = 0 before the WFBE_SE_PLAYERLIST loop at playerObjectsList.sqf:17; stable, release, Miksuu and perf still reset _i inside the loop at :18.	Do not treat stable/release as carrying this fix until source changes. Route through Source fix propagation queue and player join/disconnect lifecycle.
Commander-built ARTY ownership	Docs/source HEAD@f5bcaf91 uses the commander-team gunner handoff at Construction_StationaryDefense.sqf:91-94. Current stable/B74.1 origin/master@f8a76de34, B69 origin/claude/b69@8d465fce and B74 origin/claude/b74-aicom-spend@b23f557f use marker-based discovery: WFBE_CommanderArtillery* at Construction_StationaryDefense.sqf:166-168 plus same-side marked-vehicle scanning in Common_GetTeamArtillery.sqf:46-78 (WFBE_CommanderArtillerySide read at :56). Historical release a96fdda2 / 7ff18c49 carries the older marker line shape at Construction_StationaryDefense.sqf:133-135. Miksuu/perf keep the old DefenseTeam path only.	Current stable/B74.1/B69/B74 are no longer "missing" commander ARTY evidence, but their implementation is not the docs/source handoff. Historical release evidence is not a live release-head claim. Use Construction and CoIn systems.

Historical 2026-06-05 Refetch Delta

The section below is kept as branch history. It is superseded for current-head routing by the 2026-06-14 snapshot above.

git fetch --all --prune was rerun on 2026-06-05. This did not re-prove every matrix row below; it only refreshes the branch-head routing state so agents do not treat old commit IDs as current.

Ref	Earlier matrix head	Fetched head on 2026-06-05	Delta / action
origin/docs/developer-wiki-index	source-check basis 154b7f38	f3e157f2 on 2026-06-06	Docs/source has advanced through documentation and source-backed wiki maintenance. Use it for documentation truth and branch-local source evidence only; it is not stable-master or release proof.
origin/master	2cdf5fb8	89ae9dad on 2026-06-06	Historical transient stable evidence. The 2026-06-22 refresh supersedes this row with current stable origin/master@0139a346, where Server_CleanupExpiredTownDefenseAssets.sqf is absent and DR-45 still needs the tracked-vehicle crew guard at server_town_ai.sqf:309.
origin/release/2026-06-feature-bundle	a9219d88	7ff18c49	The release branch advanced through d482c742, fb3084c2, 7195b331 and 7ff18c49. d482c742 removes the Chernarus-only PR8 static smoke helper from the release payload; fb3084c2 is a broad live-playtest hardening commit touching Chernarus, maintained Vanilla and tooling; 7195b331 replaces the old FPS-only menu slot with a GPS toggle; 7ff18c49 hardens delegated AI locality checks and delays/clamps cleaner/restorer startup in both maintained roots. PR8-specific deltas are routed in PR cleanup lab. The propagated-fix lane status below is superseded by the 7195b331 spot-check plus the 7ff18c49 delta note.
miksuu/master	8bcc42b1	89ae9dad	Historical upstream evidence for the Marty town-defense overhaul. The 2026-06-22 Miksuu refetch returned b8389e748243, where the persistence helper is absent; keep the 89ae9dad helper notes as archaeology for branches that still contain that commit.
Other named feature refs in the 2026-06-04 matrix	As listed below	unchanged in this refetch	Keep existing branch-review gates until a later source audit proves a new delta.

Historical 2026-06-03 Branch Matrix

The rows below preserve the older branch evidence that caused several status corrections. Do not read them as current stable/release truth when they conflict with the 2026-06-14 snapshot above.

Checked refs: docs/source HEAD 4163faba, stable origin/master 2cdf5fb8, and origin/release/2026-06-feature-bundle a9219d88.

Follow-up release-head spot-check on 2026-06-05: origin/release/2026-06-feature-bundle 3282ff3f still had the same propagated-fix lane status as the a9219d88 matrix for hosted FPS, supply command-center scan, client Skill_Init idempotency and paratrooper marker registration, and still lacked commander-built ARTY ownership in both maintained roots.

Follow-up release-head spot-check on 2026-06-05 after git fetch --all --prune: release head 7195b331 changed several earlier release conclusions. Release Chernarus and release Vanilla both register HandleParatrooperMarkerCreation (Common/Init/Init_PublicVariables.sqf:34), run one Skill_Init.sqf call (Client/Init/Init_Client.sqf:564) followed by WFBE_SK_FNC_Apply at :587, guard serverFpsGUI.sqf with if (!isDedicated) exitWith {}; at :4 while deleting the redundant Server/Module/serverFPS/monitorServerFPS.sqf, and use the narrowed supply command-center scan at supplyMissionStarted.sqf:52,58. Release Chernarus and release Vanilla also both have the camp-capture str _newSide flag texture at server_town_camp.sqf:135 and the resistance patrol && loop at server_patrols.sqf:26. The same spot-check found release 7195b331 still lacks the docs/source commander-team gunner handoff: both maintained roots keep the base-area DefenseTeam manning path in Construction_StationaryDefense.sqf:88-97. A 2026-06-06 follow-up corrected the release interpretation: current release 7ff18c49 carries a different commander ARTY discovery path in both maintained roots by setting WFBE_CommanderArtillery* variables on non-repair-truck artillery defenses (Construction_StationaryDefense.sqf:133-135) and letting the commander team scan same-side marked vehicles inside the HQ/base-area radius (Common_GetTeamArtillery.sqf:46-78). The 7195b331 delta removes the FPS-only RUBFPSHUD mode and makes menu action 19 toggle GPS instead. Arma smoke remains pending for all runtime claims.

Follow-up branch-scope correction on 2026-06-06: origin/docs/developer-wiki-index head f3e157f2 still carries the branch-local typed supply command-center scan in both maintained roots at supplyMissionStarted.sqf:28. Current local checkout / origin/master / Miksuu 89ae9dad and origin/perf/quick-wins 0076040f did not carry that scan and still used broad nearestObjects [..., [], 80] plus the Base_WarfareBUAVterminal post-filter. 2026-06-22 supersession: current stable origin/master@0139a346 now carries the heli-aware typed scan in both maintained roots, while direct current Miksuu b8389e748243 and perf remain old-shape. Keep docs/source, stable master and release branch status separate.

Follow-up release-head spot-check on 2026-06-06: current release head 7ff18c49 does not change the propagated-fix conclusions above. Its new delta is PR8 runtime-hardening evidence: both maintained release roots now relax delegated AI fallback-group creation around null/empty groups and non-local leaders (Client_DelegateAIStaticDefence.sqf:27, Client_DelegateTownAI.sqf:27, Common_CreateUnit.sqf:34-36, Common_CreateUnitForStaticDefence.sqf:68-69), and cleaner/restorer scripts now clamp timers and sleep before the first broad scan (crater_cleaner.sqf:5,7,50, droppeditems_cleaner.sqf:5,7,46, ruins_cleaner.sqf:5,7,30, buildings_restorer.sqf:4,6,18,31). Treat this as release-branch evidence only until HC/delegation and long-session cleanup smoke exists.

Lane	docs/source HEAD	origin/master	release a9219d88	Interpretation
Hosted server FPS loop	Repo docs branch HEAD@4a1bc13edde6 is source-unchanged from d0161083 / a27086cd: Chernarus and Vanilla Server/GUI/serverFpsGUI.sqf:1 plus Server/Module/serverFPS/monitorServerFPS.sqf:1 exit on !isDedicated.	Current stable/B74.1 origin/master@f8a76de34 Chernarus and Vanilla guard Server/GUI/serverFpsGUI.sqf:4, start the single publisher at Chernarus Init_Server.sqf:950 / Vanilla :937, document monitorServerFPS.sqf removal at :996-998 / :983-985, and have no maintained-root monitor file. Current B74.2 matches the FPS contract with source-Chernarus init/removal line drift to :983 and :1029-1031; B69/B74 and live FPS-named branches also keep the single-publisher shape.	Historical a9219d88/3282ff3f checks were Chernarus-only or stale. Historical a96fdda2 matches the guarded single-publisher shape in both maintained roots with older init anchors :579 and :595-597; no current release/* head was exposed on 2026-06-24.	docs/source and current stable/B74-shaped refs carry hosted/listen guards by different publisher shapes; current Miksuu/perf old-loop status and release evidence live on Hosted server FPS loop sleep. Arma smoke remains pending.
Supply command-center scan	Docs/source Chernarus and Vanilla use the typed command-center scan at Server/Module/supplyMission/supplyMissionStarted.sqf:28: ["Base_WarfareBUAVterminal"]; the 8m nearby-player/object scan remains broad by design.	Historical 2026-06-06 local HEAD / origin/master evidence broad-enumerated at supplyMissionStarted.sqf:28, but this is superseded for current stable by origin/master@0139a346, which carries the heli-aware typed scan at :7,55,61,83.	Historical a9219d88/3282ff3f checks were Chernarus-only or stale; local release-line commit 7ff18c49 carries the PR-compatible heli-aware typed scan from 7195b331 in both maintained roots at supplyMissionStarted.sqf:52,58.	docs/source and current stable carry typed scans; current Miksuu/perf still need the typed scan if that performance cleanup is desired; truck/heli command-center smoke remains pending.
Client Skill_Init idempotency	Docs/source HEAD@b2738971 Chernarus and Vanilla have one Skill_Init.sqf call at Client/Init/Init_Client.sqf:547, followed by WFBE_SK_FNC_Apply at :571.	Historical origin/master evidence in this older matrix duplicated the init, but current stable origin/master@0139a346 supersedes that state with one call at :624 and apply at :647 in both maintained roots; current B69/B74 match stable for the checked shape at :805 / :828.	Historical a9219d88 release matrix duplicated the init. Later local release-line commits a96fdda2 and 7ff18c49 carry the one-call shape at :563 / :586 and :564 / :587 in both maintained roots, but current origin exposes no live release/* head.	docs/source, current stable/B69/B74, live client-fps and historical release-line commits carry the single-init shape; current Miksuu/perf and historical feat-ai still duplicate; Arma smoke remains pending.
Paratrooper marker registration	Chernarus and Vanilla Common/Init/Init_PublicVariables.sqf:39 include HandleParatrooperMarkerCreation; refreshed docs/source HEAD@7e88d609 keeps that shape.	Historical origin/master evidence in this older matrix omitted the handler. Current stable origin/master@0139a346 supersedes that state and registers it at Common/Init/Init_PublicVariables.sqf:38 in both maintained roots; current B69/B74 match stable for the checked paths.	Historical a9219d88 release matrix omitted the handler. Later local release-line commits a96fdda2 and 7ff18c49 carry the HandleParatrooperMarkerCreation registration at Common/Init/Init_PublicVariables.sqf:34 in both maintained roots, but current origin exposes no live release/* head.	docs/source, current stable/B69/B74 and historical release-line commits carry the static registration; current Miksuu omits it and perf is Chernarus-only; Arma marker smoke remains pending.
Commander-built ARTY ownership	Chernarus and Vanilla Construction_StationaryDefense.sqf:91-93 switch manned artillery-class defense gunners to the current commander team when one exists.	Historical origin/master / local master 89ae9dad Chernarus and Vanilla kept the base-area DefenseTeam path only and had no WFBE_CommanderArtillery* marker variables or marked-vehicle scan in Common_GetTeamArtillery.sqf; this is superseded for current stable by origin/master@0139a346, which carries marker discovery at Construction_StationaryDefense.sqf:166-168 plus Common_GetTeamArtillery.sqf:46-78.	Historical release 7ff18c49 Chernarus and Vanilla keep DefenseTeam manning, but non-repair-truck artillery defenses set WFBE_CommanderArtillery, WFBE_CommanderArtillerySide and WFBE_CommanderArtilleryIndex at Construction_StationaryDefense.sqf:133-135; Common_GetTeamArtillery.sqf:46-78 lets the commander team add same-side marked vehicles inside HQ/base-area radius.	docs/source, current stable and historical release all have source evidence for commander Tactical discovery, but by different designs. All runtime claims remain Arma-smoke-pending.

2026-06-04 Feature Branch Matrix

Checked after git fetch --all --prune. Most rows below were written against the then-stable origin/master 2cdf5fb8; the 2026-06-06 refetch later advanced origin/master to 89ae9dad. Rows with a different merge base name that base explicitly. These rows are branch evidence, not shipped-status proof. Use Pending owner decisions, agent-release-readiness.json and the branch-only feature smoke pack before merge/release claims.

The docs mirror branch row records the source-check basis for this matrix, not a durable branch-head promise. Documentation-only commits can move origin/docs/developer-wiki-index after the matrix is written; re-fetch before using that branch head as evidence.

Branch / upstream ref	Checked head	Delta from origin/master	Current interpretation
docs mirror branch origin/docs/developer-wiki-index	source-check basis 154b7f38; current checked head f3e157f2	Documentation and source-backed wiki maintenance since the source-fix batch; follow-up 2026-06-06 grep confirmed the branch-local source line shapes remain propagated for paratrooper markers, single Skill_Init, hosted FPS exits and the typed supply command-center scan.	Current wiki/docs mirror truth for documentation and branch-local source evidence. Do not treat this branch name alone as stable-master or gameplay release proof.
miksuu/master / origin/master	89ae9dad	Historical 2026-06-06 branch evidence: that checked line included diagnostics/creation guards, capture-state reset and captured-defender persistence/cleanup in both maintained roots. Latest delta 69e1958a..89ae9dad added Common_MarkTownDefenseAsset, Server_CleanupExpiredTownDefenseAssets, Server_SendTownDebugChat, TownDefenseDiagnosticsEnabled and capture-persistence handling.	Superseded for current-head routing by the 2026-06-22 caveat above. Current stable origin/master@0139a346 and Miksuu b8389e748243 do not contain the helper; use the Town AI owner page for DR-45 status.
origin/feat/ai-commander	c20ce153	Source-Chernarus-only: 9 files, +416/-5. Adds default-on AI commander, supervisor/workers/order executor and upgrade cost fixes; guards but does not restore old UpdateSupplyTruck. Later cleanup commits b4b0333f..c20ce153 rewrite lazy condition blocks across the five AI commander scripts.	Branch-review needed. Stable origin/master remains partial/latent; no maintained Vanilla propagation or runtime smoke proof.
origin/feat/drone-saturation-strike	8ca4be90	Mission runtime changes are source-Chernarus-only: 15 mission files, +379/-4, with 0 maintained Vanilla mission files changed. Total branch diff is 17 files, +1133/-4 because it also carries docs/superpowers plan/spec files. Latest drone tuning branch: 4-Ka package, HP 20, cruise altitude 300, scatter 6 and cooldown 300.	Branch-review needed. Treat as paid support; server-side authority, generated scope and runtime smoke remain gates.
origin/feat/recon-uav	563418ea	Mission runtime changes are source-Chernarus-only: 22 mission files, +593/-657, with 0 maintained Vanilla mission files changed. Total branch diff is 25 files, +1461/-657 because it also carries drone/recon docs/superpowers files. Adds ReconUAV/ReconUAVRecall, removes old Client/Module/UAV/uav*.sqf and old Server/Support/Support_UAV.sqf; includes drone history only through 93b47594.	Branch-review needed. Resolve latest DroneStrike tuning baseline and old-UAV replacement behavior before merge claims.
origin/feat/wf-menu-ops-console	0767c0b5	UI-only branch from origin/master: 23 files, +1033/-154. Touches Chernarus and maintained Vanilla dialog/style/HUD files plus docs/superpowers/*; adds Client/Images/brand_chevron.jpg.	Branch-review needed. Treat as visual/theme evidence, not release proof. Gate on Arma 2 OA UI smoke, font/texture load, Chernarus/Vanilla parity, and branch git diff --check cleanup because the branch currently has trailing whitespace in docs/superpowers/plans/2026-06-03-wf-menu-ops-console.md.
origin/feat/buymenu-easa-qol	a66d4691	Three Chernarus client UI files, +42/-6, merge base 2cdf5fb8. Adds unaffordable buy-unit price tint (Client_UIFillListBuyUnits.sqf:1,61-62,104), live factory-tab queue counts (GUI_Menu_BuyUnits.sqf:201-210), selected-unit cost formula/display work (GUI_Menu_BuyUnits.sqf:280,335,388,444,487) and EASA current-loadout color/preselect (GUI_Menu_EASA.sqf:29-40). git diff --check is clean.	Branch-review needed but narrow; see BuyMenu EASA QoL branch audit. UI-only QoL; smoke affordability color versus full/crew cost, queue labels/no flicker, final price field and EASA current loadout before merge. No maintained Vanilla propagation in this branch.
origin/feat/player-stats	e01e47e1	23 files, +1919/-1. Adds feature-flagged SQF stat instrumentation (WFBE_C_STATS_ENABLED = false at Init_CommonConstants.sqf:443), kill stat hooks (RequestOnUnitKilled.sqf:51-65), server stat scripts and a DiscordBot RPT-tail-to-stats.json pipeline. git diff --check is clean, and branch tests passed locally: dotnet test DiscordBot.Tests\DiscordBot.Tests.csproj -> 13/13.	Branch-review needed; see Player stats branch audit. Off by default and absent from Vanilla, but deployment needs RPT path, log volume, UID/privacy, tail-state, corrupt-JSON recovery and Arma runtime smoke decisions before enabling.
origin/feat/player-stats-names / PR #84	177539ed	Open non-draft stack on origin/feat/player-stats@e01e47e1, clean GitHub merge state, scoped stack diff 6 files / +57 / -7 and clean git diff --check. Adds source Chernarus StatsFlush.sqf:24-25,44-50 name suffix emission plus DiscordBot nullable name parsing/accumulation/JSON contract at StatsBatchParser.cs:5,31-40,49, StatsAccumulator.cs:21-23, PlayerStat.cs:22-24; tests are updated at StatsBatchParserTests.cs:43-69 and StatsPipelineIntegrationTests.cs:77-83. No Missions_Vanilla, Modded_Missions, Tools or Extension payload.	Branch-review stack; see PR #84 current snapshot and Player stats branch audit. Local test rerun blocked by missing .NET SDK; run SDK-backed tests plus Arma RPT name/separator smoke before deployed/current-stable wording.
origin/perf/quick-wins	0076040f	18 Chernarus files, +27/-27, merge base 2cdf5fb8. Clean git diff --check. Fix families include side-supply clamp (Common_ChangeSideSupply.sqf:25, Server_ChangeSideSupply.sqf:12,36), crewless factory queue decrement (Client_BuildUnit.sqf:366-368), paratrooper marker PV registration (Init_PublicVariables.sqf:40), mine/garbage/resource-loop cleanup (mines_cleaner.sqf:17, server_collector_garbage.sqf:17, updateresources.sqf:74), patrol loop exits (server_patrols.sqf:26, server_town_patrol.sqf:18), camp-bunker nil-code EH removal (Server_HandleSpecial.sqf:235-236) and kill-assist bounty type (RequestOnUnitKilled.sqf:92).	High-value bugfix branch, but Chernarus-only; see Perf quick wins branch audit. Missions_Vanilla has no branch diff and still shows old clamp/EH/kill-assist/resource-loop shapes. Review against existing docs/source fixes, propagate maintained Vanilla deliberately and smoke economy debit, factory queues, paratrooper markers, mine/cleaner/resource loops, camp repair/destruction and WASP actions before release wording.
origin/feat/commander-positions	560db61c	Merge base f5985b77, not current stable 2cdf5fb8. 83 files, +524/-2025 across Chernarus and maintained Vanilla. The actual WDDM commander-position runtime is source-Chernarus only: anchors (Structures_CO_US.sqf:168-174, Structures_CO_RU.sqf:166-172), template map (Init_Defenses.sqf:93-183), compile (Init_Server.sqf:26) and builder (Server_ConstructPosition.sqf:1-66). No Server_ConstructPosition or WFBE_POSITION_TEMPLATE_MAP hits exist under maintained Vanilla on the branch. git diff --check reports trailing whitespace in source files.	Broad branch-review needed; see Commander positions branch audit. Do not treat as a clean construction feature branch or as Vanilla-propagated until unrelated deltas, whitespace, DR-6 authority, build-position smoke, CoIn/HQ cleanup and propagation scope are reviewed.
origin/feature/zargabad-map	e9294ede	Massive map branch from origin/master: 832 files, +77733/-95. Adds maintained Vanilla Zargabad mission folder, terrain integration (ZARGABAD.cs:1-13, SqfFileGenerator.cs:127-130), Chernarus source hooks for low-pop Zargabad (initJIPCompatible.sqf:121-124, Init_Boundaries.sqf:4-10, Server/Init/Init_Zargabad.sqf:1-125) and guide/test-gate packets. The refreshed head also tunes low-pop defaults: AI max 6, player AI max 8, Soldier skill cap 3, team supply cap 30000, UAV 650, town mortar/patrol 420/300, chopper/plane countermeasures 12/18, starting funds 8000, starting supply 3600, ordnance ranges 1500, Air AA/flares/thermal on and ICBM off. Static validation passed locally at e9294ede with Tools\Validate-ZargabadMission.ps1; git diff --check reports 3542 whitespace findings in generated mission files.	Map-release branch, not a small feature. See Zargabad branch audit. Static layout evidence is strong, and the head now has explicit low-pop balance/evidence gates, but playable/maintained wording still requires hosted/dedicated/JIP/HC runtime evidence, screenshot/RPT packet validation, class-load checks, edge-guard/black-market smoke and whitespace cleanup/acceptance.
historical origin/feat/supply-helicopter	262dc431	2026-06-22 remote check found no live origin/feat/supply-helicopter, origin/*supply* or origin/release/* head. This row is retained as historical PR #1 evidence: old merge base f5985b77, Air-factory gating, lobby toggle and load/unload timers (Rsc/Parameters.hpp:4-10, Init_CommonConstants.sqf:168-180), Air upgrade 3 load/action gates (Skill_Apply.sqf:62-72, supplyMissionStart.sqf:21-29) and Air upgrade 4 cash-run branch (supplyMissionCompleted.sqf:24-35). Completion clears amount/source but not SupplyByHeli (supplyMissionCompleted.sqf:40-41). No SupplyByHeli/heli constant hits were found in maintained Vanilla on that historical head.	Historical branch-review evidence only. Current stable origin/master@0139a346 now carries the maintained-root supply-heli/cash-run shape; use Supply mission architecture for current branch scope before reviving old PR #1 gates.

Current Interpretation

• PR #122 release guardrail (2026-07-01): PR #122 was previously reviewed at e47366be8bbfc53ffe667aeec42ec33cf3516c7d, later observed at 722f5d05705b93503d18d079575a5f4815dca8f6, then at 6176c70aa34ea4040876e7a3e3e329d17cdcff33, then at 3694c068639db015de52e1f7d9f433859010522c, then at mission-content head f5c41461508e117d13d0b6172cbd66698091a8eb, and currently at scanner/tooling head 4c66c3b6b1c20321163e732d6d06f5dacaeb4e5a. It contains source changes for audit-only editor-slot tagging, same-UID disconnect retry clear, the WFBE_Client_Logic upgrade-completion guard, the visiblePosition name-tag overlay path, default-off AI-heli terrain guard, slope/flatness gating, corpse proximity cleanup guard, startup-banner RPT windowing, the release RPT scanner, redacted scanner summaries, HC civilian-registry hardening, the scanner -RequireHcRegistry gate, HC/client PV handler guards, parenthesized SQF count guards, startup-banner scanner gate, both-terrain scanner gate and stronger AICOM telemetry gate. The latest mission-content head remains f5c41461508e117d13d0b6172cbd66698091a8eb; 4c66c3b6 is tooling-only. These are source-backed on PR #122, not runtime-proven here. Client-side changes must be released under a new PBO filename for the July 2 package so clients do not reuse stale cached mission content. WEST AI-commander 0-team founding is superseded by the separate command-center fallback intake below for active release testing. See the 2026-06-30 PR #122 Source Intake above.
• release-command-center (local static/package intake, 2026-06-30/2026-07-01): codex/release-command-center-20260630@5face13a0a has generated RPT release markers for Chernarus and Takistan, a propagated client upgrade-completion logic guard, propagated HC/client PV handler guards, propagated SQF count guard parenthesization, the 8de3c4a60/b4df22ede AICOM starved-infantry fallback in both maintained terrains, AICOM HC reconnect/drop audit telemetry, AICOM late-JIP feed request status rebroadcast, AI commander donation authority guard, AICOM command-console authority guard, AICOM HCTopUp draft exclusion, AICOM wildcard A2 command-dialect cleanup, AICOM Strategy snapshot town-cache reuse and GUER armor classifier string-match cleanup in both maintained terrains, a source-map runtime RPT packet builder with release identity drift rejection, strict runtime RPT packet matrix tooling, runtime run-ledger validation with exact role proof, candidate/git/archive identity, archive-SHA and source-bound RPT binding, duplicate content, role-identity and per-role-proof RPT gates, windowed redaction-safe RPT scorer/summary tooling, a summary release-identity proof gate, a runtime packet manifest gate-proof check, a startup-banner scorer gate, a local HC registry CIV-connect scorer gate, a stronger no-human AICOM scorer gate, a per-terrain runtime evidence gate, Windows PowerShell-safe final-check tooling, Chernarus/Takistan A2/OA lint FAIL 0 / REVIEW 0 each, BugHunt HIGH clean, local _MISSIONS.7z full git-tracked payload provenance proof (SHA256 06A7E8C3EF1DFE9BC67306D43C5CF66AD79D26401CA87E815434B92B13A17608) and a self-contained redaction-safe release handoff packet with synthetic contract coverage. The local final check passed static smoke clean, Chernarus/Takistan A2/OA lint with FAIL 0 / REVIEW 0 each, and BugHunt HIGH clean; runtime evidence plus live deployment proof are still missing. Use 2026-06-30 Release Command-Center Static Intake for wording.
• origin/master@f8a76de34 is the current fetched stable baseline for the 2026-06-23 Source Fix Propagation Queue scope refresh and equals origin/claude/b74.1-aicom@f8a76de34. Older rows naming 0139a346, cf2a6d6a or 89ae9dad are historical or lane-specific unless a later owner page explicitly says the same source shape was rechecked on the current head.
• Branch-local or release-branch code changes are not shipped on origin/master until source evidence proves the branch or equivalent source shape landed there.
• "Propagated" means the named source Chernarus and maintained Vanilla Takistan roots both carry the change on the named ref; it does not mean Arma 2 OA runtime smoke passed.
• Branch-feature smoke packs are planned gates, not proof of in-game behavior.
• Old worklog/event/knowledge lines and older matrices are append-only history. The 2026-06-14 snapshot, owner pages and explicit supersession records beat old timestamps.

Continue Reading

Previous: Arma 2 OA compatibility audit | Next: Feature status register

Main map: Home | Fast path: LLM agent entry pack | Agent file: agent-context.json