Wiki Pruning And Relevance Ledger

This ledger records decisions to condense, archive, merge or keep wiki material. Its purpose is to stop the documentation set from growing forever after a finding has already been absorbed into canonical pages.

Rule of thumb: preserve evidence, reduce repeated narration.

Recent Pruning Decisions

Date	Page / area	Action	Why	Preserved / route
2026-06-24	WASP base repair, Service menu affordability guards, PR cleanup, Feature status, Testing workflow	PR #63 repair anti-spam route	The branch splits across an existing WASP base-repair action loop and the existing service-menu repair path. A standalone PR #63 page would duplicate both owner pages and make local anti-spam flags look like service economy or server-authority closure.	Preserved PR #63 as open draft branch-only evidence: `origin/claude/trello-repair-antispam@9ba13a66` is stale-base after the B75/GUER master move (`f8a76de34` base/merge-base, current master `origin/master@4a163bb65`, local counts `95 1`, GitHub mergeability currently `null` / `unknown`), with 8 maintained-root files / +82 / -12 and clean `git diff --check`. Branch anchors add `WASP_BaseRepair_Running`, `wfbe_veh_repairing`, repair price `0` while already repairing and `STR_WF_INFO_Repair_Veh_InProgress`; current master lacks those symbols. No gameplay source changed.
2026-06-24	Structure damage reduction and friendly-fire, PR cleanup, Feature status, Testing workflow	PR #66 debug anti-TK route	The branch touches the existing satchel anti-TK fired handler and structure-damage friendly-fire wrapper, so a standalone PR #66 page would duplicate the structure/friendly-fire owner and make a debug-only tester bypass look like production friendly-fire semantics.	Preserved PR #66 as open draft branch-only evidence: `origin/claude/trello-debug-antitk@98440121` is GitHub-clean but stale-base after B751b (`f8a76de34` base/merge-base, current master `origin/master@f39665d79`, local counts `80 1`), with 4 maintained-root files / +10 / -0 and clean `git diff --check`. Branch anchors add `WF_Debug` exits to `WFBE_CL_FNC_OnFiredSatchel` and `Server_BuildingHandleDamages`; current master lacks those exits and `WF_Debug` defaults false. No gameplay source changed.
2026-06-24	PR cleanup, Feature status, Construction and CoIn systems, Testing workflow	PR #72 anti-base-trap route	The focused `RequestDefense` anti-base-trap candidate belongs on the construction/server-request owner and branch-only smoke gate. A standalone anti-trap page would duplicate the PR board and make a specific static-defense rejection look like broader DR-6 construction-authority closure.	Preserved PR #72 as open draft branch-only evidence: `origin/claude/trello-antibasetrap@b79c5cee` is GitHub-clean but stale-base after B751b (`f8a76de34` base/merge-base, current master `origin/master@f39665d79`, local counts `80 1`), with 8 maintained-root files / +296 / -2 and clean `git diff --check`. Branch anchors add `WFBE_C_BASE_DEFENSE_BUILD_BLOCK_*`, `BaseDefenseTrapGate` and an `_atReject` gate around `RequestDefense`; current master keeps only the older budget/threat gate. No gameplay source changed.
2026-06-24	Feature status, Current source status, Testing workflow, PR cleanup	PR #83/#80 post-B751b status-route correction	The PR cleanup board already proved the post-B751b merge-state drift. Updating the compact status rows prevents future agents from treating pre-B751b branch-intake checks as current merge readiness, without creating another PR-status page.	Preserved PR #83 as dirty/not mergeable after `origin/master@f39665d7950ddf14cb0bbfacb7ee1e40121e93b4` (`mergeable=false` / `dirty`, local counts `80 8`) while keeping its base-relative 46-file Chernarus-only branch evidence; preserved PR #80 as GitHub-clean but stale-base (`mergeable=true` / `clean`, local counts `80 1`) while keeping its base-relative 10-file maintained-root evidence. No gameplay source changed.
2026-06-24	PR cleanup, Progress dashboard and compact machine records	Post-B751b open PR board refresh	The open PR board already owned PR routing; adding a standalone page for base/merge-state drift would duplicate the board and hide the key operating instruction that old branch-intake stats are pre-B751b unless rechecked.	Preserved current source stable `origin/master@f39665d7950ddf14cb0bbfacb7ee1e40121e93b4`, live open roster #84/#83/#80/#74/#72/#66/#63/#59/#54/#53/#9, dirty/not-mergeable PR #83 and PR #9, clean-but-stale-base PR #80/#74/#72/#66/#63/#59/#54/#53, PR #84 as a stats-branch stack, and PR #85-#89 as merged current-master history. No gameplay source changed.
2026-06-24	Current source status, Feature status, Source fix queue, Testing workflow, Progress dashboard	B751b Takistan playable-slot current-master route	PR #89/B751b is a narrow maintained Vanilla Takistan mission/texture delta. A standalone page would duplicate the current-master merge route and overstate a Takistan-only `mission.sqm` change as a general gameplay-code fix.	Preserved current master `origin/master@f39665d79` / PR #89 proof: scoped `7bfcf09a9..origin/master` is 19 maintained Vanilla Takistan files / +511 / -1224 and clean under `git diff --check`; all changed paths are Takistan `mission.sqm` plus 18 added `Textures/*.paa`, with no source Chernarus, Modded, Tools or Extension payload. Merged Takistan now has 34 `PLAY CDG` slots (14 WEST, 14 EAST, 4 GUER, 2 CIV), ids `7000-7033`, owner syncs at `mission.sqm:599`, `:618` and `:2831`, and release-ready wording remains blocked on package/hash, generated `version.sqf`, RPT and texture-load smoke. No gameplay source changed.
2026-06-24	Current source status, Feature status, Source fix queue, AI commander autonomy, Client UI systems, Testing workflow, Progress dashboard	B751 current-master AICOM/client-error route	PR #88/B751 is a small current-master follow-up on the already-canonical B745/B750 merge route. A new B751 page would duplicate the current-source, AICOM, client UI and testing owner pages while hiding that the source delta is not release-smoked and has whitespace cleanup pending.	Preserved current master `origin/master@7bfcf09a9` / PR #88 proof: scoped `c4c9a6479..origin/master` is 14 maintained-root files / +16 / -10; full `f8a76de34..origin/master` is 242 files / +8330 / -9146. Both roots raise `WFBE_C_AICOM_TEAMS_HARD_CAP` to 13 (`Init_CommonConstants.sqf:159`; clamps `AI_Commander_Teams.sqf:113-114,184`) and add GUER/JIP guards at `updateavailableactions.fsm:58-59`, `Client_UIFillListBuyUnits.sqf:40`, `GUI_Menu.sqf:130`, `GUI_Menu_Tactical.sqf:172`, `Init_Client.sqf:812` and `Action_RepairMHQDepot.sqf:7`. `Client_UI_Gear_FillCargoList.sqf` and `server_town.sqf` remain separate follow-ups; source `git diff --check` reports trailing whitespace at `updateavailableactions.fsm:59` in both roots. No gameplay source changed.
2026-06-24	Factory and purchase systems, Feature status, Source fix queue, Progress dashboard	Buy-menu price/key current-master B750/B751 refresh	The existing price/key matrix already owned selected-detail display, modifier reset and driver-default key evidence. A new B750 or B751 page would split adjacent buy-list hardening away from the canonical factory/purchase owner and duplicate the B750 route row.	Preserved current master `origin/master@7bfcf09a9` proof: both maintained roots use modifier-bearing list/purchase/detail price anchors at `Client_UIFillListBuyUnits.sqf:96` and `GUI_Menu_BuyUnits.sqf:105,:420,:621`, mirror driver-default compatibility keys at `GUI_Menu_BuyUnits.sqf:48-49,:194-195,:443-444,:488,:494,:500,:533-534,:546-547`, and still lack a level-0 `UNIT_COST_MODIFIER` reset (`Init_CommonConstants.sqf:661`; `Client_UIFillListBuyUnits.sqf:11,14`). B751 is current-master source-present adjacent hardening (`Client_UIFillListBuyUnits.sqf:40` faction-filter nil `_c` guard; `Init_CommonConstants.sqf:159` AICOM hard cap), not a price/key closure. No gameplay source changed.
2026-06-24	Factory and purchase systems, Feature status, Progress dashboard	B750 factory/purchase owner-page route	The broad B745/B750 merge intake already proved PR #87, but buy-list nil guarding and infantry squad-cap restoration belong on the factory/purchase owner page, not only on UI/status pages. A new B750 page would duplicate the current-master intake and split purchase evidence away from the existing price/refund/queue matrices.	Preserved current master `origin/master@c4c9a6479` / PR #87 purchase-side proof: scoped `6a34799b4..origin/master` purchase subset is four maintained-root files / +24 / -16 and clean under `git diff --check`; both roots guard nil `_c` before `QUERYUNITUPGRADE` at `Client_UIFillListBuyUnits.sqf:88-92`, restore infantry cap growth at `GUI_Menu_BuyUnits.sqf:137-138`, and keep commander bonus at `:139-145`. AICOM effectiveness remains routed through AI commander autonomy. No gameplay source changed.
2026-06-24	Feature status, Current source status, Source fix queue, Tools/build workflow, Player join/disconnect, AI commander autonomy, Client UI systems, Performance sweep, Testing workflow	B74.5/B74.9/B75/B750 current-master merge intake	Fetch-before-commit repeatedly superseded older route text: PR #85 merged `origin/claude/b745@dd1401811`, PR #86 merged `origin/feat/b749-enrollment-bodyfix@2327e5c6a`, direct branch `origin/VBIED_factory_kill_rewards@756d6918` advanced B75 with no PR route, and PR #87 merged `origin/feat/b750-factory-aicom@605ad7326`, advancing current stable to `origin/master@c4c9a6479`. A new page would duplicate existing current-status, tooling, JIP, UI, AICOM, GUER reward and smoke-gate owner routes; canonical pages need the merged source evidence plus package/smoke gates, not another standalone branch note.	Preserved current master `origin/master@c4c9a6479` evidence: broad B745 226 files / +7611 / -9082, PR #85 B748 settings 9 files / +265 / -7, PR #86 B749 14 files / +308 / -21, B75 2 maintained-root files / +88 / -2, B750 8 maintained-root files / +72 / -54, full previous-stable..current-master 238 files / +8316 / -9138. Maintained Vanilla now carries checked B74.7.2 nil-side retry, B748 settings, B75 VBIED reward and B750 buy-list nil guard / infantry cap / AICOM effectiveness draw source; target-package smoke, generated `version.sqf`, LoadoutManager output and release/package proof remain open. No gameplay source changed.
2026-06-24	PR cleanup, Player stats branch audit, Feature status, Current source status, Testing workflow	PR #84 player-stats name stack intake	Open non-draft PR #84 is a small stack on the existing player-stats branch. A new page would duplicate the player-stats audit and branch-only smoke gates; leaving it only in GitHub would hide that it targets `feat/player-stats`, not `master`, and that the external website receiver is not in this repo.	Preserved compact branch evidence: PR #84 / `origin/feat/player-stats-names@177539ed` stacks on `origin/feat/player-stats@e01e47e1`, has clean GitHub merge state, clean scoped `git diff --check`, 6 files / +57 / -7 and no `Missions_Vanilla`, `Modded_Missions`, `Tools` or `Extension` payload. Route in-repo evidence through the player-stats audit: `StatsFlush.sqf` appends optional `~<name>`, DiscordBot parses/accumulates/serializes nullable `name`, tests are updated, local rerun is blocked by missing .NET SDK, and Arma RPT name/separator plus privacy smoke remain open. No gameplay source changed.
2026-06-24	Feature status, Current source status, Player join/disconnect, Testing workflow, AI commander autonomy, Client UI systems, Performance opportunity sweep	B74.7.2 stamped-slot enrollment current-head refresh	`origin/claude/b745` advanced one source-Chernarus commit past the documented `a9145e4da` B74.7.1 veteran-cap head. Leaving `a9145e4da` as current head would hide the server enrollment resolver fix for transient/non-slot groups. A new page would duplicate the existing branch-intake, JIP, testing and owner-route surfaces.	Preserved current head `origin/claude/b745@d52f65466` as branch-only evidence: full branch is 133 files / +4138 / -4401 over current stable, B74.2..current-head is 113 files / +3715 / -4364, `712a7a668..d52f65466` is four clean source-Chernarus commits / 5 files / +49 / -14, and `a9145e4da..d52f65466` is one source-Chernarus `Server_OnPlayerConnected.sqf` file / +7 / -2 with no `Missions_Vanilla`, `Modded_Missions` or `Tools` payload. Source Chernarus now accepts playable-unit UID matches only when `group _x` has `wfbe_side` at `Server_OnPlayerConnected.sqf:31`; the nil-side path logs/re-arms bounded retry at `:71-75`. Route smoke through the B74.7 JIP enrollment gate. No gameplay source changed.
2026-06-24	Feature status, Current source status, AI commander autonomy, Performance opportunity sweep, Testing workflow	B74.7.1 veteran-cap previous-head refresh	`origin/claude/b745` advanced one commit past the documented `29ca9519` B74.7.1 cap commit. Leaving `29ca9519` as current head would hide the one-line veteran-slot follow-up, where the post-clamp `+1` path now respects the same eight-team hard cap. A new page would duplicate the existing branch-intake, AI and testing owner routes.	Preserved then-current head `origin/claude/b745@a9145e4da` as branch-only evidence: full branch was 133 files / +4131 / -4399 over current stable, B74.2..that head was 113 files / +3708 / -4362, `712a7a668..a9145e4da` was three clean source-Chernarus commits / 5 files / +42 / -12, and `29ca9519..a9145e4da` was one source-Chernarus file / +1 / -1 with no `Missions_Vanilla`, `Modded_Missions` or `Tools` payload. Source Chernarus caps `AI_Commander_Teams.sqf:184` with `min _teamsHardCap`; route smoke through the existing AICOM hard-cap gate. Superseded for current-head routing by the B74.7.2 stamped-slot row above. No gameplay source changed.
2026-06-24	Feature status, Current source status, AI commander autonomy, Player join/disconnect, Client UI systems, Performance opportunity sweep, Testing workflow	B74.7/B74.7.1 previous-head refresh	`origin/claude/b745` advanced again after the B74.6 docs pass, then advanced once more during fetch-before-commit. Leaving `712a7a668` or `1cc995246` as current head would hide a source-Chernarus-only EAST JIP enrollment / 30 FPS picker delta plus a small AI-commander founding hard-cap delta. A new page would duplicate the existing branch-intake, AI, JIP, UI and performance owner routes.	Preserved then-current head `origin/claude/b745@29ca9519` as branch-only evidence: full branch was 133 files / +4130 / -4398 over current stable, B74.2..that head was 113 files / +3707 / -4361, and `712a7a668..29ca9519` was two clean source-Chernarus commits / 5 files / +41 / -11 with no `Missions_Vanilla`, `Modded_Missions` or `Tools` payload. Source Chernarus adds a side `wfbe_teams` UID fallback plus connect diagnostics in `Server_OnPlayerConnected.sqf`, a 30 FPS picker preset in `Rsc/Dialogs.hpp` / `FPSPicker_Open.sqf`, and `WFBE_C_AICOM_TEAMS_HARD_CAP = 8` plus clamp logic in `AI_Commander_Teams.sqf`. Superseded for current-head routing by the B74.7.1 veteran-cap row above. No gameplay source changed.
2026-06-24	PR cleanup, Commander vote/reassignment, Support specials, Feature status, Current source status, Testing workflow	PR #80 vote/paratrooper guard intake	Open draft PR #80 has two focused maintained-root changes, but a new page would duplicate existing commander vote and support/tactical owners. Leaving it only in GitHub would make future agents rediscover whether the paratrooper cap guard is branch-only, Vanilla-propagated or stable behavior.	Preserved compact branch evidence: PR #80 / `origin/claude/trello-vote-para-guards@92101abe` is based on current stable `origin/master@f8a76de34`, clean under GitHub merge-state and `git diff --check`, 10 maintained-root files / +148 / -14, with no `Modded_Missions` or `Tools` payload. Route commander tie-break through the commander playbook and paratrooper AI-cap guard through Support Specials plus branch-smoke gates. Do not call it current stable, release-ready or Miksuu-proven. No gameplay source changed.
2026-06-24	PR cleanup, Feature status, Current source status, Testing workflow	PR #83 wiki-wins branch-intake classification	Open draft PR #83 is broad enough to trigger rediscovery loops across commander vote, HC, economy/service, supply, vehicle IRS, construction and cleanup pages if left only in GitHub. A new owner page would duplicate the existing PR cleanup, feature-risk and smoke-gate surfaces before any subsystem has dedicated smoke evidence.	Preserved compact branch evidence: PR #83 / `origin/claude/wiki-wins-batch@a61823265` is based on current stable `origin/master@f8a76de34`, clean under GitHub merge-state and `git diff --check`, Chernarus-source-only, 46 files / +124 / -86, with no `Missions_Vanilla`, `Modded_Missions` or `Tools` payload. Route future work through owner-sized smoke/propagation lanes; do not call it current stable, release-ready or Vanilla-propagated. No gameplay source changed.
2026-06-24	Feature status, Current source status, Client UI systems, Respawn/death lifecycle, Performance opportunity sweep, Testing workflow	B74.5/B74.6 previous-head refresh	`origin/claude/b745` advanced one commit beyond the documented B74.5 head, so leaving `b996bcb3` as "the head" would make agents miss the B74.6 client RPT/FPS regression fix or reclassify it from git history. A new page would duplicate existing branch-intake, UI, respawn and performance owners.	Preserved then-current head `origin/claude/b745@712a7a668` as branch-only B74.6 evidence: the full branch was 132 files over current stable, B74.2..that head was 112 files, and `b996bcb3..712a7a668` is one clean 9-file B74.6 delta. Source Chernarus gets RHUD/common nil guards plus death-camera guards; maintained Vanilla and touched full modded forks get death-camera guards only. Previous B74.4/B74.5 AICOM/JIP/tooling evidence remains included but unchanged by B74.6. Superseded for current-head routing by the B74.7/B74.7.1 row above. No gameplay source changed.
2026-06-24	Attack-wave authority, Feature status, Source Fix queue, Server authority map, Public variable channel index, attack-wave machine rows	Attack-wave authority current B74.2 refresh	Attack-wave DR-41 rows were current through B74.1/B69/B74 but omitted current B74.2 `origin/claude/b74.2-aicom@21b62b04`. Leaving that gap could make the source-Chernarus B74.2 buy-menu/constants line drift look like an authority rescue. A new page would duplicate the existing playbook.	Preserved the Attack-wave authority playbook as canonical: docs/source `HEAD@426de4570993` is source-unchanged from `a764d51107de` for checked attack-wave paths; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f`, Miksuu, perf and historical refs all keep the direct request/detail trust. B74.2 scoped deltas touch only source-Chernarus `GUI_Menu_BuyUnits.sqf` and `Init_CommonConstants.sqf`; `d472da6a..21b62b04` is empty for checked attack-wave paths. No gameplay source changed.
2026-06-24	AI commander autonomy, Commander/HQ lifecycle, Construction and CoIn systems, Feature status	B74.5 AICOM helper route split	The B74.5 branch-intake row grouped attack-heli cap/base reaper, AH1Z enrollment, base sell and MHQ relocation together. Leaving them bundled would make future agents rediscover branch scope and could incorrectly imply the MHQ relocation worker itself is new in B74.5. A new page would duplicate the AI commander, HQ lifecycle and construction authority owners.	Historical route split: preserved refined branch evidence in owner pages when `origin/claude/b745@d52f65466` still carried these helper symbols only in source Chernarus. Superseded for current-head routing by the B74.5 LoadoutManager/Vanilla merge row above: `origin/claude/b745@9199bfab8` now carries the checked AICOM hard cap, attack-heli cap/reaper, base-sell and MHQ abort-cooldown paths in maintained Vanilla too, while current stable/B74.2/Miksuu/perf remain without those new helper symbols. No gameplay source changed.
2026-06-24	Client UI systems, Player join/disconnect, Commander vote/reassignment	B74.5 primitive roster/vote route split	The B74.5 branch-intake row named primitive roster evidence, but leaving the details only inside the broad bundle would make future agents rediscover the same vote/JIP path and could blur display fallback with vote outcome policy. A new page would duplicate existing UI, JIP and vote owners.	Historical route split: preserved branch-only source-Chernarus evidence when `origin/claude/b745@d52f65466` still had no maintained Vanilla primitive-roster payload. Superseded for current-head routing by the B74.5 LoadoutManager/Vanilla merge row above: `origin/claude/b745@9199bfab8` now carries primitive roster server push, early client receiver/poll-adopt and primitive vote rows in maintained Vanilla too, while the B74.7.2 stamped-slot server guard remains source-Chernarus-only. No gameplay source changed.
2026-06-24	Feature status, Current source status, Testing workflow, AI commander autonomy, Tools/build workflow	B74.5 branch-intake classification	A newly fetched `origin/claude/b745` branch is broad enough to create rediscovery loops if left only in git history, but a new page would duplicate existing owner routes.	Preserved B74.5 as compact branch-intake evidence: `origin/claude/b745@b996bcb3` branches from current stable `origin/master@f8a76de34`, has no PR route, is clean under `git diff --check`, includes B74.2 as an ancestor, and carries broad bundle payload. Route B74.2 payload through the existing B74.2 row, B74.4 AICOM/JIP through AI Commander, intro-video/asset shrink through Current Source Status, smoke gates through Testing workflow and branch-only tooling through Tools/build. No gameplay source changed.
2026-06-24	Mission entrypoints/lifecycle, Lifecycle wait-chain, AI/headless, Headless delegation, Architecture overview, compact machine index	Mission entrypoint and HC bootstrap current B74.2 route refresh	The boot owner page and machine row still routed current branch scope through older June/stable wording, and the HC timing note flattened current-stable/B74-shaped reseat behavior onto docs/source even though docs/source remains simple sleep-plus-notify. A new page would duplicate the lifecycle owner and wait-chain graph.	Preserved Mission Entrypoints as the boot/include/role owner and Lifecycle Wait Chain as the flag graph: repo docs branch `HEAD@55cb55e2170f` is unchanged from `05664f17` / `2de2de92` for checked boot paths; current stable/B74.1 `origin/master@f8a76de34`, current B74.2 `origin/claude/b74.2-aicom@21b62b04`, B69, B74, Miksuu, perf and historical release-line refs keep the same front-door topology. Current B74.2 changes only source-Chernarus `Init_Client.sqf` / `Init_Server.sqf` among checked boot paths, while maintained Vanilla stays stable-shaped. Docs/source, Miksuu, perf and historical release-line refs keep simple HC sleep+notify; current stable/B74.1/B74.2 use the reseat/deadspawn/watchdog HC bootstrap. No gameplay source changed.
2026-06-24	Commander/HQ lifecycle, Commander reassignment call shape, Commander vote/reassignment	Commander/HQ reassignment route current B74.2 refresh	The Commander/HQ gateway still routed manual reassignment through older `8c3942d2` / `cf2a6d6a` branch-scope wording after the canonical reassignment pages had current stable/B74.1 and current B74.2 evidence. A new page would duplicate the dedicated reassignment call-shape matrix.	Preserved Commander/HQ Lifecycle as the gateway and Commander Reassignment Call Shape as canonical detail: repo docs branch `HEAD@1f07b39d` is unchanged from `60c35c05` for checked reassignment paths and remains old-shape in both maintained roots; current stable/B74.1 `origin/master@f8a76de34`, current B74.2 `origin/claude/b74.2-aicom@21b62b04`, B69, adjacent B74, Miksuu, perf, historical release and historical AI refs fix helper unpacking in both maintained roots while duplicate notifications, visible-name UI targeting, requester authority and current-stable full modded fork drift remain open. No gameplay source changed.
2026-06-24	Economy authority, Resistance supply scaffold, compact side-supply machine context	Side-supply compact context current B74.2 refresh	Compact DR-22 and machine-index rows still routed current side-supply status through older `origin/master@0139a346` wording after canonical economy/resistance pages and current machine JSONL rows already carried current stable/B74.1 and current B74.2 evidence. A new page would duplicate the economy authority owner route.	Preserved Economy Authority First Cut and Resistance Supply Scaffold as canonical: repo docs branch `HEAD@cce86ab80a5d` is unchanged from `3bedb86dca88` for checked side-supply paths; current stable/B74.1 `origin/master@f8a76de34` and current B74.2 `origin/claude/b74.2-aicom@21b62b04` match for checked side-supply/resistance paths, with source Chernarus flooring west/resistance/east server negatives to `0` and adding `wfbe_supply_temp_resistance`, while maintained Vanilla remains old-shape. `d472da6a..21b62b04`, `origin/master..B74.2` and B69..B74 are empty for checked side-supply/resistance/reason paths; live `origin/claude/faction-tint-sidefix@32acd272f92e` removes the resistance handler if revived without rebase. No gameplay source changed.
2026-06-24	Supply mission architecture, Supply authority cleanup, compact supply cooldown/authority machine rows	Supply cooldown current B74.2 compact-context refresh	Compact DR-18 and supply authority rows still routed current stable through older `origin/master@0139a346` wording, while the canonical supply pages already carried current stable/B74.1 and current B74.2 branch scope. A new page would duplicate the existing supply architecture and authority cleanup owner routes.	Preserved Supply Mission Architecture as canonical: repo docs branch `HEAD@915f4441c1c9` is unchanged from `15563691` for checked supply paths and, like Miksuu `b8389e748243` and perf `0076040f`, keeps the old cooldown split; current stable/B74.1 `origin/master@f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce` and B74 `b23f557f` seed/read `LastSupplyMissionRun` with default `0` and carry the supply-heli typed-scan/dead-twin cleanup shape in both maintained roots. No gameplay source changed.
2026-06-24	AI headless/performance, AI commander autonomy audit, Feature status, compact AI commander machine rows	AI commander supervisor current B74.2 route refresh	The AI runtime gateway and compact context still routed current AICOM supervisor evidence through older `origin/master@0139a346` wording or stale no-loop language, while the autonomy audit already had current stable/B74.1 source-present evidence. A new AI commander page would duplicate the existing runtime gateway and autonomy audit.	Preserved AI-Headless-And-Performance as the broad gateway and AI-Commander-Autonomy-Audit as canonical detail: repo docs branch `HEAD@c0e865626ff2` lacks checked maintained-root `AI_Commander.sqf` / `AI_Commander_Produce.sqf`; current stable/B74.1 `origin/master@f8a76de34` compiles/spawns the supervisor in both maintained roots (`Init_Server.sqf:72/:1028` and Vanilla `:66/:1015`), calls upgrades at `AI_Commander.sqf:288` and AI production at `AI_Commander_Produce.sqf:320`; current B74.2 `21b62b04` keeps Vanilla stable-shaped and adds source-Chernarus-only pop-tier/GUER drift at `AI_Commander_Produce.sqf:28` / `Init_Server.sqf:813`. No gameplay source changed.
2026-06-24	Respawn/death lifecycle, Abandoned feature revival, Feature status, Public variable channel index, Dead/stale code, support/modules overviews and MASH machine rows	MASH marker/deploy current B74.2 route refresh	MASH rows still routed current stable through older `0139a346` wording or stopped at previous docs/B74 evidence, while the canonical owner page needed current B74.2 `21b62b04` routing. A new page would duplicate the respawn/death owner matrix.	Preserved Respawn/death lifecycle as canonical: repo docs branch `HEAD@f938b0c0b7ea` is unchanged from `443055cf`, `2b5139219faa` and `db3015f18ea3` for checked MASH deploy/relay/init/respawn paths; docs/source, current Miksuu `b8389e748243` and perf `0076040f` keep old-shape local MASH deploy plus orphaned marker sync; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` remove the maintained deploy/module path. No gameplay source changed.
2026-06-24	Factory and purchase systems, Feature status, Source Fix queue, factory buy/refund machine rows	Factory buy/refund current B74.2 Feature Status refresh	Factory buy/refund rows still named previous B74.2 `d472da6a`, and compact context still described `AIBuyUnit` as broadly latent even though current stable/B74-shaped refs call it for AI production. A new page would duplicate the existing factory atlas and Source Fix route.	Preserved Factory and purchase systems as canonical: repo docs branch `HEAD@f9601c92e0a4` is unchanged from `b8180bb319ed` / `cacd46f09163` / `4120137f` / `8d611092` for checked buy/build paths and remains old-shape; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69, B74 and historical `a96fdda2` refund the real dead/null abort; docs/source, Miksuu, perf and historical QoL `a66d4691` remain old-shape. Current B74-shaped refs call `AIBuyUnit` from `AI_Commander_Produce.sqf:320` for AI-team production, not player-buy authority. No gameplay source changed.
2026-06-24	Client skill init idempotency, Source Fix queue, Feature status, Testing workflow, client skill machine rows	Client skill init current B74.2 context refresh	Skill-init rows still omitted current B74.2 `21b62b04` or hid its source-Chernarus line drift under current-stable/B74.1 wording. A new page would duplicate the existing client skill-init owner route.	Preserved Client skill init idempotency and Source Fix as canonical: repo docs branch `HEAD@1df5200fa485` is unchanged from `b2738971` for checked skill-init paths and keeps `Init_Client.sqf:547,571`; current stable/B74.1 `f8a76de34` uses `:805,:828` in both roots; current B74.2 `21b62b04` uses source Chernarus `:828,:851` and Vanilla `:805,:828`; B69/B74/client-fps and historical release-line evidence carry single-init shape; Miksuu/perf/historical feat-ai still duplicate before apply. No gameplay source changed.
2026-06-24	Construction and CoIn systems, Source Fix queue, Feature status, Testing workflow, commander-built ARTY machine rows	Commander-built ARTY current B74.2 context refresh	Commander-built ARTY rows still routed current stable through older `origin/master@0139a346` wording or omitted current B74.2 `21b62b04`. A new artillery page would duplicate the existing StationaryDefense and Source Fix owner routes.	Preserved Construction/CoIn and Source Fix as canonical: docs/source `HEAD@3dc43a3dca7d` is unchanged from `f5bcaf91` for checked ARTY paths and keeps commander-team gunner handoff; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce` and B74 `b23f557f` share marker-based `WFBE_CommanderArtillery*` discovery at `Construction_StationaryDefense.sqf:166-168` / `Common_GetTeamArtillery.sqf:41-78`; Miksuu/perf remain old `DefenseTeam` shape. No gameplay source changed.
2026-06-24	Hosted server FPS loop sleep, Client UI systems, Feature status, Source Fix queue, Performance sweep, runtime/testing gates and hosted-FPS machine rows	Hosted FPS/status-counter current B74.2 refresh	Hosted-FPS and status-counter rows still routed current stable through older `origin/master@0139a346` wording and omitted current B74.2 `21b62b04`; a new page would duplicate the existing hosted-FPS owner page and UI status-counter split.	Preserved Hosted server FPS loop sleep as canonical: repo docs branch `HEAD@4a1bc13edde6` is unchanged from `d0161083` / `a27086cd` and keeps two guarded compatibility publishers; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f`, live client-fps `709258e7`, live ASR FPS `07609ef4` and historical `a96fdda2` keep one guarded `serverFpsGUI.sqf:4` publisher with no maintained-root monitor file; Miksuu `b8389e748243` and perf quick-wins `0076040f` remain old-loop-shaped. No gameplay source changed.
2026-06-24	Abandoned feature revival, Feature status, Commander/HQ lifecycle, Client UI systems, Networking/public variables, commander task machine rows	Old TaskSystem / Objective Ping current B74.2 refresh	Several rows still routed current stable through older `origin/master@0139a346` wording and omitted current B74.2 `21b62b04`. A new page would blur the important distinction between the old town `TaskSystem` helper and the current-stable-shaped commander Objective Ping route.	Preserved the existing owner pages as canonical: repo docs branch `HEAD@c5937045f`, Miksuu `b8389e748243`, perf `0076040f` and historical `c20ce153` keep commented `SetTask` sends and old `Client_TaskSystem.sqf`; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f` and naval-HVT `2e1c5931` send targeted Objective Ping at `GUI_Menu_Command.sqf:336,344`, register `SetTask` at `Init_PublicVariables.sqf:40` and remove the old helper. Historical `a96fdda2` has live ping sends but no live release head. No gameplay source changed.
2026-06-24	`agent-context.json`, PVF dispatch implementation, Server authority migration map, Source Fix queue	PVF dispatch compact-context current B74.2 refresh	Compact `agent-context.json` still routed current stable through older `origin/master@0139a346` and omitted current B74.2 while canonical PVF pages already carried the current branch split. A new page would duplicate the focused PVF dispatch and server-authority owner routes.	Preserved PVF dispatch / Server Authority / Source Fix pages as canonical: repo docs branch `HEAD@af208505c229` is unchanged from `925d56e01a1e` / `a0721301d4f5` for checked PVF init/dispatcher/send-helper paths and still uses dispatch-time `Call Compile` at `Server_HandlePVF.sqf:14` and `Client_HandlePVF.sqf:22`; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 and B74 use `missionNamespace getVariable` plus `CODE` guards at `Server_HandlePVF.sqf:14-15` and `Client_HandlePVF.sqf:32-33`; current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` remain old-shape. No gameplay source changed.
2026-06-24	`agent-context.json`, WASP marker wait cleanup, Performance sweep, Source Fix queue	WASP marker wait compact-context current B74.2 refresh	Compact `agent-context.json` DR-40/performance rows still routed current stable through older `origin/master@0139a346` and B69-only wording after the canonical WASP page and Source Fix queue already carried current stable/B74.1 and current B74.2 branch scope. A new page would duplicate the focused WASP marker wait owner route.	Preserved WASP marker wait cleanup as canonical: repo docs branch `HEAD@8703f4c3b7d5` is unchanged from `46840f048bd4` for checked `Client/Init/Init_Client.sqf` plus `WASP/global_marking_monitor.sqf` paths and still keeps the unslept display-54 loop in both maintained roots; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69, B74 and client-fps carry `sleep 0.1` before `findDisplay 54` in both roots; current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` remain old-shape. No gameplay source changed.
2026-06-24	UI resource parity cleanup, UI IDD collision repair, Client UI systems, Feature status, Dead/stale code, duplicate IDD machine rows	Duplicate UI IDD current B74.2 head refresh	Duplicate EASA/Economy dialog IDD and title-ID caveat rows still routed current stable through older `0139a346` wording and omitted current B74.2 `21b62b04`; a new page would duplicate the existing UI resource parity cleanup and UI IDD collision repair owner pages.	Preserved UI resource parity cleanup and UI IDD collision repair as canonical: repo docs branch `HEAD@5990557155b0` is unchanged from `edbd341e` / `b5219d47` for checked `Rsc/Dialogs.hpp` / `Rsc/Titles.hpp` IDD paths; docs/Miksuu/perf keep duplicate EASA/Economy `23000`; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` split EASA to `24000` while Economy remains `23000`; title `10200` remains shared by `RscOverlay` / `OptionsAvailable`; no checked hard-coded `findDisplay 23000/24000/10200` callers. No gameplay source changed.
2026-06-24	Paratrooper marker revival, Feature status, Source Fix queue, compact paratrooper machine context	Paratrooper marker B74.2 context refresh	The paratrooper owner page, Feature Status and compact context still routed current stable through older `origin/master@0139a346` wording and omitted current B74.2 `21b62b04`, even though this is a branch-route refresh rather than a new support-system finding.	Preserved Paratrooper marker revival as canonical: repo docs branch `HEAD@d2da2a9c9388` is source-unchanged from `7e88d609` for checked sender/handler/registration paths; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce` and B74 `b23f557f` register `HandleParatrooperMarkerCreation` at `Init_PublicVariables.sqf:38` in both maintained roots; historical `a96fdda2` registers at `:34`; Miksuu omits the checked registration and perf is Chernarus-only. No gameplay source changed.
2026-06-24	AI runtime and HC loop map, Town AI vehicle despawn safety	AI runtime Town AI B74.2 route refresh	The AI runtime route row still named B74.2 `d472da6a` for tracked-vehicle cleanup even though the canonical Town AI matrix already routes current B74.2 through `21b62b04`; creating another Town AI page would duplicate the focused DR-45 owner page.	Preserved Town AI vehicle despawn safety as canonical: repo docs branch `HEAD@6ee7c754abb6` is source-unchanged from `ce3cf871e1e7` and remains old-shape at `server_town_ai.sqf:214`; current stable/B74.1, B69 and adjacent B74 protect source Chernarus at `:312,:325`, current B74.2 `21b62b04` line-drifts source Chernarus to `:324,:337`, maintained Vanilla remains leader-only at `:319`, and checked `d472da6a..21b62b04` is empty for both maintained-root Town AI files. No gameplay source changed.
2026-06-24	UI resource parity cleanup, Client UI systems, Feature status, Dead/stale code, stale upgrade dialog machine rows	Stale upgrade dialog current B74.2 head refresh	Stale old upgrade dialog rows still routed current stable through older `0139a346` wording and did not name current B74.2 `21b62b04`; a new page would duplicate the existing UI resource parity owner route.	Preserved UI resource parity cleanup as canonical: repo docs branch `HEAD@208062b4e` is unchanged from `427346b0d`, `0fdd5602` and `d4cfef80` and still keeps stale `RscMenu_Upgrade` / missing `GUI_Menu_Upgrade.sqf` / missing `wf_*.paa` icon refs. Current stable/B74.1 `f8a76de34`, previous B74.2 `d472da6a`, current B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` remove the stale class in both maintained roots and keep live `WFBE_UpgradeMenu`. Checked B74.2/current-stable/B69-B74 upgrade-dialog diffs are empty; no gameplay source changed.
2026-06-24	UI resource parity cleanup, Client UI systems, Feature status, Dead/stale code, Economy dialog machine rows	Economy dialog current B74.2 head refresh	Economy-control rows still routed current stable through older `0139a346` wording and did not name current B74.2 `21b62b04`; a new page would duplicate the existing UI resource parity owner route.	Preserved UI resource parity cleanup as canonical: repo docs branch `HEAD@427346b0d` is unchanged from `21f0d53b` / `d2a3f995` / `b5219d47` and still writes stale `23004/23005/23006`; current stable/B74.1 `f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` use declared `23020` in both maintained roots. Checked B74.2 head diffs are empty; no gameplay source changed.
2026-06-24	`agent-context.json`, Commander vote/reassignment, Commander reassignment call shape	Commander reassignment compact-context current-head cleanup	`agent-context.json` still summarized DR-15 as broadly current-source-unpatched after the canonical commander pages already split docs/source helper-unpacking debt from current stable/B74-shaped maintained-root evidence. A new page would duplicate the existing commander owner routes.	Preserved commander playbook and reassignment call-shape pages as canonical: docs/source tree `HEAD@1e08d0d91` still uses `_side = _this` at `Server_AssignNewCommander.sqf:3` in both maintained roots, while current stable/B74.1 `origin/master@f8a76de34`, current B74.2 `21b62b04`, B69 `8d465fce`, adjacent B74 `b23f557f`, Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2` and `c20ce153` use `_side = _this select 0` at `:4`. Duplicate reassignment notifications, visible-name UI targeting, requester authority, docs/source propagation, modded forks and Arma smoke remain open. No gameplay source changed.
2026-06-24	`agent-context.json`, Source Fix queue, `agent-release-readiness.json`, LoadoutManager/generated-input machine facts	LoadoutManager compact context B74.2 current-head cleanup	`agent-context.json` and the Source Fix queue embedded agent facts still summarized LoadoutManager root discovery / packaging through stale B74.2 `d472da6a` wording after the canonical queue and release-readiness route had current B74.2 `21b62b04` evidence. A separate tooling page would duplicate the existing Source Fix and Tools/build owner pages.	Preserved Source Fix queue and release-readiness as canonical: docs/source `HEAD@101930f47` is unchanged through repo `HEAD@025d5cf` for checked tooling/generated-input paths; scoped `d472da6a..21b62b04` and `origin/master..origin/claude/b74.2-aicom` deltas are empty for those paths; stable/B74.2/B69/B74 use marker-root discovery without checked `A2WASP_SKIP_ZIP`; Miksuu/perf remain named-root-only; and `origin/codex/version-sqf-current-b74@499c2543` is docs/wiki-tip evidence with docs-source tooling shape, not a current stable/B74.2 generated-input rescue. No gameplay source changed.
2026-06-24	Victory/endgame atlas, Feature status, Source Fix queue, victory/endgame machine rows	Victory/endgame B74.2 current-head follow-up	Victory/endgame rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Victory/endgame canonical atlas and DR-11/DR-36 route.	Preserved Victory/endgame atlas as canonical: docs/source `HEAD@c2b614e8cc87` is unchanged from `4c87efd2` / `d30d23466` / `a0a86da2` / `2f2132f8` for checked victory/endgame paths; current B74.2 matches current stable/B74.1 checked server/client/logger behavior, checked `d472da6a..21b62b04` is empty for maintained-root victory paths, and `origin/master..origin/claude/b74.2-aicom` only line-drifts source-Chernarus victory constants to `Init_CommonConstants.sqf:869-870`. No gameplay source changed.
2026-06-24	Client UI systems, Feature status, Source Fix queue, vote/help/main-menu machine rows	Vote/help/main-menu UI B74.2 current-head follow-up	Vote/help/main-menu UI rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Client UI owner matrix.	Preserved Client UI systems as canonical: docs/source `HEAD@72007de93f00` is unchanged from `322ef95e` / `087152f5` / `68bd4dc5` for checked vote/help/router paths; current B74.2 still keeps inclusive vote loops, row-color offset, help namespace mismatch and handler-only `MenuAction` `17/18`; checked `d472da6a..21b62b04` only touches source-Chernarus `Init_Client.sqf` vehicle-tint/join-ACK/intro-music code among checked paths. No gameplay source changed.
2026-06-24	Gear template profile filter, Gear/loadout/EASA atlas, Feature status, Source Fix queue, gear-template machine rows	Gear template profile B74.2 current-head follow-up	Gear profile-template save/import/create/display rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing gear template owner matrix and Gear/Loadout/EASA atlas route.	Preserved Gear Template Profile Filter as canonical: docs/source `HEAD@4b9591314c96` is unchanged from `72b5f0de98f9` / `43c3ba05` for checked template paths; checked `d472da6a..21b62b04`, `origin/master..origin/claude/b74.2-aicom` and B69..B74 are empty for those paths; current stable/B74.1/current B74.2/B69/B74 fix the save filter to `(_get select 3)` at `Client_UI_Gear_SaveTemplateProfile.sqf:34,57,82`, while all checked refs still keep the profile import guard/index mismatch and add/display upgrade-gate split. No gameplay source changed.
2026-06-24	AI commander capture/fun plan, AI commander autonomy, Testing workflow, `agent-release-readiness.json`	AI commander capture-plan B74.2 current-head follow-up	The capture/fun design page and release-readiness branch-only gate still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing AI commander branch-intel owner route.	Preserved AI Commander Autonomy and Testing workflow as canonical: current B74.2 `21b62b04` remains source-Chernarus-only, no PR route, no `Missions_Vanilla` payload, `origin/master..origin/claude/b74.2-aicom` is 29 files / +424 / -38 and `git diff --check` clean. The `d472da6a..21b62b04` delta is four source Chernarus files / +100 / -14 for GUER stipend/tier startup/rebroadcast and join/connect recovery. No gameplay source changed.
2026-06-24	AI commander autonomy, Upgrades and research, Feature status, Source Fix queue, AI-upgrade machine rows	AI commander upgrade debit B74.2 current-head follow-up	AI commander upgrade debit/cost lookup rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing AI commander upgrade matrix and upgrade atlas route.	Preserved AI Commander Autonomy Audit as canonical: docs/source `HEAD@c70785e4be30` is unchanged from `031a253fe` / `ade4d356` for checked worker/menu paths; checked `d472da6a..21b62b04` is empty; current B74.2 matches current stable/B74.1/B69/B74 resolved maintained-root worker lines `:75,:89,:92,:97,:125,:131-132,:136`, while docs/source/Miksuu/perf remain old-shape at `:27,:34,:36,:47,:50`. No gameplay source changed.
2026-06-24	Town AI vehicle despawn safety, Feature status, Source Fix queue, town-AI machine rows	Town AI vehicle despawn B74.2 current-head follow-up	Town AI vehicle despawn rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the focused DR-45 owner matrix.	Preserved Town AI Vehicle Despawn Safety as canonical: docs/source `HEAD@ce3cf871e1e7` is unchanged from `2a4020586` / `3a9ba92e` for checked `server_town_ai.sqf` paths; checked `d472da6a..21b62b04` is empty; current B74.2 keeps the source-Chernarus crew-count guard at `:337` while maintained Vanilla remains leader-only at `:319`. No checked current ref contains `Server_CleanupExpiredTownDefenseAssets.sqf`. No gameplay source changed.
2026-06-24	Client UI systems, Feature status, Source Fix queue, fast-travel machine rows	Fast-travel fee B74.2 current-head follow-up	Fast-travel fee rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Client UI owner matrix.	Preserved Client UI Systems Atlas as canonical: docs/source `HEAD@003d0c4c044e` is unchanged from `1154f5d43` for checked fast-travel paths; checked `d472da6a..21b62b04` is empty for Tactical GUI/constants paths; current B74.2 only line-drifts source Chernarus constants to `Init_CommonConstants.sqf:625,634-637`; current stable/B74.1/B74.2/B69/B74 still keep the same paid-mode local hide/marker/debit behavior with the old TODO absent. No gameplay source changed.
2026-06-24	Factory and purchase systems, Feature status, Source Fix queue, buy-menu machine rows	Buy-menu price/key B74.2 current-head follow-up	Buy-menu price/key and coupled factory refund rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Factory and Purchase Systems owner matrix.	Preserved Factory and Purchase Systems Atlas as canonical: docs/source `HEAD@b8180bb319ed` is unchanged from `4120137f` / `8d611092` / `ebd86fad0` for checked buy-menu price/key paths and from `cacd46f09163` for checked buy/build paths; checked `d472da6a..21b62b04` is empty for buy-menu price/key paths and `Client_BuildUnit.sqf`; current stable/B74.1/B74.2/B69/B74 and historical `a96fdda2` fix selected-detail/key mirroring but still lack a level-0 `UNIT_COST_MODIFIER` reset. No gameplay source changed.
2026-06-24	Marker cleanup/restoration, Feature status, Source Fix queue, empty supply-truck machine rows	Empty supply-truck B74.2 current-head follow-up	Empty supply-truck cleanup rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing marker/cleanup lifecycle owner matrix.	Preserved Marker Cleanup Restoration Systems Atlas as canonical: docs/source `HEAD@248baa289ca5` is unchanged from `499c2543` / `b4e10b5f` for checked collector/handler paths; checked `d472da6a..21b62b04` is empty for those paths; current stable/B74.1/current B74.2/B69/B74, Miksuu, perf and historical `a96fdda2` all still set supply-truck `_delay = 86400` in both maintained roots. No live release/cleanup/supply rescue head was exposed. No gameplay source changed.
2026-06-24	Vehicle cargo equip loop bounds, Gear/loadout/EASA atlas, Feature status, Source Fix queue, cargo-loop machine rows	Vehicle cargo loop B74.2 current-head follow-up	Cargo-loop rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing focused cargo-loop owner route.	Preserved Vehicle Cargo Equip Loop Bounds as canonical: docs/source `HEAD@c96ee1670ddb` is unchanged from `ebfdca96542f` / `b2544207` for checked cargo helper paths; checked `d472da6a..21b62b04` is empty for cargo helpers; current stable/B74.1/B74.2/B69/B74 and historical `a96fdda2` fix both maintained roots, while docs/source, Miksuu, historical EASA QoL and perf Vanilla remain old-shape. No gameplay source changed.
2026-06-24	Mission parameters, Dead/stale code register, Feature status, Source Fix queue, visible-parameter machine rows	Visible parameter B74.2 current-head follow-up	Visible `WFBE_C_AI_MAX` / `WFBE_C_UNITS_CLEAN_TIMEOUT` rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Mission Parameters owner route.	Preserved Mission Parameters as canonical: docs/source `HEAD@52b7f7443bbc` is unchanged from `0da6ba431` for checked parameter paths; checked `d472da6a..21b62b04` is empty for parameter/cache/cleanup/AI-consumer paths; docs/source/Miksuu/perf/historical `a96fdda2` remain old-shape, while current stable/B74.1/B74.2/B69/B74 have maintained-root live readers for `WFBE_C_AI_MAX` and `WFBE_C_UNITS_CLEAN_TIMEOUT`. No gameplay source changed.
2026-06-24	Construction/CoIn systems, Server composition spawner reference, Feature status, Source Fix queue, auto-wall machine rows	Auto-wall B74.2 current-head follow-up	Auto-wall global-toggle rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Construction/CoIn owner route and wall-template reference.	Preserved Construction/CoIn and the spawner reference as canonical: docs/source `HEAD@de471ea5ba96` is unchanged from `eca0e4a7`, `f3896116` and `89aadf8c` for checked auto-wall paths; checked `d472da6a..21b62b04` is empty for those paths; current stable/B74.1/B74.2/B69/B74 still keep one global toggle with broader structure exclusions, while docs/source/Miksuu/perf keep false-default/no-exclusion shape and live `origin/feat/oa-auto-countermeasures@2015a632` only changes default/AARadar gates. No checked ref scopes the state by player, side or requester. No gameplay source changed.
2026-06-24	Construction logic list cleanup, Construction/CoIn systems, Feature status, Source Fix queue, construction machine rows	Construction SmallSite B74.2 current-head follow-up	Construction SmallSite logic-list rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing construction cleanup and Construction/CoIn owner route.	Preserved the construction cleanup and atlas pages as canonical: docs/source `HEAD@7a7d8c48021f` is unchanged from `d81580cfbe61` and older anchors for checked construction paths; checked `d472da6a..21b62b04` is empty for the four maintained-root SmallSite/MediumSite files; current B74.2 still keeps SmallSite add/add at `Construction_SmallSite.sqf:70,99` while MediumSite removes at `Construction_MediumSite.sqf:70,114` in both maintained roots. No gameplay source changed.
2026-06-24	AI commander autonomy audit, Abandoned feature revival review, Feature status, Source Fix queue, Dead/stale code register, AI supply-truck machine rows	AI supply-truck B74.2 current-head follow-up	Autonomous AI supply-truck safe-disable rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing AI commander branch matrix and abandoned-feature route.	Preserved the existing AI commander/revival pages as canonical: docs/source `HEAD@f9bc264f45a0` is unchanged from `6d4b514c12fc` for checked supply-truck paths; current B74.2 keeps the current stable/B74.1 safe-disable shape at Chernarus `Init_Server.sqf:44,624-625` and maintained Vanilla `:44,618-619`; checked `d472da6a..21b62b04` only line-drifts source-Chernarus GUER stipend startup among checked files; docs/source, Miksuu and perf remain raw-spawn-shaped, and a broad current-origin sweep found no `Server/FSM/supplytruck.fsm`. No gameplay source changed.
2026-06-24	Economy/Towns/Supply, Resource income tick distribution, Feature status, Source Fix queue, resource-income machine rows	Resource-income B74.2 current-head follow-up	Resource-income cap/payout/display rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing economy owner matrix and tick-distribution reference.	Preserved the existing economy pages as canonical: docs/source `HEAD@f29b4a9b7900` is unchanged from `c8ec223a` / `3a32be92` / `cd9ba541` for checked income tick/display paths; checked `d472da6a..21b62b04` is empty for income paths and constants; current stable/B74.1/B74.2 still share the same income tick/display shape while Chernarus-only hybrid-refill, supply multiplier, B74.1 taper and maintained Vanilla parity/display-math decisions remain open. No gameplay source changed.
2026-06-24	Economy authority first cut, Resistance supply scaffold, Economy/Towns/Supply, Feature status, Source Fix queue, side-supply machine rows	Side-supply B74.2 current-head follow-up	Side-supply clamp/resistance/reason rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Economy Authority and Resistance Supply owner matrices.	Preserved the economy matrices as canonical: docs/source `HEAD@3bedb86dca88` keeps the old side-supply/reason shape from `973d817817d9`; checked `d472da6a..21b62b04` is empty for side-supply/resistance/reason paths; current stable/B74.1/B74.2 Chernarus is still only a partial rescue, maintained Vanilla remains old-shape, and live `origin/claude/faction-tint-sidefix@32acd272f92e` is a resistance-handler regression warning if revived. No gameplay source changed.
2026-06-24	Public variable channel index, Networking, Feature status, Source Fix queue, `SEND_MESSAGE` machine rows	SEND_MESSAGE B74.2 current-head follow-up	Direct `SEND_MESSAGE` compile rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Public Variable Channel Index owner matrix.	Preserved the channel matrix as canonical: docs/source `HEAD@c27388b4146b` is unchanged from `cd9ba541d583` / older anchors, and checked `d472da6a..21b62b04`, `origin/master..origin/claude/b74.2-aicom`, docs-source and B69..B74 diffs are empty for maintained-root `SEND_MESSAGE` paths. All checked roots still register `SEND_MESSAGE` at `updateclient.sqf:12`, compile receiver text at `Client_onEventHandler_SEND_MESSAGE.sqf:27` and compile/broadcast helper text at `Common_SendMessage.sqf:26,37-38`. No gameplay source changed.
2026-06-24	Client UI systems, Feature status, Source Fix queue, Dead/stale code, clickable-text machine rows	ClickableText soundPush B74.2 current-head follow-up	Clickable-text sound config rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing Client UI systems owner matrix.	Preserved Client UI systems as canonical: docs/source `HEAD@14d74f9d2` remains old-shape and unchanged from `1d4282eca8fd` / `0bb0f89f` / `b5219d47`; checked `d472da6a..21b62b04`, `origin/master..origin/claude/b74.2-aicom` and B69..B74 resource/dialog/title deltas are empty. Current stable/B74.1/B74.2/B69/B74/GUER branch hits carry valid `RscClickableText.soundPush[] = {"", 0.2, 1};`; docs/source, Miksuu, perf, historical release and UI theme refs remain old-shape patch targets. No gameplay source changed.
2026-06-23	UI IDD collision repair, Client UI systems, Feature status, Source Fix queue, RHUD/endgame machine rows	RHUD/endgame title-handle B74.2 current-head follow-up	RHUD/endgame title-display rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing UI owner page.	Preserved UI IDD Collision Repair as canonical: docs/source `HEAD@aeef97665` remains unchanged from `92b52e73` / `ebfdca965`; checked `d472da6a..21b62b04` title-handle deltas are empty; current B74.2 still shares `currentCutDisplay` between `OptionsAvailable`/RHUD/action icons and `EndOfGameStats` in both maintained roots. Stable-to-B74.2 changes only source-Chernarus RHUD AI-cap display text among checked files. No gameplay source changed.
2026-06-23	Service menu affordability guards, Gear/loadout/EASA atlas, Feature status, Source Fix queue, service/EASA machine rows	Service/EASA B74.2 current-head follow-up	Service/EASA rows still named the stale B74.2 snapshot `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`. A new page would duplicate the service/EASA owner pages; the useful action was refreshing current-head branch proof in place.	Preserved the existing owner pages as canonical: checked `d472da6a..21b62b04` and `origin/master..origin/claude/b74.2-aicom` are empty for Chernarus/Vanilla service menu, EASA menu/module and stringtable paths. Current B74.2 still matches stable/B74.1 for partial service rearm/refuel guards, Chernarus-only exact-funds EASA, maintained Vanilla strict EASA, and branch-only service ammo / EASA category wiring evidence. No gameplay source changed.
2026-06-23	Source Fix queue, Tools/build workflow, Mission config/version graph, release-readiness/knowledge machine rows	LoadoutManager B74.2 current-head follow-up	The top tooling/generated-input rule still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the Source Fix queue and Tools/build owner pages.	Preserved existing pages as canonical: checked `d472da6a..21b62b04`, `origin/master..origin/claude/b74.2-aicom` and B69..B74 deltas are empty for LoadoutManager root discovery, skip-zip packaging, version generation, live/template `version.sqf` presence and Chernarus/Vanilla include consumers. Current B74.2 keeps marker-root discovery at `FileManager.cs:145,150,165,170-176`, has no `A2WASP_SKIP_ZIP` support in `ZipManager.cs:7,10,18,38,71-76`, and still requires live generated `version.sqf` before pack/smoke/release claims. The tracked Chernarus `version.sqf.template:1-14` is reference-only and does not satisfy maintained Vanilla. No gameplay source changed.
2026-06-23	Commander vote/reassignment, Commander reassignment call shape, Commander/HQ lifecycle, Public variable channel index, commander status/queue/machine rows	Commander vote B74.2 current-head follow-up	Commander vote and reassignment rows still named B74.2 `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the existing commander playbook and DR-15 owner page.	Preserved existing commander pages as canonical: checked `d472da6a..21b62b04` and `origin/master..origin/claude/b74.2-aicom` are empty for source Chernarus and maintained Vanilla vote/reassignment paths. Current B74.2 keeps DR-47 vote comparison at `Server_VoteForCommander.sqf:43` and DR-15 helper unpacking at `Server_AssignNewCommander.sqf:4-5`; docs/source/full modded forks, GUI preview/visible-name targeting, duplicate notification and requester authority remain open. `origin/claude/trello-vote-para-guards@92101abe` is branch-only vote-worker tie-break context. No gameplay source changed.
2026-06-23	AI commander autonomy, Client UI systems, Player stats branch audit, Feature status, Testing workflow, B74.2 machine rows	B74.2 AICOM current-head delta refresh	B74.2 branch-candidate docs still named stale `origin/claude/b74.2-aicom@d472da6a` after the branch advanced to `21b62b04`. A new page would duplicate existing AICOM/UI/stats/testing owner pages; the useful action was refreshing the compact branch route and preserving the current-head delta.	Preserved the existing owner pages as canonical: current B74.2 is 29 source Chernarus files / +424 / -38 over `origin/master@f8a76de34`, no PR route, no `Missions_Vanilla` payload and clean `git diff --check`. `d472da6a..21b62b04` adds GUER stipend/tier launch/rebroadcast and JIP join/connect failovers only; older pop-tier/camp/marker/naval/stat writer evidence remains branch-only and source Chernarus-scoped. No gameplay source changed.
2026-06-23	Towns, camps and capture, Feature status, Source Fix queue, camp-flag machine rows	Camp flag B74.2 current-head follow-up	Camp-flag-specific rows still named B74.2 `d472da6a` after the branch advanced to `21b62b04`; a new page would duplicate the town/camp atlas.	Preserved the atlas as canonical: checked `d472da6a..21b62b04` camp flag / repair / `CampCaptured` deltas are empty, current B74.2 still fixes independent capture at source Chernarus `server_town_camp.sqf:91` and maintained Vanilla `:84`, and repair-side world-flag refresh remains open at Chernarus `Server_HandleSpecial.sqf:501,504` plus Vanilla `:468,:471`. No gameplay source changed.
2026-06-23	Supply mission architecture, Supply mission authority cleanup, Supply scan narrowing, Current PR #1 supply helicopters, Economy/Towns/Supply, Feature status	Supply PR #1 current B74.1/B74.2 refresh	Supply PR #1 and supply scan rows still named previous current stable `origin/master@0139a346`, while current stable advanced to B74.1 and B74.2 advanced to `21b62b04`. A new page would duplicate the existing supply owner pages.	Preserved Supply Mission Architecture as canonical: docs/source `15563691` remains truck-only; current stable/B74.1 `f8a76de34`, B74.2 `21b62b04`, B69 `8d465fce` and B74 `b23f557f` carry guarded killed-handler setup, heli-aware typed scan, cooldown casing fix and dead-twin removal/comment in both maintained roots. Miksuu `b8389e748243` and perf `0076040f` remain old-shape; PR/release evidence stays historical. No gameplay source changed.
2026-06-23	Towns, camps and capture, Feature status, Source Fix queue, camp-count machine rows	Camp count helper current B74.1/B74.2 refresh	Camp-count helper fallback rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 advanced to `21b62b04`. A new page would duplicate the existing town/camp atlas.	Preserved the atlas as canonical: docs/source `HEAD@6b8b12df` remains unchanged from `91d1ccf2` / `ade4d356`; current stable/B74.1 `f8a76de34`, B74.2 `21b62b04`, B69 `8d465fce`, B74 `b23f557f`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all keep the zero-camp `exitWith {1}` helpers in both maintained roots. B74.1/B74.2 caller deltas are unrelated contested/naval/pop-tier/stat context; no gameplay source changed.
2026-06-23	WASP marker wait cleanup, WASP overlay, Performance sweep, Feature status, Source Fix queue, WASP marker machine rows	WASP marker wait current B74.1/B74.2 refresh	WASP marker wait rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 moved to a newer head. A new page would duplicate the existing focused WASP marker wait route.	Preserved the canonical WASP marker wait page: docs/source `HEAD@46840f048bd4` remains old-shape; current stable/B74.1 `origin/master@f8a76de34`, B74.2 `21b62b04f`, B69, B74, client-fps and live map branches carry the `sleep 0.1` display-54 throttle in both maintained roots; current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` remain old-shape. No gameplay source changed.
2026-06-23	Towns, camps and capture, Feature status, Source Fix queue, camp-flag machine rows	Camp flag current B74.1/B74.2 refresh	Camp flag rows still named previous current stable `origin/master@0139a346` and said no live camp/town rescue head after stable advanced to B74.1, B74.2 became visible and a wildcard capture branch appeared. A new page would duplicate the existing town/camp atlas.	Preserved the atlas as canonical: docs/source `HEAD@7b635187c8a1` remains old-owner and unchanged from `de911438` / `28a7d9c5`; current stable/B74.1 `f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce`, B74 `b23f557f`, historical `a96fdda2` and naval-HVT `2e1c5931` fix independent capture in maintained roots; Miksuu remains old-owner and perf fixes Chernarus only. Repair-side world-flag refresh remains open everywhere checked; wildcard capture `ead7e854` changes marker audience/handler shape only. No gameplay source changed.
2026-06-23	Gear template profile filter, Gear/loadout/EASA atlas, Feature status, Source Fix queue, gear-template machine rows	Gear template profile current B74.1/B74.2 refresh	The profile-template rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 became visible. Miksuu's old `Gear_template_error` branch also needed routing so future gear owners do not mistake an adjacent buy-gear nil guard for profile persistence closure.	Preserved the existing focused owner page: docs/source `HEAD@1d4282eca8fd` remains source-unchanged from `72b5f0de98f9` / `43c3ba05` and old-shaped for `SaveTemplateProfile` plus import guard. Current stable/B74.1 `f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce` and B74 `b23f557f` keep the save-filter fix but leave import guard and policy split open. Miksuu/perf/historical refs and `miksuu/Gear_template_error@5b056013` are old-shape or adjacent non-rescues. No gameplay source changed.
2026-06-23	Vehicle cargo equip loop bounds, Gear/loadout/EASA atlas, Feature status, Source Fix queue, cargo-loop machine rows	Vehicle cargo loop current B74.1/B74.2 refresh	Cargo-loop rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 became visible. Live Trello gear/EASA branch names also needed routing so future gear owners do not mistake UI/category branches for cargo-loop rescue.	Preserved the focused cargo-loop page instead of creating another gear page: docs/source `HEAD@ebfdca96542f` remains source-unchanged from `b2544207` and old-shape in both maintained roots; current stable/B74.1 `origin/master@f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` fix all five loops in both maintained roots. Current Miksuu and historical EASA QoL remain old-shape; perf fixes Chernarus only. Live Trello gear/EASA branches have no checked cargo-helper delta. No gameplay source changed.
2026-06-23	UI IDD collision repair, Client UI systems, Feature status, Source Fix queue, RHUD/endgame machine rows	RHUD/endgame title-handle current B74.1/B74.2 refresh	The title-handle row still named previous current stable `origin/master@0139a346` after current stable advanced to B74.1 and B74.2 became visible. A new page would duplicate UI IDD Collision Repair; the useful action was updating branch scope and preserving the unrelated B74.2 RHUD AI-cap diff as non-closure.	Preserved the existing UI title-handle owner page: docs/source `HEAD@ebfdca965` is unchanged from `92b52e73` for checked title-handle paths. Current stable/B74.1 `origin/master@f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce`, B74 `b23f557f`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` still share `currentCutDisplay` between `OptionsAvailable`/RHUD/action icons and `EndOfGameStats` in both maintained roots. No gameplay source changed.
2026-06-23	Commander vote/reassignment, Commander reassignment call shape, Feature status, Source Fix queue, commander machine rows	Commander vote/reassignment current B74.1/B74.2 queue refresh	Commander vote and reassignment rows still included stale current stable `origin/master@0139a346` wording after current stable advanced to B74.1 and B74.2 became visible. A new page would duplicate the existing commander playbook and DR-15 owner page; the useful action was replacing stale queue/status line refs and preserving remaining smoke/authority gates.	Preserved the existing commander pages: current stable/B74.1 `origin/master@f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce` and B74 `b23f557f` have no checked vote/reassignment path delta and keep the fixed vote comparison/helper unpacking in maintained roots. Docs/source remains old-shape; GUI vote preview, visible-name reassignment targeting, duplicate notifications, requester authority and modded full forks remain open. No gameplay source changed.
2026-06-23	Town AI vehicle despawn safety, Feature status, Source Fix queue, Town AI machine rows	Town AI despawn current B74.1/B74.2 refresh	Town AI despawn rows still named previous current stable `origin/master@0139a346`, while current stable advanced to B74.1 and now carries a Chernarus-only DR-45 guard. A fresh branch scan also exposed `origin/claude/upstream-town-defense-diag-sync`, which needed routing as delegated-cleanup diagnostics rather than player-vehicle despawn closure.	Preserved the existing Town AI vehicle despawn matrix instead of creating another page: docs/source `HEAD@2a4020586` remains old-shape and unchanged from `3a9ba92e`; current stable/B74.1 `origin/master@f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce` and B74 `b23f557f` guard source Chernarus tracked-vehicle cleanup but leave maintained Vanilla leader-only at `server_town_ai.sqf:319`. Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2` and AI fleet `cc5090bed4ad` remain unsafe in both roots. `origin/claude/upstream-town-defense-diag-sync@cde1f1fc` is branch-only delegated-cleanup diagnostics. No gameplay source changed.
2026-06-23	Towns/camps/capture, Feature status, Source Fix queue, Patrols machine rows	Patrols v2 current B74.1/B74.2 refresh	Patrols v2 rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 became visible, and later B74.2 Patrols rows still named stale `d472da6a` after the branch advanced to `21b62b04`. A new page would duplicate the town atlas; the useful action was updating line drift, branch scope and smoke gates in place.	Preserved the canonical town/camp atlas route: current stable/B74.1 `origin/master@f8a76de34` keeps Patrols v2 in both maintained roots with retired town-AI launch, active `server_side_patrols`, `Common_RunSidePatrol`, friendly markers and side-slot release. Current B74.2 `21b62b04` adds source-Chernarus-only pop-tier cap reads and no `Missions_Vanilla` Patrols payload; checked `d472da6a..21b62b04` Patrols/town-AI/marker/UI cap diffs are empty. Docs/source `HEAD@665df909`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` have no Patrols v2 startup hits. No gameplay source changed.
2026-06-23	AI commander autonomy, Upgrades and research, Feature status, Source Fix queue, AI commander upgrade machine rows	AI upgrade debit current B74.1/B74.2 refresh	The AI commander upgrade debit/cost rows still named previous current stable `origin/master@0139a346` after current stable advanced to B74.1 and B74.2 became visible. A fresh branch scan also showed mixed live side branches, so stale "no matching heads" wording would hide Chernarus-only and old-shape branch evidence.	Preserved the existing AI commander matrix instead of creating another upgrade page: docs/source `HEAD@031a253fe` is unchanged from `ade4d356` for checked worker files and keeps raw AI-order lookup plus swapped debit at `Server_AI_Com_Upgrade.sqf:27,47,50`; Miksuu `b8389e748243` and perf `0076040f` match. Current stable/B74.1 `origin/master@f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce` and B74 `b23f557f` resolve both maintained roots with current-level lookup/debit/funds-fallback anchors at `:75,:89,:92,:97,:125,:131-132,:136`. Live side branches remain branch-only and mixed. No gameplay source changed.
2026-06-23	Service menu affordability guards, Gear/loadout/EASA atlas, Feature status, Source Fix queue, service/EASA machine rows	Service/EASA current B74.1/B74.2 branch refresh	Service/EASA rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 became visible. Live Trello service ammo-count and EASA category branches also needed routing so future UI owners do not mistake them for affordability or authority fixes.	Preserved the existing service/EASA owner pages instead of creating another branch page: docs/source `HEAD@b798fd66` remains old-shape and unchanged from `e9dd7f37` / `8906ee89` / `9b3fc38e` / `8b71e2a1`; current stable/B74.1 `origin/master@f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` partially guard service rearm/refuel but leave repair/heal and action-time context open. Chernarus exact-funds EASA is fixed on stable-shaped refs, maintained Vanilla remains strict. `origin/claude/trello-service-ammo-count@9159f935` is branch-only service ammo UI; `origin/claude/trello-easa-weapon-categories@08819118` is branch-only LoadoutCat wiring. No gameplay source changed.
2026-06-23	Factory and purchase systems, Feature status, Source Fix queue, buy-menu price/key machine rows	Buy-menu price/key current B74.1/B74.2 refresh	The buy-menu price/key rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 became visible. A live Trello #91 buy-menu gear-display branch also needed a small route so future UI owners do not mistake it for a price/key fix.	Preserved the existing factory/purchase owner matrix instead of creating another buy-menu page: docs/source checked price/key paths remain old-shape and unchanged from `4120137f` / `8d611092` / `ebd86fad0`; current stable/B74.1 `origin/master@f8a76de34`, B69 `8d465fce`, B74 `b23f557f`, B74.2 `d472da6a` and historical `a96fdda2` fix selected-detail display and driver-key mirroring in both maintained roots, but no checked ref resets `UNIT_COST_MODIFIER` to `1` for level 0. `origin/claude/trello-buymenu-gear-display@db1291beba` is branch-only special AT gear/ammo preview evidence, not price/key closure. No gameplay source changed.
2026-06-23	Economy, towns and supply, Resource income tick distribution, Economy authority, Feature status, Source Fix queue	Resource income current B74.1/B74.2 refresh	Resource-income rows still named previous current stable `origin/master@0139a346` after current stable advanced to B74.1 and B74.2 became visible. A new page would duplicate the existing economy owner matrix; the useful action was replacing stale line anchors and preserving the Chernarus/Vanilla branch split.	Preserved the existing economy/resource pages: docs/source `HEAD@52d6b3aa` is unchanged from `c8ec223a` for checked income files; current stable/B74.1 `origin/master@f8a76de34` and B74.2 `d472da6a` match for checked income files. Current Chernarus keeps side supply/team paychecks gated, adds B74.1 AICOM taper and hybrid-refill/supply-multiplier behavior; maintained Vanilla keeps non-hybrid/raw-supply fallback; `Client_GetIncome.sqf:24-28` still omits system-4 display multiplier. No gameplay source changed.
2026-06-23	Factory and purchase systems, Feature status, Source Fix queue, factory refund machine rows	Factory destroyed-purchase refund current B74.1/B74.2 refresh	The destroyed-factory purchase refund rows still named previous current stable `origin/master@0139a346` after stable advanced to B74.1 and B74.2 became visible. Leaving that wording would hide that B74.2 only line-drifts source Chernarus buy-menu anchors and could send old-root patch work through stale line refs.	Preserved the existing factory atlas refund matrix instead of creating another page: docs/source `HEAD@cacd46f09163` is unchanged from `4120137f` / `8d611092` for checked buy/build paths and still lacks the `_currentCost` payload/refund; current stable/B74.1 `origin/master@f8a76de34`, B69 `8d465fce`, B74 `b23f557f`, B74.2 `d472da6a` and historical `a96fdda2` pass `_currentCost` and refund the dead/null abort in both maintained roots. Miksuu `b8389e748243`, perf `0076040f` and historical QoL remain old-shape. No gameplay source changed.
2026-06-23	Economy authority, Resistance supply scaffold, Feature status, Source fix propagation queue, Public variable channel index, Server authority map	Side-supply current B74.1/B74.2 refresh	Side-supply clamp/reason/resistance rows still treated current stable as old-shape `origin/master@0139a346`, while current stable advanced to `origin/master@f8a76de34` and now carries a Chernarus partial rescue.	Preserved one canonical economy authority page plus the resistance scaffold instead of creating a duplicate: docs/source `HEAD@973d817817d9` is unchanged from `a908284c` / `4db90f1c`; current stable/B74.1/B74.2 Chernarus floors server negatives to `0` and wires `wfbe_supply_temp_resistance`; maintained Vanilla remains old-shape; DR-44 side/channel/requester validation and reason parsing remain open. No gameplay source changed.
2026-06-23	Construction and CoIn systems, Feature status, Source Fix queue, testing/release-readiness and salvage machine rows	Salvage payout current B74.1/B74.2 refresh	The salvage payout/casing rows still named previous current stable `origin/master@0139a346` after current stable advanced to B74.1 and B74.2 became visible. A new live Trello #15 interlock branch also needed routing so future salvage owners do not mistake it for a payout or authority fix.	Preserved the existing Construction/CoIn salvage matrix instead of creating a new page: docs branch `795cdbbf0`, current stable/B74.1 `origin/master@f8a76de34`, B74.2 `d472da6a`, B69/B74, Miksuu, perf and historical `a96fdda2` keep lowercase `ChangePlayerfunds`, the `updatesalvage.sqf:10` OR loop and client-local delete/reward shape. `origin/claude/salvage-w10-manfilter@2e0242b3` is W10-only evidence; `origin/claude/trello-salvage-truck-interlock@9e75c736e` is branch-only manual-salvage friendly-truck UX/interlock evidence. No gameplay source changed.
2026-06-23	Marker cleanup/restoration, Feature status, Source Fix queue, empty supply-truck machine rows	Empty supply-truck current B74.1/B74.2 refresh	Empty supply-truck cleanup rows still named previous current stable `origin/master@0139a346` after current stable advanced to B74.1 and B74.2 became visible. Leaving that wording would send future cleanup/logistics work through stale line anchors or hide that B74.2 does not touch the collector/handler paths.	Preserved the existing cleanup owner matrix instead of creating another page: docs/source `HEAD@499c2543` is unchanged from `b4e10b5f`; current stable/B74.1 `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce`, B74 `b23f557f`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all still drain `emptyVehicles` through `WFBE_SE_FNC_HandleEmptyVehicle` and set supply-truck `_delay = 86400` in both maintained roots. Checked path deltas from old stable to current stable, current stable to B74.2 and B69 to B74 are empty. No gameplay source changed.
2026-06-23	Client UI systems, Feature status, Source Fix queue, Dead/stale code register, machine rows	Vote/help/main-menu UI current B74.1/B74.2 refresh	The vote/help/router cleanup rows still named previous current stable `origin/master@0139a346` after current stable advanced to B74.1 and B74.2 became visible. Leaving that wording could make B74.1 `Init_Client.sqf` line drift look like a possible UI rescue or hide that B74.2 does not touch this cluster.	Preserved the existing Client UI owner matrix instead of creating another UI cleanup page: docs/source `HEAD@322ef95e` is unchanged from `087152f5` / `68bd4dc5`; current stable/B74.1 `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34` keeps inclusive vote loops, row-color offset, help namespace mismatch and handler-only `MenuAction` `17/18` routes; B74.2 `d472da6a` has no checked vote/help/router delta. Current B74-shaped refs use visible `MenuAction = 19` for GPS enablement, not old zoom rescue. No gameplay source changed.
2026-06-23	Mission config/version graph, Tools and build workflow, Source Fix queue, release-readiness generated-input/tooling gates	Generated `version.sqf` and LoadoutManager current B74.1/B74.2 refresh	The canonical generated-input and tooling pages still mixed previous current stable `0139a346` wording with B69/B74 template notes after stable advanced to `f8a76de34`, B74.1/B74.2 became visible and docs/source tooling gained a different skip-zip/root-discovery shape from stable-shaped refs.	Preserved the existing version graph, build workflow and queue gate instead of creating another page: docs/source `HEAD@7b1187d32`, current stable/B74.1 `f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce`, B74 `b23f557f`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` do not track live Chernarus/Vanilla `version.sqf`; current stable/B74.1/B74.2/B69/B74 track only the Chernarus template; skip-zip support is docs/source-only in the checked refs. No gameplay source changed.
2026-06-23	Client UI systems, Feature status, Source Fix queue, machine rows	Fast-travel fee current B74.1/B74.2 refresh	The Tactical fast-travel fee rows still named current stable `origin/master@0139a346` after current stable advanced to B74.1 and B74.2 became visible. Leaving that wording would blur B74.1 constants line drift with a possible UX rescue.	Preserved the existing Client UI owner matrix instead of creating another fast-travel page: current stable/B74.1 `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34` keeps the same paid-mode hide/marker/local-debit shape at `GUI_Menu_Tactical.sqf:185,195-196,215,403-404`; source Chernarus constants are `Init_CommonConstants.sqf:612,621-624`, maintained Vanilla `:414,423-426`, and B74.2 only drifts source Chernarus constants to `:625,634-637`. Docs/source, current Miksuu, perf and historical release keep the old TODO/line shape. No gameplay source changed.
2026-06-23	Victory/endgame atlas, Feature status, Source Fix queue, testing/release-readiness and victory machine rows	Victory/endgame current B74.1 refresh	Current stable advanced to `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34`, making the prior `0139a346` victory matrix stale. Without a compact refresh, future match-outcome work could mistake the B74.1 Chernarus guard/client rescue for release closure or miss that maintained Vanilla remains server-open.	Preserved the existing Victory/endgame atlas as the canonical page instead of creating another status page. Current stable/B74.1 Chernarus has `_victory` trap removal, same-tick guard/short-circuit and winner-payload client behavior, but still writes `_x` to `WF_Winner`, WASPSTAT and `LogGameEnd`; maintained Vanilla remains gated/mixed and lacks the GUER label. B74.2 adds no checked victory-path delta. No gameplay source changed.
2026-06-23	Mission parameters, Feature status, Source Fix queue, Dead/stale code register, machine rows	Visible parameter current B74.1/B74.2 refresh	The visible-parameter rows still named previous current stable `origin/master@0139a346` for `WFBE_C_AI_MAX` and `WFBE_C_UNITS_CLEAN_TIMEOUT` after current stable advanced to B74.1 and B74.2 became visible. Dead Code also had a stale shorthand implying current Miksuu had live readers.	Preserved the existing Mission Parameters owner page instead of creating another parameter page: docs/source `HEAD@0da6ba431`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` keep old readless/comment-only evidence, while current stable/B74.1 `origin/master@f8a76de34`, B69 `8d465fce`, B74 `b23f557f` and B74.2 `d472da6a` read `WFBE_C_AI_MAX` at `AI_Commander_Produce.sqf:234` and `WFBE_C_UNITS_CLEAN_TIMEOUT` at `Common_TrashObject.sqf:21` in both maintained roots. Player follower caps remain `WFBE_C_PLAYERS_AI_MAX`. No gameplay source changed.
2026-06-23	Support specials, Upgrades and research, Feature status, Source Fix queue, machine rows	Upgrade-sync current B74.1/B74.2 refresh	`RequestSpecial` `upgrade-sync` rows still named stale current-stable `origin/master@0139a346`/current-B74 wording after current stable advanced to B74.1 and B74.2 became visible. Leaving it stale would blur the separate B74.1 `wfbe_upgrading_end_time` improvement with the still-open tuple-parser cleanup.	Preserved the existing compact support/upgrades matrix instead of creating another upgrade-sync page: docs/source `HEAD@a7f383b6` keeps `Server_HandleSpecial.sqf:3,67-73`, caller `GUI_UpgradeMenu.sqf:171` and sync lifecycle `Server_ProcessUpgrade.sqf:26,29,35`; current stable/B74.1 `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34` and B74.2 `d472da6a` keep the mixed parser while adding server end-time state at `Server_ProcessUpgrade.sqf:27,55`. `origin/master..B74.2` and B69..B74 checked path deltas are empty. No gameplay source changed.
2026-06-23	AI commander autonomy, AI commander capture plan, Client UI systems, Towns/camps/capture, Player stats branch audit, Feature status, Testing workflow, release-readiness gates	B74.2 AICOM branch intel	`origin/claude/b74.2-aicom@d472da6ae` is broad source Chernarus branch work over current stable/B74.1 `origin/master@f8a76de34`, but it has no GitHub PR route and no `Missions_Vanilla` payload. If left only as branch metadata, future agents could mistake pop-tier, camp anti-stall, marker replay, carrier HVT, stats fast-follow and tint defaults for current stable or maintained Vanilla behavior.	Preserved source Chernarus branch-only evidence on existing owner pages instead of creating another B74.2 page. The branch changes 26 source Chernarus files / +324 / -24 and `git diff --check` is clean. Promotion remains gated on AICOM pop-tier/team founding, UI cap display, marker replay/JIP, camp anti-stall, tiered towns/defenders/patrols, carrier air-shop/respawn, stats writers and a maintained Vanilla/Takistan scope decision. No gameplay source changed.
2026-06-23	AI commander autonomy audit, Abandoned feature revival review, Feature status, Source Fix queue, Dead/stale code register, machine rows	AI supply-truck current B74.1 refresh	The autonomous AI supply-truck rows still named `origin/master@0139a346` and old `Init_Server.sqf:43,462-463` safe-disable anchors after current stable advanced to B74.1 and `origin/claude/b74.2-aicom` became visible. Leaving stale wording would make current-stable safety look line-drifted or could hide that docs/source, Miksuu and perf still raw-spawn the missing worker.	Preserved the existing AI commander matrix as the canonical route instead of creating another logistics page: current stable/B74.1 `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34` safe-disables at Chernarus `Init_Server.sqf:44,624-625` and maintained Vanilla `:44,618-619`; B74.2 keeps the same shape; docs/source `HEAD@6d4b514c12fc`, Miksuu `b8389e748243` and perf `0076040f` remain raw-spawn-shaped; no checked ref restores `Server\FSM\supplytruck.fsm`. No gameplay source changed.
2026-06-23	Attack-wave authority, Feature status, Source Fix queue, Public variable channel index, Server authority migration, machine rows	Attack-wave direct-PV B74.1 branch-scope refresh	Current stable advanced to `origin/master@f8a76de34` / B74.1 while attack-wave authority rows still cited previous current stable `0139a346`. Leaving stale current-head wording would send future authority work through rediscovery or make constants-only drift look like a possible rescue.	Preserved one canonical playbook and refreshed compact evidence in existing owner pages and JSONL rows instead of creating another branch page. Request/detail trust remains open; constants drift is source-scoped; no gameplay source changed.
2026-06-23	Commander reassignment call shape, Commander vote/reassignment, Feature status, Server authority migration	Commander reassignment current B74.1 refresh	The commander vote/reassignment route still named `origin/master@0139a346` as current stable after stable advanced to `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34`. Leaving that wording would send future commander owners to a stale baseline even though the checked maintained reassignment paths did not change.	Preserved the existing owner pages instead of creating another commander status page: scoped diff `0139a3468609..f8a76de34` touches no maintained-root `Server_VoteForCommander.sqf`, `GUI_VoteMenu.sqf`, `RequestNewCommander.sqf`, `Server_AssignNewCommander.sqf` or `GUI_Commander_VoteMenu.sqf` files. Current stable/B74.1/B69/B74 maintained roots still have DR-47 vote comparison and DR-15 helper unpacking source-present, while duplicate reassignment notifications, visible-name UI targeting, requester authority and old-shape docs/source/modded helpers remain open. No gameplay source changed.
2026-06-23	`docs/wiki` mirror, Available-actions gate FSM, Stringtable localization catalog, UI theme palette, Home, `_Sidebar.md`, `agent-context.json`	Wiki remote reference mirror	Live wiki `origin/master@4d4014a` added three source-verified reference pages and front-door routes while the repo mirror still lacked them. Leaving the mirror stale would make future agents rediscover or miss the latest client-actions, localization and UI-theme reference routes.	Mirrored the exact wiki payload into `docs/wiki` and kept touched-file SHA parity between the wiki checkout and repo mirror. This lane did not re-author the source evidence and made no gameplay source changes.
2026-06-23	Client UI systems, Commander/HQ lifecycle, Construction and CoIn systems, Respawn/death lifecycle, Medic redeployment truck, Feature status, Testing workflow, release-readiness gates	Trello map-radius circles branch intel	Draft PR #78 / Trello #80/#76 / `origin/claude/trello-map-radius-circles@77dd71ba` is a current-stable-based local map-marker/map-indicator branch that could be mistaken for current stable behavior or for authority/eligibility changes if left only in PR metadata. Existing UI, Commander/HQ, construction, respawn and Medic redeploy pages already own the concepts.	Preserved branch-only evidence on existing owner pages instead of creating another branch page: the branch is one commit on current stable merge-base `f8a76de34`, six maintained-root files / +192 / -4 and `git diff --check` clean. It adds local HQ build-area circles and local ambulance/redeploy range circles in source Chernarus plus maintained Vanilla Takistan. It does not change construction authority, placement validation, respawn eligibility, cargo checks, default gear, AI respawn, server state or PV channels; the redeploy watcher also does not duplicate Medic-only, parked/engine-off, cargo or enemy-town eligibility gates. No gameplay source changed.
2026-06-23	Client UI systems, Upgrades and research, Feature status, Testing workflow, release-readiness gates	Trello upgrade icons branch intel	Draft PR #77 / Trello #164 / `origin/claude/trello-upgrade-icons@baf8d9c304ad` is a small current-stable-based visual UI branch that could be mistaken for current stable behavior or new asset work if left only in PR metadata. Existing Client UI and Upgrades pages already own active `WFBE_UpgradeMenu` behavior and upgrade image config.	Preserved branch-only evidence on existing owner pages instead of creating another branch page: the branch is one commit on current stable merge-base `f8a76de34`, two maintained-root `GUI_UpgradeMenu.sqf` files / +8 and `git diff --check` clean. It uses existing `WFBE_C_UPGRADES_IMAGES` entries from `Labels_Upgrades.sqf:104-125` and paints them into upgrade-list column `0` at `GUI_UpgradeMenu.sqf:27-28` and `:173-174`. It does not add image assets, fix stale `RscMenu_Upgrade`, alter upgrade authority or change gameplay source.
2026-06-23	Deployable bipod / weapon resting, Feature status, Testing workflow, release-readiness gates	Trello auto-bipod branch intel	Draft PR #76 / `origin/claude/trello-auto-bipod@5af02b8438e1` is a small current-stable-based client QoL branch that could be mistaken for merged bipod behavior if it stayed only in the upstream-mining ledger. The existing deployable bipod page already owns TAB, stance, whitelist, sound, localization and recoil caveats.	Preserved evidence on the owner page instead of creating another branch page: the branch is one commit on current stable merge-base `f8a76de34`, four maintained-root files / +46 / -2 and `git diff --check` clean. It adds local `AnimChanged` auto-prone deploy by reusing `15 call Bipod_ON`, plus `Client_OnKilled.sqf:90` reattachment. It does not change the whitelist, sound media, `str_bipod` debt, recoil reset, server state or PV channels. No gameplay source changed.
2026-06-23	Support specials and tactical modules, Modules atlas, Assets/config/localization/parameters, Feature status, Testing workflow, release-readiness gates	Trello audio cues branch intel	A fresh fetch exposed `origin/claude/trello-audio-cues@a0e4fb458`, a small current-stable-based feedback branch that could be mistaken for merged behavior or support authority work if it stayed only in the upstream-mining ledger.	Preserved evidence on existing owner pages instead of creating another branch page: the branch is one commit on current stable merge-base `f8a76de34`, four maintained-root files / +74 / -2 and `git diff --check` clean. #90 adds a throttled friendly-client paradrop sound plus local 30-second drop-zone marker; #91 adds a delayed IR-smoke ready-again cue reusing `ARTY_cooldown_over`. No new media files, no support authority changes and no gameplay source changed.
2026-06-23	Client UI systems, Upgrades and research, Commander/HQ lifecycle, Feature status, Testing workflow, release-readiness gates	Trello upgrade/HQ cost info branch intel	Draft PR #75 / `origin/claude/trello-upgrade-hqcost-info@34fd202c8865` is a small current-stable-based UI/info-text branch that could be misread as current stable behavior if left only in PR metadata. Existing owner pages already cover upgrade notifications, Transfer Menu/HQ deploy-cost visibility and promotion gates.	Preserved branch-only evidence on canonical pages instead of creating another page: merge-base is current stable `origin/master@f8a76de34`, payload is six maintained-root files / +96 and `git diff --check` clean. The branch adds value lines for artillery reload and respawn range upgrade completion and shows New HQ cost in Transfer Menu in source Chernarus plus maintained Vanilla. Current stable has the constants/arrays but no branch string keys/UI lines. No gameplay source changed.
2026-06-23	Zeta Cargo sling-load reference, Support specials and tactical modules, ICBM authority, Construction and CoIn systems, Feature status, Testing workflow, release-readiness gates	Trello base-integrity branch intel	A fresh fetch exposed `origin/claude/trello-base-integrity-fixes@66d80160`, a small branch that could be mistaken for current stable Zeta/Nuke behavior or for ICBM authority closure if recorded only by branch name. It also revealed a current-stable split: source Chernarus has the Zeta detach-argument fix, but maintained Vanilla still does not.	Preserved evidence on existing owner pages instead of creating another branch-intel page: branch payload is two commits on current stable merge-base `f8a76de34`, six maintained-root files / +70 / -10 and `git diff --check` clean. #87 adds friendly-HQ lift filtering and ground-drop behavior; #97 deletes in-progress construction logics with `WFBE_B_Type` inside the nuke blast. Maintained Vanilla still needs the Zeta detach argument before parity claims, and ICBM `RequestSpecial` authority remains separate. No gameplay source changed.
2026-06-23	Support specials, Client UI systems, Feature status, Testing workflow, release-readiness gates	Trello artillery UI branch intel	Fresh fetch exposed two small Trello artillery UI branches that could be mistaken for current stable behavior or lost in broad Trello backlog notes. They are directly based on current stable, so they fit best as compact branch-intel rows on existing owner pages rather than a new page.	Preserved exact branch evidence: `origin/claude/trello-arty-cooldown-hud@471fc0580fd6` adds RHUD artillery cooldown controls in source Chernarus plus maintained Vanilla; `origin/claude/trello-arty-to-gunner@2dc3e7403399` adds Tactical `Crew All Artillery` button/action and string keys in both roots. Both merge-base on `origin/master@f8a76de34`, both payload diffs are `git diff --check` clean, and current stable lacks `RUBHUD_Arty`, exact `if (MenuAction == 50)` and crew-artillery strings. No gameplay source changed.
2026-06-23	Upgrades and research, Factory and purchase systems, Feature status, Testing workflow, release-readiness gates	Upstream Barracks 4th-level branch intel	A fresh fetch exposed `origin/claude/upstream-barracks-4th-level@e83de9c4`, a broad-looking config branch that could be mistaken for current stable behavior or mixed with B74.1 base drift if recorded only by branch name.	Preserved evidence in existing upgrade, purchase and promotion-gate pages instead of creating another branch-intel page: the branch is one commit on merge-base `be2bbd084`, payload is 64 maintained-root files / +700 / -688 and `git diff --check` clean, Barracks metadata expands to four levels in `Upgrades_CO_US.sqf:33,61,89,125`, infantry required levels shift in `Core_US.sqf` / `Core_RU.sqf`, and `Common_CreateUnit.sqf:101` replaces `US_Soldier_AT_EP1` HEDP with HEAT in both maintained roots. It remains branch-only; porting must preserve B74.1 player-stats constants and needs Barracks/purchase/loadout smoke. No gameplay source changed.
2026-06-23	`agent-hardening-backlog.jsonl`, Arma 2 OA compatibility audit, Arma 2 OA external reference guide	Validator cleanup; keep pages/records	Strict validation had progressed past Markdown links and failed first on legacy backlog machine refs, then on compatibility-audit self-references to modern/A3-only terms. The records/pages were useful; the issue was machine-reference shape and same-line guardrail wording.	Normalized backlog `wikiRefs` to existing wiki page names and added missing refs from existing owner-page metadata; kept findings intact. Added same-line guardrail wording to the compatibility audit/reference examples. Strict `ValidateWiki.ps1 -WikiPath <live checkout> -SkipGitDiffCheck` now passes. No gameplay source changed.
2026-06-23	Upstream mining ledger, Home, `_Sidebar.md`, `llms.txt`, `mkdocs.yml`, `agent-context.json`	Upstream mining ledger navigation wire	Claude created a useful batch-level upstream-mining audit page, but left the Codex-owned navigation handoff open. Without a front-door route, future upstream reviewers would rediscover the same branch/Trello funnels or miss draft PR outcomes and no-port/needs-design findings.	Preserved one batch-level ledger and linked it beside Upstream Miksuu commit intel and Developer history instead of duplicating PR tables into broad pages. Branch-specific behavior still routes through owner pages and Feature Status. No gameplay source changed.
2026-06-23	Commander/HQ lifecycle, Feature status, Testing workflow, release-readiness gates	Upstream HQ repair price branch intel	A fresh fetch exposed `origin/claude/upstream-hq-repair-price`, a small branch that could be confused with the older reverted PR #3 HQ repair price work or with server-side MHQ repair authority closure. Keeping it on the Commander/HQ owner page avoids a duplicate page while preserving the exact branch-only evidence.	Preserved route: `origin/claude/upstream-hq-repair-price@440be3da0bda` is one clean payload commit on merge-base `be2bbd084`; it changes Chernarus and maintained Vanilla `Action_RepairMHQ.sqf`, `Init_Unit.sqf` and `stringtable.xml` to show repair action/hint prices, but has no server/PVF payload. It is a UI/economy candidate only; any port must preserve B74.1 stats constants and keep MHQ repair server-authority work separate. No gameplay source changed.
2026-06-23	Source fix propagation queue, Current source status snapshot, Testing workflow, release-readiness source-only rows	Source Fix queue current B74.1 branch-scope refresh	The propagated-fix queue still treated `origin/master@0139a346` as current stable in its branch matrix after current stable advanced to `origin/master@f8a76de34`, the same commit as `origin/claude/b74.1-aicom`.	Preserved the existing queue/snapshot/testing pages instead of creating another propagated-fix status page: scoped queue-path diff `0139a3468609..f8a76de34` touches only maintained-root `Client/Init/Init_Client.sqf`; current stable/B74.1 skill init/apply anchors are `:805/:828`, paratrooper registration remains `:38`, FPS remains one guarded `serverFpsGUI.sqf:4` publisher, supply scan remains `:7,:55,:61,:83`, player-list reset remains inside the loop at `:18`, and commander ARTY remains marker-based at `Construction_StationaryDefense.sqf:166-168` plus `Common_GetTeamArtillery.sqf:41-78`. No gameplay source changed.
2026-06-23	Valhalla vehicle climbing assist, Client UI systems, Feature status, Testing workflow, release-readiness gates	Upstream AN-2 / mounted-player blink branch intel	A fresh fetch exposed two small upstream-mining branch heads that could look like current stable behavior if only their branch names were recorded. They share older merge-base `be2bbd084`, while current stable is `origin/master@f8a76de34`; future reviewers needed the payload separated from B74.1 `Init_CommonConstants.sqf` stats drift without creating another branch-intel page.	Preserved evidence in canonical owner pages and machine gates: `origin/claude/upstream-an2-climb-boost@63e6b4142` adds `An2_TK_EP1` low-gear actions plus `Air` `_min = 100` Valhalla assist in both maintained roots; `origin/claude/upstream-blinking-mapicons@6e31f7fd5` adds mounted gunner/commander soldier-marker blinking in both roots. Both are branch-only candidates, not current stable behavior; porting must preserve B74.1 player-stats constants and needs AN-2/map-marker smoke before promotion. No gameplay source changed.
2026-06-23	Navigation inventory, Progress dashboard, `_Sidebar.md`, `llms.txt`, `agent-context.json`	Navigation live-count refresh and mirror divergence note	The inventory still described the 2026-06-13 148-page / MkDocs parity snapshot while the live wiki rebased over `origin/master@d2bad96` has 275 Markdown files and the visible local mirrors are dirty/stale. Future docs work needed a current count without flattening uncommitted local checkout work.	Preserved the existing navigation inventory page instead of creating a new audit page: live wiki count is 275 Markdown / 273 content pages, sidebar now has 242 link refs / 242 unique targets after removing two duplicate cross-family refs, footer has 58 unique targets after the footer prune, broad local link pass found 0 broken local links, and the two AI Commander B69 pages missing `Continue Reading` were fixed. Strict repo validation failed on pre-existing hardening-backlog machine-reference rows; JSON/link/diff checks otherwise passed or warned only on LF/CRLF. Mirror sync remains a separate preservation-first task. No gameplay source changed.
2026-06-23	Commander/HQ lifecycle, Feature status, Source fix propagation queue, Upstream Miksuu commit intel, Developer history	HQ score Miksuu branch intel	A fresh Miksuu fetch exposed score/HQ/bounty branch names that could look like DR-50 rescue branches by name alone. Future commander/HQ work needed branch-name negative evidence without adding another HQ score page.	Preserved the canonical HQ score matrix and upstream-history pages: current Miksuu `master@b8389e748243` still has the double-award handler in both maintained roots; `ScoreForKillingFactories@f17445c15190`, `Fix0ScoreBountyBug@415615c9662a` and `FixNukeMoneyGain@2ad3a7d38837` are old-layout one-award ancestry; `AntiHQTeamkillDisabledInDebugMode@5bafe566951a` is branch-only one-award evidence; `BountyModifierTo4@cc127ef40b4d` predates the HQ score award. No gameplay source changed.
2026-06-23	Feature status, Server authority migration, PVF dispatch implementation, Networking, Public variable channel index, Source fix propagation queue	PVF sender-auth current B74.1 refresh	Current stable advanced to `origin/master@f8a76de34` / `origin/claude/b74.1-aicom@f8a76de34`, while DR-55 rows still cited `0139a346` as current and needed current line refs before any network hardening owner work.	Preserved the existing canonical PVF/network pages instead of creating a duplicate security page: docs/source `HEAD@925d56e01a1e` remains old-shape for checked PVF paths; current stable/B74.1, B69 and B74 still forward only the value tuple at `Init_PublicVariables.sqf:56,61` while dispatching via namespace/`CODE` guards. Checked B69..B74 and B74..B74.1 generic PVF deltas are empty, so DR-55 remains open and separate from dispatcher allowlisting. No gameplay source changed.
2026-06-23	Commander/HQ lifecycle, Feature status, Source fix propagation queue	HQ score current B74.1 refresh	`origin/master` advanced from `0139a346` to `f8a76de34`, matching `origin/claude/b74.1-aicom`, and the existing DR-50 row needed current-stable line refs before code-owner work.	Preserved the existing HQ score/bounty matrix instead of creating a duplicate page: docs/source `HEAD@c2d513ecb` is source-unchanged from `9b7eb4bc`; current stable/B74.1 `f8a76de34` keeps generic `_points` at `Server_OnHQKilled.sqf:64/:66` plus second `_score = 900` at `:109/:112` in both maintained roots; coefficient value remains `3` at Chernarus `Init_CommonConstants.sqf:753` and maintained Vanilla `:555`. B69/B74/B74.1 smoke/sting code is not a DR-50 fix. No gameplay source changed.
2026-06-23	Modules atlas, Dead/stale code register, Reaktiv machine rows	Reaktiv current B74 refresh	The Reaktiv dormant-module matrix still named 2026-06-14 stable `cf2a6d6a` while current stable advanced again to `f8a76de34` and B69/B74 needed explicit current-head coverage.	Preserved the compact module owner table instead of creating a duplicate page: docs/source `HEAD@c2d513ecb672`, direct current Miksuu `b8389e748243` and perf `0076040f` still carry maintained-root Reaktiv files without an init caller; current stable `f8a76de34`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` have no maintained-root Reaktiv hits; all checked refs still carry stale modded Napf/Eden/Lingor copies. No gameplay source changed.
2026-06-23	Mission config/version graph, Feature status, Source fix propagation queue, release-readiness generated-input gate	Generated `version.sqf` current B74 refresh	The generated `version.sqf` row still used a 2026-06-14 docs checkout and stable `cf2a6d6a` proof, and did not distinguish B69/B74's tracked Chernarus template from the live generated file required at boot.	Preserved one canonical version/include page and the queue gate instead of creating a duplicate: docs/source `HEAD@ded20d3d`, current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f`, current Miksuu `b8389e748243` and perf `0076040f` do not track live Chernarus/Vanilla `version.sqf`; fresh checkout has neither file present; B69/B74's `version.sqf.template` is a reference only and does not satisfy the generated-input release gate. No gameplay source changed.
2026-06-23	Tools and build workflow, Source fix propagation queue, Testing workflow, release-readiness tooling gate	LoadoutManager root discovery current B74 refresh	The tooling page and queue mixed docs/source marker-root behavior with current stable/B69/B74 marker-root behavior, which could make future agents run Miksuu/perf or stable-shaped refs from the wrong workspace layout.	Preserved one operational tooling page plus the Source Fix queue rule instead of creating a duplicate: docs/source `HEAD@ffdfaa24` accepts named-root or `Missions` + `Missions_Vanilla` + `Tools/LoadoutManager/LoadoutManager.csproj`; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` accept named-root or Chernarus mission + `Tools/LoadoutManager` + `AGENTS.md`; current Miksuu `b8389e748243` and perf `0076040f` remain named-root-only. No gameplay source changed.
2026-06-23	Victory/endgame atlas, Feature status, Source fix propagation queue, victory/endgame machine rows	Victory/endgame current B74 refresh	Victory/endgame rows still used the 2026-06-21 current-stable framing and did not distinguish B69/B74 Chernarus partial fixes from maintained Vanilla drift. Future match-outcome work would otherwise re-audit whether B69/B74 fixed the guard, client payload, GUER label or threeway gate everywhere.	Preserved one canonical Victory/endgame owner page instead of adding another page: docs/source `HEAD@4c87efd2` remains old-shape; current stable `0139a346` keeps the gated default path with HQ nil/null skip and direct `_x` WASPSTAT/logger in both maintained roots; B69 `8d465fce` and B74 `b23f557f` partially patch Chernarus only (`server_victory_threeway.sqf:16,26,45`, `Client_EndGame.sqf:6-11`, `GUI_EndOfGameStats.sqf:8-10`) while maintained Vanilla remains stable-shaped for the server loop and lacks the GUER stats label. No gameplay source changed.
2026-06-23	UI resource parity cleanup, UI IDD collision repair, Client UI systems atlas, duplicate IDD status/dead-code/machine rows	UI IDD collision current B74 refresh	Duplicate dialog/title IDD rows still used older 2026-06-14 stable/release wording and lacked current stable/B69/B74 branch-tip evidence. Future UI work would otherwise re-audit whether B74 changed the EASA/Economy split or title `10200` state.	Preserved the existing UI resource parity and UI IDD owner pages instead of creating a duplicate: docs/source `HEAD@edbd341e` is unchanged from `b5219d47` for checked Dialogs/Titles IDD paths and still duplicates EASA/Economy `23000` in both maintained roots. Current Miksuu `b8389e748243` and perf `0076040f` keep the duplicate; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` split EASA to `24000` while Economy stays `23000`. `RscOverlay`/`OptionsAvailable` still duplicate title `10200` everywhere checked, and no checked maintained root has `findDisplay 23000/24000/10200` callers. No gameplay source changed.
2026-06-23	UI resource parity cleanup, Client UI systems atlas, Economy dialog controls status/dead-code/machine rows	Economy dialog controls current B74 refresh	Economy stale-control rows still used 2026-06-14 stable/release wording, and one dead-code row incorrectly implied current stable still wrote `23004/23005/23006`. Future UI cleanup would otherwise re-audit whether B74 changed the stable `23020` controller shape.	Preserved the existing UI resource parity owner page instead of creating a duplicate: docs/source `HEAD@21f0d53b` is unchanged from `d2a3f995` / `b5219d47` for checked Economy controller/resource paths and still writes `23004/23005/23006` at `GUI_Menu_Economy.sqf:7-8` in both maintained roots while declaring `23002`, `23003` and `23008` without `23020`. Current Miksuu `b8389e748243` and perf `0076040f` keep that old shape. Current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` use `DisplayCtrl 23020` at `GUI_Menu_Economy.sqf:25` and declare `23020` in both maintained roots; B74 only changes Chernarus dashboard label text versus stable among checked paths. No gameplay source changed.
2026-06-23	UI resource parity cleanup, Client UI systems atlas, stale upgrade dialog status/dead-code/machine rows	Stale upgrade dialog current B74 refresh	The stale upgrade dialog row still used a 2026-06-14 branch check, and one dead-code row incorrectly implied current `origin/master` still carried the stale `RscMenu_Upgrade` class. Future UI cleanup would otherwise re-audit whether current stable/B69/B74 still needed missing-controller cleanup.	Preserved the existing UI resource parity owner page instead of creating a duplicate: docs/source `HEAD@0fdd5602` is unchanged from `d4cfef80` for checked upgrade dialog/controller paths and still carries `RscMenu_Upgrade` at `Rsc/Dialogs.hpp:2425` with missing `Client\GUI\GUI_Menu_Upgrade.sqf` onLoad at `:2428` in both maintained roots. Current Miksuu `b8389e748243` and perf `0076040f` keep the stale class at `:2435,:2438`. Current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f`, historical `a96fdda2` and historical `b061c905` have no checked maintained-root stale-class hits and keep only live `WFBE_UpgradeMenu` at `Rsc/Dialogs.hpp:4-7`; checked stable-to-B74 and B69-to-B74 dialog/controller deltas are empty. No gameplay source changed.
2026-06-23	Factory and purchase systems atlas, buy-menu price/key status/queue/machine rows	Buy-menu price/key current B74 refresh	Buy-menu rows already captured docs/source, current stable and historical QoL/release split, but adjacent B69/B74 was missing and future factory/UI work would otherwise need to re-check whether B74 changed selected-detail pricing, unit-cost reset or driver-default key mirroring.	Preserved the existing factory/purchase owner matrix instead of creating a duplicate: docs/source `HEAD@4120137f` is unchanged from `8d611092` / `ebd86fad0` for checked buy-menu controller/list-filler paths and still carries selected-detail price drift at `GUI_Menu_BuyUnits.sqf:261`, no level-0 `UNIT_COST_MODIFIER` reset and mixed driver-default profile keys in both maintained roots. Current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` fix selected-detail display and mirror both driver keys in both maintained roots, but no checked ref resets `UNIT_COST_MODIFIER` to `1` in `Client_UIFillListBuyUnits.sqf` for level 0. B69..B74 changes only Chernarus constants among checked paths; Miksuu `b8389e748243` and perf `0076040f` stay old-shape. No gameplay source changed.
2026-06-23	Vehicle cargo equip loop bounds, Gear/loadout/EASA atlas, cargo-loop status/queue/machine rows	Vehicle cargo loop current B74 refresh	Cargo-loop rows already captured the old-shape docs/Miksuu split and current-stable fix, but adjacent B69/B74 was missing and future gear/cargo work would otherwise need to re-check whether B74 changed the loop-bound rescue.	Preserved the existing focused cargo-loop page instead of creating a duplicate: docs/source `HEAD@bd0ec67d` is unchanged from `b2544207` for checked cargo helper paths and still carries inclusive loops at `Common_EquipVehicle.sqf:27,33,39` plus `Common_EquipBackpack.sqf:35,41` in both maintained roots; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` fix all five loops to `(count(_items) - 1)` in both maintained roots. Current Miksuu `b8389e748243` and historical EASA QoL `a66d4691` remain old-shape; perf `0076040f` fixes Chernarus only. No gameplay source changed.
2026-06-23	Gear template profile filter, Gear/loadout/EASA atlas, gear-template status/queue/machine rows	Gear template profile current B74 refresh	Gear profile/template rows already captured docs/source, current stable and old-ref split, but adjacent B69/B74 was missing and future gear/UI work would otherwise need to re-check whether B74 changed the save-filter fix, import bounds or creation/display policy.	Preserved the existing focused gear-template page instead of creating a duplicate: docs/source `HEAD@c7f361f4` is unchanged from `72b5f0de98f9` / `43c3ba05` for checked template paths and still carries undefined `_u_upgrade` at `Client_UI_Gear_SaveTemplateProfile.sqf:33,52,75` plus `Init_ProfileGear.sqf:17,25` import-bound debt; current stable `0139a346`, B69 `8d465fce` and B74 `b23f557f` fix the save-filter comparisons at `:34,:57,:82` in both maintained roots but keep the import guard and AddTemplate/FillTemplates policy split. B69..B74 and older-B69-to-B74 checked deltas are empty; no gameplay source changed.
2026-06-23	Towns, camps and capture, camp flag status/queue/machine rows	Camp flag current B74 refresh	Camp flag rows already captured current B69 and naval-HVT evidence, but adjacent B74 was missing and future town/camp work would otherwise need to re-check whether B74 changed independent capture or repair-side flag refresh.	Preserved the existing towns/camps atlas instead of creating a duplicate page: docs/source `HEAD@de911438` is unchanged from `28a7d9c5` for checked camp flag, `repair-camp` and `CampCaptured` client-handler paths and still flags old `_side` at `server_town_camp.sqf:135`; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f`, historical `a96fdda2` and naval-HVT `2e1c5931` fix independent capture in both maintained roots at `server_town_camp.sqf:83-86`; Miksuu `b8389e748243` remains old-owner and perf `0076040f` fixes Chernarus only. Repair-side world-flag refresh remains open everywhere checked; B69..B74 and older-B69-to-B74 checked deltas are empty. No gameplay source changed.
2026-06-23	Construction and CoIn systems, Server composition spawner reference, auto-wall status/queue/machine rows	Auto-wall current B74.1/B74.2 refresh	Auto-wall rows already captured current stable/B69/B74 global-toggle evidence, but current stable has advanced to B74.1 and B74.2 is visible; future construction/CoIn work would otherwise need to re-check whether either branch changed the global-vs-side/requester scope.	Preserved the existing Construction/CoIn owner matrix instead of creating a duplicate page: docs/source `HEAD@eca0e4a7` is unchanged from `f3896116` / `89aadf8c`; docs/source, current Miksuu `b8389e748243` and perf `0076040f` keep the old false-default/no-exclusion global shape; current stable/B74.1 `f8a76de34`, B74.2 `d472da6a`, B69 `8d465fce` and B74 `b23f557f` still keep one mission-global `isAutoWallConstructingEnabled`, default it true, and consume it with SmallSite `AARadar`/`CBRadar` plus MediumSite `AARadar`/`Bank`/`Reserve`/`ArtilleryRadar` exclusions. B74.1/B74.2 construction deltas are unrelated bank/stat work; no checked ref scopes it by player, side or requester. No gameplay source changed.
2026-06-23	Attack-wave authority, attack-wave status/queue/machine rows	Attack-wave authority current B74 refresh	Attack-wave rows already captured current B69 direct-PV authority evidence and mentioned adjacent B74, but current-facing status still said current-B69 and future support/economy work would otherwise need to re-check whether B74 changed the authority path.	Preserved the existing attack-wave authority playbook instead of creating a duplicate: docs/source `HEAD@6d263dc` is unchanged from `1c1ea559` / `f3e157f2`; current stable `0139a346`, B69 `8d465fce` and B74 `b23f557f` all keep client `_supply` / `_side` trust in `ATTACK_WAVE_INIT` plus trusted `ATTACK_WAVE_DETAILS` in both maintained roots. Checked B69..B74 and older-B69-to-B74 attack-wave deltas only touch constants; B74 Chernarus constants drift to `Init_CommonConstants.sqf:528,572-574` while maintained Vanilla stays `:349,393-395`. No gameplay source changed.
2026-06-23	Support specials, Upgrades and research, upgrade-sync status/queue/machine rows	Upgrade-sync current B74 refresh	RequestSpecial `upgrade-sync` rows already captured current B69 tuple-parser evidence, but adjacent B74 was missing and future networking/upgrade work would otherwise need to re-check whether B74 changed the mixed parser.	Preserved the existing compact support/upgrades matrix instead of creating a duplicate page: docs/source `HEAD@b27717f5` is unchanged from `bc21f520` / `ff8dd884`; current stable `0139a346`, B69 `8d465fce` and B74 `b23f557f` all keep mixed `_args` / `_this` parsing at `Server_HandleSpecial.sqf:3,67-73`, caller `GUI_UpgradeMenu.sqf:292` and sync lifecycle `Server_ProcessUpgrade.sqf:32,35,41` in both maintained roots. Checked B69..B74 and older-B69-to-B74 handler/caller/process-upgrade deltas are empty. No gameplay source changed.
2026-06-23	Towns, camps and capture, camp-count status/queue/machine rows	Camp-count helper current B74 refresh	Camp-count helper rows already captured current B69 fallback evidence, but adjacent B74 was missing and future town/respawn work would otherwise need to re-check whether B74 changed the zero-camp helper semantics.	Preserved the existing towns/camps atlas and Camp Helper Risks route instead of creating a duplicate page: docs/source `HEAD@6b8b12df` is source-unchanged from `91d1ccf2` / `ade4d356`; current stable `0139a346`, Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2`, B69 `8d465fce` and B74 `b23f557f` all keep `Common_GetTotalCamps.sqf:10` and `Common_GetTotalCampsOnSide.sqf:16` returning `1` in both maintained roots. Checked B69..B74 and older-B69-to-B74 helper/caller deltas are empty. No gameplay source changed.
2026-06-23	Construction logic list cleanup, Construction and CoIn systems, construction status/queue/machine rows	Construction SmallSite current B74 refresh	SmallSite logic-list rows already captured current B69 add/add evidence, but adjacent B74 was missing and future construction work would otherwise need to re-check whether B74 changed the one-line cleanup debt.	Preserved the existing construction cleanup owner page instead of creating a duplicate: docs/source `HEAD@7562c803` is unchanged from `6b8eba5e` / `3406ffa0`; current stable `0139a346`, Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2`, B69 `8d465fce` and B74 `b23f557f` all keep SmallSite add/add at `Construction_SmallSite.sqf:70,99` while MediumSite removes at `Construction_MediumSite.sqf:70,114` in both maintained roots. Checked B69..B74 and older-B69-to-B74 construction deltas are empty. No gameplay source changed.
2026-06-23	Town AI vehicle despawn safety, Town AI status/queue/machine rows	Town AI despawn current B74 refresh	Town AI despawn rows already captured current B69 Chernarus candidate evidence, but adjacent B74 was missing and future town-AI work would otherwise need to re-check whether B74 changed DR-45 or Vanilla propagation.	Preserved the existing Town AI vehicle despawn matrix instead of creating a duplicate page: docs/source `HEAD@3a9ba92e` still deletes tracked vehicles at `server_town_ai.sqf:214` without a player `crew` check; current stable `0139a346`, Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2` and live AI fleet `cc5090bed4ad` remain unsafe in both maintained roots. B69 `8d465fce` and B74 `b23f557f` are identical for checked paths: Chernarus has the candidate guard at `:325`, maintained Vanilla remains unsafe at `:319`, and no checked current ref contains `Server_CleanupExpiredTownDefenseAssets.sqf`. No gameplay source changed.
2026-06-23	Commander reassignment call shape, Commander vote/reassignment, commander status/queue/machine rows	Commander reassignment current B74 refresh	Commander reassignment rows already captured current stable/B69 helper-unpacking evidence, but adjacent B74 was missing and future commander work would otherwise need to re-check whether B74 changed DR-15 or the remaining duplicate-notification/UI risks.	Preserved the existing reassignment owner matrix instead of creating a duplicate page: docs/source `HEAD@60c35c05` is unchanged from `337ed166` / `b44aaaf8` and still carries `_side = _this`; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f`, current Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2` and historical `c20ce153` all fix maintained-root helper unpacking at `Server_AssignNewCommander.sqf:4-5`. B69..B74 and older-B69-to-B74 reassignment deltas are empty, but duplicate `new-commander-assigned` senders, visible-name UI selection, requester authority and modded full-fork drift remain open. No gameplay source changed.
2026-06-23	Marker cleanup/restoration, empty supply-truck status/queue/machine rows	Empty supply-truck current B74 refresh	Empty supply-truck cleanup rows already captured current B69, but adjacent B74 was missing and future cleanup/logistics work would otherwise need to re-check whether B74 changed the 24-hour supply-truck policy.	Preserved the existing cleanup owner matrix instead of creating a duplicate page: docs/source `HEAD@7e7aebec` is unchanged from `b4e10b5f` for checked collector/handler paths; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all still drain `emptyVehicles` through `WFBE_SE_FNC_HandleEmptyVehicle` and set supply-truck `_delay = 86400` in both maintained roots. B69..B74 and older-B69-to-B74 cleanup deltas are empty; no live `release/*` or cleanup/supply rescue head is exposed. No gameplay source changed.
2026-06-23	Respawn and death lifecycle, Abandoned feature revival, MASH status/PV/dead-code/machine rows	MASH marker current B74 refresh	MASH rows already captured current B69 deploy-removal evidence, but adjacent B74 was missing and future respawn/marker work would otherwise need to re-check whether B74 changed the maintained-root MASH split.	Preserved one canonical MASH split matrix instead of creating a duplicate: docs/source `HEAD@443055cf` is unchanged from `2b5139219faa` / `db3015f18ea3` for checked MASH paths; docs/source, Miksuu `b8389e748243` and perf `0076040f` keep local MASH deploy plus orphaned marker relay; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and historical `a96fdda2` expose only `Skill_Apply.sqf:43` deploy-removed wording and no maintained-root MASH module/deploy paths. No gameplay source changed.
2026-06-23	Commander/HQ lifecycle, HQ score status/queue/machine rows	HQ score current B74 refresh	HQ score rows already captured current B69 base-fall spectacle drift, but adjacent B74 was missing and future commander/HQ work would otherwise need to re-check whether B74 changed DR-50 scoring.	Preserved one canonical HQ score matrix instead of creating a duplicate: docs/source `HEAD@9b7eb4bc` is source-unchanged from `97e4cdd0` / `4d4610f1`; current stable `0139a346`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` keep the double-award shape; B69 `8d465fce` and B74 `b23f557f` have no `Server_OnHQKilled.sqf` delta and keep generic award `:64/:66` plus second bounty `:112`. B74 only line-drifts Chernarus constants; coefficient remains `3`. No gameplay source changed.
2026-06-23	Economy authority first cut, Resistance supply scaffold, side-supply status/queue/machine rows	Side-supply current B74 refresh	Side-supply rows already captured current B69 Chernarus candidate evidence, but adjacent B74 was missing and future economy work would otherwise need to re-check whether B74 changed clamp/reason/resistance paths.	Preserved one canonical economy authority route instead of creating a duplicate: docs/source `HEAD@a908284c` is source-unchanged from `4db90f1c` / `7047da5d9` / `f52ccee8`; current stable `0139a346`, current Miksuu `b8389e748243`, perf Vanilla and historical `a96fdda2` keep old-shape floors/reason guards; B69 `8d465fce` and B74 `b23f557f` have no checked side-supply path delta and fix only Chernarus server arithmetic plus `wfbe_supply_temp_resistance`. Maintained Vanilla, validation and reason parsing remain open. No gameplay source changed.
2026-06-23	Public variable channel index, Networking and public variables, `SEND_MESSAGE` status/queue/machine rows	`SEND_MESSAGE` direct compile current B74 refresh	`SEND_MESSAGE` rows already captured current B69 and PVF-dispatch separation, but adjacent B74 was missing and future network work would otherwise need to re-check whether B74 changed this direct publicVariable channel.	Preserved one canonical direct-channel route instead of creating a duplicate: docs/source `HEAD@3a32be92` is source-unchanged from `40c477be` / `16247fc8f`; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all keep `SEND_MESSAGE` direct registration at `updateclient.sqf:12`, receiver compile at `Client_onEventHandler_SEND_MESSAGE.sqf:27`, and helper compile/broadcast at `Common_SendMessage.sqf:26,38` in both maintained roots. No gameplay source changed.
2026-06-22	Service menu affordability guards, Gear/loadout/EASA atlas, service/EASA status/queue/machine rows	Service/EASA affordability current B74 refresh	Service/EASA rows already captured current B69 and finalpieces provenance, but adjacent B74 was missing and future UI/gear work would otherwise need to re-check whether B74 changed service or exact-funds EASA behavior.	Preserved one canonical service/EASA route instead of creating a duplicate: docs/source `HEAD@e9dd7f37` is source-unchanged from `8906ee89` / `9b3fc38e` / `8b71e2a1`; current stable `0139a346`, B69 `8d465fce` and B74 `b23f557f` partially guard service rearm/refuel but leave repair/heal open; B69/B74 exact-funds EASA is Chernarus-only while maintained Vanilla remains strict. No gameplay source changed.
2026-06-22	Commander vote/reassignment, Commander/HQ lifecycle, commander vote status/queue/machine rows	Commander vote current B74 refresh	Commander vote rows already captured the current stable/B69 server comparison fix, but adjacent B74 was missing and the Commander/HQ gateway still carried older all-branches-unpatched wording.	Preserved one canonical vote/reassignment route instead of creating a duplicate: current stable `0139a346`, B69 `8d465fce` and B74 `b23f557f` use `_highest >= _aiVotes` at `Server_VoteForCommander.sqf:43` in both maintained roots; `GUI_VoteMenu.sqf:88` still needs UI/policy smoke. Docs/source `HEAD@e0d82714`, Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2` and historical `c20ce153` keep old `>=
2026-06-22	PVF dispatch implementation, Networking and public variables, Public variable channel index, Server authority migration map, PVF status/queue/machine rows	PVF dispatcher current B74 refresh	PVF dispatcher rows already separated current stable/B69 namespace lookup from old compile-shaped refs, but adjacent B74 was missing and DR-55 pages could still imply stable+B69 was the whole current branch picture.	Preserved the existing PVF dispatcher and authority owner pages instead of creating a duplicate: docs/source `HEAD@a0721301d4f5`, current Miksuu `b8389e748243`, perf `0076040f8a5e` and historical `a96fdda2` keep dispatch-time `Call Compile`; current stable `0139a346`, B69 `8d465fce` and B74 `b23f557f` use namespace/CODE dispatch at server `:14-15` and client `:32-33`, but still have value-only PVEHs at `Init_PublicVariables.sqf:56,61` and no registered-handler allowlist/rejection log. DR-55 and direct PV channels remain separate. No gameplay source changed.
2026-06-22	WASP marker wait cleanup, Performance opportunity sweep, WASP overlay, WASP status/queue/machine rows	WASP marker wait current B74/client-fps refresh	The WASP marker branch route already corrected current stable/B69, but adjacent B74 and live client-fps were missing, leaving future UI/perf work to re-check branches before knowing whether the one-line throttle was already source-present.	Preserved the existing owner page instead of creating a duplicate: docs/source `HEAD@46840f048bd4`, current Miksuu `b8389e748243`, perf `0076040f8a5e` and historical `a96fdda2` keep the old unslept wait; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and client-fps `709258e7` carry `sleep 0.1` at `global_marking_monitor.sqf:64` in both maintained roots. No live `release/*` head is exposed; marker-dialog smoke remains separate. No gameplay source changed.
2026-06-22	Client UI systems, Commander/HQ lifecycle, Networking and public variables, Objective Ping status/machine rows	Objective Ping current stable/B69/B74 refresh	Commander task rows still mixed older stable/release wording and could make current stable look old-shape or make Objective Ping look like old town `TaskSystem` revival.	Preserved one cross-linked branch split instead of creating a new page: docs/source `HEAD@86ab85b9d0b1`, Miksuu `b8389e748243`, perf `0076040f` and historical `c20ce1534be0` keep `SetTask` sends commented at `GUI_Menu_Command.sqf:335,337,343` with `Init_PublicVariables.sqf:33` registration; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f` and `origin/feat/naval-hvt-objectives@2e1c59317186` send Objective Ping at `:336,344` with `:40` registration; historical `a96fdda2` has live sends/`:36` registration but no live `release/*` head. No gameplay source changed.
2026-06-22	Paratrooper marker revival, paratrooper marker status/queue/machine rows	Paratrooper marker current stable/B69/B74 refresh	The paratrooper marker page still contradicted itself by saying current master was patched while its table said `origin/master` omitted the registration, and several rows treated `7ff18c49` as a live release head.	Preserved one canonical paratrooper page instead of creating a duplicate: docs/source `HEAD@7e88d609` registers `HandleParatrooperMarkerCreation` at `Init_PublicVariables.sqf:39` in both maintained roots; current stable `origin/master@0139a346`, B69 `8d465fce` and B74 `b23f557f` register at `:38`; historical `a96fdda2` / `7ff18c49` registers at `:34` but no live `release/*` head exists; current Miksuu keeps sender/handler without the checked registration and perf is Chernarus-only. No gameplay source changed.
2026-06-22	Construction and CoIn commander ARTY scope, commander ARTY status/queue/machine rows	Commander ARTY current B69/B74 marker refresh	Commander-built ARTY rows still mixed older docs/stable/release anchors and could make current stable look missing even though current stable/B69/B74 carry marker-based discovery.	Preserved one canonical Construction/CoIn branch matrix instead of creating a duplicate page: docs/source `HEAD@f5bcaf91` is unchanged from `4bd37b98` for checked commander ARTY paths and keeps `Construction_StationaryDefense.sqf:91-94` plus `Common_GetTeamArtillery.sqf:10-30`; current stable `origin/master@0139a346`, B69 `8d465fce` and B74 `b23f557f` use marker variables at `Construction_StationaryDefense.sqf:166-168` plus `Common_GetTeamArtillery.sqf:46,56`; historical `a96fdda2` / `7ff18c49` uses `:133-135`; Miksuu/perf keep old `DefenseTeam`-only discovery. No gameplay source changed.
2026-06-22	Client UI vote/help/main-menu, UI status/queue/machine rows	Vote/help/router current B69/B74 refresh	The UI matrix still used older docs/stable anchors and did not name current B69/B74, which could send future UI work toward stale line refs or blur the difference between visible action `19` GPS enablement and the old handler-only `17/18` zoom routes.	Preserved one canonical Client UI matrix instead of creating a duplicate page: docs/source `HEAD@087152f5` is unchanged from `68bd4dc5` for checked vote/help/router paths; current stable `0139a346`, current B69 `8d465fce`, adjacent B74 `b23f557f`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all keep inclusive vote loops, `GUI_VoteMenu.sqf:80,82` row-color offset, help namespace mismatch and handler-only `MenuAction` `17/18` GPS zoom routes in both maintained roots. No gameplay source changed.
2026-06-22	Construction and CoIn salvage, AI commander treasury, salvage status/queue/machine rows	Salvage W10 branch-status refresh	A fresh fetch exposed live `origin/claude/salvage-w10-manfilter@2e0242b3`, and the existing salvage rows said no current salvage branch existed. Future readers could confuse that branch's W10 corpse-filter patch with the still-open manual/truck payout typo and authority lane.	Preserved one canonical salvage matrix instead of creating a duplicate page: docs/source `HEAD@98eb9607` is unchanged from `fb8d4ebc` for checked manual/truck salvage files; current stable `0139a346`, current B69 `8d465fce`, adjacent B74 `b23f557f`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all keep lowercase `ChangePlayerfunds`, `updatesalvage.sqf:10` OR-loop and client-local delete/reward in both maintained roots. The live W10 branch is older B39/GUER-based branch evidence with merge-base `8fac20df`; commit `2e0242b3` changes only `AI_Commander_Wildcard.sqf` in both maintained roots and adds `!(_wk isKindOf "Man")` at `:794`. No gameplay source changed.
2026-06-22	Attack-wave authority, Public variable channel index, attack-wave status/queue/machine rows	Attack-wave authority current B69 head refresh	Attack-wave rows still used older branch proof and did not name current B69 `origin/claude/b69@8d465fce`, where readers could wrongly treat B69 as a possible direct-PV authority rescue.	Preserved one canonical owner playbook instead of creating a duplicate page: docs/source `HEAD@1c1ea559` is unchanged from `f3e157f2` for checked attack-wave request/detail/client-price paths; current stable `0139a346`, current B69 `8d465fce`, Miksuu `b8389e748243`, perf `0076040f`, historical release `a96fdda2`, historical AI commander `c20ce153` and historical AttackWave `994150da` all still keep `ATTACK_WAVE_INIT` side/supply trust and `ATTACK_WAVE_DETAILS` side/modifier/duration trust in both maintained roots. B69 checked path deltas from `0a1ccb4d` and `b8530477` are empty. Adjacent B74 `origin/claude/b74-aicom-spend@b23f557fc912` changes only Chernarus constants among checked attack-wave paths and keeps the same request/detail trust. No gameplay source changed.
2026-06-22	Commander reassignment call shape, Commander vote/reassignment, commander status/queue/machine rows	Commander reassignment current B69 head refresh	Commander reassignment rows named current stable helper-unpacking proof but did not yet name current B69 `origin/claude/b69@8d465fce`, where readers could reopen helper unpacking despite B69 matching current stable in maintained roots.	Preserved the existing commander reassignment page instead of creating a duplicate: docs/source `HEAD@337ed166` is unchanged from `b44aaaf8` for checked reassignment paths and still carries `_side = _this` in both maintained roots; current stable `0139a346`, current B69 `8d465fce`, Miksuu `b8389e748243`, perf `0076040f`, historical release `a96fdda2` and historical AI-commander `c20ce153` fix helper unpacking in maintained roots. Duplicate reassignment notifications, visible-name UI selection, requester authority and stable/B69 full modded fork drift remain open. No gameplay source changed.
2026-06-22	Public variable channel index, Networking and public variables, Hardening implementation roadmap, `SEND_MESSAGE` status/queue/machine rows	`SEND_MESSAGE` direct compile current B69 head refresh	Direct-channel `SEND_MESSAGE` rows lacked current B69 `origin/claude/b69@8d465fce` evidence after later B69 merges, where readers could wrongly assume current stable/B69 PVF dispatcher lookup changes also cover direct publicVariable channels.	Preserved the canonical branch matrix on Public variable channel index instead of creating a duplicate page: docs/source `HEAD@40c477be` is unchanged from `16247fc8f` for checked Chernarus/Vanilla `SEND_MESSAGE` paths; current stable `0139a346`, current B69 `8d465fce`, Miksuu `b8389e748243` and perf `0076040f` still keep direct registration at `updateclient.sqf:12` plus receiver/helper `call compile` at `Client_onEventHandler_SEND_MESSAGE.sqf:27` and `Common_SendMessage.sqf:26,37-38` in both maintained roots. B69 checked deltas `0a1ccb4d..8d465fce` and `b8530477..8d465fce` are empty. No gameplay source changed.
2026-06-22	Service menu affordability guards, Gear/loadout/EASA atlas, service/EASA status/queue/machine rows	Service/EASA affordability current B69 head refresh	Service/EASA rows still used B69 finalpieces `80d3267c` as current branch evidence after later B69 merges advanced `origin/claude/b69` to `8d465fce`.	Preserved one canonical branch matrix instead of creating a duplicate page: docs/source `HEAD@8906ee89` is unchanged from `9b3fc38e` and `8b71e2a1` for checked Chernarus/Vanilla `GUI_Menu_Service.sqf` and `GUI_Menu_EASA.sqf` paths. Current B69 `8d465fce` is unchanged from finalpieces `80d3267c` and older proof `0094647d` for those paths; service matches current-stable partial rearm/refuel guards in both maintained roots, exact-funds EASA is Chernarus-only at `GUI_Menu_EASA.sqf:118`, and maintained Vanilla remains strict `_funds > price`. No gameplay source changed.
2026-06-22	Marker cleanup/restoration, empty supply-truck status/queue/machine rows	Empty supply-truck current B69 head refresh	Empty supply-truck cleanup rows still used B69 `0094647d` and finalpieces `80d3267c` as current branch evidence after later B69 merges advanced `origin/claude/b69` to `8d465fce`.	Preserved the existing cleanup owner matrix instead of creating a duplicate page: docs/source `HEAD@a3bbcd48` is unchanged from `b4e10b5f` for checked empty-vehicle collector/handler paths; current stable `0139a346`, current B69 `8d465fce`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all still drain `WF_Logic` `emptyVehicles` through `emptyvehiclescollector.sqf:9,12,15-17,19` and set supply-truck `_delay = 86400` in both maintained roots. B69 checked path deltas `0094647d..8d465fce` and `80d3267c..8d465fce` are empty; no live `release/*` or cleanup/supply rescue head was exposed. No gameplay source changed.
2026-06-22	Support specials, Upgrades and research, upgrade-sync status/queue/machine rows	Upgrade-sync current B69 head refresh	RequestSpecial `upgrade-sync` rows were current-stable focused and did not yet name current B69 `origin/claude/b69@8d465fce`, where future readers could otherwise assume B69 rescued or changed the tuple parser.	Preserved the existing compact matrix instead of creating a duplicate page: docs/source `HEAD@bc21f520` is unchanged from `ff8dd884` for checked handler/caller/process-upgrade paths; current stable `0139a346` and current B69 `8d465fce` both keep the mixed `_args` / `_this` parser at `Server_HandleSpecial.sqf:3,67-73`, caller `GUI_UpgradeMenu.sqf:292` and sync lifecycle `Server_ProcessUpgrade.sqf:32,35,41`; `0a1ccb4d..8d465fce` is empty for checked B69 paths. Miksuu/perf/historical refs remain old-shape with caller line drift. No gameplay source changed.
2026-06-22	Commander/HQ lifecycle, Feature status, Source fix propagation queue, HQ score machine rows	HQ score current B69 head refresh	DR-50/HQ-kill score rows had current stable proof but did not name current B69 `origin/claude/b69@8d465fce`, where line drift and base-fall spectacle code could be mistaken for a scoring change.	Preserved one canonical branch matrix on the Commander/HQ page instead of duplicating proof: docs/source `HEAD@97e4cdd0`, current stable `0139a346`, current B69 `8d465fce`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all still keep generic HQ building score plus a separate `_score = 900` HQ bounty in both maintained roots. Current B69 line drift is generic award `Server_OnHQKilled.sqf:64,66`, non-teamkill guard `:106`, `_score = 900` at `:109` and second award `:112`; base-fall smoke/sting at `:57,103` is not a DR-50 scoring fix. No gameplay source changed.
2026-06-22	Feature status, Server authority migration map, PVF dispatch implementation, Networking and public variables, Public variable channel index, PVF sender-auth machine rows	PVF sender-auth current B69 head refresh	DR-55/PVF rows still cited B69 `0a1ccb4d` as current branch evidence after later B69 merges advanced `origin/claude/b69` to `8d465fce`, and the new B69 `HandleSpecial` delta needed to be separated from sender-auth closure.	Preserved the existing authority/networking owner route instead of creating a duplicate page: docs/source `HEAD@4d4610f1` is unchanged from `ade4d356` for checked PVF init/dispatcher paths. Current stable `0139a346` and current B69 `8d465fce` both use `missionNamespace`/`CODE` dispatch but still forward only the PVEH value tuple at `Init_PublicVariables.sqf:56,61`; `0a1ccb4d..8d465fce` changes only `Client/PVFunctions/HandleSpecial.sqf` in both maintained roots among checked PVF paths, adding default-off `aicom-team-merge` at `:57,59`. DR-55 remains authenticated requester context plus per-handler re-derivation. No gameplay source changed.
2026-06-22	Towns, camps and capture, camp-count status/queue/machine rows	Camp-count helper current B69 head refresh	Camp-count helper rows still cited B69 `0a1ccb4d` as current branch evidence after later B69 merges advanced `origin/claude/b69` to `8d465fce`.	Preserved the existing owner page instead of creating a duplicate: docs/source `HEAD@91d1ccf2` is unchanged from `ade4d356` for checked helper/caller paths, and `git diff --name-status 0a1ccb4d..origin/claude/b69` is empty for checked B69 helper/caller paths. Docs/source, current stable `0139a346`, Miksuu `b8389e748243`, perf `0076040f`, historical release `a96fdda2` and current B69 all keep `Common_GetTotalCamps.sqf:10` and `Common_GetTotalCampsOnSide.sqf:16` returning `1` in both maintained roots. Future work remains real-count versus safe-denominator semantics plus 0/partial/all-camp smoke. No gameplay source changed.
2026-06-22	Construction logic list cleanup, Construction and CoIn systems, construction status/queue/machine rows	Construction SmallSite logic current B69 head refresh	The construction logic-list rows still cited B69 `0a1ccb4d` as current branch evidence after later B69 merges advanced `origin/claude/b69` to `8d465fce`.	Preserved the existing owner/playbook route instead of creating a duplicate: docs/source `HEAD@6b8eba5e` is unchanged from `3406ffa0` for checked construction paths; `git diff --name-status 0a1ccb4d..origin/claude/b69` is empty for checked Chernarus/Vanilla `Construction_SmallSite.sqf` and `Construction_MediumSite.sqf` paths. Docs/source, current stable `0139a346`, Miksuu `b8389e748243`, perf `0076040f`, historical release `a96fdda2` and current B69 all keep SmallSite add/add at `Construction_SmallSite.sqf:70,99` while MediumSite removes at `Construction_MediumSite.sqf:70,114` in both maintained roots. No gameplay source changed.
2026-06-22	Town AI vehicle despawn safety, town-AI status/queue/machine rows	Town AI vehicle despawn current B69 head refresh	The player-safety row still cited B69 `0a1ccb4d` as current branch evidence after later B69 merges advanced `origin/claude/b69` to `8d465fce`.	Preserved the existing owner page instead of creating a duplicate: `git diff --name-status 0a1ccb4d..origin/claude/b69` is empty for checked Chernarus/Vanilla `server_town_ai.sqf` paths. Current B69 Chernarus still has the candidate crew scan at `server_town_ai.sqf:325`, but maintained Vanilla remains leader-only at `:319`. Docs/source `HEAD@948db4ab`, current stable `0139a346`, Miksuu `b8389e748243`, perf `0076040f`, historical release `a96fdda2` and aicom-fleet `cc5090bed4ad` remain unsafe in both maintained roots. No checked current ref contains `Server_CleanupExpiredTownDefenseAssets.sqf`. No gameplay source changed.
2026-06-22	Economy authority first cut, Resistance supply scaffold, side-supply status/queue/machine rows	Side-supply current B69 head refresh	Side-supply/resistance rows still used `origin/claude/b69@39eed5c0` as if it were the live B69 head after later PR #50/#51 merges advanced the branch to `8d465fce`.	Preserved the old commit as provenance while routing current evidence through existing owner matrices: `git diff --name-status 39eed5c0..origin/claude/b69` is empty for checked side-supply paths; current B69 `8d465fce` still fixes Chernarus server arithmetic at `Server_ChangeSideSupply.sqf:12,36,60` and adds `wfbe_supply_temp_resistance` at `:25`, but maintained Vanilla remains old-shape at `Common_ChangeSideSupply.sqf:25` / `Server_ChangeSideSupply.sqf:12,36`; stable/Miksuu remain old-shape and perf is Chernarus-only. No gameplay source changed.
2026-06-22	WASP marker wait cleanup, Performance opportunity sweep, WASP overlay, WASP status/queue/machine rows	WASP display-54 wait branch-split correction	The 2026-06-21 refresh said the stable branch still had the unslept display-54 loop; fresh source checks showed the stable/B69 pair already carried the one-line `sleep 0.1` throttle in both maintained roots. This row is superseded for adjacent branch scope by the current B74/client-fps row above.	Preserved the existing owner page instead of creating a duplicate: docs/source `HEAD@46840f048bd4`, current Miksuu `b8389e748243` and perf `0076040f8a5e` still kept the unslept loop; the checked stable ref `origin/master@0139a3468609` and B69 ref `origin/claude/b69@8d465fcede7f` carried `sleep 0.1` at `global_marking_monitor.sqf:64` in both maintained roots. Later 2026-06-22 verification adds B74 `b23f557f` and client-fps `709258e7` as throttled too. No gameplay source changed.
2026-06-22	AI commander autonomy audit, B69 roadmap, B69 sketches, PR cleanup lab, Feature status	B69 PR #51 / B73 troop-truck current-head refresh	B69 docs still pointed at PR #50 `b8530477` as current head after remote `origin/claude/b69` advanced to PR #51 merge commit `8d465fce`.	Preserved the existing B69 pages instead of creating a duplicate page: PR #51 merged `claude/ch-truck-fix@70a1c808` into `claude/b69` at `8d465fce` on 2026-06-22T14:03:51Z; `b8530477..8d465fce` is one Chernarus `AI_Commander_Teams.sqf` file / +5 / -1, with `AI_Commander_Teams.sqf:414-418` gating the B66 pure-infantry troop-truck prepend on `WFBE_C_AICOM_ARMED_TRANSPORT_ONLY <= 0`. PR #50 remains the maintained Vanilla/Takistan propagation proof; PR #51 has no maintained Vanilla/Takistan diff. No gameplay source changed.
2026-06-22	Progress dashboard, Takistan FPV design, July route machine records	July FPV branch-route current-head correction	The July FPV route still pointed future code owners at `dev/july-takistan-airfield-fpv-drone` as if it were a current remote branch. Fresh 2026-06-22 branch checks found no such head, while `dev/july-2026-update` exists as a closed draft PR #21 roadmap branch.	Preserved the existing design page and smoke route instead of creating a duplicate: current planning evidence is `origin/dev/july-2026-update@e3f530ed` plus closed unmerged draft PR #21; `origin/dev/july-2026-update:docs/july-2026-update.md` names the Takistan captured-airfield FPV drone as flagship but says planning/no gameplay code yet. `origin/feat/drone-saturation-strike@8ca4be90` and `origin/feat/recon-uav@563418ea` remain separate branch-only features. No gameplay source changed.
2026-06-22	AI runtime/HC loop map, AI/headless/performance, Headless delegation/failover	AI/HC runtime current-stable line-anchor refresh	The HC runtime gateway pages still mixed docs-source and historical `cf2a6d6a`/release line refs with current stable `origin/master@0139a346`, and one page still implied town static defenses were resistance-only. That risked sending future code owners toward a side-gate patch instead of DR-21/DR-42 work records, callback/failback and smoke.	Preserved one route across the existing AI/HC pages instead of creating another page: docs HEAD `4b6f5ca9` is unchanged from earlier AI/HC source anchors for checked paths; current stable Chernarus and maintained Vanilla checked HC/runtime files are identical. Current stable HC reseat/reannounce + idempotent registration is `Init_HC.sqf:94-129` and `Server_HandleSpecial.sqf:406-431`; town HC delegation/update-back is `server_town_ai.sqf:242-248`, `Server_DelegateAITownHeadless.sqf:22-56`, `Client_DelegateTownAI.sqf:29-44` and `Server_HandleSpecial.sqf:86-115`; active-side static-defense HC delegation has no side gate at `Server_OperateTownDefensesUnits.sqf:55-67`; Patrols v2 current-stable HC/local dispatch remains routed through the topology/Patrols owner pages. Direct Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` remain branch-scoped. No gameplay source changed.
2026-06-22	Headless client scaling and topology, Patrols v2 HC route	Patrols v2 topology current-stable refresh	The topology page still said patrols were structurally server-pinned and cited `cf2a6d6a` as current Patrols v2 HC evidence even though current stable has line drift and adjacent pages already route Patrols v2 through current `origin/master@0139a346`. It also kept stale static-defence west/east side-gate and multi-HC random-selection wording beside newer current-stable rows.	Preserved one compact topology route instead of duplicating the Patrols owner matrix: current stable `origin/master@0139a346` starts `server_side_patrols.sqf` at `Init_Server.sqf:690`, dispatches HC/local at `server_side_patrols.sqf:64-69`, receives `delegate-sidepatrol` at `Client/PVFunctions/HandleSpecial.sqf:50`, and updates slot/marker state through `Common_RunSidePatrol.sqf:54-56,82-84,245-247,264-266`, `Server_HandleSpecial.sqf:345-372` and `updatepatrolmarkers.sqf:3,19`. Docs HEAD `ff5b95dabb06`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` lack Patrols v2 files; `cf2a6d6a` is historical stable evidence only. Current stable static-defence spawn uses the active town side and no side gate at `Server_OperateTownDefensesUnits.sqf:55-67`; current stable town AI uses least-loaded + round-robin HC selection at `Server_DelegateAITownHeadless.sqf:22-56`; DR-42/report-back and smoke remain open. No gameplay source changed.
2026-06-22	Hosted server FPS loop sleep, July update route, runtime/status machine rows	Hosted-FPS branch-route correction	The owner page was mostly branch-aware, but adjacent Feature Status, runtime, roadmap/testing, machine and dashboard rows still mixed stale docs/stable line anchors with an asserted `origin/dev/july-update-hosted-server-fps-loop-fix` branch that is not currently published.	Preserved one refreshed branch route instead of creating a new page: docs HEAD `d0161083` is source-unchanged from `a27086cd` for checked FPS paths; current stable `origin/master@0139a346` uses the single guarded publisher at `serverFpsGUI.sqf:4`, starts it from `Init_Server.sqf:769` and documents monitor removal at `:815-817`; historical `a96fdda2` matches with older anchors; Miksuu `b8389e748243` and perf `0076040f` remain old-loop-shaped; no current July hosted-FPS dev branch or live `release/*` head was found. No gameplay source changed.
2026-06-22	Feature status, resistance side-supply route	Resistance side-supply status-row de-duplication	The Feature Status row still repeated the old generic west/east-only statement after the scaffold page gained the branch matrix, which risked hiding the current-stable owner/read split and B69 Chernarus-only handler candidate.	Preserved one compact status row that links to the canonical matrices: docs `HEAD@56370c44` is source-unchanged from `4db90f1c`; docs/current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` have generic temp publishing, no checked maintained-root `WFBE_L_GUE` owner logic, no resistance handler and blocking resistance reads; current stable `origin/master@0139a346` has owner logic plus funds-only `0` reads but no handler; B69 `origin/claude/b69@39eed5c0` adds the handler only in Chernarus. No gameplay source changed.
2026-06-22	Resistance supply scaffold, economy side-supply routes	Resistance side-supply branch matrix refresh	The page contradicted itself by saying Chernarus both had and lacked `WFBE_L_GUE` owner logic, and the B69 side-supply lane had only a compact resistance-handler note.	Preserved exact branch split on the owner page instead of duplicating in status rows: docs `e46a7330`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` have the present-side loop but no checked maintained-root `WFBE_L_GUE` mission owner logic or resistance temp handler; current stable `origin/master@0139a346` adds owner logic and a funds-only non-blocking read but no handler; B69 `origin/claude/b69@39eed5c0` adds the handler only in Chernarus. No gameplay source changed.
2026-06-22	Economy authority first cut, Economy, towns and supply, side-supply status/queue rows	Side-supply B69 current-head refresh	The side-supply clamp/reason rows were current for stable/Miksuu/perf but did not include the latest B69 head, where side-supply arithmetic and resistance handling are materially different from current stable.	Preserved exact branch proof on the existing owner matrix: docs `4db90f1c` is source-unchanged from `7047da5d9` / `f52ccee8`; current stable `origin/master@0139a346`, current Miksuu `b8389e748243` and historical `a96fdda2` remain old-shape in both maintained roots; perf `0076040f` fixes only Chernarus arithmetic; B69 `origin/claude/b69@39eed5c0` fixes Chernarus server arithmetic and adds Chernarus `wfbe_supply_temp_resistance`, but Vanilla propagation, side/channel/requester validation and reason parsing remain open. No gameplay source changed.
2026-06-22	AI commander autonomy audit, B69 roadmap, B69 sketches, B69 status/PR cleanup rows	B69 PR #49 / B72 tints-on head refresh	`origin/claude/b69` advanced from PR #48 merge head `4dcc10b143a0` to `39eed5c0` after PR #49 merged `claude/b72-tints-on` into `claude/b69`. The previous PR #48 row was still correct for B71 harvest, but current B69 routing needed the new head and tint-default caveat.	Preserved exact branch proof without duplicating every hunk: `origin/claude/b69@39eed5c0`, first parent `4dcc10b143a0`, second parent `7e1026ea`, merge commit `39eed5c02d8ba9c5a27b7a4173607526edc0677e`; `4dcc10b143a0..39eed5c0` is one Chernarus constants file / +1 / -1 with no maintained Vanilla diff, and `b8a1505f..39eed5c0` is 22 files / +699 / -91. No gameplay source changed.
2026-06-22	Current PR #1 supply helicopters, Economy, towns and supply	Supply mission economy/PR current-stable follow-up	The concurrent supply-scan refresh made the architecture matrix current, but the PR #1 page and economy overview still mixed older stable/release wording with current stable supply-heli/cash-run evidence.	Preserved exact routing without gameplay edits: PR #1 is closed/unmerged and no live origin supply/heli feature head was found; current stable `origin/master@0139a346` is the live supply-heli/cash-run baseline; docs/source `15563691`, current Miksuu `b8389e748243` and perf `0076040f` remain truck-only.
2026-06-22	Supply mission scan narrowing, Supply mission architecture, supply authority/status/queue rows	Supply scan current-stable refresh	Several scan rows still mixed older `89ae9dad` / `cf2a6d6a` / live-release wording, making current stable look broad-scan or release evidence look live.	Preserved one branch matrix instead of creating a new page: docs `15563691` truck-only typed scan at `supplyMissionStarted.sqf:25,28,44`; current stable `origin/master@0139a346` heli-aware typed scan at `:7,55,61,83`; direct current Miksuu `b8389e748243` and perf `0076040f` broad-enumerate/post-filter at `:25,28,44`; historical `a96fdda2` / `7ff18c49` release-line evidence only. No gameplay source changed.
2026-06-22	Gear template profile filter, Gear/loadout/EASA, gear profile/template status and queue rows	Gear template profile current-head refresh	The profile/template pages and machine rows already had the right branch split, but still used the 2026-06-21 docs-head anchor after current docs advanced to `72b5f0de98f9`.	Preserved exact branch proof without gameplay edits: docs `72b5f0de98f9` is source-unchanged from `43c3ba05` for checked template paths and still keeps undefined `_u_upgrade` plus `Init_ProfileGear.sqf:17,25` in both maintained roots; current stable `origin/master@0139a3468609` fixes only the save-filter comparisons; current Miksuu `b8389e748243`, perf `0076040f8a5e`, historical release `a96fdda28087` and historical EASA QoL `a66d46912e2a` remain old-shape; no live origin release/gear/template heads were found.
2026-06-22	Marker cleanup/restoration, empty supply-truck status and queue rows	Empty supply-truck timeout current-stable refresh	The empty supply-truck cleanup row still cited older `cf2a6d6a` stable evidence and live release wording after current stable and the wiki mirror advanced.	Preserved exact branch proof without gameplay edits: docs head `b4e10b5f`, current stable `origin/master@0139a346`, direct current Miksuu `master@b8389e748243`, perf `0076040f`, B69 `0094647d` and B69 finalpieces `80d3267c` all keep the collector drain and supply-truck `_delay = 86400` in both maintained roots. Current origin exposes no live `release/*` or cleanup/supply feature heads; historical `a96fdda2` matches the same 24-hour policy, but is not current release proof.
2026-06-22	AI commander autonomy audit, B69 roadmap, B69 sketches, B69 status/PR cleanup rows	B69 PR #47 merged-head refresh	`origin/claude/b69` advanced from `0a1ccb4d05c5` to merge commit `0094647d7b64` after PR #47 merged `claude/b69-finalpieces` into `claude/b69`. The previous finalpieces row correctly captured the branch while PR #47 was open, but current routing needed the merged-head status.	Preserved exact branch proof without duplicating every hunk: `origin/claude/b69@0094647d7b64`, first parent `0a1ccb4d05c5`, second parent `80d3267c1b2b`, merge commit `0094647d7b641bb79202e77e7f480d6d39aadcdb`; `0a1ccb4d05c5..0094647d7b64` is 8 Chernarus AI commander/client files / +242 / -13 with no maintained Vanilla diff, and `b8a1505f..0094647d7b64` is 17 files / +659 / -78. No gameplay source changed.
2026-06-22	Service menu affordability guards, Gear/loadout/EASA, service/EASA status, queue and hardening rows	Service/EASA affordability current-stable refresh	The service affordability rows still mixed older `89ae9dad`/release evidence with current stable `origin/master@0139a346`, and needed to consume the same corrected Miksuu-head provenance established by the `d9506078` correction lane.	Preserved exact branch proof without changing gameplay source: docs `HEAD@9b3fc38e` remains source-unchanged from `8b71e2a1`, current Miksuu upstream `master@b8389e748243`, perf `0076040f` and historical EASA QoL `a66d4691` keep old direct service rearm/refuel debit shape plus strict EASA `_funds > price`; current stable `origin/master@0139a346`, local checkpoint `d9506078` and historical release `a96fdda2` partially guard service rearm/refuel but leave repair/heal positive-price-only and strict EASA; B69 finalpieces changes exact-funds EASA only in Chernarus while maintained Vanilla remains strict. No gameplay source changed.
2026-06-22	Cargo-loop, auto-wall, visible-parameter and LoadoutManager root-discovery rows	Miksuu current-head `d9506078` provenance correction	Several 2026-06-22 rows treated local `d9506078` as current Miksuu after a local fetch/ref mixup. Direct `git ls-remote https://github.com/miksuu/a2waspwarfare.git refs/heads/master` verified current upstream as `b8389e748243`; `d9506078` is only contained by local `origin/claude/*` branches unless a future direct upstream fetch changes that.	Preserved exact branch distinction without creating new owner pages: current Miksuu `b8389e748243` is old-shape for cargo loops, auto-wall false default/no exclusions, visible AI/cleanup parameter readers and LoadoutManager ancestor-name-only root discovery. Current stable `origin/master@0139a346` remains separate source-present/fixed evidence where documented. No gameplay source changed.
2026-06-22	Respawn/death lifecycle, MASH status/PV/support rows	MASH marker current-stable branch refresh	The canonical MASH split and dependent rows still cited older stable/release wording, and two gateway pages still made current stable look like it kept the old relay path.	Preserved exact branch proof without creating a new page: docs head `db3015f18ea3`, Miksuu `b8389e748243` and perf `0076040f8a5e` keep local deploy plus orphaned marker relay in both maintained roots; current stable `origin/master@0139a3468609`, historical `a96fdda28087`, B69 `0a1ccb4d05c5` and finalpieces `80d3267c1b2b` remove the maintained-root deploy/module path and keep `Skill_Apply.sqf:43` removal wording plus residues. No gameplay source changed.
2026-06-22	Construction and CoIn salvage, salvage status/queue rows	Salvage payout current-head refresh	The salvage rows still carried 2026-06-21 current-head wording after other construction rows moved on.	Preserved exact branch proof without gameplay source edits: docs `fb8d4ebc`, current stable `0139a346`, current Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all keep lowercase `ChangePlayerfunds`, `updatesalvage.sqf:10` OR-loop and local delete/reward in both maintained roots; no live origin release/salvage heads; historical Miksuu salvage heads `99bfaeb8` / `291c6cb4` remain inherited debt.
2026-06-22	AI commander autonomy audit, B69 roadmap, B69 sketches, B69 status/PR cleanup rows	B69 finalpieces branch refresh	`origin/claude/b69-finalpieces` advanced from the then-current B69 head and opened PR #47, but the wiki had no `b69-finalpieces` route or branch-status caveat yet. Superseded for current routing by the PR #47 merged-head row above.	Preserved exact branch proof without duplicating every hunk: `origin/claude/b69-finalpieces@80d3267c1b2b` descends from `origin/claude/b69@0a1ccb4d05c5`; `0a1ccb4d..80d3267c` is 8 Chernarus AI commander/client files / +242 / -13, no maintained Vanilla diff, and PR #47 was open as `claude/b69-finalpieces` -> `claude/b69` at that snapshot. Source-present town-punch, armed-transport and stranded-merge code is separated from default-off HC merge/top-up draft scaffolding not proven compiled/live. No gameplay source changed.
2026-06-22	Vehicle cargo equip loop bounds, Gear/loadout/EASA, cargo status/queue rows	Vehicle cargo loop current/Miksuu refresh	The cargo rows initially flattened old docs/Miksuu/EASA evidence with current stable and later misidentified local `d9506078` as current Miksuu.	Corrected branch proof without creating another page: docs branch `b2544207`, current Miksuu `b8389e748243` and historical EASA QoL `a66d4691` still carry inclusive loops at `Common_EquipVehicle.sqf:27,33,39` and `Common_EquipBackpack.sqf:35,41` in both maintained roots; current stable `origin/master@0139a346` and historical release `a96fdda2` fix all five loops in both maintained roots; perf `0076040f` fixes Chernarus only. No gameplay source changed.
2026-06-22	Construction logic list cleanup, Construction and CoIn systems, construction status/queue rows	Construction SmallSite logic current-stable refresh	The SmallSite logic-list rows still cited old stable `origin/master cf2a6d6a` evidence after current stable and B69 branch status moved on.	Preserved exact branch proof without repeating the implementation walkthrough: docs `3406ffa0`, current stable `origin/master@0139a346`, Miksuu `b8389e74`, perf `0076040f`, historical release `a96fdda2` and active B69 `0a1ccb4d` all keep SmallSite add/add at `Construction_SmallSite.sqf:70,99` while MediumSite removes at `Construction_MediumSite.sqf:70,114` in both maintained roots. The canonical patch remains one SmallSite add-to-remove edit plus Vanilla propagation and Arma construction smoke. No gameplay source changed.
2026-06-22	Town AI vehicle despawn safety, Feature status, Source fix propagation queue, current-source/upstream routing and hardening rows	Town AI despawn current-stable refresh	Town-AI safety/status rows still cited stable `origin/master cf2a6d6a` and some upstream/snapshot rows still presented the `89ae9dad` persistence helper as current evidence after current stable had advanced to `origin/master@0139a346`.	Preserved exact branch proof without gameplay source edits: current stable `0139a346` still deletes tracked vehicles at `server_town_ai.sqf:309` without a crew guard; Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2` and `origin/feat/aicom-fleet-improvements@cc5090bed4ad` remain unsafe; B69 `origin/claude/b69@0a1ccb4d` has a Chernarus candidate guard at `:325` while maintained Vanilla remains unsafe at `:319`. The `89ae9dad` persistence helper is now explicitly historical/branch-only.
2026-06-22	Dead/stale code register, Feature status, Abandoned feature revival	Dead-code TaskSystem/map-blink current-stable refresh	The old TaskSystem and old map-blink rows still flattened docs/Miksuu/perf residue with current stable and older release wording, making it look like current stable still carried the same old plural marker comments and helper file state.	Preserved the branch split: docs checkout `3406ffa0`, Miksuu `b8389e74` and perf `0076040f` keep old TaskSystem comments plus `Client_TaskSystem.sqf` and old plural/server map-blink comments; current stable `origin/master@0139a346` keeps only TaskSystem comment residue while `Client_TaskSystem.sqf` is absent, sends Objective Ping separately via `GUI_Menu_Command.sqf:336,344`, and has removed the old plural/server map-blink comments while preserving live singular `Client_BlinkMapIcon`. Historical `a96fdda2` keeps TaskSystem helper/comment residue plus Objective Ping sends but not the old plural/server map-blink comments. No gameplay source changed.
2026-06-22	Dead/stale code register, AI supply-truck dead-code row	Dead-code AI supply-truck current-stable refresh	The SQF reachability row still cited current `origin/master cf2a6d6a` for the AI supply-truck safe-disable after the AI supply-truck owner/status rows had already moved to `origin/master@0139a346`.	Preserved the latest branch split without reopening gameplay code: docs checkout still comments the compile at `Init_Server.sqf:36` but raw-spawns at `:382-383`; current stable `origin/master@0139a346` comments at `:43` and warning-disables at `:462-463`; `origin/perf/quick-wins@0076040f` still raw-spawns; historical `a96fdda2` safe-disables; historical `c20ce153` guards Chernarus only; `AI_UpdateSupplyTruck.sqf:17` still points at missing `Server/FSM/supplytruck.fsm`. No gameplay source changed.
2026-06-22	Towns, camps and capture, camp flag status/queue rows	Camp flag texture current-stable refresh	The camp flag rows still cited stale stable `origin/master cf2a6d6a` evidence after current stable line drift and new branch refs changed the useful merge guidance.	Preserved exact branch proof without duplicating the full matrix: docs branch `28a7d9c5` and Miksuu `b8389e74` still use old-owner independent-capture flag textures; `perf/quick-wins@0076040f` fixes Chernarus only; current stable `origin/master@0139a346`, historical `a96fdda2`, B69 `origin/claude/b69@0a1ccb4d` and `origin/feat/naval-hvt-objectives@2e1c5931` fix independent capture in both maintained roots. Repair-side flag refresh remains open everywhere checked, with current-stable `repair-camp` line drift at `Server_HandleSpecial.sqf:468,471`. No gameplay source changed.
2026-06-22	Towns, camps and capture, camp-count status/queue rows	Camp-count helper current-stable refresh	The camp-count helper rows still cited stale stable `origin/master cf2a6d6a` evidence and one owner-page current-stable line drift cell pointed at older release-style `Client_GetRespawnAvailable.sqf:56` / Buy Units `:119-120` anchors.	Preserved exact branch proof without duplicating the matrix: docs branch `ade4d356`, current stable `origin/master@0139a346`, Miksuu `b8389e74`, perf `0076040f`, historical `a96fdda2` and active B69 `origin/claude/b69@0a1ccb4d` all keep the helper fallback at `Common_GetTotalCamps.sqf:10` and `Common_GetTotalCampsOnSide.sqf:16`. Current-stable consumers are now anchored to `server_town.sqf:167-183`, `Client_GetRespawnAvailable.sqf:92` and `GUI_Menu_BuyUnits.sqf:120-121`; future work remains real-count versus safe-denominator semantics plus 0/partial/all-camp smoke. No gameplay source changed.
2026-06-22	AI commander autonomy audit, Upgrades and research, AI commander upgrade status/queue rows	AI upgrade debit current-stable resolution refresh	The AI upgrade debit/cost rows still described current stable as debit-fixed but cost-index-open after `origin/master@0139a346` gained the maintained-root current-level lookup and corrected debit shape.	Preserved exact branch proof: docs branch `ade4d356`, Miksuu `b8389e74` and perf `0076040f` still keep raw AI-order lookup plus swapped debit at `Server_AI_Com_Upgrade.sqf:27,47,50`; current stable resolves both maintained roots at `:75,125,136` with funds-fallback surcharge at `:131-132`; historical `a96fdda2`/`b061c905` fix debit only, and `c20ce153` is Chernarus-only. Current origin exposes no matching release/feature heads. No gameplay source changed.
2026-06-22	AI commander autonomy audit, B69 roadmap, B69 sketches, Feature status	B69 current-head branch refresh	`origin/claude/b69` advanced from the documented Patch A/A-2 head `edb9f776` to `0a1ccb4d`, adding multiple hardening and QoL/FX files; leaving the old row as current would hide branch drift.	Preserved exact current scope: `b8a1505f..0a1ccb4d` is 13 files / +417 / -65, all Chernarus current mission plus `B69-IMPLEMENTATION-PLAN.md`; `edb9f776..0a1ccb4d` is 11 Chernarus files / +316 / -57; maintained Vanilla diff is empty and no PR exists for `claude/b69` on 2026-06-22. Routed detail through the B69 audit and roadmap instead of duplicating every hunk in Feature Status. No gameplay source changed.
2026-06-22	Server authority migration map, PVF dispatch implementation, Networking and public variables, Feature status, PVF machine rows	PVF sender-auth current-stable refresh	DR-55 rows still mixed older value-only/`Call Compile` docs evidence with current stable's namespace/CODE dispatcher lookup, making it too easy to read dispatch lookup as sender-auth closure.	Preserved exact branch proof: docs `HEAD@ade4d356`, Miksuu `b8389e74` and perf `0076040f` keep value-only PVEHs plus `Call Compile` dispatchers; current stable `origin/master@0139a346` and B69 `0a1ccb4d` remove dispatch-time compile but still forward only the PVEH value tuple. Future work remains authenticated requester context plus per-handler side/role/funds/object re-derivation, not another broad PVF rediscovery pass. No gameplay source changed.
2026-06-22	AI commander autonomy audit, Abandoned feature revival, AI supply-truck status/queue rows	AI supply-truck current-stable anchor split	The supply-truck rows still cited `origin/master cf2a6d6a` and sometimes said "current source" for the safe-disable, flattening the docs branch raw-spawn checkout with current stable.	Preserved exact branch proof: docs branch `ea0e0f1b`, Miksuu `b8389e74` and perf `0076040f` still raw-spawn the commented/missing worker; current stable `origin/master@0139a346` safe-disables at `Init_Server.sqf:43,462-463`; historical `a96fdda2` has the older safe-disable line shape; historical `c20ce153` guards only Chernarus. Current origin exposes no `release/*` or `feat/ai-commander` heads. No gameplay source changed.
2026-06-22	Client UI systems atlas, fast-travel status/queue rows	Fast-travel fee current-stable branch refresh	The fast-travel matrix and machine rows still carried older stable refs and line anchors, making current stable look like it still had the completed fee-policy TODO.	Preserved exact branch proof: current stable `origin/master@0139a346` keeps paid-mode local UX/debit behavior in both maintained roots but has no TODO (`GUI_Menu_Tactical.sqf:185,195-196,215,403-404`; constants `Init_CommonConstants.sqf:388,398-400`). Docs `a489e6ff`, Miksuu `b8389e74`, perf `0076040f` and historical `a96fdda2` keep the old TODO at `GUI_Menu_Tactical.sqf:147` and the same fee/debit shape with line drift. Routed future work to policy/recheck/smoke, not current-stable TODO removal. No gameplay source changed.
2026-06-22	AI commander autonomy audit, B69 roadmap, B69 sketches, Feature status	B69 Patch A-2 capture-interrupt status refresh	`origin/claude/b69` advanced from the documented `35547c47` Patch A head to `edb9f776`, so the wiki's "capture interrupt not implemented" caveat had become stale.	Preserved exact branch scope: `35547c47..edb9f776` is one Chernarus `Common_RunCommanderTeam.sqf` diff, +16 / -1, adding order-sequence checks and capture-loop aborts; `b8a1505f..edb9f776` remains Chernarus-only with no maintained Vanilla diff and no PR for `claude/b69`. No gameplay source changed.
2026-06-22	Economy, towns and supply, Economy authority first cut, economy status/queue rows	Resource-income current B69/B74 branch split	The resource-income rows already separated current stable from old-shape refs, but still lacked current B69/B74 proof and used older docs-branch anchors.	Preserved exact branch proof: docs/source `HEAD@c8ec223a`, Miksuu `b8389e748243`, `origin/perf/quick-wins@0076040f` and historical `a96fdda2` keep AI commander funds inside the cap guard; current stable still guards side supply/team paychecks but has the AI commander fallback at `updateresources.sqf:102-109`; B69 `8d465fce` and B74 `b23f557f` are identical for checked income files, adding fallback at `:115-121`, Chernarus hybrid-refill cash checks and Chernarus supply multiplier behavior while maintained Vanilla stays raw-supply/non-hybrid. Routed full branch proof through Economy, towns and supply and kept income-system `4` display drift open. No gameplay source changed.
2026-06-22	Construction and CoIn systems, Feature status, Source fix propagation queue, auto-wall machine rows	Auto-wall current-stable scope refresh	The auto-wall global-toggle rows still cited stale stable `cf2a6d6a` evidence, then later misidentified local `d9506078` as current Miksuu.	Corrected branch proof without reopening gameplay code: docs branch `origin/docs/developer-wiki-index@89aadf8c`, current Miksuu `b8389e748243` and perf `0076040f` keep the old false-default/no-exclusion global at SmallSite `:110` / MediumSite `:125`; current stable `origin/master@0139a346` keeps one global but defaults it true and consumes it at `:123` / `:160` with AARadar plus related exclusions; historical `a96fdda2` only adds the AARadar guard; B69 `origin/claude/b69@35547c47` matches current-stable global scope. No gameplay source changed.
2026-06-22	Client UI systems atlas, Hosted server FPS loop sleep, Performance opportunity sweep, status/debug indicator row	Status-counter audience split and hosted-FPS branch refresh	The indicator matrix still grouped player HUD FPS, compatibility FPS PVs, admin/status signals and PerformanceAudit RPT counters as one "status/debug/admin" bucket, while the performance sweep still described current `origin/master` as old-loop-shaped.	Preserved exact branch proof: docs `a27086cd` has two guarded maintained-root publishers (`SERVER_FPS_GUI` and `WFBE_VAR_SERVER_FPS`); current stable `origin/master@0139a346` and historical `a96fdda2` use one guarded `SERVER_FPS_GUI` publisher; Miksuu `b8389e74` and perf `0076040f` keep the old two-publisher loop shape. Routed future changes by audience: player HUD, compatibility PV, admin/status signal or RPT/tooling output. No gameplay source changed.
2026-06-22	AI commander autonomy audit, B69 roadmap, B69 sketches, Feature status	B69 Patch A branch-status refresh	A new `origin/claude/b69@35547c47` branch head exists after the B69 planning/sketch pages were published, so the docs needed to stop treating all B69 material as sketches while also avoiding overclaiming unfinished pieces.	Preserved exact branch scope: `b8a1505f..35547c47` is Chernarus-only Patch A code for HQ-strike order/gate/picker, no maintained Vanilla diff, no PR for `claude/b69`, and capture interrupt is only a constant until `Common_RunCommanderTeam.sqf` gets executor logic. No gameplay source changed.
2026-06-22	Mission parameters, Mission start parameters, Dead/stale code, Player AI caps, parameter status rows	Visible-parameter current-stable branch split	Several pages still described `WFBE_C_AI_MAX` and `WFBE_C_UNITS_CLEAN_TIMEOUT` as current no-op/comment-only parameter cleanup after current stable gained live readers, then later misidentified local `d9506078` as current Miksuu.	Corrected branch proof: docs branch `origin/docs/developer-wiki-index@ac932fbe`, current Miksuu `b8389e748243`, `origin/perf/quick-wins@0076040f` and historical release `a96fdda2` keep the old readless/comment-only shape; current stable `origin/master@0139a346` reads `WFBE_C_AI_MAX` at `AI_Commander_Produce.sqf:89` and `WFBE_C_UNITS_CLEAN_TIMEOUT` at `Common_TrashObject.sqf:21` in both maintained roots. Player follower caps still use `WFBE_C_PLAYERS_AI_MAX`; body, wreck and empty-vehicle cleanup stay separate. No gameplay source changed.
2026-06-22	AI commander B69 roadmap, AI commander implementation sketches, AI commander autonomy audit, `agent-context.json`	B69 route follow-up plus stale AICOM no-loop correction	The mirror/routing B69 lanes landed first, but Home/agent-context still needed the B69 route and the autonomy audit/machine context still repeated older no-active-loop wording that current stable source no longer supports.	Routed the B69 pages from Home and machine context, preserved B69 as branch/live-Chernarus planning evidence, and corrected current stable evidence: `origin/master@0139a346` compiles/spawns `WFBE_SE_FNC_AI_Commander` in both maintained roots at `Init_Server.sqf:64,847`, sets/clears `wfbe_aicom_running` at `AI_Commander.sqf:127,253` and calls the upgrade worker at `:161`. No gameplay source changed.
2026-06-22	AI commander autonomy audit, LLM agent entry pack, B69 AI commander docs	B69 routing follow-up	The B69 pages were mirrored and sidebar-linked, but the canonical AI commander owner page and AI/headless task bundle still routed agents only through older autonomy/HC pages.	Added a compact B69 route that points to the roadmap and sketches while preserving the caveat that B69 is live-B68 planning/sketch evidence, not `origin/master` or maintained Vanilla proof. No gameplay source changed.
2026-06-22	`docs/wiki` mirror, B69 AI commander docs	Mirror-only sync	Live wiki `master@3be04f1` had the B69 AI commander roadmap/sketch pages and sidebar routing while repo mirror `origin/docs/developer-wiki-index@77b38d07` missed two top-level pages and had a stale `_Sidebar.md`.	Mirrored AI Commander B69 implementation sketches, AI Commander B69 improvement roadmap, `_Sidebar.md` and coordination records into `docs/wiki`; preserved the source-backed page content unchanged. No gameplay source changed.
2026-06-21	Gear template profile filter, Gear/loadout/EASA, gear status/machine rows	Gear template current-stable branch split	The profile-template pages and machine rows flattened old docs/source evidence with current stable and contradicted whether `_u_upgrade` was still broken on master.	Preserved exact branch proof: docs `43c3ba05` is source-unchanged from `8b71e2a1` and still carries `_u_upgrade` at `Client_UI_Gear_SaveTemplateProfile.sqf:33,52,75`; current stable `origin/master@0139a346` fixes the save-filter comparison at `:34,57,82` but keeps `Init_ProfileGear.sqf:17,25` import-bound debt and the AddTemplate/FillTemplates policy split. Miksuu/perf/historical release/QoL old-shape evidence stays branch-scoped. No gameplay source changed.
2026-06-21	Commander reassignment call shape, Feature status, Source fix propagation queue	Commander reassignment current-stable closeout without duplicating commander vote context	The reassignment owner page and status rows still described the DR-15 helper unpacking as a current-source patch everywhere, after the commander vote closeout had already shown current stable `origin/master@0139a346` fixed the maintained-root helper shape.	Preserved branch split with exact scope: current stable Chernarus and maintained Vanilla unpack `_side = _this select 0` / `_commander = _this select 1` at `Server_AssignNewCommander.sqf:4-5`; docs branch `b44aaaf8` and current stable full modded Napf/Eden/Lingor forks still carry `_side = _this`; duplicate `new-commander-assigned` senders, visible-name UI targeting and requester authority remain open. No gameplay source changed.
2026-06-21	Factory and purchase systems, Feature status, Source fix propagation queue, factory hardening rows	Factory refund current-stable branch refresh	The destroyed-purchase refund matrix still mixed old `origin/master@cf2a6d6a` and live release/QoL head wording after current stable advanced to `origin/master@0139a346` and current origin exposed no `release/*` or `feat/buymenu-easa-qol` heads.	Preserved exact branch proof: docs branch `ebd86fad0` is source-unchanged from `8d611092` for checked buy/build paths and remains old-shape; current stable refunds the dead/null factory abort at `Client_BuildUnit.sqf:276-280`; historical `a96fdda2` carries the same dead/null refund at `:212-216`; intermediate `7ff18c49` only refunded the empty/crewless branch and is superseded; Miksuu, perf and historical QoL `a66d4691` remain old-shape. No gameplay source changed.
2026-06-21	Economy authority first cut, Feature status, Source fix propagation queue, side-supply machine rows	Side-supply current-stable refresh without reopening broad economy prose	The side-supply clamp/reason rows still used older `origin/master@cf2a6d6a` and release-head wording, while current stable is `origin/master@0139a346` and current origin exposes no `release/*` heads.	Preserved exact branch proof: docs branch `7047da5d9` is source-unchanged from `f52ccee8` for checked side-supply/reason paths; current stable and Miksuu keep `_currentSupply - _amount` at `Common_ChangeSideSupply.sqf:25` and `Server_ChangeSideSupply.sqf:12,36` plus payload-side trust in both maintained roots; `origin/perf/quick-wins@0076040f` fixes only the Chernarus arithmetic floor. Vanilla propagation, side/channel/requester validation and reason parsing remain open. No gameplay source changed.
2026-06-21	Towns/camps/capture, AI/runtime Patrols routes and live machine rows	Patrols v2 current-stable refresh	The Patrols v2 matrix/status rows still named `origin/master@cf2a6d6a`, old line refs and live release-branch wording after fetched stable advanced to `origin/master@0139a346`; docs branch `d30d23466` remains source-unchanged for checked Patrols paths.	Preserved old DR-57/AI1 evidence as historical branch scope, refreshed current stable anchors for `WFBE_UP_PATROLS = 23`, side caps, `server_side_patrols.sqf`, `Common_RunSidePatrol.sqf`, `Server_HandleSpecial.sqf`, `updatepatrolmarkers.sqf` and `server_patrols.sqf:31`, and kept `a96fdda2` as historical release evidence because current origin exposes no `release/*` heads. No gameplay source changed.
2026-06-21	`docs/wiki` mirror, Headless client init and stat loop, Home, _Sidebar, `agent-context.json`	Mirror live HC reference instead of rewriting it	Live wiki `master@e03c3bf` added the HC init/stat-loop reference and routed it from Home/sidebar/agent context, while repo mirror `docs/developer-wiki-index@f81ec4145` still missed the page and three routing updates.	Preserved the existing source-stamped page unchanged, copied the four wiki files into `docs/wiki`, and recorded the mirror-only lane in dashboard/worklog/events. No gameplay source changed.
2026-06-21	AI commander audit, Map marker catalog, Feature status, PR cleanup lab	PR #43 / B68 live branch route without duplicating the worklog	Claude's B68 live deployment note was detailed but not yet routed through canonical branch/status pages, and PR #43 head metadata had advanced to `b8a1505f`.	Preserved exact branch evidence: PR #43 is open from `claude/b57-soak-proposals` to `master`, head `b8a1505f8a89881f487a03262f066c8b33eca94d`; B68 changes four Chernarus files, removes the W17 global Supply Convoy marker route at `AI_Commander_Wildcard.sqf:994`, adds/tunes AICOM controls at `Init_CommonConstants.sqf:277-284,319`, `AI_Commander_Strategy.sqf:41-68,99,441,571-590` and `AI_Commander_Produce.sqf:90-151`; current `origin/master@0139a346` still creates the W17 global marker at `AI_Commander_Wildcard.sqf:981-984`. No gameplay source changed.
2026-06-21	Support specials, Upgrades and research, `upgrade-sync` status rows	Current-stable tuple-cleanup refresh without broad upgrade re-audit	The `upgrade-sync` matrix still used older `origin/master@cf2a6d6a` stable evidence and live release/upgrade-queue branch wording, while current stable has advanced to `origin/master@0139a346` and current origin exposes no `release/*` or `feat/upgrade-queue-stacking` heads.	Preserved `ff8dd884` as docs/source line-anchor proof because checked handler/caller/process-upgrade paths are unchanged through `docs/developer-wiki-index@ad05401a3`; refreshed current stable refs for the mixed `_args` / `_this` parser at `Server_HandleSpecial.sqf:67-73`, caller `GUI_UpgradeMenu.sqf:292` and sync lifecycle `Server_ProcessUpgrade.sqf:32,35,41`; routed `a96fdda2` and `b061c905` as historical evidence. No gameplay source changed.
2026-06-21	Commander vote/reassignment, Feature status, Source fix propagation queue	Commander vote current-stable closeout	The commander vote playbook and status row still treated the old DR-47 `_highest >= _aiVotes
2026-06-21	Source fix propagation queue	Current-stable scope refresh without duplicating owner pages	The queue's current branch section still mixed older `cf2a6d6a` stable/release wording with checked docs-source state after stable advanced to `origin/master@0139a346` and current origin stopped advertising `release/*` heads.	Preserved `4bd37b98` as line-anchor proof because the checked queue source paths are unchanged through `docs/developer-wiki-index@d30d23466`; added current stable line refs for queue PVFs/paratrooper registration, `Skill_Init`/apply, one guarded FPS publisher, heli-aware supply scan, marker-based commander ARTY and Patrols v2 `Server/FSM` paths; kept supply player-list indexing docs-only and routed `a96fdda2` as historical release evidence. No gameplay source changed.
2026-06-21	Attack-wave authority, Feature status, Source fix propagation queue, Public variable channel index, Server authority migration map	Attack-wave current-stable refresh	The attack-wave matrix and status rows still called older `origin/master@cf2a6d6a` stable evidence current and treated `a96fdda2` / `c20ce153` as live branch heads.	Preserved the branch split with current proof: current stable `origin/master@0139a346` Chernarus and maintained Vanilla still trust client `_supply` / `_side` and direct detail payloads at `Common_AttackWaveActivate.sqf:6,8`, `Server_AttackWave.sqf:5-6,15,23,27,36,38` and `AttackWave.sqf:19,23-25,40`; Miksuu `b8389e74`, perf `0076040f`, historical `c20ce153`, historical `a96fdda2` and historical `994150da` stay unrescued branch evidence. No gameplay source changed.
2026-06-21	Victory/endgame atlas, Feature status, Source fix propagation queue, victory hardening machine rows	Victory/endgame current-stable branch refresh	The owner/status rows still used older `origin/master@cf2a6d6a` and release-head wording, while current stable `origin/master@0139a346` changed the logger/WASPSTAT shape and current origin exposes no `release/*` heads.	Preserved branch-specific proof instead of flattening the finding: docs/Miksuu/perf/historical `a96fdda2` keep the older opposite-side logger block at `server_victory_threeway.sqf:23-41`, where all-towns wins log the loser; current stable adds the HQ nil/null skip at `:18-22`, keeps the mixed condition at `:29`, writes WASPSTAT `_x` at `:41-46` and logs `[_x]` at `:49`, so HQ/factory eliminations still log the loser and the guard/side-loop exit remain open. `origin/claude/b57-soak-proposals@b8a1505f` is recorded as Chernarus-only live-support evidence, not stable or Vanilla propagation. No gameplay source changed.
2026-06-21	Construction and CoIn systems, salvage/status owner rows	Salvage current-stable branch refresh	The salvage payout/loop matrix still named older stable `cf2a6d6a` and release-head wording while current fetched stable is `origin/master@0139a346` and current origin exposes no `release/*` heads.	Preserved evidence by refreshing the salvage branch matrix, Feature status, Source fix propagation queue and machine rows: docs checkout `10097961`, stable `origin/master@0139a346`, Miksuu `b8389e74`, perf `0076040f` and historical release commit `a96fdda2` all keep lowercase `ChangePlayerfunds`, the `updatesalvage.sqf:10` `
2026-06-21	Hardening roadmap, Pending owner decisions, Server authority migration map	PVF dispatcher cross-link follow-up	The PVF owner pages were refreshed for current stable, but these routing pages still framed dispatcher hardening as replacing current-stable `Call Compile`.	Preserved the current branch split: current stable `origin/master@0139a346` already uses `missionNamespace getVariable` plus a `CODE` guard at `Server_HandlePVF.sqf:14-15` / `Client_HandlePVF.sqf:32-33`; remaining current-stable work is explicit registered-handler membership and forged-name rejection before `Spawn _code`. No gameplay source changed.
2026-06-21	Public variable channel index, Networking and public variables, Feature status, Source fix propagation queue	SEND_MESSAGE current-stable evidence refresh	The DR-46 branch matrix still called `cf2a6d6a` current stable and treated a deleted release head as current proof, even though fetched `origin/master` is `0139a346` and current origin advertises no `release/*` heads.	Preserved the P0 direct-channel RCE finding with exact current refs: docs head `16247fc8f`, stable `origin/master@0139a346`, Miksuu `upstream/master@b8389e74`, `origin/perf/quick-wins@0076040f`, unchanged receiver/helper paths from `1e16527b` and `cf2a6d6a`, and historical-only release `a96fdda2` wording. No gameplay source changed.
2026-06-21	PVF dispatch implementation, Networking/PV, Public variable channel index, Feature status, Source fix propagation queue	Current-stable PVF dispatch partial-closeout follow-up	The first current-stable closeout fixed the main owner/status pages, but follow-up source checks added exact blame, corrected current registry counts and made the no-`release/*` head scope explicit.	Preserved exact branch evidence: current stable Chernarus and maintained Vanilla use `missionNamespace getVariable _script` plus `CODE` guards at `Server_HandlePVF.sqf:14-15` and `Client_HandlePVF.sqf:32-33`; Chernarus blame is `7d60b02b4`, maintained Vanilla propagation is `9b49883cb`; `Init_PublicVariables.sqf:55-61` still lacks registered-handler allowlists/logging; Miksuu `b8389e74` and perf `0076040f` still use `Spawn (Call Compile _script)`; current origin has no `release/*` heads. No gameplay source changed.
2026-06-21	WASP marker wait cleanup, WASP overlay, Performance opportunity sweep, Source fix propagation queue	WASP marker wait current-head refresh	The WASP marker wait page still named older `89ae9dad` / `7ff18c49` branch evidence and the old `Init_Client.sqf:279` launch line, while current stable `origin/master@0139a346` moved the helper launch and current origin exposes no `release/*` heads.	Preserved the open cleanup but corrected current evidence: current stable Chernarus and maintained Vanilla still keep the display-54 busy wait at `global_marking_monitor.sqf:57,62,65,69-70`, display-12 throttling at `:81` and helper launch at `Client/Init/Init_Client.sqf:309`; Miksuu `b8389e74` and perf `0076040f` remain unrescued with line drift. No gameplay source changed.
2026-06-21	Map boundaries and off-map enforcement	Current-head refresh of one historical source stamp	The cf2 source-stamp caveat correctly prevented overclaiming, but this compact page could be rechecked directly against current `origin/master@0139a346`.	Replaced the historical caveat with current-head wording, updated shifted line anchors and clarified `Server/Init/Init_Towns.sqf` for town distribution. This reduces one page from the 38-page recheck backlog without duplicating boundary behavior elsewhere. No gameplay source changed.
2026-06-21	PVF dispatch implementation, Networking and public variables, Public variable channel index, Feature status, Source fix propagation queue	PVF dispatcher current-stable closeout	The PVF dispatcher pages still treated current stable `origin/master@cf2a6d6a` as dispatching registered handlers through `Call Compile`, but current `origin/master@0139a346` has moved both maintained roots to namespace+`CODE` lookup.	Preserved old docs/perf/Miksuu/release branch evidence while correcting current stable: Chernarus and maintained Vanilla use `missionNamespace getVariable` at `Server_HandlePVF.sqf:14-15` and `Client_HandlePVF.sqf:32-33`, no `PVF_ALLOWED` allowlist exists, current stable still has direct `SEND_MESSAGE` compile at receiver/helper lines, and DR-55 sender authentication remains open. No gameplay source changed.
2026-06-21	Commander/HQ lifecycle, Feature status, Source fix propagation queue	HQ score current stable refresh	The DR-50 matrix still called older `origin/master@cf2a6d6a` stable evidence current after the fetched stable branch had advanced to `0139a346`, leaving Feature Status and Source Fix queue with stale current-head wording.	Preserved older docs/Miksuu/perf/release/feat-ai rows as branch-scoped history while adding current `origin/master@0139a346` proof: both maintained roots still award generic HQ building score at `Server/Functions/Server_OnHQKilled.sqf:52/54`, then award `_score = 900` again at `:86` under the non-teamkill guard, with coefficient `3` at `Init_CommonConstants.sqf:529`. No gameplay source changed.
2026-06-21	Dead/stale code register, `ICBM_launched` PVEH row	Branch-scope evidence refresh	The row still cited a release branch as current branch proof even though current origin exposes no `release/*` heads, and it did not name exact checked docs/stable/Miksuu/perf refs or current nuke-route line drift.	Preserved the receiver-only finding with exact refs: docs head `4c01dfb`, stable `origin/master@0139a346`, Miksuu `upstream/master@b8389e74`, `origin/perf/quick-wins@0076040f`, no sender hits, current `RequestSpecial "ICBM"` / `HandleSpecial "icbm-display"` route and a retire-vs-revive owner-decision handoff. No gameplay source changed.
2026-06-21	PR cleanup and integration lab, dashboard/current-lane routing	Current PR board closure refresh	2026-06-21 GitHub metadata returned only `3` open PRs (`#43`, `#40`, `#9`), while the old AICOM deploy umbrella PR `#35` and deploy-child PR `#34` / `#36`-`#39` / `#41` are closed and PR `#29` / `#31` merged on 2026-06-17. Leaving the old deploy lane active would misroute future reviewers.	Preserved the closed AICOM deploy stack as historical review evidence, routed live PR-board work through PR `#43`, PR `#40` and PR `#9`, and removed the stale active dashboard lane. No gameplay source changed.
2026-06-21	Client UI systems atlas, Feature status, Source fix propagation queue	ClickableText soundPush current stable closeout	The clickable-text matrix still described current `origin/master@cf2a6d6a` as carrying malformed `RscClickableText.soundPush[]`, but current stable had advanced to `0139a346` where both maintained roots now carry the valid empty-sound value.	Preserved the branch history while correcting current state: Chernarus `Rsc/Ressources.hpp:556` is fixed by `1a5e0b40`, maintained Vanilla `:556` by `9b49883c`, current master derives 14 controls per root at refreshed `Rsc/Dialogs.hpp` refs, and older docs/source, Miksuu, perf, release and UI theme evidence stays branch-scoped until rechecked or merged. No gameplay source changed.
2026-06-21	`docs/wiki` mirror, GUER Insurgents branch audit, Feature status, Gameplay systems atlas	Mirror sync plus stale GUER audit correction	The broad mirror sync made the repo mirror match live wiki `master@743daf4` and removed the docs-only GUER audit, then `cf2-source-stamp-current-head-caveat` advanced the wiki to `e4fc668`. The GUER page still held useful branch-intake evidence, but its Chernarus-only/Takistan-dormant wording was stale against current `origin/master@0139a346`.	Restored the GUER audit as a current-source page after rebasing over `master@e4fc668`, and rewrote the status against `origin/master@0139a346`: `9af83596` is merged and both maintained roots carry the GUER gate, overlay, economy loop, VBIED action/handler and buy/service hooks. Runtime smoke remains separate. No gameplay source changed.
2026-06-21	Source fix propagation queue, docs branch source anchor	Docs-head source-scope note instead of row rewrite	The mirror sync advanced `docs/developer-wiki-index` to `4c01dfb7`, but the queue's branch rows still correctly use `4bd37b98` as line-anchor proof. Rewriting every row would create churn without changing source evidence.	Added one compact 2026-06-21 docs-source refresh note and updated the Agent Index fact after confirming the queue's checked propagation source paths are unchanged from `4bd37b98` to `4c01dfb7`. No gameplay source changed.
2026-06-21	38 source-stamped reference pages, Player skill abilities	Historical source-stamp caveat instead of current-head rewrite	Current fetched `origin/master` is `0139a346`, while the broad page stamp still called ancestor `cf2a6d6a4` simply `master`. Rechecking every cited path would be a larger source-refresh lane, but leaving the wording as current master would overstate the evidence.	Preserved the `cf2a6d6a4` verification as then-current/historical master evidence, added a current-head recheck caveat to all 38 headers and changed the Player Skill Officer/MASH note to snapshot wording. No gameplay source changed.
2026-06-21	`docs/wiki` mirror, GitHub wiki checkout	Current wiki mirror sync	Fresh comparison found `116` normalized top-level differences between live wiki `master@743daf4` and repo mirror branch `origin/docs/developer-wiki-index@11f535d9`, mostly newer wiki pages missing from the mirror.	Mirrored the current top-level wiki files into `docs/wiki`, removed mirror-only `GUER-Insurgents-Branch-Audit.md`, and kept the human wiki as the source baseline for this batch. Validation is recorded in `agent-events.jsonl`. No gameplay source changed.
2026-06-21	QoL trio player hints, Experimental feature flags / Player UI routes	New canonical page instead of scattered consumer notes	Existing wiki coverage listed `WFBE_C_QOL_TRIO` and consumer line refs but did not own the live player-visible hint behavior.	Preserved detailed source evidence on QoL trio player hints, then linked compact routes from Home, _Sidebar, Player UI workflow, Experimental feature-flag constants and `agent-context.json`. No gameplay source changed.
2026-06-21	Modules atlas, `Client/Module/Engines`	Promoted thin module paragraph into a focused reference page	Existing wiki coverage for `Engine.sqf`, `Startengine.sqf` and `Stopengine.sqf` was only a compact Modules Atlas paragraph, old audit rows and file indexes; that was too thin for the action/EH/fuel/refuel behavior and one atlas line ref had drifted.	Added Engine stealth fuel toggle, routed Modules Atlas/Home/sidebar/function index/agent context there, and left the atlas as a compact route with current `Client_BuildUnit.sqf:417-418`, `Init_Server.sqf:521-522` and `Init_Server.sqf:539-540` anchors. No gameplay source changed.
2026-06-21	Skin selector and class swap, player UI/WASP routes	New canonical page instead of scattered notes	Existing wiki coverage mentioned the Skin Selector only as an earplugs/action-restoration return path, while current source has a default-off gate, dialog, per-side class pools, class-swap apply chain and respawn persistence. Repeating those details in UI, WASP and Skill pages would bloat the route pages.	Preserved detailed source evidence on Skin selector and class swap, then linked compact routes from Home, _Sidebar, Player UI workflow, Player skill abilities, WASP overlay, Feature status and `agent-context.json`. No gameplay source changed.
2026-06-16	Gameplay systems atlas, Feature status, Testing workflow	GUER branch intake without a new page	Brain had a source-checked `origin/feat/guer-insurgents-faction` handoff ready after the mirror sync lane closed. A standalone page would duplicate branch-review machinery for one broad feature branch.	Preserved the detailed branch evidence as a compact matrix on Gameplay systems atlas, added a single Feature Status row, and added planned smoke gates to the branch-only smoke pack plus machine release ledger. No gameplay source changed.
2026-06-16	PR cleanup and integration lab, AICOM/Experital PR board	Current-state PR board refresh	The page still described the 2026-06-05 board with PR #8 and PR #14 as open candidates, while 2026-06-16 GitHub metadata shows both merged and the current open AICOM/Experital work has moved to PR #29/#30/#34-#41 with PR #35 as the deploy umbrella.	Preserved older PR8 ancestry and lab history, refreshed the current board, recommendation, AICOM stack table, triage rows, cleanup actions, Discord summary and validation note. No gameplay source changed.
2026-06-16	`docs/wiki` mirror, GitHub wiki checkout	Wiki mirror current wiki sync	The standalone human wiki had advanced to `origin/master@3745638`, while the repo mirror on `docs/developer-wiki-index@e2d994246` still differed on `35` top-level files by SHA256. Leaving the mirror stale would make future agents read old coordination/status pages.	Mirrored the current top-level wiki files into `docs/wiki` without gameplay source edits. Preserved the human wiki as the source baseline, kept Latest Batch compact and validated JSON/JSONL, wiki validation, `git diff --check` and wiki/docs normalized-content parity after the copy.
2026-06-14	Client UI systems atlas, UI/Rsc source-scope route	Client UI atlas current source-scope route prune	The UI atlas still named `a03a1fb5` as its visible docs checkpoint after later docs-only atlas batches, even though the checked UI/Rsc source paths had not changed.	Preserved source evidence by naming current docs head `68bd4dc5`, confirming checked Chernarus and maintained Vanilla `description.ext`, `Rsc`, `Client/GUI`, `Init_Client.sqf`, `Client_UpdateRHUD.sqf`, client action/marker FSMs and core UI helper paths are unchanged from `a03a1fb5` and `b5219d47` through `HEAD`, and keeping earlier `a71b42fe`, `2fef1e3d` and `f7bc72a8` as source-anchor provenance. Branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f`, `wf-menu-ops-console` `0767c0b5` and BuyMenu/EASA QoL `a66d4691` still resolve. The atlas stays route-first; detailed resource parity, title-handle, vote/help/router, clickable-text and branch-only UI behavior route to owner pages. No gameplay source changed.
2026-06-14	Server runtime and operations, server-runtime source-scope route	Server runtime operations current source-scope route prune	The server-runtime gateway still named `a6785f51` as its visible docs checkpoint after later docs-only atlas batches, even though the checked runtime source paths had not changed.	Preserved source evidence by naming current docs head `f74b3822`, confirming checked Chernarus and maintained Vanilla `Init_Server.sqf`, server FSM/module paths, `Server_SideMessage.sqf`, `Server_OnHQKilled.sqf` and server-FPS publisher paths are unchanged from `a6785f51` and `4277a2ad` through `HEAD`, and keeping earlier `92c5cf05` / `6afcc58e` as source-anchor provenance. Branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f` still resolve. The gateway stays short; branch-sensitive AI supply-truck startup, Patrols v2 and FPS publisher cleanup route to Server gameplay runtime atlas. No gameplay source changed.
2026-06-14	Architecture overview, top-level architecture source-scope route	Architecture overview current source-scope route prune	The top-level architecture gateway still named `adb9dbc8` as its visible docs checkpoint after later docs-only atlas batches, even though the cited runtime and tooling source paths had not changed.	Preserved source evidence by naming current docs head `2de2de92`, confirming cited runtime/bootstrap/tooling paths are unchanged from `adb9dbc8` and `4277a2ad` through `HEAD`, and keeping earlier `1bef8801` / `1aa178f8` as source-anchor provenance. Branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f` still resolve. The overview remains a gateway; branch behavior, line drift and smoke gates route to SQF code atlas, Mission entrypoints and lifecycle, Lifecycle wait-chain, Tools and build workflow, Source fix propagation queue and subsystem owner pages. No gameplay source changed.
2026-06-14	SQF code atlas, compile/PVF source-scope route	SQF atlas current source-scope route prune	The SQF atlas still named `34212d6a` as its visible docs checkpoint after later docs-only batches, and the PVF contract repeated no-drift wording already owned by the compile summary and networking/channel owner pages.	Preserved source evidence by naming current docs head `94b09c73`, keeping the original `04a60e43` compile-count snapshot as provenance, rerunning the count command (`738` total, `460` `preprocessFileLineNumbers`, `278` plain, `22` commented), confirming checked Chernarus and maintained Vanilla SQF/PVF/init paths are unchanged from `34212d6a` and `4277a2ad` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Routed repeated PVF proof back to the compile summary, Public variable channel index, Networking and public variables and PVF dispatch implementation, while adding explicit dispatcher anchors for `Server_HandlePVF.sqf:14` and `Client_HandlePVF.sqf:22`. No gameplay source changed.
2026-06-14	Networking and public variables, PVF/direct-channel gateway route	Networking/PV gateway source-scope route prune	The networking gateway still named `4277a2ad` as its visible docs checkpoint after later docs-only batches, and its `Call Compile` security section repeated the same source-continuity proof already stated in Current Branch Scope.	Preserved source evidence by naming current docs head `1e16527b`, confirming checked Chernarus and maintained Vanilla network, PVF and direct-channel paths are unchanged from `4277a2ad` through `HEAD`, and keeping branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Routed repeated dispatch proof back to Current Branch Scope, Public variable channel index, PVF dispatch implementation and Server authority migration map. No gameplay source changed.
2026-06-14	Marker cleanup/restoration, empty supply-truck timeout proof route	Marker cleanup atlas source-scope route prune	The marker/cleanup atlas still named `634a907b` as its visible source checkpoint after later docs-only batches, and the same empty supply-truck 24-hour timeout proof was repeated in the atlas top scope, patch-ready row, Feature Status and Source Fix queue.	Preserved source evidence by naming current docs head `7eea6b6c`, confirming checked Chernarus and maintained Vanilla marker, cleaner, restorer and empty-vehicle paths are unchanged from `634a907b` through `HEAD`, and keeping branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Routed repeated proof back to Empty Supply Truck Branch Matrix while aligning Feature status and Source fix propagation queue. No gameplay source changed.
2026-06-14	Gear, loadout and EASA atlas, gear/EASA branch-proof route	Gear/EASA atlas source-scope route prune	The gear atlas still named `8b71e2a1` as its visible docs checkpoint and repeated profile-template, import-guard, cargo-loop and EASA/Economy IDD branch proof in risk rows, while Feature Status also carried detailed branch text already preserved by owner pages.	Preserved source evidence by naming current docs head `3fdf1898`, confirming checked Chernarus, maintained Vanilla and `Tools/LoadoutManager` gear/EASA paths are unchanged from `8b71e2a1` through `HEAD`, and keeping branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f` and BuyMenu/EASA QoL `a66d4691`. Routed repeated branch proof back to Current Branch Scope, Gear template profile filter, Vehicle cargo equip loop bounds, Service menu affordability guards, UI IDD collision repair and BuyMenu EASA QoL branch audit, while aligning Feature status. No gameplay source changed.
2026-06-14	Construction and CoIn systems, construction/CoIn branch-proof route	Construction/CoIn atlas source-scope route prune	The construction atlas still named `4bd37b98` as its visible source checkpoint and repeated auto-wall, SmallSite, StationaryDefense and salvage branch proof inside multiple local sections and risk rows, even though the atlas Current Branch Scope and dedicated cleanup pages already preserve that evidence.	Preserved source evidence by naming current docs head `7d248610`, confirming checked Chernarus and maintained Vanilla construction/CoIn, base-area, structure-config, commander ARTY and salvage paths are unchanged from `4bd37b98` and `1aa178f8` through `HEAD`, and keeping branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Routed repeated branch proof back to Current Branch Scope, Construction logic list cleanup, Source fix propagation queue and the local salvage matrix while aligning Feature status. No gameplay source changed.
2026-06-14	Mission entrypoints and lifecycle, Lifecycle wait-chain, boot/source-scope route	Lifecycle entrypoints / wait-chain source-scope route prune	The paired lifecycle architecture pages still named `9da5f1d0` as their visible source checkpoint after several docs-only atlas batches landed, and the wait-chain page repeated branch-scope wording already owned by the entrypoints Source Scope.	Preserved source evidence by naming current docs head `05664f17`, confirming checked Chernarus bootstrap, mission-object town init, common/server/client/headless init and HC role-helper paths are unchanged from `9da5f1d0` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Routed duplicated branch-scope wording from Lifecycle wait-chain back to Mission entrypoints and lifecycle. No gameplay source changed.
2026-06-14	Respawn and death lifecycle, MASH local respawn and marker-relay route	Respawn lifecycle atlas source-scope route prune	The respawn atlas was linked from the function/module and module routes but did not expose a top source-scope checkpoint, while MASH risk rows repeated source anchors already preserved by the atlas MASH split matrix. Feature Status also still named `1f0b9018` as the visible docs checkpoint for MASH.	Preserved source evidence by naming current docs head `a640e722`, confirming checked Chernarus and maintained Vanilla respawn, MASH, skill, camp/threeway and AI-respawn paths are unchanged from `1f0b9018` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Updated the MASH docs-head row and routed duplicate risk-row source detail back to MASH split, while aligning Feature status. No gameplay source changed.
2026-06-14	Modules atlas, module init and dormant-module route	Modules atlas current-scope route prune	The module atlas still named `20a19676` as its visible docs checkpoint after newer source-family routes pointed developers there. That left the Reaktiv table and page header looking older than the current docs head even though checked module source paths had not moved.	Preserved source evidence by naming current docs head `86244c24`, confirming checked Chernarus common/client/server init, unit-creation, module folders and paratrooper support paths are unchanged from `20a19676` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Updated the Reaktiv dormant-module table to current docs head while keeping exact branch matrices routed to owner pages except for that compact local module table. No gameplay source changed.
2026-06-14	Function and module index, module/source-family routes	Function/module index route prune	The function index still named `1f0b9018` as its visible checkout and repeated branch-sensitive commander DR-15, Reaktiv, MASH and paratrooper proof already preserved by owner pages. That made a source-family locator behave like a second patch-status page.	Preserved source evidence by naming current docs head `6ecac3ae`, confirming checked Chernarus common/client/server init, commander helper, AI upgrade, MASH, Reaktiv and paratrooper support paths are unchanged from `1f0b9018` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Replaced repeated local branch proof with routes to Commander reassignment call shape, Commander vote/reassignment, Modules atlas, Respawn and death lifecycle, Source fix propagation queue and Paratrooper marker revival. No gameplay source changed.
2026-06-14	Gameplay systems atlas, gameplay gateway branch/source routes	Gameplay systems atlas route prune	The broad gameplay gateway still named `ca40f202` as its visible docs checkpoint and repeated branch-sensitive DR-15, Patrols v2, latent `AIBuyUnit` and victory/endgame proof that narrower owner pages already preserve. That made a quick orientation page behave like a second branch-status register.	Preserved source evidence by naming current docs head `2d88dd5a`, confirming checked Chernarus town, town-AI/patrol, economy, commander, construction, factory and victory paths are unchanged from `ca40f202` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Replaced repeated local branch proof with routes to Commander reassignment call shape, Towns/camps/capture, AI runtime/HC loop map, Factory and purchase systems atlas and Victory/endgame atlas. No gameplay source changed.
2026-06-14	Victory/endgame atlas, stale logger and server-init cleanup routes	Victory/endgame atlas route prune	The victory atlas still named `2f2132f8` as the visible docs checkpoint and repeated stale `LogGameEnd` plus server-init duplicate-bind branch proof already preserved on cleanup owner pages. It also had no compact Source Fix queue row for the patch-ready winner/double-fire fix.	Preserved source evidence by naming current docs head `a0a86da2`, confirming checked Chernarus victory constants, victory loop, live/stale loggers and server-init bind paths are unchanged from `2f2132f8` through `HEAD`, and keeping branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Replaced repeated stale logger/init-bind branch proof with routes to Dead/stale code register and Server init bind cleanup, while adding the victory/endgame patch-ready implementation route to Source fix propagation queue. No gameplay source changed.
2026-06-14	Commander/HQ lifecycle, commander vote/reassignment and HQ score routes	Commander/HQ atlas route prune	The HQ lifecycle atlas still named `f82a9127` as the visible docs checkpoint and repeated manual-reassignment helper proof that the vote/reassignment playbook and call-shape owner page already preserve. That made the HQ gateway behave like a second reassignment matrix instead of a lifecycle map.	Preserved source evidence by naming current docs head `8c3942d2`, confirming checked Chernarus and maintained Vanilla commander vote, reassignment, HQ score, disconnect, task and base-area/HQ authority paths are unchanged from `f82a9127`/`e2c9f6ed` through `HEAD`, and keeping branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f` and AI commander `c20ce153`. Replaced repeated local reassignment proof with routes to Commander reassignment call shape, Commander vote/reassignment, Feature status and Source fix propagation queue, while adding missing commander-disconnect and HQ build/base-area source anchors. No gameplay source changed.
2026-06-14	Towns, camps and capture, camp flag / zero-camp helper / Patrols v2 routes	Towns/camps atlas route prune	The towns atlas already owned the right branch matrix but still named `3eefcb00` as the visible docs checkpoint and repeated camp-flag plus zero-camp helper branch detail in section prose, risk rows and status rows. That made the owner page read like multiple local copies of the same matrix.	Preserved source evidence by naming current docs head `5243f91d`, confirming checked Chernarus and maintained Vanilla town init, town/camp AI loops, camp helpers, respawn, buy-menu and patrol paths are unchanged from `3eefcb00` through `HEAD`, and keeping branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f` and AI commander `c20ce153`. Replaced repeated local branch proof with routes to Current Branch Scope, Feature status and Source fix propagation queue; Patrols v2 source-present/smoke-pending routing remains on the atlas and AI runtime pages. No gameplay source changed.
2026-06-14	Support specials and tactical modules, `RequestSpecial` / support authority / branch-only support routes	Support specials authority route prune	The support atlas still named `ff8dd884` as the visible current checkpoint and repeated broad `RequestSpecial` authority scout detail that the Server Authority, ICBM, Service, AI Commander, Client UI, Feature Status and Testing pages already own. That made a support gateway double as a second authority migration map.	Preserved source evidence by naming current docs head `6c919abf`, confirming checked Chernarus and maintained Vanilla Tactical UI, `RequestSpecial`, artillery, UAV/Nuke/Zeta/MASH, AAR/ordnance, para-ammo and Rsc parameter paths are unchanged from `ff8dd884` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f`, upgrade queue `b061c905`, drone strike `8ca4be90` and recon UAV `563418ea`. Replaced repeated support-authority and transport proof with routes to Server authority migration map, ICBM authority, Service menu affordability guards, AI commander autonomy, Client UI systems, Feature status and Testing workflow. No gameplay source changed.
2026-06-14	Economy, towns and supply, side-supply / supply-mission / AI economy routes	Economy/supply atlas route prune	The economy atlas still named `8a6695b8` as the visible current checkpoint and repeated branch proof already owned by economy authority, supply mission architecture, AI commander and upgrades pages. That made an economy gateway double as a branch-status page.	Preserved source evidence by naming current docs head `8cb43e4e`, confirming checked Chernarus and maintained Vanilla economy/supply constants, resource loop, income display, supply mission, side-supply helper, AI upgrade, kill-bounty and stringtable paths are unchanged from `8a6695b8` and `6d05cb5a` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. Replaced repeated local branch proof with routes to Economy authority first cut, Supply mission architecture, AI commander autonomy and Upgrades and research. No gameplay source changed.
2026-06-14	Upgrades and research atlas, AI debit / `upgrade-sync` / stale dialog routes	Upgrades atlas route prune	The upgrades atlas still named `d4cfef80` as the visible current checkpoint after later docs-only batches and repeated branch proof already owned by the AI commander, support-specials and UI resource pages. That made the atlas behave like a second branch-status register instead of a quick upgrade-system map.	Preserved source evidence by naming current docs head `1b07716d`, confirming checked Chernarus and maintained Vanilla upgrade UI/server/config/Rsc paths are unchanged from `d4cfef80` through `HEAD`, and preserving branch refs for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f`, AI commander `c20ce153` and upgrade queue `b061c905`. Replaced repeated local branch proof with routes to AI upgrade debit matrix, upgrade-sync matrix and UI resource parity cleanup. No gameplay source changed.
2026-06-14	Factory and purchase systems atlas, buy-menu/refund/queue routes	Factory purchase atlas route prune	The factory atlas still named `8d611092` as the visible current checkpoint and repeated buy-menu price/key plus destroyed-factory refund branch detail in section prose and the risk table, even though the detailed matrices on the same owner page and the factory queue playbook already preserve that proof.	Preserved source evidence by naming current docs head `3b911594`, confirming checked Chernarus and maintained Vanilla factory/purchase source paths are unchanged from `8d611092` through `HEAD`, and preserving the branch matrices for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f` and BuyMenu/EASA QoL `a66d4691`. Replaced repeated local branch proof with routes to buy-menu price and driver-key branch matrix, destroyed-factory refund branch matrix and Factory queue cleanup. No gameplay source changed.
2026-06-14	AI, headless and performance, AI runtime/HC loop map, server-FPS route	AI/headless gateway FPS route prune	The broad AI gateway still named `ee383941` as the visible current checkpoint and repeated server-FPS publisher branch detail that the server runtime and hosted-FPS owner pages already preserve. The runtime loop map also still told smoke readers to expect "both FPS publishers" even though stable/release use a single-publisher shape.	Preserved source evidence by naming current docs head `ca028bff`, confirming checked Chernarus and maintained Vanilla mission source paths are unchanged from `b9e80da0` and `ee383941` through `HEAD`, and keeping AI supply-truck, Patrols v2 and town-AI vehicle risk routes on owner pages. Replaced local server-FPS detail with routes to Server gameplay runtime atlas, Hosted server FPS loop sleep, Performance opportunity sweep, Testing workflow and Source fix propagation queue. No gameplay source changed.
2026-06-14	Client UI systems atlas, branch-only UI theme/QoL routes	Client UI atlas branch route prune	The atlas still repeated branch-only UI theme and BuyMenu/EASA QoL branch detail that owner pages already preserve, and it still named `b5219d47` as the visible current checkpoint after a later docs-only head landed. That made a navigation atlas behave like a second branch-promotion register.	Preserved source evidence by naming current docs head `a03a1fb5` and confirming checked Chernarus and maintained Vanilla UI/Rsc paths are unchanged from `b5219d47` through `HEAD`: `Rsc`, `Client/GUI`, `Init_Client.sqf`, `Client_UpdateRHUD.sqf` and `updateavailableactions.fsm`. Kept compact local branch routes in Client UI systems atlas, and routed exact `origin/feat/wf-menu-ops-console` / `origin/feat/buymenu-easa-qol` promotion detail to Feature status, Pending owner decisions, Testing workflow and BuyMenu/EASA QoL branch audit. No gameplay source changed.
2026-06-14	Architecture overview, generated/tooling route	Architecture overview tooling route prune	The overview still named `4277a2ad` as the visible current checkpoint and repeated LoadoutManager branch/root-discovery details that the tooling pages already preserve. That made the architecture gateway behave like a second propagation/tooling matrix.	Preserved source evidence by naming current docs head `adb9dbc8` and confirming checked overview runtime/tooling paths are unchanged from `4277a2ad` through `HEAD`: `description.ext`, `initJIPCompatible.sqf`, Common/Server/Client/Headless init, `FileManager.cs`, `SqfFileGenerator.cs` and `ZipManager.cs`. Kept compact local anchors in Architecture overview, and routed branch matrices plus operational rules to Tools/build workflow, Source fix propagation queue and Mission config/version include graph. No gameplay source changed.
2026-06-14	Server gameplay runtime atlas, Server runtime and operations	Server runtime gateway route prune	The server runtime atlas carried the same branch-sensitive FPS, AI supply-truck and Patrols v2 facts in both the branch-scope table and the runtime-risk table, while the operations gateway still pointed at the older `4277a2ad` source-continuity checkpoint.	Preserved source evidence by naming current docs head `a6785f51` and confirming checked server runtime paths are unchanged from `4277a2ad` through `HEAD`: `Init_Server.sqf`, `Server/FSM`, `Server/Module`, `Server_SideMessage.sqf`, `Server_OnHQKilled.sqf` and `serverFpsGUI.sqf`. Kept exact startup/branch proof in Server gameplay runtime atlas, Hosted server FPS loop sleep, AI commander autonomy, Towns/camps/capture and SQF code atlas. No gameplay source changed.
2026-06-14	SQF code atlas, compile/PVF/deferred-signal routes	SQF atlas compile route prune	The SQF atlas was already shorter after the registered-PVF table removal, but it still repeated branch-specific PVF registry, attack-wave, `LogGameEnd`, supply-truck and FPS details that owner pages already preserve. That made the atlas behave like a second branch-status register instead of a compile ownership map.	Preserved source evidence by naming current docs head `34212d6a`, confirming checked PVF/server/client/common-init and AI supply-truck paths are unchanged from `4277a2ad`, and keeping exact local anchors for `Init_PublicVariables.sqf`, `Init_Server.sqf`, `Init_Client.sqf`, `Init_Common.sqf` and `AI_UpdateSupplyTruck.sqf`. Routed registry counts to Public variable channel index, direct attack-wave proof to Attack-wave authority, duplicate `LogGameEnd` bind status to Server init bind cleanup, AI logistics to AI commander autonomy, FPS publisher status to Hosted server FPS loop sleep, and dead/dormant helpers to Abandoned feature revival plus Dead/stale code register. No gameplay source changed.
2026-06-14	Networking and public variables, Public variable channel index	Networking/PV gateway prune route	The networking gateway still carried old ad-hoc PVF command inventories and repeated dispatcher, post-dispatch authority and attack-wave proof that canonical owner pages already preserve. That made developers read the same source evidence twice before finding the implementation owner.	Preserved evidence by keeping Networking as the transport/trust-boundary gateway and retaining its unique registered client PVF runtime matrix. Routed command/channel inventory to Public variable channel index, dispatcher patch shape to PVF dispatch implementation, post-dispatch handler authority to Server authority migration map, and direct attack-wave proof to Attack-wave authority. Checked source files are unchanged from `4277a2ad` through `aa1a4b76`; no gameplay source changed.
2026-06-14	Client UI systems atlas, UI resource parity cleanup, UI IDD collision repair, Feature status, Source fix propagation queue	Client UI atlas continuity route	The UI atlas and linked UI-resource/status rows still named older docs-checkout hashes as visible current source anchors after later docs-only batches landed. That was accurate provenance but slowed readers trying to tell whether current docs head changed the cited UI/Rsc paths.	Preserved evidence by naming current docs checkout `b5219d47`, recording that checked UI/Rsc paths are unchanged from earlier UI snapshots (`a71b42fe`, `2fef1e3d`, `f7bc72a8`), and keeping detailed branch behavior routed through UI resource, IDD, vote/help/router and clickable-text owner sections for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. No gameplay source changed.
2026-06-14	Architecture overview, SQF code atlas, Server gameplay runtime atlas, Server runtime and operations, Networking/public variables	Architecture/SQF anchor continuity route	Several gateway pages still named older docs-checkout hashes as the visible current source anchor after later docs-only batches landed. That is accurate as provenance but slows developers trying to understand whether the current docs head changed the cited source paths.	Preserved evidence by naming current docs checkout `4277a2ad`, recording that checked architecture/SQF/server/network source paths are unchanged from earlier anchor snapshots (`1bef8801`, `8701aacc`, `92c5cf05`, `59deb306`, `6afcc58e`, `04a60e43` as applicable), and keeping detailed branch behavior routed to owner pages for stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`. No gameplay source changed.
2026-06-14	Feature status, Source fix propagation queue, client UI/economy machine rows	Client UI economy/fast-travel status route	Two status rows still carried older `89ae9dad` / `7ff18c49` branch wording after the UI parity batch: Economy release Vanilla was documented as stale even though current stable/release repair both maintained roots, and fast-travel fee UX still cited old branch heads.	Preserved evidence by naming docs checkout `d2a3f995`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`; routing Economy controller parity to UI resource parity cleanup and Tactical fee UX to Client UI systems; updating `agent-feature-status.jsonl` without changing gameplay source.
2026-06-14	Client UI systems atlas, UI resource parity cleanup, UI IDD collision repair	Client UI title/resource current-branch route	The UI atlas and parity pages still mixed older stable/release truth with current branch heads: stable and release now fix stale upgrade/Economy/EASA dialog resources in both maintained roots, while the title IDD and shared display-handle risks remain open everywhere.	Preserved evidence by naming docs checkout `2fef1e3d`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`; routing resource parity to UI resource parity cleanup, detailed title/handle patch shape to UI IDD collision repair, and updating Feature status, Source fix propagation queue plus machine rows without changing gameplay source.
2026-06-14	SQF code atlas, Networking/public variables	SQF/network branch caveat route	Two gateway caveats were stale enough to misroute readers: SQF still said the `UpdateSupplyTruck` branch matrix was needed, and Networking still framed supply-heli mechanics as PR-only even after stable/release carried the source shape.	Preserved evidence by naming docs checkout `8701aacc` source-continuity checks, routing `UpdateSupplyTruck` to AI commander autonomy, and documenting supply-heli as stable/release-present but docs/Miksuu/perf truck-only with deeper mechanics routed to Supply mission architecture and Economy, towns and supply. No gameplay source changed.
2026-06-14	Client skill init idempotency, client-init status rows	Client skill init current-branch route	The owner page and machine row still mixed older stable/release truth with current branch heads, saying stable duplicated `Skill_Init` after stable and release had advanced to single-init shapes.	Preserved evidence by naming docs checkout `719455a2`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f` and `feat/ai-commander` `c20ce153`; documenting docs/stable/release as single-init plus later apply in both maintained roots; leaving Miksuu/perf/feat-ai open; and aligning Feature status, `agent-feature-status.jsonl` and `agent-context.json` without duplicating broader performance guidance. No gameplay source changed.
2026-06-14	SQF code atlas, Public variable channel index, Networking/public variables	SQF PVF registry route	The SQF atlas still carried copied registered-command tables and missed branch-sensitive PVF registry drift: docs checkout has 13 server / 15 client commands, stable/release add queue PVFs, and paratrooper registration differs on Miksuu/perf/AI-commander.	Removed the duplicated registered-command tables from the SQF atlas, made Public variable channel index the canonical registry owner, and aligned the Networking gateway. Preserved source evidence for docs checkout `40c97e74`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f` and `feat/ai-commander` `c20ce153`. No gameplay source changed.
2026-06-14	PR cleanup lab, release workflow/status rows	PR8 release current-branch route	PR8/release docs still mixed older `7195b331` / `7ff18c49` current-head wording with the fetched release head `a96fdda2`, and one machine row still said stable/release lacked commander-built ARTY even though current stable/release use marker-based discovery.	Preserved evidence by naming release `a96fdda2`, stable `cf2a6d6a`, current release commander ARTY anchors `Construction_StationaryDefense.sqf:132-135` plus `Common_GetTeamArtillery.sqf:46-78`, delegated town-AI update-back anchors `Client_DelegateTownAI.sqf:29-44` plus `Server_HandleSpecial.sqf:86-115`, and static-defense HC update-back still commented at `Client_DelegateAIStaticDefence.sqf:27-30`; aligned Testing workflow, Feature status and `agent-release-readiness.json` without duplicating the full release matrix across gateway pages. No gameplay source changed.
2026-06-14	Economy authority first cut, economy authority/status rows	Economy authority current-branch route	The economy authority page and linked status rows still cited older `89ae9dad` / `7ff18c49` branch evidence for side-supply clamp, reason-string and resource-income drift after stable/release advanced.	Preserved evidence by naming docs checkout `f52ccee8`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`; documenting that docs/stable/release/Miksuu still keep the side-supply overspend-as-credit floor, direct temp-channel payload trust and reason-string off-by-one in both maintained roots; keeping perf scoped to the Chernarus arithmetic floor only; and aligning Feature status, Source fix propagation queue plus machine rows without duplicating the full economy atlas. No gameplay source changed.
2026-06-14	Hosted server FPS loop sleep, hosted-FPS status and machine rows	Hosted FPS current-branch route	The hosted-FPS owner page and status rows mixed old release/stable wording with the current branch shape: docs/source now has two guarded publishers, stable/release have one guarded publisher with the monitor removed, and Miksuu/perf still have the old unguarded two-loop shape.	Preserved evidence by adding a current branch matrix for docs checkout `db7667c9`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`; keeping implementation guidance on the hosted-FPS owner page; and aligning Feature status, Pending owner decisions, release readiness and machine status rows without repeating the full branch proof in every status file. No gameplay source changed.
2026-06-14	Upgrades and research, AI commander autonomy, AI upgrade/status rows	Upgrades/research current-source route	The upgrades atlas and AI debit owner matrix still named docs checkout `e785f1e9` as the current docs/source anchor after later docs batches landed, which made current readers chase an older hash even though the cited upgrade source files were unchanged.	Preserved evidence by naming docs checkout `d4cfef80`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74`, perf `0076040f`, AI-commander `c20ce153` and upgrade-queue `b061c905`; documenting that docs-checkout upgrade files are unchanged from the `e785f1e9` anchor; and aligning Feature status plus Source fix propagation queue without duplicating the AI debit or `upgrade-sync` owner matrices. No gameplay source changed.
2026-06-14	Construction and CoIn systems, Construction logic list cleanup, construction/status rows	Construction/CoIn atlas current-source route	The construction atlas still carried older `1aa178f8` source-snapshot wording and repeated branch-scope details across auto-wall, StationaryDefense, SmallSite/MediumSite and salvage sections; linked status rows also needed the 2026-06-14 source-fix anchor.	Preserved evidence by naming docs checkout `4bd37b98`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`; keeping detailed construction branch scope on the atlas and cleanup page; routing repeated status through canonical construction/queue pages; and aligning Feature status, Source fix propagation queue and Function/module index. No gameplay source changed.
2026-06-14	Current source status snapshot, Source fix propagation queue	Current source status snapshot route	The status snapshot still preserved older 2026-06-03/05 matrices with wording that could be read as current stable/release truth, and the propagation queue overstated stable/release as carrying the supply player-list index fix.	Preserved evidence by adding a current 2026-06-14 matrix for docs checkout `76674ae4`, stable `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and perf `0076040f`; marking older matrices historical; and correcting the supply player-list index route so docs/source has `_i = 0` before the loop at `playerObjectsList.sqf:17` while stable/release/Miksuu/perf still reset it inside the loop at `:18`. No gameplay source changed.
2026-06-14	Supply mission architecture, supply/cooldown/status rows	Supply mission branch-scope route	The supply owner page still mixed older truck-only docs-source wording with newer stable/release supply-heli behavior, and its PR-vs-master section repeated stale branch-review caveats instead of routing current developers by target ref.	Preserved evidence by adding a current branch matrix for docs checkout `8a6695b8`, stable `cf2a6d6a`, Miksuu `b8389e74`, perf `0076040f` and release `a96fdda2`; replaced the stale PR-vs-master matrix with a truck-only versus stable/release supply-heli shape; refreshed Economy/Towns/Supply docs-checkout refs; and aligned supply cooldown, scan and dead-twin rows in Feature status. No gameplay source changed.
2026-06-14	Assets/config/localization/parameters atlas, generated `version.sqf` wording and parameter caveats	Assets/config parameters source-scope route	The assets/config atlas still read like an older local-source snapshot: it repeated detailed parameter caveats already owned by the mission-parameter pages and still routed through stale wording that implied local ignored `version.sqf` copies were present.	Preserved source evidence by adding a use-route table and current branch-scope note for docs checkout `85679dba`, stable `cf2a6d6a`, Miksuu `b8389e74`, perf `0076040f` and release `a96fdda2`; kept full parameter detail on Mission parameters and Mission start parameters index; corrected the generated-version contract on Mission config/version include graph, Feature status, Tools/build workflow, Coverage ledger, Hardening roadmap and Pending owner decisions. No gameplay source changed.
2026-06-14	Commander/HQ lifecycle, HQ score and commander task branch rows	Commander/HQ source-scope route	The Commander/HQ page had useful flow detail but still read like a local-source-only atlas: manual reassignment was described as universally broken, HQ score line refs mixed docs checkout with stable-master refs, and Objective Ping wording still pointed at older release-era evidence.	Preserved evidence by adding a top use-route table and current branch-scope snapshot for docs checkout `f82a9127`, stable `cf2a6d6a`, Miksuu `b8389e74`, perf `0076040f`, release `a96fdda2` and feat-ai `c20ce153`; refreshed HQ score double-award line drift, DR-15 helper branch split, Objective Ping branch split and old `TaskSystem` residue in Feature status plus Source fix propagation queue. No gameplay source changed.
2026-06-14	Support specials and tactical modules, `RequestSpecial`/artillery source anchors	Support specials source-scope route	The support/tactical gateway had a useful route table but still named older docs-checkout `e785f1e9` for `upgrade-sync` and repeated the same `RequestSpecial` dispatch/artillery path in several sections.	Preserved source evidence by adding a docs checkout `ff8dd884` source snapshot for Tactical UI, PVF transport, server special dispatch, artillery, UAV/nuke/Zeta and RU para-ammo anchors; kept deep authority on Server authority migration map, ICBM authority, Service menu affordability guards and Supply mission authority cleanup; refreshed `upgrade-sync` branch evidence for stable `cf2a6d6a`, Miksuu `b8389e74`, perf `0076040f`, release `a96fdda2` and upgrade-queue `b061c905`. No gameplay source changed.
2026-06-14	Networking/public variables, `SetTask` / Objective Ping branch wording	Networking public-variable source-scope route	The networking gateway had useful routes but did not name current docs-checkout source scope like the newer atlas pages, and its registered client `SetTask` row still used historical release `7ff18c49` wording after current release was `a96fdda2`.	Preserved source evidence by adding a docs checkout `59deb306` source-scope note and compact branch-route table, keeping full channel inventory on Public variable channel index, dispatcher patch status on PVF dispatch implementation, and server-handler authority on Server authority migration map. Corrected Objective Ping scope: docs/Miksuu/perf/feat-ai leave `SetTask` sends commented, while stable `cf2a6d6a` and release `a96fdda2` send targeted Objective Ping tasks in both maintained roots. No gameplay source changed.
2026-06-14	AI/headless/performance, AI runtime/HC loop map, Patrols v2 branch wording	AI/headless performance gateway route	The broad AI page lacked the route/source-scope pattern used by newer atlas pages and still named old `feat/ai-commander` head `4dba060e`; the AI runtime map also overstated release `a96fdda2` as carrying Patrols v2 even though release lacks the Patrols v2 files in checked maintained roots.	Preserved source evidence by adding route and branch-scope tables to the AI/headless gateway, keeping AI commander/HC/town-AI/performance matrices on owner pages, updating `feat/ai-commander` to current head `c20ce153`, and correcting Patrols v2 scope: stable `origin/master` `cf2a6d6a` carries Patrols v2 in both maintained roots; docs checkout, release, Miksuu, perf and `feat/ai-commander` do not. No gameplay source changed.
2026-06-14	Function and module index, Respawn/death lifecycle, MASH/paratrooper status rows	Function/module index source-scope route	The function index is a useful SQF source-family map but still duplicated stale module status: commander reassignment was described as universally broken, paratrooper markers as absent from the client PVF registry, and MASH/Reaktiv as current-source-only facts without current branch scope.	Preserved source evidence by adding source-scope and route tables to the function index, routing module detail to Modules atlas, Respawn and death lifecycle, Commander reassignment call shape and Source fix propagation queue. Refreshed MASH branch scope: docs/Miksuu/perf keep local MASH/orphaned marker relay, while stable `cf2a6d6a` and release `a96fdda2` remove the maintained-root deploy/module/init path. Refreshed paratrooper branch scope: docs/stable/release register both maintained roots, Miksuu omits, perf is Chernarus-only. No gameplay source changed.
2026-06-14	Architecture overview, source-scope and generated-target route	Architecture overview source-scope route	The overview was already a lean gateway but still lacked the current source-scope note pattern used by newer atlas pages, and its LoadoutManager root row could flatten docs/stable/release/Miksuu/perf branch differences.	Preserved the existing line refs by rechecking the runtime/tooling paths as unchanged from `1aa178f8` to docs checkout `1bef8801`; added a compact branch-scope table for stable `origin/master` `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and `perf/quick-wins` `0076040f`; kept detailed branch behavior routed to Current source status snapshot, Source fix propagation queue and subsystem owner pages. No gameplay source changed.
2026-06-14	Client UI systems atlas, main-menu and clickable-text UI matrices	Client UI atlas source-scope route	The Client UI atlas still named docs/source `HEAD` as `f7bc72a8` in the clickable-text matrix and treated `MenuAction 19` too broadly, which could make developers confuse docs/Miksuu/perf FPS-HUD behavior with stable/release GPS enablement.	Preserved existing line refs by rechecking the relevant UI paths as unchanged from `f7bc72a8` to docs checkout `a71b42fe`; updated the source-scope note, main-menu router row, vote/help/main-menu branch matrix and clickable-text matrix for stable `origin/master` `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and `perf/quick-wins` `0076040f`. No gameplay source changed.
2026-06-14	Server gameplay runtime atlas, Server runtime and operations	Server runtime atlas source-scope route	The server runtime gateway and atlas still named `6afcc58e` as the docs checkout source anchor, even though current docs branch is `92c5cf05`; the page also needed release/Miksuu/perf distinctions so broad server-runtime prompts do not overstate stable `origin/master` truth.	Preserved the existing line refs by rechecking the relevant server-runtime paths as unchanged from `6afcc58e` to `92c5cf05`; updated branch scope for stable `origin/master` `cf2a6d6a`, release `a96fdda2`, Miksuu `b8389e74` and `perf/quick-wins` `0076040f`; and kept detailed AI supply-truck, Patrols v2 and FPS proof routed through Server gameplay runtime atlas, AI commander autonomy and Performance opportunity sweep. No gameplay source changed.
2026-06-14	SQF code atlas, compile registry and server-init caveats	SQF atlas source snapshot route	The SQF atlas snapshot was still useful but named an older docs checkout without explaining that the mission source tree was unchanged, and its server-init caveats repeated branch-sensitive behavior already owned by server/AI pages.	Preserved the 738-reference preprocess snapshot by rechecking docs checkout `b13308ff` against `04a60e43`, fixing the regenerate command's path trim, and replacing stale duplicate-bind, `UpdateSupplyTruck` and server-FPS monitor wording with branch-specific links to Server init bind cleanup, AI commander autonomy and Server gameplay runtime atlas. No gameplay source changed.
2026-06-14	Gear/loadout/EASA atlas, gear/service/cargo status rows	Gear/EASA branch-scope route	The gear atlas had useful source maps but still lacked a current branch-scope summary, while focused gear/cargo/service owner pages and status rows preserved stale `89ae9dad` / `7ff18c49` wording after stable/release advanced.	Preserved evidence by adding a compact branch-scope table for docs checkout `8b71e2a1`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f`, release `a96fdda2` and EASA QoL `a66d4691`; kept deep patch guidance on Gear template profile filter, Vehicle cargo equip loop bounds and Service menu affordability guards; corrected cargo stable/release fixed scope and service partial-guard scope in Feature status plus Source fix propagation queue. No gameplay source changed.
2026-06-14	Victory/endgame atlas, init-bind/status rows	Victory/endgame branch-scope route	The victory atlas lacked a top route table/current branch scope and still described stale logger plus duplicate init binds as local-source-only truth, while linked status rows kept older release/stable wording.	Preserved evidence by adding a route table and current branch-scope note for docs checkout `2f2132f8`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; confirmed the default victory condition defect remains open across checked maintained roots; clarified `Server/PVFunctions/LogGameEnd.sqf` is present only on docs/Miksuu/perf and absent on stable/release; and aligned Server init bind cleanup, Feature status, Pending owner decisions, SQF code atlas and Dead/stale code. No gameplay source changed.
2026-06-14	Gameplay systems atlas, gameplay gateway routes	Gameplay systems atlas route prune	The broad gameplay atlas repeated branch-sensitive commander, HQ scoring, factory and victory details already owned by narrower pages, and still carried stale universal wording for DR-15 plus older `Server_OnHQKilled.sqf` line refs.	Preserved broad system flow by adding a top route table and branch-scope note for docs checkout `ca40f202`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; routed towns, economy, commander, upgrades, construction, factories, AI/HC, supports and victory to owner pages; corrected DR-15 to branch-split evidence; and moved HQ score/idempotency line-sensitive detail to Commander/HQ lifecycle. No gameplay source changed.
2026-06-14	Modules atlas, Dead/stale code register, Reaktiv machine rows	Modules atlas Reaktiv branch-scope route	The modules atlas opened with repeated "covered elsewhere" bullets instead of a gateway route table, and its Reaktiv/dead-code branch notes still preserved older stable/release refs after `origin/master` and release advanced.	Preserved evidence by adding a top route table and compact owner routes for ICBM/EASA/AntiStack/supply/MASH/UAV/serverFPS/AFK; refreshed the Reaktiv branch matrix for docs checkout `20a19676`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; confirmed docs/Miksuu/perf still carry unreachable maintained-root `Common/Module/Reaktiv`, stable/release have no maintained-root Reaktiv hits, and all checked refs still carry stale modded Napf/Eden/Lingor copies. No gameplay source changed.
2026-06-14	Marker cleanup/restoration, empty supply-truck status rows	Marker cleanup/restoration branch-scope route	The marker/lifecycle atlas had useful cleanup-loop coverage but no top routing map, still mixed older cleanup startup line refs with current docs source, and its empty supply-truck matrix/status rows cited older `89ae9dad` / `7ff18c49` branch heads after stable and release advanced.	Preserved evidence by adding a top route table and current branch-scope note for docs checkout `634a907b`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; updated server cleanup startup anchors to `Init_Server.sqf:528-560`; confirmed all checked Chernarus and maintained Vanilla roots still drain `emptyVehicles` via `emptyvehiclescollector.sqf:9,15-19,30` and hard-code supply-truck `_delay = 86400` at `Server_HandleEmptyVehicle.sqf:23`; aligned Feature status plus Source fix propagation queue. No gameplay source changed.
2026-06-14	Commander vote/reassignment, Commander reassignment call shape, commander/status rows	Commander vote/reassign branch-scope route	The commander playbook still read like a local-source-only page even though DR-15 helper status is branch-split, and Feature Status kept a stale "resolved on master" row beside docs-branch source-unpatched wording.	Preserved evidence by adding a top route table and current branch-scope matrix for docs checkout `e2c9f6ed`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f`, release `a96fdda2` and `feat/ai-commander` `c20ce153`; confirmed vote AI/no-commander semantics remain unpatched everywhere checked; routed DR-15 helper truth to Commander reassignment call shape; aligned Feature status plus Source fix propagation queue; and refreshed Objective Ping current-head wording. No gameplay source changed.
2026-06-13	AI runtime and HC loop map, Town AI vehicle despawn safety, AI/town status rows	AI runtime/HC branch-scope route	The AI runtime page had useful loop coverage but no top route table, still repeated AI supply-truck detail already owned by the AI commander audit, and status rows preserved older `89ae9dad` persistent-defense helper evidence as if it were current branch truth.	Preserved evidence by adding a top route table and current branch-scope matrix for docs checkout `b9e80da0`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f`, release `a96fdda2` and `feat/ai-commander` `c20ce153`; routed AI supply-truck detail to AI commander autonomy; refreshed Town AI vehicle despawn safety; and aligned Feature status plus Source fix propagation queue. No gameplay source changed.
2026-06-13	Towns, camps and capture, town/status owner pages	Towns/camps atlas branch-scope route	The towns atlas had useful Patrols v2 coverage, but camp flag and camp helper sections still mixed older `89ae9dad` / `7ff18c49` current-head wording with newer stable/release source, and the page lacked a top route table for developers choosing between town capture, camp repair, helpers and patrols.	Preserved evidence by adding a top route table and current branch-scope matrix for docs checkout `3eefcb00`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; separated stable/release independent camp-capture flag fixes from still-open repair-side flag refresh; refreshed zero-camp helper consumer line drift; and aligned Feature status plus Source fix propagation queue. No gameplay source changed.
2026-06-13	Upgrades and research, upgrade/status owner pages	Upgrades research atlas branch-scope route	The upgrades atlas had useful source maps but no top route table, repeated AI commander and `upgrade-sync` explanations already owned by narrower pages, and still carried stale branch-status wording for AI debit and the abandoned old upgrade dialog.	Preserved evidence by adding a top route table and current branch-scope matrix for docs checkout `e785f1e9`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f`, release `a96fdda2`, `origin/feat/ai-commander` `c20ce153` and `origin/feat/upgrade-queue-stacking` `b061c905`; routed AI debit detail to AI commander autonomy and `upgrade-sync` detail to Support specials; refreshed stale old upgrade dialog scope and aligned Feature status plus Source fix propagation queue. No gameplay source changed.
2026-06-13	Factory and purchase systems, factory/status owner pages	Factory purchase atlas branch-scope route	The factory atlas still had stale price/key and destroyed-factory refund branch matrices, no top route table, and status rows that repeated old `89ae9dad` / `7ff18c49` conclusions after stable/release advanced.	Preserved evidence by adding a top route table and current branch-scope matrix for docs checkout `8d611092`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f`, release `a96fdda2` and `origin/feat/buymenu-easa-qol` `a66d4691`; split stable/release selected-detail/key/refund fixes from docs/Miksuu/perf old-shape debt; kept the still-open level-0 `UNIT_COST_MODIFIER` reset on the owner matrix; and refreshed factory rows in Feature status plus Source fix propagation queue. No gameplay source changed.
2026-06-13	Construction and CoIn systems, construction/status owner pages	Construction atlas branch-scope route	The construction atlas had source-backed findings but no top route table, and several construction rows still used older branch hashes for auto-wall, salvage and commander ARTY behavior.	Preserved evidence by adding a top route table and current branch-scope matrix for docs checkout `1aa178f8`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; split docs-checkout commander-team ARTY/null-guard evidence from stable/release marker-based ARTY and Miksuu/perf older `DefenseTeam` shape; refreshed auto-wall, SmallSite/MediumSite and salvage routes in Feature status and Source fix propagation queue. No gameplay source changed.
2026-06-13	Economy, towns and supply, AI commander autonomy audit, economy/supply owner pages	Economy atlas branch-scope route	The economy atlas still used older branch refs and repeated supply-mission details that now differ by current branch; its AI commander debit route also pointed into an owner matrix that still named older current-head refs.	Preserved evidence by adding a top route table and current branch-scope matrix for docs checkout `6d05cb5a`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; refreshed resource-income anchors; split truck-only versus stable/release heli/cash-run reward flow; and aligned the AI commander upgrade debit matrix while keeping side-supply and supply authority routed to Economy authority first cut and Supply mission architecture. No gameplay source changed.
2026-06-13	Source fix propagation queue, propagated-fix owner pages	Source-fix queue branch-scope refresh	The queue still presented older `89ae9dad` / `7ff18c49` branch notes as current-root discovery and propagated-fix truth, even after stable `origin/master` and release advanced.	Preserved evidence by adding a top branch-scope table for docs checkout `56d2f856`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; updating LoadoutManager root discovery; and separating docs-checkout commander-team ARTY handoff (`Construction_StationaryDefense.sqf:91-93`) from stable/release marker-based ARTY discovery (`Construction_StationaryDefense.sqf:133-135`, `Common_GetTeamArtillery.sqf:46-78`). Older patch-ready rows now explicitly preserve lane-specific checked refs until their owner pages are refreshed. No gameplay source changed.
2026-06-13	Support specials and tactical modules, support/authority owner pages	Support specials route and upgrade-sync refresh	The support atlas mixed UI, server-authority, economy, artillery, supply, MASH, UAV and ordnance detail without a top route, and its `upgrade-sync` matrix still cited older `89ae9dad` / `7ff18c49` branch heads.	Preserved evidence by adding a top route table and branch-scope note while keeping deep authority on Server authority migration map, ICBM authority, Service menu affordability guards and Supply mission authority cleanup. Refreshed `upgrade-sync` to docs checkout `295cc9d5`, stable `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; all checked roots still keep mixed `_args` / `_this` reads at `Server_HandleSpecial.sqf:67-73`. No gameplay source changed.
2026-06-13	Networking and public variables, network/PVF owner pages	Networking public-variable route prune	The networking atlas mixed architecture orientation with canonical channel inventory, dispatcher matrices and per-handler authority routes, so broad network prompts could duplicate work already owned by the channel index, PVF playbook and server-authority map.	Preserved source evidence by adding a top route table and current branch-scope anchors for `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`; generic PVF dispatch anchors stay `Init_PublicVariables.sqf:48,53`, `Server_HandlePVF.sqf:14`, `Client_HandlePVF.sqf:32`, and direct `SEND_MESSAGE` anchors stay `updateclient.sqf:12`, `Client_onEventHandler_SEND_MESSAGE.sqf:27`, `Common_SendMessage.sqf:26,38`. Full inventory routes to Public variable channel index, dispatcher branch status to PVF dispatch implementation, and per-handler authority to Server authority migration map. No gameplay source changed.
2026-06-13	Server gameplay runtime atlas, Server runtime and operations	Server runtime branch-scope route	Server runtime prompts could still land on docs-checkout source anchors and accidentally treat them as current `origin/master` truth, even though AI supply-truck startup, Patrols v2 and FPS publisher cleanup differ by branch.	Server gameplay runtime atlas now owns the branch-scope map for docs checkout `6afcc58e` versus `origin/master` `cf2a6d6a`, while the operations gateway routes broad prompts there before source line refs are cited. Detailed AI supply-truck, Patrols v2 and FPS smoke gates stay on owner pages. No gameplay source changed.
2026-06-13	SQF code atlas, architecture/SQF owner pages	SQF atlas compile registry refresh	The compile-registry snapshot still carried the 2026-06-02 totals and broad routing bullets, while the current docs/source checkout had drifted by one compile reference and needed clearer branch-scope warnings.	SQF code atlas now routes developers through a compact "How To Use This Atlas" table, updates the docs-branch `04a60e43` source mission snapshot to 738 total `preprocessFile` references (460 line-numbered, 278 plain, 22 commented), corrects the Client area / `Init_Client.sqf` counts and warns that `origin/master` `cf2a6d6a` must be recounted separately. No gameplay source changed.
2026-06-13	Architecture overview, architecture/SQF owner pages	Architecture overview owner-route prune	The overview repeated init/data-flow explanation already owned by the SQF atlas and lifecycle pages, while lacking a top routing map for developers trying to find the right owner page quickly.	Preserved evidence by adding source-backed runtime owner, generated-target and bootstrap source anchors, keeping branch-sensitive LoadoutManager detail routed to Tools and build workflow, and linking deep boot, networking, server, client, economy, AI/support and release-status detail to canonical owner pages. No gameplay source changed.
2026-06-13	Client UI systems, SQF code atlas, UI owner pages	Client UI atlas owner-route prune	The Client UI atlas mixed broad orientation, patch matrices and leaf-system risk detail, making it easy to duplicate resource, vote, factory, gear, support and performance rows already owned by narrower pages. Live wiki also had atlas/SQF deltas that were not mirrored into `docs/wiki`.	Preserved evidence by keeping current-source anchors and stable incoming anchors, adding a top owner-route table, shortening Known UI Risks into canonical owner links, and refreshing the fast-travel / clickable-text matrices to `origin/master` `cf2a6d6a`, Miksuu `b8389e74`, `perf/quick-wins` `0076040f` and release `a96fdda2`. No gameplay source changed.
2026-06-13	Client UI systems, Feature status, Source fix propagation queue, Dead/stale code register	Clickable text soundPush current-master refresh	Current `origin/master` advanced to `cf2a6d6a` and release to `a96fdda2`, while the clickable-text rows still described `89ae9dad` / `7ff18c49` as branch-head evidence and overstated the release/current-master derived-control count.	Preserved one canonical branch matrix in Client UI systems: every checked Chernarus and maintained Vanilla root keeps malformed `RscClickableText.soundPush[] = {, 0.2, 1};` at `Rsc/Ressources.hpp:556` with valid empty-sound precedent at `:92`; current master/release now have 14 derived controls per maintained root, while docs/source, Miksuu, perf and UI theme branches have 17. No gameplay source changed.
2026-06-13	AI commander autonomy, Support specials, AI supply-truck status rows	AI supply-truck current-master safe-disable route	Current `origin/master` advanced to `cf2a6d6a`, while older docs and machine rows still treated the `89ae9dad` raw-spawn shape as current-master evidence.	AI commander autonomy owns branch truth: current master and release `a96fdda2` safe-disable at `Init_Server.sqf:383-384`; Miksuu `b8389e74` and perf `0076040f` still raw-spawn; `feat/ai-commander` guards Chernarus only. No gameplay source changed.
2026-06-13	PVF dispatch implementation, Public variable channel index, Networking, P0 network status rows	P0 network current-master route	Current `origin/master` advanced to `cf2a6d6a`, Miksuu to `b8389e74` and release to `a96fdda2`, while PVF dispatcher and `SEND_MESSAGE` matrices still presented `89ae9dad` / `7ff18c49` as current branch-head evidence.	Preserved canonical split: PVF dispatch implementation owns DR-1/DR-38 handler-name lookup hardening; Public variable channel index owns DR-46 direct `SEND_MESSAGE` compile removal; Networking and Server authority migration map keep DR-55 sender authentication separate. No gameplay source changed.
2026-06-13	Towns/camps/capture, AI runtime, patrol status rows	Patrols v2 current-master route	Current `origin/master` advanced to `cf2a6d6a`, while several pages and machine rows still presented `89ae9dad` DR-57 / AI1 resistance-patrol findings as current-master patch-ready debt.	Evidence preserved as historical branch truth in the Resistance patrol branch matrix. Current master now routes through Patrols v2 side-upgrade path: source Chernarus and maintained Vanilla carry `server_side_patrols.sqf`, `Common_RunSidePatrol.sqf`, friendly marker publication and the `server_patrols.sqf:26` `&&` loop. Arma smoke remains pending; no gameplay source changed.
2026-06-13	Agent worklog archive, Navigation inventory, sidebar / MkDocs	Agent worklog archive route	Claude's 2026-06-07 worklog debloat moved historical chronology into Agent worklog archive, but the archive was not exposed in the sidebar/MkDocs mirror.	Agent worklog remains the active coordination surface; Agent worklog archive is now mirrored under `docs/wiki`, linked from the sidebar/MkDocs, and classified as archive evidence in the navigation inventory.
2026-06-08	Dead/stale code register, Towns/camps/capture	Wiki-maintenance pass 2 (additive; partial — high verifier-failure rate)	Second multi-agent pass. Applied only solidly-verified results: added `receiverMASHmarker.sqf` (dead client MASH receiver) and `monitorServerFPS.sqf` (no-op duplicate broadcaster) to the dead-code register; authored a Town Patrol Mechanic section correcting the towns atlas with DR-57/AI6 alongside the AI1 note.	Evidence preserved. Rejected: `UI-HUD-And-Dialogs` / `Agent-Development-Pack` "merge" — intentional compatibility aliases (prior decision). Codex/owner handoff: `Miksuu-Wiki-Archive-Discord-Bot` empty-stub delete (MkDocs-nav); ~25 candidate dead `STR_*` keys + dup-IDD (unverified — confirm before acting); the apply-ready condense lane and most doc-gap proposals failed verification this run and were not applied.
2026-06-07	Dead/stale code register, Deep-review findings, Instructions for Codex, Feature status	Wiki-maintenance megapass (71-agent team): dead-code harvest, DR-15 resolution, doc accuracy	A multi-lane read-only team (dead-code, LLM/token, unnecessary-docs, resolved-issue, links) was adversarially verified. Dead-code: ~18 newly-confirmed unreachable files added to the register (namespace helpers, getXxxPlayers cluster, HandleMissiles, ModifyAirVehicle, HandleATReloadVehicle, GetMarkerColoration, SetAttackWaveDetails, ReplaceArray, GetClosestEnemyLocation, GetUnitsPerSide, PVFunctions/LogGameEnd dup, Client_TaskSystem, PVFunctions/SetTask, WASP GearYouUnit/car_wheel_new) + two ⚠️ flagged (Server_AI_Com_Upgrade, Server_AI_SetTownAttackPath — uncalled, consistent with the dormant AI-commander FSM). Resolved: DR-15 (`Server_AssignNewCommander.sqf:4` now `_side=_this select 0`) marked fixed on master; the sweep otherwise confirmed DR-1..57 remain open.	Evidence preserved; the two ⚠️ AI-commander items flagged for owner verification (they bear on the AI-commander audit). Handed to Codex (mirror/nav lane): the link-lane `--`→`-` anchor reformats target the MkDocs slugger, not the live GitHub wiki (em-dash headings legitimately produce `--`), and two empty Miksuu archive stubs (`Miksuu-Wiki-Archive-Home`, `-Discord-Bot`) are MkDocs-nav removals; token condensations of standalone pages remain a follow-up.
2026-06-07	Agent worklog, Agent worklog archive	Archive worklog history to debloat the live page	The live Agent worklog had grown to 3642 lines (539 entries, ~15% of the whole wiki by line count) with mixed top-newest/bottom-appended ordering — by far the largest single bloat surface. Useful deltas are already promoted to owner pages, so the raw chronology is provenance, not active state.	No evidence deleted — moved verbatim. Agent worklog now keeps only recent entries (2026-06-06 onward, 82 entries, 515 lines) plus a Read-This-First/Future-Agents/Continue-Reading frame; the full 2026-06-01→06-06 history (448 dated entries + the old VERIFICATION/ROUND audit entries) is preserved verbatim in Agent worklog archive. Entry order is unchanged in both pages; machine history also lives in `agent-events.jsonl`.
2026-06-06	Function and module index, Dead/stale code	Legacy compiled alias route	The compiled-helper scout found old globals with no active static callers, but several helper files are still live through newer `WFBE_*` function names. A separate table avoids turning stale aliases into incorrect dead-file claims.	Function and module index owns the table; Dead/stale code has one route row and warns about dynamic/runtime uncertainty.
2026-06-06	Client UI systems, Performance opportunity sweep	Client modal loop cadence index	The returned client-loop scout found high-frequency dialog loops that were not yet separated from already-instrumented HUD/marker loops. Without a compact route, future agents could either miss the `.01` modal cadence or overstate it as a blind patch target.	Client UI systems now owns the cadence map, and Performance opportunity sweep carries only the `.01` Buy Gear/Transfer/Respawn/Upgrade row as measurement-first P3 work.
2026-06-06	UI resource parity cleanup, Client UI systems	Missing `wf_*.paa` icon block route	The indicator/resource backlog asked for image integrity checks, and the stale upgrade dialog row only said old `wf_*.paa` icons were missing without naming exact refs or maintained Vanilla scope.	UI resource parity cleanup now preserves the exact current Chernarus and maintained Vanilla `Rsc/Dialogs.hpp:2644-2831` missing `Client\Images\wf_*.paa` block and distinguishes it from resolving `Rsc/Ressources.hpp:300,302,304` button skins.
2026-06-06	Client UI systems, Support specials, Networking and public variables, Performance opportunity sweep, UI resource parity cleanup	Indicator surface matrix index	The indicator backlog already had family-level anchors, but still invited duplicate "all indicators" audits because the runtime fields were missing.	Client UI systems now owns the compact matrix for HUD/title, map/tactical, support/special, menu/resource and status/debug surfaces. Future cleanup should pick one row and update the canonical owner page instead of creating another broad indicator checklist.
2026-06-06	Client UI systems, Commander/HQ lifecycle, Feature status, Dead/stale code	Commander task / Objective Ping branch split	Current-source docs collapsed visible dormant commander `SetTask` UI, old town `TaskSystem` residue and release's branch-only Objective Ping revival into one "partial task" bucket.	Current source/stable/perf remains documented as dormant/commented for command-menu sends and old town TaskSystem. Release `7ff18c49` is now separately routed as branch-only Objective Ping in both maintained roots, with OA menu, target/audience, JIP and task-spam smoke still required before promotion.
2026-06-06	Function and module index, PerformanceAuditAnalyzer	PerformanceAudit writer index	The offline analyzer page was already strong, but the mission-side `PerformanceAudit_*` writer family was only a one-line function-index entry, making it easy to confuse parser limits with missing instrumentation.	Function and module index now owns the mission-side writer map: local enablement/buffers, RPT row emission, flush loop and representative client/server instrumentation. PerformanceAuditAnalyzer remains the parser/tooling owner.
2026-06-06	AI commander autonomy, Upgrades and research, Feature status, Source fix propagation queue	AI commander upgrade debit current-head refresh	The AI upgrade debit machine/status rows still carried `origin/master@2cdf5fb8` as branch evidence after current stable advanced to `89ae9dad`.	AI commander autonomy remains canonical: current stable/Miksuu `89ae9dad` and perf `0076040f` still keep raw AI_ORDER cost lookup plus swapped funds/supply debit in both maintained roots; `2cdf5fb8` is historical baseline only; release `7ff18c49` fixes debit order in both roots; `feat/ai-commander` fixes the cost-level lookup only in Chernarus.
2026-06-07	Service menu affordability guards, Feature status, Source fix propagation queue	Service/EASA affordability current-head refresh	The service affordability matrix still described release Chernarus as the only partial release rearm/refuel guard and used older stable/upstream wording after `origin/master` advanced to `89ae9dad`.	Service menu affordability guards remains canonical: current stable/Miksuu `89ae9dad` improves button-enable ordering but still has client-side action debit risks; release `7ff18c49` guards rearm/refuel in both maintained roots; repair/heal action-time affordability/context and strict EASA exact-funds/client-debit behavior remain open everywhere checked.
2026-06-07	Modules atlas, Dead/stale code register	Reaktiv current-head refresh	The Reaktiv unreachable-module rows still described stable `2cdf5fb8` as current-facing branch evidence after `origin/master` / local `master` advanced to `89ae9dad`.	Modules atlas remains canonical: current stable/Miksuu `89ae9dad` and perf `0076040f` still carry unreachable `Common/Module/Reaktiv` in both maintained roots; current `Init_Common.sqf:321-325` initializes ICBM, IRS and CIPHER with no Reaktiv init call; release `7ff18c49` removes maintained-root Reaktiv while current modded Napf/Eden/Lingor copies remain stale.
2026-06-06	Tools/build workflow, Source fix propagation queue, LoadoutManager machine rows	LoadoutManager root current-head refresh	Human tooling pages were mostly current, but the hardening backlog row still described current source/stable as `origin/master` `2cdf5fb8`.	Tools/build workflow and Source fix propagation queue remain canonical: current stable/Miksuu `89ae9dad` and perf `0076040f` still require an ancestor named `a2waspwarfare`; release `7ff18c49` adds `IsA2WaspWarfareRoot` marker-root discovery; `A2WASP_SKIP_ZIP=1` remains the propagation-only packaging bypass.
2026-06-06	Towns/camps/capture, camp-count machine rows	Camp-count current-head machine refresh	The canonical towns/camps and Feature Status rows were current, but an older hardening backlog row still described stable `2cdf5fb8` as current-facing camp-count evidence.	Towns/camps/capture remains canonical: current stable/Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` all keep `Common_GetTotalCamps.sqf:10` and `Common_GetTotalCampsOnSide.sqf:16` returning `1` for zero-camp towns; real-count versus safe-denominator semantics remain future town/respawn owner work.
2026-06-06	AI commander autonomy audit, Feature status, Source fix propagation queue, AI supply-truck machine rows	AI supply-truck current-head refresh	After `origin/master` advanced to `89ae9dad`, AI supply-truck rows still mixed current-stable wording with historical `2cdf5fb8` raw-spawn line refs.	AI commander autonomy audit remains canonical: current source/Vanilla, stable/Miksuu `89ae9dad` raw-spawn the uncompiled worker at `Init_Server.sqf:386-387`; historical `2cdf5fb8` raw-spawned at `:382-383`; release `7ff18c49` warning/disables both maintained roots at `:385-386`; `feat/ai-commander` guards only Chernarus and does not restore `supplytruck.fsm`.
2026-06-06	Towns/camps/capture, Source fix propagation queue, resistance-patrol machine rows	Resistance patrol current-head refresh	After `origin/master` advanced to `89ae9dad`, older patrol rows still carried `HEAD@2cdf5fb8` / older launch-line refs even though the active-latch bug itself remained in `server_patrols.sqf`.	Towns/camps/capture remains canonical: current source/Vanilla, current stable/Miksuu `89ae9dad` launch from `server_town_ai.sqf:295-298` and still use the `server_patrols.sqf:26` `
2026-06-06	Town AI vehicle despawn safety, Feature status, town-AI machine rows	Town AI despawn current-head refresh	After `origin/master` advanced to `89ae9dad`, one Feature Status row still presented historical stable `2cdf5fb8` as current-facing evidence and treated Miksuu as the only head with the moved diagnostics-heavy cleanup block.	Town AI vehicle despawn safety remains canonical: current source/Vanilla, current stable/Miksuu `89ae9dad` keep the no-player-crew vehicle guard at `server_town_ai.sqf:278` and add `Server_CleanupExpiredTownDefenseAssets.sqf:61-64` with the same player-leader-style deletion risk; historical `2cdf5fb8`, perf `0076040f` and release `7ff18c49` keep the older `server_town_ai.sqf:216-221` guard.
2026-06-06	Client UI systems, Feature status, Source fix propagation queue, fast-travel machine rows	Fast travel fee stable-head refresh	After `origin/master` advanced to `89ae9dad`, Tactical fast-travel fee rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked Tactical menu/constants files were unchanged through `89ae9dad`.	Client UI systems keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` still keep fee-mode TODOs, hidden unaffordable destinations, marker-only fee text and local travel debit; UX policy and action-time recheck remain future UI owner work.
2026-06-06	Client UI systems, Feature status, Source fix propagation queue, Dead/stale code, clickable-text machine rows	ClickableText soundPush stable-head refresh	After `origin/master` advanced to `89ae9dad`, clickable-text sound config rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked `Rsc/Ressources.hpp` and `Rsc/Dialogs.hpp` files were unchanged through `89ae9dad`.	Client UI systems keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f`, release `7ff18c49` and UI theme branches still keep malformed `RscClickableText.soundPush[] = {, 0.2, 1};`; base-class config repair and representative UI smoke remain future UI owner work.
2026-06-06	Vehicle cargo equip loop bounds, Feature status, Source fix propagation queue, cargo machine rows	Vehicle cargo loop stable-head refresh	After `origin/master` advanced to `89ae9dad`, vehicle/backpack cargo loop rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked equip/get-cargo helper files were unchanged through `89ae9dad`.	Vehicle cargo equip loop bounds keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad` and release `7ff18c49` still keep the five inclusive cargo-application loops; `perf/quick-wins` `0076040f` fixes Chernarus only, so source Chernarus plus maintained Vanilla patch/propagation remains future gear owner work.
2026-06-06	Gear template profile filter, Feature status, Source fix propagation queue, gear machine rows	Gear template/profile stable-head refresh	After `origin/master` advanced to `89ae9dad`, gear profile/template rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked AddTemplate, FillTemplates, SaveTemplateProfile and Init_ProfileGear files were unchanged through `89ae9dad`.	Gear template profile filter keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` still keep undefined `_u_upgrade`, the six-field import guard and the Barracks-or-Gear creation versus Gear-only display mismatch; save/import fixes and the Barracks/Gear semantics decision remain future gear owner work.
2026-06-06	Support specials, Upgrades and research, Feature status, Source fix propagation queue, RequestSpecial machine rows	RequestSpecial upgrade-sync stable-head refresh	After `origin/master` advanced to `89ae9dad`, `upgrade-sync` rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked handler/caller/process-upgrade files were unchanged through `89ae9dad`.	Support specials keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` still keep the mixed `_args` / `_this` parser; tuple normalization remains future upgrade/network owner work.
2026-06-06	Construction and CoIn systems, Feature status, Source fix propagation queue, salvage machine rows	Salvage payout stable-head refresh	After `origin/master` advanced to `89ae9dad`, salvage payout/cleanup rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked salvage skill/FSM/client-init/build-unit files were unchanged through `89ae9dad`.	Construction and CoIn systems keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f`, release `7ff18c49` and historical salvage branches still keep lowercase `ChangePlayerfunds`, the salvage-truck `
2026-06-06	Construction and CoIn systems, Feature status, Source fix propagation queue, auto-wall machine rows	Auto-wall toggle stable-head refresh	After `origin/master` advanced to `89ae9dad`, auto-wall global-toggle rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked CoIn toggle, request handler and SmallSite/MediumSite consumer files were unchanged through `89ae9dad`; `Init_Common.sqf` only gained unrelated town-defense helper compile wiring.	Construction and CoIn systems keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` still route `User14` through one global `isAutoWallConstructingEnabled`; the global-versus-side/requester policy decision remains future construction owner work.
2026-06-06	Marker cleanup/restoration, Feature status, Source fix propagation queue, empty-supply machine rows	Empty supply-truck stable-head refresh	After `origin/master` advanced to `89ae9dad`, empty supply-truck cleanup rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked empty-vehicle collector/handler files were unchanged through `89ae9dad`.	Marker cleanup/restoration keeps branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` still set supply-truck `_delay = 86400`; the keep-and-label versus shorter/parameterized timeout decision remains future runtime/logistics owner work.
2026-06-06	WASP marker wait cleanup, Source fix propagation queue, WASP machine rows	WASP marker wait stable-head refresh	After `origin/master` advanced to `89ae9dad`, WASP marker wait rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked WASP helper/client-init files were unchanged through `89ae9dad`.	WASP marker wait cleanup keeps the branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` still keep the display-54 input-lock busy wait; the tiny throttled-wait patch and marker-dialog smoke remain future code-owner work.
2026-06-06	Factory and purchase systems, Feature status, Source fix propagation queue, factory machine rows	Factory purchase stable-head refresh	After `origin/master` advanced to `89ae9dad`, buy-menu price/key and destroyed-factory refund rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked factory buy-menu/list/build-unit files were unchanged through `89ae9dad`.	Factory and purchase systems and destroyed-factory refund matrix keep branch truth: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` remain separated; price/key alignment and purchase acceptance/debit/refund policy stay future code-owner work.
2026-06-06	PVF dispatch implementation, Public variable channel index, Networking and public variables, Feature status, Source fix propagation queue, network machine rows	Network P0 current-head refresh	After `origin/master` advanced to `89ae9dad`, PVF dispatcher and `SEND_MESSAGE` rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked network files were unchanged through `89ae9dad`.	Branch truth stays on PVF dispatch implementation and Public variable channel index: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` remain separated; PVF dispatcher lookup hardening and structured/localized `SEND_MESSAGE` payload work stay future code-owner work.
2026-06-06	Economy authority first cut, Economy, towns and supply, Feature status, Source fix propagation queue, economy machine rows	Economy current-head branch refresh	After `origin/master` advanced to `89ae9dad`, the side-supply clamp/reason and resource-income rows still presented stable `2cdf5fb8` as current-facing evidence even though the checked economy files were unchanged through `89ae9dad`.	Economy branch truth stays on Economy authority first cut and Economy, towns and supply: current source/Vanilla, stable `89ae9dad`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49` remain separated; side-supply clamp/reason and resource-income behavior stay future code-owner work.
2026-06-06	Current source snapshot, Source fix propagation queue, Construction and CoIn systems, Testing workflow	Release ARTY marker ownership route	Commander/construction scout found the release branch has alternate commander-built ARTY discovery even though it lacks the docs/source commander-team gunner handoff. Older rows collapsed this into "release absent."	Current routing now separates docs/source `f3e157f2` gunner-handoff evidence, current stable `89ae9dad` still lacking both ARTY discovery shapes, and release `7ff18c49` marker-based discovery through `WFBE_CommanderArtillery*` plus `Common_GetTeamArtillery.sqf:46-78`. Arma smoke remains required.
2026-06-06	Current source snapshot, Upstream Miksuu commit intel, Towns/camps/capture, Town AI vehicle safety	Origin master town-defense merge correction	Fresh fetch advanced `origin/master` from `2cdf5fb8` to `89ae9dad`, making the previous "upstream-only / not rayswaynl stable" town-defense wording stale.	Routing now says current stable master and Miksuu are both `89ae9dad`; town-defense persistence/diagnostics is stable-master source evidence, while DR-45 player-occupancy hardening and Arma smoke remain open.
2026-06-06	Current source snapshot, Upstream Miksuu commit intel, Towns/camps/capture, Town AI vehicle safety	Miksuu town-defense overhaul refresh	Refetch showed current `miksuu/master` is `89ae9dad`, while the current snapshot/upstream intel still described `69e1958a` as the current upstream head.	Superseded by the origin-master correction above after `origin/master` advanced to `89ae9dad`; the preserved route is that the persistence/diagnostics model exists on current stable master and still needs the DR-45 player-occupancy guard plus smoke.
2026-06-06	Current source snapshot, `agent-context.json`, Progress dashboard	Release context current-head correction	Compact context still repeated release `3282ff3f` / Chernarus-only wording for paratrooper markers and hosted FPS after current release `7ff18c49` propagated those fixes into both maintained release roots.	Current release-head routing now says `7ff18c49` carries paratrooper registration, single `Skill_Init` and hosted FPS guard in both maintained release roots, while stable master still lacks those fixes and release/stable still lack commander-built ARTY ownership.
2026-06-06	Modules atlas, Dead/stale code register, Reaktiv machine rows	Reaktiv branch status refresh	The Reaktiv row already said dead/unreachable, but it missed that release `7ff18c49` removes the module from maintained roots while stale modded copies remain.	Modules atlas remains the canonical module owner: current source/Vanilla, stable `2cdf5fb8`, Miksuu `89ae9dad` and perf `0076040f` keep unreachable Reaktiv in both maintained roots; release `7ff18c49` has no maintained-root Reaktiv, so cleanup is archive-or-revive plus modded policy.
2026-06-06	Gear template profile filter, Feature status, Source fix propagation queue, gear profile machine rows	Gear profile filter current-head refresh	The paired profile save/import rows still had broad branch wording even though current heads keep the same source-unpatched shapes in every checked maintained root.	Gear template profile filter now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: all checked maintained roots still carry undefined `_u_upgrade` in `SaveTemplateProfile` and the six-field `Init_ProfileGear` import guard before index-6 backpack reads.
2026-06-06	Vehicle cargo equip loop bounds, Feature status, Source fix propagation queue, cargo machine rows	Vehicle cargo loop current-head refresh	The cargo loop playbook and status rows had a broad branch matrix without current head hashes and missed that `perf/quick-wins` is Chernarus-only for this fix.	Vehicle cargo equip loop bounds now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: current source/Vanilla, stable, Miksuu and release still carry the five inclusive loops; perf fixes Chernarus only, while perf Vanilla still needs propagation.
2026-06-06	Construction and CoIn systems, Feature status, Source fix propagation queue, auto-wall machine rows	Auto-wall toggle current-head refresh	The live auto-wall machine row still cited older Miksuu/release heads even though current branch heads preserve the same global toggle scope with a small release consumer-condition nuance.	Construction and CoIn systems now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: every checked maintained root still uses one global `isAutoWallConstructingEnabled`; release only adds an `AARadar` exclusion to SmallSite/MediumSite wall creation, so the global-vs-side/requester policy decision remains unchanged.
2026-06-06	Public variable channel index, dashboard/status records	Marker creation direct-channel index sharpening	The returned public-variable scout found `MARKER_CREATION` still described as generic marker code even though the source path is a mixed caller-to-clients direct relay outside PVF hardening.	`MARKER_CREATION` now has exact sender/receiver/caller anchors, current-head branch scope and a future validation route for sender/side/schema plus delete/JIP/replay smoke.
2026-06-06	Hardening roadmap, Networking/public variables, network machine rows	Network hardening current-head refresh	The roadmap and networking overview still named older Miksuu/release refs for PVF dispatcher and `SEND_MESSAGE` compile surfaces, while canonical queue rows already had current branch heads.	PVF dispatch implementation and Public variable channel index remain the canonical matrices. Roadmap/overview now name stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: PVF dispatcher `Spawn (Call Compile _script)` and direct `SEND_MESSAGE` receiver/helper compile remain separate P0 source-unpatched lanes.
2026-06-06	Towns, camps and capture, Feature status, Source fix propagation queue, machine status rows	Camp-count current-head refresh	The camp helper fallback rows still cited older Miksuu/release refs even though current branch heads keep the same zero-camp fallback semantics.	Towns, camps and capture now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: all checked maintained roots still return `1` for zero-camp towns in `Common_GetTotalCamps.sqf` / `Common_GetTotalCampsOnSide.sqf` and feed capture mode 2, threeway respawn and depot-buy gates; release only shifts Buy Units callers to `:117-118`.
2026-06-06	Client UI systems, Client UI/HUD gateway, dashboard/status records	Indicator backlog sharpening	The returned indicator scout had useful exact source anchors, while the existing backlog table was still broad enough that future agents could restart discovery instead of filling the matrix.	Client UI systems now keeps one exact-anchor route for HUD/title, marker, support, menu/list, status/debug and image/resource indicator families; the quick-reference UI page links to it.
2026-06-06	Factory and purchase systems, Feature status, Source fix propagation queue, machine status rows	Factory purchase current-head refresh	Buy-menu price/key and destroyed-factory refund rows still named older Miksuu/release refs, while current branch heads sharpen release scope without changing current-source patch readiness.	Factory and purchase systems now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: current source/Vanilla, stable, upstream and perf still keep selected-detail price drift, no level-0 modifier reset, mixed driver-default keys and no dead/null factory refund; release fixes selected-detail parity and mirrors both driver keys in several write paths, but modifier reset, one-key normalization and dead/null factory refund remain open.
2026-06-06	Feature status, Construction and CoIn systems, salvage/camp machine rows	Status provenance current-head refresh	Scout returns and stale-ref scans found current-looking rows still naming older upstream/source labels even though owner pages or current branch checks already had newer evidence.	Feature Status now points the broad upstream note and camp flag row at Miksuu `89ae9dad`; Construction and CoIn systems now labels salvage as current source/Vanilla, Miksuu `89ae9dad` and release `7ff18c49` while preserving the same casing-first salvage patch route.
2026-06-06	Marker cleanup/restoration, Feature status, Source fix propagation queue, machine status rows	Empty supply-truck current-head refresh	The empty supply-truck cleanup owner/status/machine rows still cited older Miksuu/release refs for a current-looking branch matrix, while current Miksuu and release heads keep the same 24-hour timeout shape.	Marker cleanup/restoration now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: all checked maintained roots drain `emptyVehicles` into `WFBE_SE_FNC_HandleEmptyVehicle` and set supply-truck `_delay = 86400`; the keep-and-label versus shorter/parameterized timeout decision remains unchanged.
2026-06-06	Gear template profile filter, Feature status, Source fix propagation queue, machine status rows	Gear template current-head refresh	The gear-template owner/status/machine rows still cited older Miksuu evidence for a current-looking branch matrix, while current Miksuu and release heads keep the same creation/display/save gate shape.	Gear template profile filter now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: all checked maintained roots keep the Barracks-or-Gear AddTemplate creation gate, Gear-only FillTemplates display gate and undefined `_u_upgrade` save filter; owner-decision scope remains unchanged.
2026-06-06	Support specials, Upgrades and research, Feature status, Source fix propagation queue, machine status rows	RequestSpecial upgrade-sync current-head refresh	The tuple-cleanup route still cited older Miksuu/release refs and one stale upgrade-menu timer line, even though current branch heads keep the same parser shape.	Support specials now names stable `2cdf5fb8`, Miksuu `89ae9dad`, perf `0076040f` and release `7ff18c49`: all checked maintained roots keep the mixed `_args` / `_this` parser; release shifts both maintained-root callers to `GUI_UpgradeMenu.sqf:254`, while current/stable/Miksuu/perf callers remain `:241`.
2026-06-06	AI commander autonomy, Abandoned feature revival, Feature status, Source fix propagation queue, machine status rows	AI supply-truck current-head refresh	The AI supply-truck owner/revival pages and machine rows still cited older Miksuu/release heads, while current status snippets already referenced the newer release.	AI commander autonomy now names current Miksuu `89ae9dad` and release `7ff18c49`: current/stable/upstream/perf remain raw-spawn plus missing-FSM, release logs/disables both maintained roots, and `feat/ai-commander` remains Chernarus-only guard evidence rather than Vanilla propagation or logistics revival.
2026-06-06	WASP marker wait cleanup, WASP overlay, Source fix propagation queue, machine status rows	WASP marker wait current-head refresh	The owner and machine rows still cited older Miksuu/release heads and the overlay launch line had drifted after later client-init edits.	WASP marker wait cleanup now names current Miksuu `89ae9dad` and release `7ff18c49`: all checked maintained roots still keep the display-54 input-lock busy wait; current/stable/Miksuu/perf launch at `Init_Client.sqf:279`, release at `:283`, and `WASP-Overlay` now uses the current source launch line.
2026-06-06	AI commander autonomy, Upgrades and research, Economy, towns and supply, Feature status, Source fix propagation queue	AI commander upgrade debit branch route	The AI upgrade worker debit issue was repeated across economy/upgrade/status docs with older line refs and no exact branch matrix.	AI commander autonomy now owns the matrix: current source/Vanilla, stable, Miksuu and `perf/quick-wins` keep raw AI_ORDER cost lookup plus swapped funds/supply debit; release `7ff18c49` fixes debit order in both maintained roots; `feat/ai-commander` also fixes the cost lookup only in Chernarus.
2026-06-06	Towns, camps and capture, Source fix propagation queue, machine status rows	Town/camp release parity refresh	Earlier camp flag and resistance patrol rows still reflected older Chernarus-only or intermediate release evidence. Current release head `7ff18c49` has maintained-root parity for the independent camp-capture flag line and resistance patrol loop exit, while current source still needs the patch.	Towns, camps and capture now owns the matrix: current source/Vanilla, stable and Miksuu remain source-unpatched; `perf/quick-wins` is Chernarus-only; release `7ff18c49` fixes both maintained release roots for capture flag and patrol loop exit. Repair-side camp flag refresh remains open everywhere checked.
2026-06-06	PR cleanup lab, Current source snapshot, Feature status, Headless delegation/failover, Marker cleanup/restoration	Release 7ff18c49 PR8 delta route	The release branch advanced past the documented `7195b331` intermediate; the new `7195b331..7ff18c49` diff is real but narrow, so it needed source-backed routing without turning release-branch evidence into current-source claims.	PR cleanup lab now owns the current head summary: delegated-AI locality guards and cleaner/restorer startup hardening are present in both maintained release roots; prior propagated-fix conclusions carry forward, DR-42 update-back/failover remains open and HC/cleaner Arma smoke is still required.
2026-06-06	Town AI vehicle despawn safety, Feature status, Source fix propagation queue	Town-AI vehicle despawn branch route	DR-45 already had a patch playbook, but the source refs were stale and branch status was absent from the owner page/patch-ready queue.	Town AI vehicle despawn safety now owns the matrix: current source/Vanilla, stable `origin/master`, Miksuu upstream, `perf/quick-wins` and release all still lack a player-occupancy guard before deleting tracked town-AI vehicles.
2026-06-06	Mission start parameters index, Mission parameters	Start parameter index extraction	Steff asked for all start parameters. Keeping a dedicated source-order page prevents the mission-parameter flow page from becoming an unreadable 89-row table while still making the host/lobby contract easy to find.	Mission start parameters index now owns the complete maintained Chernarus/Vanilla lobby parameter table, category ranges and caveats for commented/forced/no-op/mislabeled parameters.
2026-06-06	Client UI systems, Feature status, Pending owner decisions, Progress dashboard	Indicator exploration backlog	"All indicators" spans HUD/title controls, map/tactical markers, support markers, menu/list icons, status/debug channels and image/resource integrity. One canonical exploration checklist prevents repeated scattered TODOs before any pruning or redesign.	Client UI systems now owns the source anchors and required output matrix: surface, owner script, state source, audience, cadence, cleanup path, known risk, branch scope and smoke target.
2026-06-06	Mission parameters, Feature status	Air Event parameter doc gap	The old Air Event setting still exists in source but was mostly discoverable only through code search and scattered ICBM/history mentions. Creating a separate page would duplicate parameter, ICBM and unit-config facts.	Mission parameters now owns the compact source-backed explanation: `WFBE_AIR_EVENT_ENABLED` feeds `IS_air_war_event`, forces event economy/upgrade defaults, hides ICBM and omits Avenger/Tunguska-style heavy AA.
2026-06-06	Hosted server FPS loop sleep, Pending owner decisions, release machine rows	Hosted FPS release status refresh	The owner page and decision register still reflected the older `3282ff3f` Chernarus-only release status, while current release head `7195b331` carries the guarded/no-redundant-monitor shape in both maintained release roots.	Hosted server FPS loop sleep now owns the current branch matrix: docs/source and release carry the fix shape, stable `origin/master` still keeps the old loop shape, and dedicated/hosted Arma smoke remains pending.
2026-06-06	Paratrooper marker revival, Current source snapshot, Feature status	Paratrooper release status refresh	The owner page and one status row still reflected older release-branch absence wording, while current release head `7195b331` now registers `HandleParatrooperMarkerCreation` in both maintained release roots.	Paratrooper marker revival now owns the current branch matrix: docs/source and release carry the static registration, stable `origin/master` still omits it, modded folders still drift and Arma marker smoke remains pending.
2026-06-05	PVF dispatch implementation, Networking, Public variable channel index, Hardening roadmap, Feature status, Source fix propagation queue	PVF dispatcher lookup branch route	DR-1/DR-38 already had a patch playbook, but the current/stable/upstream/perf/release status was scattered and release's adjacent HC client filter could be mistaken for dispatcher hardening.	PVF dispatch implementation now owns the branch matrix: all checked maintained roots/branches still use `Spawn (Call Compile _script)`; future work is the allowlisted `missionNamespace getVariable` source patch plus maintained Vanilla propagation and PVF smoke.
2026-06-06	Public variable channel index, Networking, Hardening roadmap, Feature status, Source fix propagation queue	SEND_MESSAGE direct compile branch route	DR-46 was already known, but it lacked a compact branch/root matrix and could be mistaken for work covered by the PVF dispatcher hardening lane.	Public variable channel index now owns the branch matrix: current source/Vanilla, stable, upstream, perf and release all keep the direct receiver/helper `call compile` route; future work is a separate P0 direct-PV source patch plus localized-message and forged-payload smoke.
2026-06-06	Client skill init idempotency, Current source snapshot, Feature status, Source fix propagation queue	Client skill release status refresh	The owner page and machine rows still carried older release-branch wording from `3282ff3f`/`fb3084c2`, even though current release head `7195b331` now has one `Skill_Init.sqf` call in both maintained roots.	Current release-head truth is now single-sourced through Client skill init idempotency and Current source snapshot: docs/source and release carry the single-init shape, stable `origin/master` still duplicates, and Soldier/non-Soldier/respawn Arma smoke remains pending.
2026-06-06	Gear template profile filter, Feature status, Source fix propagation queue	Gear template creation gate branch route	The owner-decision row named the AddTemplate gate mismatch, but it lacked branch/root scope and could be confused with the profile save/import bug or broader gear purchase authority hardening.	Gear template profile filter now owns the creation/display/save branch matrix: current source/Vanilla, stable, upstream, perf and release all keep the Barracks-or-Gear creation gate, Gear-only display gate and undefined save-filter `_u_upgrade`; future work is a Barracks/Gear semantics decision before code propagation.
2026-06-06	AI commander autonomy, Abandoned feature revival, Feature status, Source fix propagation queue	AI supply-truck branch route	The abandoned AI supply-truck finding was correct, but it did not clearly separate current nil-code/FSM breakage from release `7195b331`'s safe-disable candidate and `feat/ai-commander`'s Chernarus-only guard.	AI commander autonomy now owns the branch matrix: current source/Vanilla, stable/upstream/perf remain raw; release logs/disables in both maintained roots; `feat/ai-commander` is not a Vanilla propagation or logistics revival.
2026-06-05	Dead/stale code register, Mission parameters, Progress dashboard	Dead-code parameter duplicate prune	The same `WFBE_C_AI_MAX` and `WFBE_C_UNITS_CLEAN_TIMEOUT` parameter findings appeared twice in Dead/stale code: once as actionable current findings and again as a parameter-scan table.	Kept the actionable rows in Current Findings plus the priority backlog, and replaced the later duplicate table with a pointer to the single-sourced rows and Mission parameters.
2026-06-05	Source fix propagation queue, Construction and CoIn, Progress dashboard	Source-fix salvage duplicate prune	The patch-ready queue had two live salvage rows with the same branch scope and next action, making future agents likely to treat one cleanup lane as two.	Removed the older generic row and kept one canonical salvage row anchored to Construction and CoIn salvage matrix, preserving the casing-first fix, maintained Vanilla propagation and manual/truck salvage smoke gates.
2026-06-06	Factory and purchase systems, Feature status, Source fix propagation queue	Factory destroyed-purchase refund branch route	The destroyed-factory no-refund finding already existed, but it lacked branch/root scope and could be confused with DR-33 queue-counter cleanup or with the release branch's adjacent empty/crewless refund code.	Factory and purchase systems now owns the branch matrix: current source/Vanilla, stable, upstream and perf still have no dead/null factory refund; release `7195b331` has `_currentCost` plumbing and an empty/crewless-branch refund only.
2026-06-05	Agent worklog, Factory and purchase systems, Construction and CoIn	Claude branch divergence harvest check	`origin/docs/developer-wiki-claude` advanced to `5d0db9d2`, but it is highly divergent from the curated docs branch and would reintroduce broad wiki-state churn if merged wholesale.	Checked latest Claude commits `3cd1798c` and `5d0db9d2`; the useful construction and buy-menu facts are already canonical in owner pages. Future agents should treat the Claude branch as scout evidence and harvest missing source-backed deltas only.
2026-06-06	Economy authority first cut, Economy, towns and supply, Feature status, Source fix propagation queue	Side-supply reason-string branch route	The reason-string off-by-one was already documented as a terse auditability bug, but it lacked branch/root scope and could be confused with direct-channel side-supply authority.	Economy authority first cut now owns the branch matrix: current source/Vanilla, stable, upstream, perf and release all keep the reason guard; future work is a small diagnostics fix paired with the clamp helper edit, not authority closure.
2026-06-06	Feature status, Architecture overview, Construction and CoIn, AI runtime/HC loop map	Stable low-priority TODO cluster prune	Three vague Feature Status rows repeated TODO comments without branch scope or owner-page context.	Collapsed them into one branch-checked low-priority TODO cluster; useful details now live on the architecture, construction/CoIn and AI runtime owner pages, while the old one-line rows are removed from the live register.
2026-06-06	Economy, towns and supply, Economy authority first cut, Feature status, Source fix propagation queue	Resource income payout/display branch route	The resource income row already existed as a terse scout note, but it lacked current branch/root scope and could be mistaken for a UI-only display cleanup instead of balance-sensitive payout logic.	Economy, towns and supply now owns the branch matrix: current source/Vanilla, stable `origin/master` `2cdf5fb8`, current Miksuu `89ae9dad`, `perf/quick-wins` `0076040f` and release `7ff18c49` all keep the shared cap guard and income-system `4` server/client multiplier drift; future work is code-owner balance review plus capped/uncapped income smoke.
2026-06-06	Progress dashboard, Agent worklog, Client UI systems, Support specials	Latest Batch trim after resource income	The resource-income payout branch route made Latest Batch grow past five rows during rebase.	Kept the newest five dashboard rows; fast-travel fee remains preserved in Client UI systems, Support specials, Feature status, Source fix propagation queue, Agent worklog, `agent-events.jsonl` and git history.
2026-06-05	Current source snapshot, PR cleanup lab, Feature status, Source fix propagation queue	Release `7195b331` status refresh	The release branch moved after earlier `3282ff3f`/`d482c742` evidence rows, then advanced through `fb3084c2` to `7195b331`; several old rows would mislead future agents by saying release Vanilla still lacked fixes now present on the release head.	Current release-head truth is centralized in Current source snapshot: release Chernarus and maintained Vanilla now carry paratrooper registration, single `Skill_Init`, hosted-FPS guard/removal, narrowed supply scan, camp-capture flag fix and resistance-patrol `&&`; `7195b331` adds the GPS-toggle replacement for the old FPS-only slot. Supersession: the later `release-arty-marker-ownership-route` row corrects commander-built ARTY as marker-based in release `7ff18c49`, while current stable master still lacks both ARTY discovery shapes.
2026-06-06	Support specials, Upgrades and research, Feature status, Source fix propagation queue	RequestSpecial upgrade-sync branch route	The upgrade-sync note existed as a terse fragility warning and an older machine record, but it lacked branch/root scope and could be misread as a proven runtime bug instead of tuple-parser cleanup debt.	Support specials now owns the branch matrix: current source/Vanilla, stable, upstream, perf and release all keep the same mixed `_args` / `_this` shape; because `_args = _this`, future work is normalization plus smoke, not emergency authority repair.
2026-06-06	Client UI systems atlas, Feature status, Source fix propagation queue	Vote/help UI edge branch route	The UI edge-case row mixed vote loops, help lifecycle, GPS router and WASP marker wait in one long status entry without a branch matrix for the non-WASP pieces.	Client UI systems now owns the vote/help/main-menu branch matrix: current source/Vanilla, stable, upstream, perf and release all keep the same source-unpatched shapes; WASP marker input-lock remains routed to WASP marker wait cleanup.
2026-06-06	Progress dashboard, Agent worklog, Marker cleanup/restoration	Latest Batch trim after fast-travel	The fast-travel fee branch route made Latest Batch grow to six rows again during rebase.	Kept the newest five dashboard rows; empty supply-truck cleanup remains preserved in Marker cleanup/restoration, Feature status, Source fix propagation queue, Agent worklog, `agent-events.jsonl` and git history.
2026-06-06	Progress dashboard, Agent worklog, Client UI systems	Latest Batch trim after vote/help	The vote/help UI edge batch made Latest Batch grow to six rows again, despite the dashboard's compact current-state role.	Kept the newest five dashboard rows; clickable-text soundPush remains preserved in Client UI systems, Feature status, Source fix propagation queue, Agent worklog, `agent-events.jsonl` and git history.
2026-06-05	Client UI systems, Support specials, Feature status, Source fix propagation queue	Fast-travel fee branch route	The old fast-travel row only said a TODO existed, which made a working local flow look like a missing feature and did not prove stable/upstream/release status.	Client UI systems now owns the branch matrix: current source/Vanilla, stable, upstream, perf and release all keep the same fee-mode UX; future work is a hide/disabled/prompt policy decision plus final local guard and smoke.
2026-06-06	Economy authority first cut, Economy/towns/supply, Feature status, Source fix propagation queue	Side-supply clamp branch route	The side-supply clamp-first lane existed in machine backlog, but the canonical page did not show which branches still carry the old arithmetic versus the `perf/quick-wins` partial fix.	Economy authority first cut now owns the branch matrix: current source/Vanilla, stable, upstream and release remain unpatched; `perf/quick-wins` is Chernarus-only arithmetic evidence, not Vanilla propagation or DR-44 authority closure.
2026-06-05	Wiki pruning ledger, Construction and CoIn, Agent worklog, `agent-events.jsonl`	Salvage duplicate row trim	The newer `salvage-payout-cleanup-branch-route` row already supersedes the older mini-scout `salvage-payout-loop-branch-route` row with broader branch coverage and Miksuu salvage-branch checks.	Removed the older row from Recent Pruning Decisions; provenance remains in Agent worklog, `agent-events.jsonl`, git history and the canonical Construction and CoIn salvage matrix.
2026-06-05	WASP marker wait cleanup, Feature status, Source fix propagation queue, `agent-hardening-backlog.jsonl`	WASP marker wait branch route	The marker wait cleanup page had the local patch shape but lacked stable/upstream/perf/release branch scope.	WASP marker wait cleanup now owns the branch matrix: every checked maintained root/branch keeps the display-54 input-lock busy wait; future work is the tiny throttled wait patch plus marker-dialog smoke.
2026-06-05	Progress dashboard, Agent worklog, `agent-events.jsonl`	Latest Batch re-trim	Helper batches kept growing Latest Batch past the dashboard's compact current-state surface rule.	Kept the newest five rows on the dashboard; visible-parameter, salvage, auto-wall, RHUD/endgame and buy-menu price/key rows remain preserved in the worklog, event feed, owner pages and git history.
2026-06-05	Towns, camps and capture, Feature status, Source fix propagation queue, `agent-feature-status.jsonl`	Camp count helper fallback branch route	The zero-camp helper fallback was already known, but it lacked branch/root scope and was not visible in the patch-ready propagation queue.	Towns, camps and capture now owns the branch matrix: current source/Vanilla, stable, upstream, perf and release all keep the `1` fallback and affected capture/respawn/depot consumers.
2026-06-05	Client UI systems, Feature status, Source fix propagation queue, Dead/stale code	Clickable text soundPush branch route	DR-25b was verified but still had only terse status rows and older worklog mentions, so future agents could recheck the same UI config across branches.	Client UI systems now owns the branch matrix: no checked maintained root or UI branch fixes the malformed base-class `soundPush[]`; future code work is one config edit plus maintained Vanilla propagation and OA dialog smoke.
2026-06-05	Feature status, Construction and CoIn, `agent-events.jsonl`, `agent-knowledge.jsonl`	Auto-wall duplicate row prune	The rebase after the RHUD/salvage lanes left the branch-checked auto-wall row beside the older pre-branch row.	Kept the branch-checked row that cites current source/Vanilla, stable, Miksuu upstream, `perf/quick-wins` and release; removed the stale duplicate wording from Feature status.
2026-06-05	Construction and CoIn, Feature status, Source fix propagation queue, `agent-hardening-backlog.jsonl`	Salvage payout/cleanup branch route	The salvage payout casing and client-led loop/deletion risks were already known, but the Miksuu salvage branches and current release/perf branches had not been scoped.	Construction and CoIn now owns the branch-checked route: no checked branch fixes the casing/loop/authority shape; future code work should fix payout casing first, then smoke and review authority.
2026-06-05	Construction and CoIn, Feature status, Source fix propagation queue, `agent-hardening-backlog.jsonl`	Auto-wall toggle scope branch route	The existing auto-wall global-toggle finding was correct, but it lacked a branch/root check and was easy to confuse with broader construction authority hardening.	Construction and CoIn now owns the branch-checked route: every checked maintained root/branch keeps the global toggle; future code work is a policy choice plus two-player/two-side smoke.
2026-06-05	Mission parameters, Dead/stale code register, Feature status, Source fix propagation queue, Player AI caps	Visible parameter runtime-consumer branch route	`WFBE_C_AI_MAX` and `WFBE_C_UNITS_CLEAN_TIMEOUT` were correct stale-parameter leads, but they were scattered across dead-code and AI-cap pages without a branch/root matrix.	Mission parameters now owns the branch-checked route: every checked maintained root/branch keeps `WFBE_C_AI_MAX` no-reader and `WFBE_C_UNITS_CLEAN_TIMEOUT` comment-only; remaining work is code-owner parameter policy/cleanup plus host/cap/cleanup smoke.
2026-06-05	UI IDD collision repair, Client UI systems atlas, Feature status, Source fix propagation queue	RHUD/endgame title handle branch route	Existing wording named the local lifecycle-handle defect but did not prove stable/upstream/release status or clearly separate display-handle work from duplicate-IDD cleanup.	UI IDD collision repair now owns the branch matrix; current source/Vanilla, stable/upstream and release all still share `currentCutDisplay`, so the title display-variable split or endgame gate remains future code work.
2026-06-05	Factory and purchase systems, Feature status, Client UI systems, BuyMenu EASA QoL branch audit, Source fix propagation queue	Buy-menu price/key branch route	The stale unit-cost and driver-default rows were correct but did not say that release/QoL branch only fixes Chernarus selected-detail price while Vanilla, modifier reset and driver key remain open.	Factory and purchase systems now owns the branch matrix; Feature Status keeps one compact row; branch audit names the partial fix boundary.
2026-06-05	Towns/camps/capture, AI runtime, Feature status, Source fix propagation queue	Resistance patrol latch branch route	Existing wording named the local active-latch defect but did not show that `perf/quick-wins` and release Chernarus already carry a partial loop-exit fix while Vanilla remains old.	Towns/camps/capture now owns the branch matrix; future code work is a current-source port plus maintained Vanilla propagation and patrol death/relaunch smoke.
2026-06-05	Construction logic list cleanup, Construction/CoIn atlas, Feature status, Source fix propagation queue	Construction SmallSite branch route	Existing wording named the local asymmetry but did not prove stable/upstream/release status.	Construction logic list cleanup now owns the branch matrix; no branch rescue exists; the one-line SmallSite add-to-remove edit remains future code work.
2026-06-05	Towns, camps and capture, Feature status, Source fix propagation queue	Camp flag texture branch route	The old row was correct for current source but did not show that release Chernarus partially fixed independent capture while release Vanilla and repair-side flag refresh stayed open.	Towns, camps and capture now owns the branch matrix; Feature Status and the propagation queue keep compact code-owner rows.
2026-06-05	Vehicle cargo equip loop bounds, Feature status, Source fix propagation queue, Gear/loadout/EASA atlas	Vehicle cargo loop bounds branch route	Existing wording named the local defect but did not prove upstream/release status or expose it in the main feature register.	Vehicle cargo equip loop bounds now owns the branch matrix; Feature Status carries one compact row; the five loop-bound edits remain future code work.
2026-06-05	Gear template profile filter, Feature status, Source fix propagation queue, Gear/loadout/EASA atlas	Gear template profile branch route	Existing wording named the current defect but did not prove upstream/release status or pair the save/import bugs consistently.	Gear template profile filter now owns the branch matrix; no branch rescue exists, and save-filter replacement plus import guard/default remain paired patch work.

Decision Rules

Action	Use when	Requirement
Keep	The page owns a live system, source-backed bug, release gate or agent-readable artifact.	Keep source paths, branch scope and next action visible.
Condense	The page is useful but repeats a canonical page.	Replace repeated proof with a short summary plus canonical links.
Merge	Two pages answer the same developer question.	Pick one owner and leave the other as a gateway or archive note.
Archive	Material is historical, imported or low-action but still valuable as provenance.	Label it historical and link to the current owner page.
Remove	Content is duplicated elsewhere and has no unique source evidence or provenance value.	Only after confirming no inbound navigation depends on it.

Pruning Backlog Completion State

Priority	Area	Completion state	Evidence / route
P0	`Instructions-For-Codex.md`	Completed	Condensed into a current operating contract; history remains in Wiki quality audit, Deep-review findings, Agent worklog and `agent-events.jsonl`.
P0	Research intake pages	Completed	External research reports is an intake ledger; unique deltas are routed through Deep-review findings, Feature status, subsystem pages and the manifest.
P0	Deep-review findings	Completed	DR evidence is preserved and indexed by finding family; daily work routes through owner pages instead of expanding the ledger.
P1	Progress/status pages	Completed for this pruning goal	Progress dashboard is compacted toward current-state use; long chronology is in Agent worklog, `agent-status.json` and `agent-events.jsonl`.
P1	Imported Miksuu wiki archive	Completed	Archive pages are caveated as historical provenance, routed through Miksuu upstream wiki import and Community & Dev, and demoted from sidebar page-by-page prominence.
P1	Scout-wave pages	Completed	Subagent discovery swarm is a compact gateway; raw chronology stays in Agent worklog, `agent-events.jsonl` and git history.
P2	Overlapping atlases	Completed for the discovered bloat set	Core systems index, Gameplay systems atlas, Feature Status, UI gateways and runtime quick-reference pages have been pruned into owner-page routing.

Decisions

Date	Page	Action	Reason	Preserved evidence / destination
2026-06-23	UI IDD collision repair, Feature status, Source fix propagation queue, RHUD/endgame machine rows	RHUD/endgame title-handle current B74 refresh	Source Fix queue still had 2026-06-14 stable `cf2a6d6a` wording even though the canonical UI owner pages already carried current stable/B69/B74 evidence. This risked making B74's unrelated Chernarus UI additions look like a title-handle fix.	Preserved the existing UI IDD Collision Repair owner page instead of creating another RHUD/endgame page: docs/source `HEAD@92b52e73` is unchanged from `edbd341e` / `b5219d47`; current stable `0139a346`, B69 `8d465fce`, B74 `b23f557f`, Miksuu `b8389e748243`, perf `0076040f` and historical `a96fdda2` all still share `currentCutDisplay` between `OptionsAvailable`/RHUD/action icons and `EndOfGameStats` in both maintained roots. No gameplay source changed.
2026-06-23	Client UI systems, Feature status, Source fix propagation queue, Dead/stale code register, clickable-text machine rows	ClickableText soundPush current B74 refresh	Human-facing rows already treated current stable as fixed, but older machine/dead-code rows still said current stable was malformed. Adjacent B69/B74 also needed to be named so future UI work does not reopen the base-class edit on current stable-shaped refs.	Preserved one canonical Client UI matrix instead of creating a duplicate page: docs/source `HEAD@0bb0f89f` is unchanged from `b5219d47` and still malformed at `Rsc/Ressources.hpp:556`; current stable `0139a346`, B69 `8d465fce` and B74 `b23f557f` carry valid `{"", 0.2, 1}` in both maintained roots; Miksuu `b8389e748243`, perf `0076040f`, historical `a96fdda2` and UI theme branches remain old-shape. No gameplay source changed.
2026-06-05	Commander reassignment call shape, Commander vote/reassignment, Feature status, Source fix propagation queue	Commander reassignment branch route	Commander reassignment wording treated the helper bug as globally current even though stable/upstream/release already fixed helper unpacking, while duplicate notification and UI identity risks remained separate.	Commander reassignment call shape now owns the matrix: current source/Vanilla still need the helper fix; stable/upstream/release have it; duplicate senders, UI row identity and requester authority remain open.
2026-06-05	Factory queue cleanup, Feature status, Source fix propagation queue	Factory queue branch route	Factory queue wording treated `perf/quick-wins` as a general queue cleanup candidate without separating the crewless counter leak from the low-entropy FIFO token or Vanilla propagation.	Factory queue cleanup now owns the matrix: current source/Vanilla/stable/upstream keep both DR-33 issues; `perf/quick-wins` and release Chernarus fix only the crewless counter leak; token cleanup and maintained Vanilla propagation remain open.
2026-06-05	Service menu affordability guards, Feature status, Source fix propagation queue	Service/EASA authority route	Service/EASA affordability wording repeated the same DR-28 risk without saying which branches had partial fixes versus current-source debt.	Service menu affordability guards now owns the branch/root matrix: current source/Vanilla still need action-time guards; stable/upstream only improve button-enable order; release Chernarus is partial rearm/refuel QoL; release Vanilla and exact-funds EASA remain open.
2026-06-05	Feature status, Pending owner decisions, SQF atlas, Server runtime	Server-init bind route	DR-43b duplicate-bind wording was scattered and lacked a branch/root matrix, especially after release Chernarus removed the live duplicates while release Vanilla did not.	Server init bind cleanup now owns the matrix, patch order and smoke scope. Other pages link there and keep only local context.
2026-06-05	Respawn lifecycle, Feature status, PV channel index, Dead/stale code register	MASH decision-route consolidation	Noether's MASH scout confirmed current wiki facts but showed the finding still invited repeated rediscovery: local respawn and shared marker sync are separate.	Respawn and death lifecycle now owns the branch/root matrix and canonical wording. Other pages route there and keep only channel/status/dead-code local context.
2026-06-05	Client UI systems atlas, Feature status, Dead/stale code register, UI IDD collision repair	UI parity consolidation	Stale `RscMenu_Upgrade`, Economy stale IDC writes and duplicate IDDs were each correct but repeated branch caveats in several places. That made it easy for future agents to rediscover the same UI facts separately.	UI resource parity cleanup now owns the branch/root matrix and patch order; owner pages link there and keep only local runtime or repair details.
2026-06-05	Supply mission architecture, Supply scan narrowing, Supply authority cleanup, Feature status	Status-collapse cleanup	Supply pages mixed docs/source propagated status, stable/upstream broad-scan status, release Chernarus cleanup status, release Vanilla drift, dead-twin cleanup and authority work. That made future agents likely to ask "is supply fixed?" repeatedly.	Supply mission architecture now owns the canonical branch/root matrix. Other pages link there and keep only their local role: scan sub-step, implementation playbook or risk register.
2026-06-05	Client UI systems, Feature status, Dead/stale code register	Branch-scope cleanup	The main-menu GPS 17/18 row still looked like a mini-scout lead and did not prove whether stable/upstream/release shared the same handler-only shape.	Owner pages and machine records now say current source/Vanilla, stable, Miksuu upstream and release all keep the router cases while no fixed-string `MenuAction = 17/18` emitter was found in maintained roots. Remaining work is a low-risk UI cleanup or deliberate GPS-control revival, not another broad UI audit.
2026-06-05	External integrations, Dead/stale code register	Contract-scope cleanup	The Extension/DiscordBot rows were correct but still sounded like broad live failure candidates instead of contract-test and stale-copy cleanup work.	Owner pages now distinguish the live display/fallback risk from stale comments/default arrays, keep `TypeNameHandling` security as a separate hardening path, and route the copied DiscordBot `WriteToFile` terrain API as stale shared code while LoadoutManager remains the actual mission writer/propagator.
2026-06-05	Public variable channel index, Dead/stale code register	Branch-scope cleanup	The `ICBM_launched` row already said receiver-only, but future agents still had to recheck stable/upstream/release before deciding retire vs revive.	Owner pages and machine records now say current source/Vanilla, stable, Miksuu upstream and release all keep the receiver-only PVEH and stale handler comments, while no active assignment or `publicVariable "ICBM_launched"` sender was found. The live nuke path remains `NukeIncoming` -> `RequestSpecial ["ICBM", ...]` -> `HandleSpecial "icbm-display"`; remaining work is owner decision plus ICBM smoke.
2026-06-05	Client UI systems, Dead/stale code register	Branch-scope cleanup	The Parameters display `22005` row could still be rediscovered as a missing-control bug because grep sees the old line even though it is block-commented.	Owner pages and machine records now say current source, maintained Vanilla, modded copies, stable/upstream and release all keep the old uptime write comment-only; the live Parameters dialog writes rows through `22003` and has no `22005` control. Remaining work is safe comment cleanup or deliberate uptime-row revival, not another broad UI audit.
2026-06-05	UI IDD collision repair, Client UI systems, Feature status, Dead/stale code register	Branch-scope cleanup	The duplicate UI IDD row still read like an open audit and did not distinguish current-source risk from release-branch partial cleanup.	Owner pages and machine records now say source/stable/upstream keep dialog `23000` and title `10200` collisions; release Chernarus fixes only the EASA/Economy dialog collision by moving EASA to `24000`; release Vanilla and release titles remain duplicated. No current source `findDisplay 23000/10200` caller was found, so remaining work is code-owner parity cleanup or a formal waiver plus smoke.
2026-06-05	Client UI systems, Feature status, Dead/stale code register	Branch-scope cleanup	The Economy IDC issue was already documented, but the P1 row still invited another audit and did not show that release Chernarus partially fixed/rewrote the path while release Vanilla did not.	Owner pages and machine records now route future agents to a UI parity cleanup: compare/import the release Chernarus Economy controller/control-map shape or remove/update stale `23004/23005/23006` writes consistently across maintained roots, then smoke disabled state, income controls, sell mode and supply-truck respawn.
2026-06-05	Respawn lifecycle, Support specials, PV channel index, Feature status, Dead/stale code register	Branch-scope cleanup	The MASH marker relay was already documented as broken, but the P1 backlog still invited another broad discovery pass.	Owner pages now state the branch shape: current source/Vanilla, stable, Miksuu upstream and release all keep the orphaned relay/commented receiver while maintained deploy paths do not send the trigger PV. Remaining work is an owner decision: JIP-safe revive with server-held marker records and delete replay, or retire/archive the stale relay.
2026-06-05	Dead/stale code register, Client UI systems, Upgrades and research, Feature status	Branch-scope cleanup	The stale `RscMenu_Upgrade` finding was repeatedly documented, but it did not clearly say that release Chernarus already removed the class while release Vanilla and current source still carry it.	Owner pages and machine records now route future agents to a parity cleanup: remove or intentionally alias `RscMenu_Upgrade` across maintained roots, then smoke the live `WFBE_UpgradeMenu` path.
2026-06-05	Source fix propagation queue, Current source status, `agent-release-readiness.json`, `agent-context.json`	Release-ledger sync	The dashboard/collaboration smoke lane included commander-built ARTY, but the release-readiness and agent boot files still described only the older propagated-fix set.	Commander-built ARTY is now recorded as docs/source Chernarus plus maintained Vanilla patched, stable/release absent and Arma-smoke-pending. Owner evidence stays in construction/support/testing/Feature Status pages.
2026-06-05	`agent-collaboration.json`	Machine-lane sync	After the dashboard/status smoke-lane sync, the collaboration machine file still scoped `source-propagated-smoke-pending` to the older four owner pages and omitted commander-built ARTY.	`agent-collaboration.json` now names commander-built ARTY in the lane output and includes construction, support, testing and Feature Status owner pages in the source scope.
2026-06-05	Progress dashboard + `agent-status.json`	Smoke-lane sync	Coordination board, Feature status and the construction/support owner pages already included commander-built ARTY as source-patched but Arma-smoke-pending, while the dashboard and compact status only named the other propagated lanes.	The source-propagated smoke-pending lane now names commander-built ARTY alongside client skill init, hosted FPS, supply scan and paratrooper markers. Evidence remains in Construction and CoIn systems, Support specials, Testing workflow and machine backlog rows.
2026-06-05	Coordination board + Progress dashboard	Route refresh	The active `documentation-finisher-loop` row still pointed future agents at Instructions for Codex as if it were a live queue, even though that page had been condensed into an operating contract.	Open docs work now routes through Progress dashboard, this ledger, Feature status, Pending owner decisions, `agent-status.json` and fresh source evidence; Instructions for Codex remains the operating contract.
2026-06-05	Instructions for Codex	Condensed	The old file duplicated completed queue items from Wiki quality audit and Deep-review findings, making new agents start from stale work.	Current loop kept here; old audit history remains in Wiki quality audit, Deep-review findings, Agent worklog and `agent-events.jsonl`.
2026-06-05	External research reports	Condensed / absorbed	The previous page repeated report-by-report synthesis even though the manifest preserves exact metadata and later DR/source checks own the actionable facts.	Replaced with a catch-up absorption matrix. Exact report paths/hashes remain in `external-research-report-manifest.json`; verified facts route to Deep-review findings, Feature status, Networking/PV, Testing workflow and subsystem atlases.
2026-06-05	Deep-review findings	Keep / index	The DR entries are source-cited evidence and false-positive guardrails, but the chronological page is too large as a navigation surface.	Added a current routing index by finding family. Original DR evidence stays on the page; daily work routes through the listed canonical owner pages.
2026-06-05	Subagent discovery swarm	Condensed	Historic scout-wave tables had become a long chronology of mostly harvested or non-evidence starts, slowing readers and risking reopened closed threads.	Promoted findings stay in owner pages, Agent worklog, `agent-events.jsonl` and git history. The swarm page now keeps current state, canonical destinations, harvest state, non-evidence rules and narrow relaunch guidance.
2026-06-05	Miksuu upstream wiki archive + `_Sidebar.md`	Archive / demote from sidebar	The individual `Miksuu-Wiki-Archive-*` pages are valuable provenance, but listing every archive page in the sidebar made historical material look like current implementation docs.	Archive pages stay intact and are linked from Miksuu upstream wiki import and Community & Dev. Sidebar now exposes the archive index, source-check leads and current upstream/history pages only.
2026-06-05	Core systems index + Gameplay systems atlas	Condense / gateway prune	The core index repeated subsystem summaries and made overconfident split-authority claims, while the gameplay atlas repeated mini-atlases for economy, commander, upgrades, construction and factories already owned by dedicated pages.	Core systems is now a route index with gateway rules. Gameplay systems keeps town evidence and balance constants, but routes duplicated implementation walkthroughs to economy, commander, upgrade, construction and factory owner pages.
2026-06-05	Feature status	Condense / route scout harvest	Dated mini-scout waves, duplicate AIBuyUnit/side-supply notes, a stale PR #1 supply-handler defect claim and a trailing deep-audit addendum made the live register read like chronology rather than current triage.	Replaced scout-wave sections with a source-harvest routing matrix, kept AI supply logistics as a config-gated broken feature, corrected PR #1 killed-handler status, removed the duplicate AIBuyUnit row, and routed economy/supply/commander evidence to owner pages.
2026-06-05	UI/runtime quick-reference pages	Condense / gateway prune	The UI and runtime quick-reference pages repeated evidence already owned by Client UI systems atlas, UI IDD collision repair, Server gameplay runtime atlas, Hosted server FPS loop sleep, External integrations and HC failover pages.	UI HUD and dialogs is now a pure alias; Client UI/HUD/menus routes risk families; Player UI workflow map stays a player-clickable tour; Server ops runbook keeps operator contracts; AI runtime/HC loop map and Headless client scaling route generic runtime and implementation-sketch detail to owner pages.
2026-06-05	Progress dashboard + this ledger	Completion audit / compact	After the pruning batches landed, the dashboard and ledger still read like open work existed.	Dashboard now keeps one current completion batch plus compact route links; this ledger records completion state and separates optional future refinements from required pruning-goal tasks.
2026-06-05	Progress dashboard	Current-lane freshness	The `Current Lanes` table had re-accumulated published docs batches and stale "commit/push" next actions, making completed work look active.	`Current Lanes` is now a live control panel only. Published batches remain in Latest Batch, Agent worklog, `agent-status.json`, `agent-events.jsonl` and git history.
2026-06-05	Onboarding pages	Condense / gateway prune	Home, Quickstart, AI Assistant Guide and LLM Agent Entry Pack all partially owned AI boot order, safety rules, current status and routing.	Home is a short front door, Quickstart is the human first-day path, AI assistant guide is a safety gateway and LLM agent entry pack owns canonical AI boot order. Volatile status routes to Progress dashboard, Current source status snapshot, Source fix propagation queue and machine files.
2026-06-05	Agent development pack	Alias / prevent duplicate page	Some prompts ask for an "agent development pack", but the canonical boot-order owner is LLM agent entry pack.	Added a lightweight alias page and wired it into sidebar, MkDocs and `llms.txt`. Do not put boot-order content on the alias; update LLM agent entry pack instead.
2026-06-05	`agent-machine-index.json`	Add compact machine index	Future agents had to open many broad pages to find source refs, owner pages, machine records and next gates.	Added a small page-to-source/risk index plus JSONL vNext envelope convention. Keep it as a lookup table, not another narrative page.

Catch-Up Matrix

Input family	Unique findings left after source-check	Already documented where	Missing destination	Decision
External PDFs and Markdown reports	Mostly corroboration of source-backed DR and subsystem pages; DR-43 remains the notable source-confirmed report-intake delta.	External research reports, Deep-review findings, `external-research-report-manifest.json`	None for broad report prose. Specific new claims need named source targets.	Absorbed; keep metadata and routing only.
Deep-review findings DR-1..DR-47	Source-backed evidence remains valuable; daily readers need owner-page routing.	Deep-review findings, Feature status, Hardening roadmap, subsystem atlases	No new page. Implementation belongs to code-owner playbooks.	Keep evidence ledger; add routing index.
Recent scout waves	Most returned reports either confirmed canonical pages or had selected deltas already promoted. Economy/commander/respawn/runtime/perf interrupted scouts are explicitly non-evidence until relaunched.	Subagent discovery swarm, Agent worklog, owner pages named in the wave tables	Optional future micro-scouts only for narrow unharvested lanes.	Keep current wave summary; avoid duplicate prose.
Miksuu wiki imports and upstream lessons	Valuable provenance and branch/commit lessons; not current implementation truth without repo verification.	Miksuu upstream wiki import, Community & Dev, Upstream changelog feature leads, Developer history and upstream lessons, Upstream Miksuu commit intel	None; current-source caveats are already present.	Keep as archive/provenance; do not sidebar every archive page.
Fresh pruning scouts on 2026-06-05	UI/runtime gateway bloat has been source-checked and pruned. Navigation-chain inconsistencies had a first small fix, and the imported archive pages already carry historical/current-truth caveats.	Client UI/HUD and menus, Client UI systems atlas, Server ops runbook, Server gameplay runtime atlas, Miksuu upstream wiki import, Progress dashboard	None for the current pruning goal. Future page-owner refinements can be reopened with fresh evidence.	Harvested; do not expand gateway pages with duplicate proof.

Completion Audit

Current evidence as of 2026-06-05:

No P0/P1/P2 pruning-backlog row above remains in an open state.
Archive pages are preserved and caveated as historical provenance rather than current implementation truth.
Major holding pages now route to canonical owner pages instead of repeating long scout/report chronology.
The dashboard is compacted back to current-state use; old batches route to Agent worklog, agent-status.json, agent-events.jsonl and git history.
Future gameplay hardening, release smoke and code-owner implementation remain valid project work, but they are not unfinished tasks in this pruning ledger.

Fresh Backlog Lead State

These cleanup leads came from the 2026-06-05 wiki-backlog scout wave. This table records whether each lead is still open so future agents do not reopen work that was already closed by later passes.

Priority	Lead	Current state	Evidence / next action
P0	Reconcile mirror drift before broad edits	Closed / operating rule	Full repo-mirror/wiki checkout SHA parity is now validated after scoped publishes. Keep the file-by-file/no-blind-copy rule, but this is not an open drift task.
P1	Separate machine/state files from human navigation	Closed for current navigation	Humans route through Progress dashboard, Coordination board, Agent worklog and compact indexes; machine files stay linked for agents rather than promoted as normal pages.
P1	Shorten Home and stop overclaiming navigation completeness	Closed for this pruning pass	Home/Quickstart/AI-guide/LLM-pack roles were separated, and the current navigation inventory now verifies `0` `Continue Reading` gaps. Reopen only with a fresh source/navigation contradiction.
P1	Maintain one navigation inventory	Closed / owner page published	Navigation inventory and page status is now the generated-current/archive/machine/hidden navigation owner. Current state: primary Markdown sidebar-only drift `0`; Miksuu archive pages stay MkDocs-visible and sidebar-demoted.
P2	Keep imported/archive and raw scout pages demoted	Closed / standing policy	Miksuu archive pages, DR ledgers, worklog and scout chronology remain reachable through index/status pages rather than first-click sidebar entries.
P2	Reduce onboarding overlap	Closed for this pruning pass	LLM agent entry pack owns canonical AI boot order; Home, Quickstart, AI assistant guide, `llms.txt` and the Agent Development Pack alias are now audience-specific gateways.

Fresh Backlog Progress

Date	Lead	Status	Evidence / next action
2026-06-24	Route PR #74 artillery cooldown HUD after B751b	Completed / validated	Support specials, Client UI systems, Feature Status, Testing workflow and PR cleanup now classify PR #74 / `origin/claude/trello-arty-cooldown-hud@471fc0580fd6` as open draft clean-but-stale-base branch evidence. GitHub is clean, but base/merge-base remain `f8a76de34` while current master is `f39665d79`; base-relative payload is four maintained-root UI files / +134 / -8, clean `git diff --check`, no Modded/Tools/Extension. No standalone PR page was created.
2026-06-24	Clean Source Fix current-stable wording after B751b	Completed / validated	Source fix propagation queue now treats `origin/master@f39665d79` as current stable and reclassifies exact `origin/master@f8a76de34` current-stable phrases as pre-B745/B751b B74.1/B74.2 baseline evidence. The dashboard July hosted-FPS row now says current master plus the old B74.1 snapshot both use one guarded `SERVER_FPS_GUI` publisher, while docs/source keeps the two-publisher compatibility shape. No gameplay source changed.
2026-06-24	Refresh salvage payout B74.2 current-head route	Completed / validated	Construction/CoIn systems, Feature Status, Source Fix queue, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Docs/source `HEAD@408479a914c7` is unchanged from `795cdbbf0` for checked salvage paths; current B74.2 still keeps lowercase `ChangePlayerfunds`, the `updatesalvage.sqf:10` `
2026-06-24	Refresh RequestSpecial upgrade-sync B74.2 current-head route	Completed / validated	Support specials, Upgrades and research, Feature Status, Source Fix queue, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Checked `d472da6a..21b62b04`, `origin/master..origin/claude/b74.2-aicom`, docs-source continuity and B69..B74 diffs are empty for the six maintained-root handler/caller/process paths; the parser remains patch-ready consistency debt because checked refs still mix `_args` and `_this`, while B74.1/B74.2 end-time state is adjacent UI/timer work, not parser cleanup.
2026-06-24	Refresh auto-wall B74.2 current-head route	Completed / validated	Construction/CoIn systems, Server composition spawner reference, Feature Status, Source Fix queue, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Checked `d472da6a..21b62b04` is empty for auto-wall paths; the global-toggle policy remains open because current stable/B74.1/B74.2/B69/B74, docs/source, Miksuu, perf, live auto-countermeasures and historical release evidence all keep one mission-global state with only default/exclusion-list drift.
2026-06-24	Refresh Construction SmallSite B74.2 current-head route	Completed / validated	Construction logic list cleanup, Construction/CoIn systems, Feature Status, Source Fix queue, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Checked `d472da6a..21b62b04` is empty for the four maintained-root SmallSite/MediumSite files; the SmallSite add/add versus MediumSite add/remove logic-list debt remains patch-ready in current docs/source, stable/B74.1/B74.2/B69/B74, Miksuu, perf and historical release evidence.
2026-06-24	Refresh AI supply-truck B74.2 current-head route	Completed / validated	AI commander autonomy, Abandoned feature revival, Feature Status, Source Fix queue, Dead/stale code, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Current stable/B74.1/B74.2/B69/B74 safe-disable the legacy branch; docs/source, Miksuu and perf still raw-spawn the commented worker; no checked ref restores `Server/FSM/supplytruck.fsm`.
2026-06-24	Refresh resource-income B74.2 current-head route	Completed / validated	Economy/Towns/Supply, Resource income tick distribution, Feature Status, Source Fix queue, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Checked `d472da6a..21b62b04` is empty for income paths and constants. Current stable/B74.1/B74.2 keeps the same income tick/display shape; side-supply/team-paycheck cap intent, Chernarus/Vanilla parity, AICOM taper/hybrid/supply-multiplier intent and income-system 4 display math remain open.
2026-06-24	Refresh side-supply B74.2 current-head route	Completed / validated	Economy authority first cut, Resistance supply scaffold, Economy/Towns/Supply, Feature Status, Source Fix queue, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Checked `d472da6a..21b62b04` is empty for side-supply/resistance/reason paths. Current stable/B74.1/B74.2 Chernarus remains a partial rescue; maintained Vanilla, DR-44 validation and reason parsing remain open; `origin/claude/faction-tint-sidefix@32acd272f92e` is a regression warning.
2026-06-24	Refresh SEND_MESSAGE B74.2 current-head route	Completed / validated	Public variable channel index, Networking, Feature Status, Source Fix queue, dashboard and machine rows now replace stale B74.2 `origin/claude/b74.2-aicom@d472da6a` wording with current `origin/claude/b74.2-aicom@21b62b04`. Checked `d472da6a..21b62b04`, `origin/master..origin/claude/b74.2-aicom`, docs-source and B69..B74 diffs are empty for maintained-root `SEND_MESSAGE` paths; DR-46 remains a direct-channel structured-localization/code-owner patch, not a PVF dispatcher task.
2026-06-23	Refresh WASP marker wait current B74.1/B74.2 route	Completed / validated	WASP marker wait cleanup, Performance sweep, WASP overlay, Current Source snapshot, Source Fix queue, dashboard and machine rows now replace stale `origin/master@0139a346` / current-B74 wording with current stable/B74.1 `origin/master@f8a76de34`, current B74.2 `origin/claude/b74.2-aicom@21b62b04` and docs/source `HEAD@c9df2a8b7264` evidence. Current stable/B74.1/B74.2/B69/B74/client-fps keep the display-54 `sleep 0.1` throttle; docs/source, Miksuu and perf remain old-shape patch targets, with marker-dialog smoke still pending everywhere.
2026-06-23	Refresh ClickableText soundPush current B74.1/B74.2 route	Completed / validated	Client UI systems, Feature Status, Source Fix queue, Dead/stale code, dashboard and machine rows now replace stale `origin/master@0139a346` wording with current stable/B74.1 `origin/master@f8a76de34`, visible B74.2 `origin/claude/b74.2-aicom@d472da6a` and docs/source `HEAD@1d4282eca8fd` evidence. Current stable/B74.1/B74.2/B69/B74 keep valid `RscClickableText.soundPush[] = {"", 0.2, 1};` in both maintained roots; docs/source, Miksuu, perf, historical release and UI theme branches remain old-shape.
2026-06-23	Refresh Construction SmallSite current B74.1/B74.2 route	Completed / validated	Construction logic list cleanup, Construction and CoIn systems, Feature Status, Source Fix queue, dashboard and machine rows now replace stale `origin/master@0139a346` wording with current stable/B74.1 `origin/master@f8a76de34` plus visible B74.2 `origin/claude/b74.2-aicom@d472da6a`. The SmallSite add/add vs MediumSite add/remove logic-list debt remains in both maintained roots; current stable/B74.2 construction deltas are unrelated source-Chernarus bank/stat work, not a cleanup rescue.
2026-06-23	Refresh SEND_MESSAGE current B74.1/B74.2 direct-channel route	Completed / validated	Public variable channel index, Networking, Feature Status, Source Fix queue, dashboard and machine rows now replace stale `origin/master@0139a346` wording with current stable/B74.1 `origin/master@f8a76de34`, visible B74.2 `origin/claude/b74.2-aicom@d472da6a` and docs/source `HEAD@cd9ba541d583` evidence. The checked maintained-root `SEND_MESSAGE` paths are unchanged across old-docs, old-stable-to-current, current-to-B74.2 and B69/B74 diffs; DR-46 remains a direct-channel structured-localization/code-owner patch, not a PVF dispatcher task.
2026-06-23	Route PR #79 artillery UX branch intel	Completed / validated	Support specials, Client UI systems, Feature Status, Testing workflow branch-only smoke pack, release-readiness gates, dashboard and machine rows now classify draft PR #79 / `origin/claude/trello-artillery-ux@c4459d4312ef` as branch-only artillery UX/marker-cleanup evidence. Payload is eight maintained-root files / +100 / -20 on current stable merge-base `origin/master@f8a76de34` with `git diff --check` clean; promotion needs range-row, gun-count, caller-disconnect/JIP marker cleanup, forged cleanup-tag and maintained Vanilla smoke before stable wording.
2026-06-22	Refresh Server Init duplicate-bind branch route	Completed / validated	Server init bind cleanup, Feature status, Hardening roadmap and machine rows now separate old-shape docs/source/Miksuu/perf-Vanilla targets from current stable/B69/B74 one-live-bind targets. Docs/source `HEAD@d830379768` and current Miksuu `b8389e748243` keep duplicate `LogGameEnd`/`PlayerObjectsList`/`AwardScorePlayer` binds at `Init_Server.sqf:64,89`, `:69,91`, `:83,93`; current stable `origin/master@0139a346` keeps one live bind at `:81,:86,:99`; current B69/B74 keep `:83,:88,:101`; perf is Chernarus-only fixed; historical `a96fdda2` is not a live `release/*` head.
2026-06-22	Refresh client Skill_Init current branch route	Completed / validated	Client skill init idempotency, Feature status, Source fix propagation queue, Current source snapshot, Testing workflow and machine rows now separate docs/source, current stable/B69/B74/client-fps, historical release-line and old-shape refs. Docs/source `HEAD@b2738971` has `Init_Client.sqf:547,571`; current stable `origin/master@0139a346` has `:624,647`; B69/B74 have `:805,828`; client-fps has Chernarus `:613,636` and Vanilla `:583,606`; Miksuu/perf/historical feat-ai still duplicate.
2026-06-22	Refresh MASH marker current-B69 head route	Completed / validated	Respawn and death lifecycle, Abandoned feature revival, Public variable channel index, Feature status, Dead/stale code register and machine rows now route MASH deploy/marker status through current B69 `origin/claude/b69@8d465fce`: docs/source `HEAD@2b513921` is unchanged from `db3015f18ea3` for checked MASH paths, old-shape docs/Miksuu/perf roots keep local deploy plus orphaned marker relay, and current stable/historical/current-B69 roots remove the maintained deploy/module path. Older `0a1ccb4d` and `80d3267c` B69 refs are provenance only.
2026-06-22	Refresh B69/Takistan AI commander current-head route	Completed / validated	Feature status, AI commander B69 roadmap, AI commander autonomy audit, B69 implementation sketches and PR cleanup lab now route PR #50 as branch-only current B69 evidence: `origin/claude/b69@b8530477` merged `claude/tk-aicom-port@3b1106a1`, `39eed5c0..b8530477` is 22 maintained Vanilla/Takistan files / +2499 / -147, and B69 is branch-propagated across current Chernarus plus maintained Vanilla/Takistan but still not master/stable or Arma-smoked proof.
2026-06-14	Route lifecycle boot flags through canonical wait-chain	Completed / validated	Mission entrypoints and lifecycle now names current source scope, corrects generated `version.sqf` checkout wording and removes the duplicated boot-flag mini-table in favor of Lifecycle wait-chain. Lifecycle wait-chain carries the canonical producer/consumer matrix and updated current-checkout line refs.
2026-06-05	Source-check stale `RscMenu_Upgrade` branch scope	Completed / validated	Dead/stale code register, Client UI systems, Upgrades and research and Feature status now record the branch split: release Chernarus removed the class in `460c0312`, but current source/stable/upstream and release Vanilla still need a consistent cleanup or alias decision.
2026-06-05	Add commander-built ARTY to release-readiness source-only fixes	Completed / validated	Source fix propagation queue, Current source status, `agent-release-readiness.json` and `agent-context.json` now include commander-built ARTY as present in docs/source Chernarus plus maintained Vanilla source, stable/release absent and Arma-smoke-pending.
2026-06-05	Sync collaboration machine lane for commander-built ARTY	Completed / validated	`agent-collaboration.json` now matches Progress dashboard, Coordination board and `agent-status.json` for the `source-propagated-smoke-pending` lane.
2026-06-05	Sync commander-built ARTY into propagated smoke lane	Completed / validated	Progress dashboard and `agent-status.json` now match Coordination board: commander-built ARTY remains source-patched/smoke-pending, not release-complete. Canonical evidence stays in Construction and CoIn systems, Support specials, Testing workflow and Feature status.
2026-06-05	Refresh Progress Dashboard footer after bottleneck demotion	Completed / validated	Progress dashboard `Continue Reading` now routes to Coordination board instead of the demoted Bottleneck removal queue.
2026-06-05	Demote old bottleneck lane page into a supporting checklist	Completed / validated	Bottleneck removal queue no longer claims `bottleneck-reducer-progress-accelerator` as active. It now points active work back to Progress dashboard, Coordination board, this ledger, Feature status, Pending owner decisions and `agent-status.json`.
2026-06-05	Remove remaining `Codex queue` wording from the wiki consistency audit footer	Completed / validated	Wiki/source consistency findings now routes readers to Progress dashboard for live work and Instructions for Codex as the operating contract.
2026-06-05	Refresh coordination board open-task route after `Instructions-For-Codex` condensation	Completed / validated	Coordination board and Progress dashboard now route the active docs loop through current-state surfaces instead of an already-condensed instruction page.
2026-06-05	Refresh dead-code OA compatibility scan after docs growth	Completed / validated	Dead/stale code register now matches the rerun `docs/analysis/dead-code-oa-compatibility-scan.json`: `3205` text files scanned, `0` code-risk implementation hits, `416` docs/reference hits and `1132` OA-safe inverse-trap hits. The runbook now uses `pwsh` because Windows PowerShell 5.1 cannot run the scanner's `System.IO.Path.GetRelativePath` call.
2026-06-05	Harvest final old-BE/current-Wasp FPS scout without report bloat	Completed / validated	Final report `C:\Users\Steff\Documents\Codex\2026-06-05\wasp-old-mission-fps-opportunity-window\outputs\Old-BE-vs-Current-Wasp-FPS-Opportunity-Scout.md` is represented as compact deltas only: Old WarfareBE comparison, Performance sweep, Testing workflow, Feature status and dashboard/status records now treat `old-be-current-wasp-fps-opportunity-scout-2` as returned/harvested.
2026-06-05	Add server runtime/operations gateway without duplicating owners	Completed / validated	Server runtime and operations now catches broad prompts and routes them to Server gameplay runtime atlas, Server ops runbook, integrations, authority, HC, performance and testing pages. Sidebar, MkDocs, `llms.txt`, Home, `agent-context.json`, `agent-machine-index.json` and Navigation inventory were updated.
2026-06-05	Compact harvested FPS helper lanes out of live dashboard	Completed / validated	Progress dashboard, `agent-status.json` and `agent-collaboration.json` no longer show `old-be-wasp-fps-archaeology` or `old-vs-current-fps-opportunity-scout` as live lanes after their findings were harvested. History remains in Agent worklog and `agent-events.jsonl`.
2026-06-05	Clean old-FPS provenance drift	Completed / validated	Old WarfareBE performance comparison no longer names an old docs-only commit as if it were the current Wasp source baseline. It routes current truth through source paths and Current source status snapshot; `agent-machine-index.json` metadata was refreshed after the FPS opportunity harvest.
2026-06-05	Harvest old-vs-current FPS opportunity audit	Completed / validated	The second FPS scout report at `C:\Users\Steff\Documents\Codex\2026-06-05\wasp-old-vs-current-fps-investigation\outputs\Old-BE-vs-Current-Wasp-FPS-Opportunity-Audit.md` is promoted as compact deltas, not mirrored wholesale: Performance sweep, Player AI caps, Old WarfareBE comparison, Testing workflow, Feature status and `agent-machine-index.json` carry the actionable pieces.
2026-06-05	Sync release-head machine ledgers after `3282ff3f` spot-check	Completed / validated	Live machine rows in `agent-feature-status.jsonl`, `agent-hardening-backlog.jsonl` and `agent-release-readiness.json` now use current `origin/release/2026-06-feature-bundle` head `3282ff3f` for propagated-fix lane status. Older `a9219d88` knowledge records remain append-only history, superseded by the newer release-head spot-check.
2026-06-05	Spot-check propagated-fix lanes at current release head and harvest old-BE FPS report	Completed / validated	Current source status snapshot now states that `origin/release/2026-06-feature-bundle` head `3282ff3f` keeps the same hosted-FPS, supply-scan, client `Skill_Init` and paratrooper-marker outcomes as the earlier `a9219d88` matrix. The delegated FPS report was promoted only as compact deltas in Old WarfareBE performance comparison, Player AI caps, Performance sweep and Testing workflow.
2026-06-05	Refresh PR8 release-head evidence after refetch	Completed / validated	PR cleanup lab now has a compact `3282ff3f` addendum for the four newer release-head commits after `a9219d88`: WF menu player/town counts, service-point full/refuel QoL, shielded HQ walls and the PR8 static smoke script. Testing workflow now routes `Tools\SmokeTests\Test-PR8StaticSmoke.ps1` as Chernarus/static-only preflight, not runtime proof.
2026-06-05	Refresh community/upstream head provenance wording	Completed / validated	Community & Dev and Developer history now separate the older `8bcc42b1` evidence pass from the current `69e1958a` / `e4be1958` upstream-candidate addendum. This prevents stale point-in-time history from reading like current upstream head truth.
2026-06-05	Intake new Miksuu town-capture state fix	Completed / validated	New upstream commit `e4be1958` is now documented as a source-unmerged candidate: it clears previous-side active town-AI state on capture in both Chernarus and maintained Vanilla Takistan. Canonical detail lives in Upstream Miksuu commit intel and Towns/camps/capture; Feature status and Testing workflow carry the import/smoke gates.
2026-06-05	Refresh current source-status branch-head routing	Completed / validated	Current source status snapshot now has a dated refetch delta for moved docs, release and upstream heads. It keeps the old matrices as point-in-time source evidence and routes new release/upstream commits to future owner-page review instead of silently treating them as current gameplay truth.
2026-06-05	Refresh Bottleneck Queue validation state	Completed / validated	Bottleneck removal queue now reflects current docs validation practice: repo wiki validation, JSON/JSONL parse, `git diff --check`, wiki-checkout validation and full SHA parity. It no longer presents mirror parity as only a 2026-06-03 required future action.
2026-06-05	Keep Progress Dashboard latest batch compact	Completed / validated	Progress dashboard now keeps only the most recent five published batches in `Latest Batch`; older published work routes to Agent worklog, Discovery swarm, `agent-status.json`, `agent-events.jsonl` and git history.
2026-06-05	Harvest returned old-FPS scout addendum without report bloat	Completed / validated	The read-only scout returned useful deltas but no durable files. Owner pages now carry the compact additions: duplicate FPS publisher consumer caveat, current `publicVariableServer` routing nuance, delegated town-AI non-global init optimization, AntiStack/PerformanceAudit A/B variable, static-defense HC readback caution and the easy-win bundle. No new chronology/report page was added.
2026-06-05	Route old-WarfareBE FPS findings into triage and agent boot files	Completed / validated	Feature status now has a compact old-WarfareBE FPS baseline row that points to Old WarfareBE performance comparison instead of repeating the report. LLM agent entry pack, `agent-machine-index.json`, `agent-context.json` and `agent-feature-status.jsonl` now route FPS/old-mission/AI-cap prompts to the canonical page and matched A/B test gate.
2026-06-05	Refresh navigation inventory after old-FPS page	Completed / validated	Navigation inventory and page status now reflects the post-Old WarfareBE performance comparison state: `143` Markdown pages, `141` content pages, `114` sidebar links including `llms.txt` and `agent-machine-index.json`, `122` MkDocs entries including `llms.txt`, `112` primary Markdown pages in both navs, `20` intentional neither-nav support pages and `0` missing `Continue Reading` blocks. Removed stale neither-nav wording for broad owner pages that had already been promoted.
2026-06-05	Add old WarfareBE FPS comparison without bloating performance pages	Completed / validated	Added Old WarfareBE performance comparison as the canonical old-vs-current FPS archaeology page, then linked it from AI, headless and performance, Performance opportunity sweep, Player AI caps and role balance, sidebar, MkDocs and `llms.txt`. This keeps the Discord/community debate in one source-backed page instead of spreading duplicate old-mission claims across performance docs.
2026-06-05	Guard old worklog rows as append-only history	Completed / validated	Agent worklog now opens with a current-truth guardrail and routes readers to Progress dashboard, Current source status snapshot, `agent-status.json` and `agent-knowledge.jsonl` before treating old historical rows as live state.
2026-06-05	Close Wiki Source Consistency Cluster B/C path and line-drift residue	Completed / validated	Wiki/source consistency findings now records Cluster B/C as closed for current docs drift. PV/channel, lifecycle, SQF and victory owner pages carry the corrected source anchors; `agent-context.json` no longer says DR-2 paratrooper markers are current-source-unpatched, and `agent-knowledge.jsonl` now has a 2026-06-05 branch-scoped source-truth supersession for older June 2 rows.
2026-06-05	Close Wiki Source Consistency Cluster A current-state contradiction risk	Completed / validated	Wiki/source consistency findings now records Cluster A as closed for docs drift: current owner pages say commander reassignment and factory queue cleanup are source-unpatched code-owner work, while paratrooper marker registration is branch-scoped/source-propagated with smoke/release gaps still visible.
2026-06-05	Close Wiki Source Consistency Batch 3 routing residue	Completed / validated	Old Batch 3 content-loss warnings are now historical: Construction and CoIn systems atlas owns construction detail, respawn selector detail routes through client UI and respawn lifecycle pages, lifecycle time-sync line drift is corrected, and the LoadoutManager `FileManager.cs` source path in `agent-machine-index.json` now matches current source. The SmallSite add/add defect remains a code-owner patch candidate, not a docs blocker.
2026-06-05	Maintain one navigation inventory	Completed / validated	Navigation inventory and page status records current sidebar, MkDocs, neither-nav and `Continue Reading` gaps. Later passes closed primary sidebar-only Markdown drift, kept `agent-machine-index.json` as the only intentional sidebar-only machine link, kept MkDocs-only Miksuu archive pages grouped under archive navigation, and classified all 20 neither-nav support pages.
2026-06-05	Close remaining `Continue Reading` gaps	Completed / validated	Queue pages now route back to owning indexes, and imported Miksuu archive pages use archive-chain `## Continue Reading` blocks that preserve the historical-provenance caveat. Recomputed missing count: `0`.
2026-06-05	Resolve primary sidebar-only MkDocs drift	Completed / validated	Added PR cleanup lab, Headless client scaling, Dead/stale code register and this ledger to `mkdocs.yml`. Primary Markdown sidebar-only drift is `0`; `agent-machine-index.json` is an intentional sidebar-only machine-file link.
2026-06-05	Promote hidden broad owner/reference pages	Completed / validated	Added Core systems, Modules atlas, Server runtime, Performance opportunity sweep, Player AI caps, Variable conventions and Arma 2 OA external reference guide to both sidebar and MkDocs. Neither-nav count drops from `27` to `20`; remaining neither-nav pages are archives, prompts, old queues, analysis notes or narrow patch handoffs.
2026-06-05	Classify remaining neither-nav support pages	Completed / validated	Navigation inventory now lists the remaining 20 neither-nav pages by status: `patch-ready`, `archive/evidence-ledger`, `agent-instruction` and `analysis-support`. This makes the remaining hidden pages intentional instead of untriaged drift.
2026-06-05	Keep dashboard current lanes fresh	Completed / validated	Progress dashboard now keeps `Current Lanes` limited to active/watchlist/code-owner/release-smoke lanes. Completed published batches route through Latest Batch, Agent worklog, machine status files and git history instead of remaining in the live lane table.
2026-06-05	Shorten onboarding gateways and stop boot-order duplication	Completed / validated	Home, Quickstart, AI assistant guide, LLM agent entry pack and `agent-entrypoint.json` now separate front-door, human first-day, AI safety, canonical AI boot order and machine-bootstrap roles.
2026-06-05	Add Agent Development Pack alias	Completed / validated	Agent development pack now exists as a compatibility alias to LLM agent entry pack.
2026-06-05	Add compact page-to-source machine index	Completed / validated	`agent-machine-index.json` maps high-risk/high-traffic systems to canonical docs, source refs, machine refs, branch scope and next gate. It also records the JSONL vNext envelope convention so new machine rows are more consistent without rewriting legacy records, and Navigation inventory marks it as the one intentional sidebar-only machine-file link.
2026-06-05	Refresh stale PR board state	Completed / validated	PR cleanup lab now reflects current GitHub metadata after the board cleanup: closed docs/feature PRs are no longer shown as open, PR #8 remains the bundle baseline, `dev/pr8-plus-testbed` remains the combined lab branch and synthetic `origin/pr/*` refs are documented as pruned.
2026-06-05	Route July update candidates out of dashboard-only state	Completed / validated	The two July dev branches now have owner-page and machine routes through Hardening roadmap, Testing workflow, `agent-machine-index.json` and `agent-release-readiness.json`. No gameplay source changed.
2026-06-05	Trim dashboard Latest Batch back to newest five	Completed / validated	Progress dashboard now matches its own compact-current-state rule again: `Latest Batch` keeps the newest five rows, while `old-fps-provenance-cleanup` is preserved under recently closed items, Agent worklog, `agent-events.jsonl` and git history.
2026-06-05	Promote worklog timestamp-order guardrail	Completed / validated	Agent worklog now warns in its top `Read This First` block that visible order is not strict timestamp order; future agents should use explicit timestamps plus current-state files instead of reopening superseded chronology.
2026-06-05	Close stale tooling release status warning	Completed / validated	Tooling release readiness audit no longer tells agents to update old `agent-status.json` propagation wording; the current status file already routes propagated lanes as smoke pending.
2026-06-05	Close stale Wiki Quality Audit Round 2 items	Completed / validated	Wiki quality audit now marks its old Round 2 Codex-lane items resolved where current owner pages already carry the requested DR links, dated SQF recount, current coordination state and sidebar de-dupe.
2026-06-05	Close mirror drift and stale SQF count audit residue	Completed / validated	Full repo-mirror/wiki checkout SHA256 parity now reports `full-diffCount=0`; Wiki mirror reconciliation plan records that evidence, and Wiki/source consistency findings marks the old SQF compile-count warning closed by the current dated SQF atlas recount. Validation passed.
2026-06-05	Route empty supply-truck cleanup status without a new page	Completed / validated	The existing compact Feature Status note is now a branch matrix in Marker cleanup/restoration, with Source fix propagation queue, dashboard/status files and machine ledgers linking there. This avoids a standalone cleanup page while preserving current/stable/upstream/perf/release evidence and the future keep-and-label versus parameterized-timeout decision.
2026-07-02	Close stale current-target status for `SEND_MESSAGE`, side-supply and AICOM donation	Completed / validated	Public variable channel index, Networking/public variables, Hardening roadmap, Feature status, Source fix queue, Economy authority, Server authority map and machine rows now reflect `origin/claude/build84-cmdcon36@6f2fc4bd`: `SEND_MESSAGE` no-compile is source-present, side-supply clamp/shape/reason is source-present while requester/server-ledger authority remains open, and AICOM donation double-debit is fixed while PR #202-style donor guards remain separate. No gameplay source changed.

Agent Guidance

Before adding a new page, answer:

Which existing page would a developer open first?
Is this a new source-backed fact or just another explanation?
Can the finding be a short section, table row or machine record instead?
What exact source path, branch or verified DR record makes it trustworthy?
What should a future agent delete or condense after this is absorbed?

Continue Reading

Previous: Wiki quality audit | Next: Progress dashboard

Main map: Home | Agent instructions: Instructions for Codex | Research intake: External research reports

Shelved AICOM concepts - revivable someday ideas (owner-shelved 2026-07-03)

Docs rule: source-backed claims only; Arma 2 OA scripting docs only; gameplay edits start in Missions/[55-2hc]warfarev2_073v48co.chernarus.

Wiki Pruning And Relevance Ledger

Wiki Pruning And Relevance Ledger

Recent Pruning Decisions

Decision Rules

Pruning Backlog Completion State

Decisions

Catch-Up Matrix

Completion Audit

Fresh Backlog Lead State

Fresh Backlog Progress

Agent Guidance

Continue Reading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!