Progress Dashboard

Progress Dashboard

This is the shared human + AI interface for seeing what Codex, Claude and Codex sub-agents are doing right now.

Keep this page open when parallel documentation work is running. It links to the live board, event feed and compact JSON status files without forcing readers through the whole sidebar.

What this page is

• Shared source-of-truth for lane state, active owners and recently validated work.
• Human + AI handoff surface for current ownership and next action.
• Quick index for where to read next when a lane claims changes.

Where this dashboard lives

• Wiki page: docs/wiki/Progress-Dashboard.md
• Runtime state files: agent-status.json, agent-events.jsonl, agent-knowledge.jsonl
• Coordination board: Coordination-Board.md
• Source of truth pointers: agent-context.json

How to use this page

1. Start with At A Glance to find active lanes and owners.
2. Read Latest Batch for the newest validated status update only.
3. Use Current Lanes to separate active docs work, watchlists and future code-owner work.
4. Use Agent worklog, Discovery swarm and agent-events.jsonl for historic scout detail.

Latest Batch

Lane	Status	Output
commander-arty-current-b69-marker-refresh-2026-06-22	Published / validated	Refreshed Construction and CoIn commander ARTY scope, Feature status, Source fix propagation queue, Testing workflow, Current source snapshot and machine rows with current stable/B69/B74 marker-path evidence. Docs/source HEAD@f5bcaf91 is unchanged from 4bd37b98 for checked commander ARTY paths and keeps the commander-team gunner handoff at Construction_StationaryDefense.sqf:91-94. Current stable origin/master@0139a346, current B69 origin/claude/b69@8d465fce and adjacent B74 origin/claude/b74-aicom-spend@b23f557f use marker discovery at Construction_StationaryDefense.sqf:166-168 plus Common_GetTeamArtillery.sqf:46,56; historical a96fdda2 / 7ff18c49 uses :133-135; current Miksuu/perf keep old DefenseTeam-only discovery. No gameplay source changed.
vote-help-router-current-b69-head-refresh-2026-06-22	Published / validated	Refreshed Client UI vote/help/main-menu matrix, Feature status, Source fix propagation queue and machine rows with current B69/B74 evidence. Docs/source HEAD@087152f5 is unchanged from 68bd4dc5 for checked vote/help/router paths. Current stable origin/master@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. Stable/B69/B74 move visible action 19 to GPS enablement but do not rescue old zoom handlers; B69/B74 checked path delta is empty. No gameplay source changed.
salvage-w10-branch-status-refresh-2026-06-22	Published / validated	Refreshed Construction and CoIn salvage, Feature status, Source fix propagation queue, AI commander treasury accessors and machine rows after fresh fetch exposed live origin/claude/salvage-w10-manfilter@2e0242b3. Docs/source HEAD@98eb9607 is unchanged from fb8d4ebc for checked manual/truck salvage files; current stable origin/master@0139a346, current B69 8d465fce, adjacent B74 b23f557f, current Miksuu b8389e748243, perf 0076040f and historical a96fdda2 still keep lowercase ChangePlayerfunds, updatesalvage.sqf:10 OR-loop and client-local delete/reward in both maintained roots. The live salvage branch is older B39/GUER-based evidence with merge-base 8fac20df; it changes only AI_Commander_Wildcard.sqf in both maintained roots, adding !(_wk isKindOf "Man") to inert W10 at :794, and does not rescue manual/truck payout or authority. No gameplay source changed.
attack-wave-authority-current-b69-head-refresh-2026-06-22	Published / validated	Refreshed Attack-wave authority playbook, Feature status, Source fix propagation queue, Public variable channel index, Server authority migration map and machine rows with current B69 origin/claude/b69@8d465fce evidence. Docs/source HEAD@1c1ea559 is unchanged from f3e157f2 for checked attack-wave request/detail/client-price paths. Current stable origin/master@0139a346, current B69, current Miksuu b8389e748243, perf 0076040f, historical a96fdda2, historical c20ce153 and historical 994150da all keep ATTACK_WAVE_INIT side/supply trust plus ATTACK_WAVE_DETAILS side/modifier/duration trust in both maintained roots. B69 path deltas 0a1ccb4d..8d465fce and b8530477..8d465fce are empty for checked attack-wave request/detail/client-price paths. 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.
commander-reassignment-current-b69-head-refresh-2026-06-22	Published / validated	Refreshed Commander reassignment call shape, Commander vote/reassignment, Feature status, Source fix propagation queue and machine rows with current B69 origin/claude/b69@8d465fce evidence. Docs/source HEAD@337ed166 is unchanged from b44aaaf8 for checked reassignment paths and still uses _side = _this in both maintained roots. Current stable origin/master@0139a346, current B69, current Miksuu b8389e748243, perf 0076040f, historical a96fdda2 and historical c20ce153 fix the helper shape in maintained roots, while duplicate reassignment notifications, visible-name UI selection, requester authority and stable/B69 full modded fork drift remain open. No gameplay source changed.
Older published batches are intentionally omitted from this table. Use Agent worklog, Discovery swarm, agent-status.json, agent-events.jsonl and git history for the long audit trail.

At A Glance

Actor	Status	Current lane	What to expect next
Codex	Ready	documentation-finisher-loop	Latest published lane: commander-arty-current-b69-marker-refresh-2026-06-22. Continue bounded source-backed docs passes from this dashboard, the refreshed PR cleanup lab, Feature Status, Source Fix queue and pruning ledger.
FPS scout window	Returned / harvested	old-be-current-wasp-fps-opportunity-scout-2	Final report returned at C:\Users\Steff\Documents\Codex\2026-06-05\wasp-old-mission-fps-opportunity-window\outputs\Old-BE-vs-Current-Wasp-FPS-Opportunity-Scout.md and has been compacted into the old-BE, performance, testing and Feature Status owner pages.
Codex-2	Ready	None	Pick a bounded source-backed lane from PVF dispatcher lookup, commander reassignment call-shape repair, remaining supply authority hardening, or another current-head status refresh.
Claude	Autonomous-ready	collaboration-follow-autonomous-ready	Coverage Ledger navigation is wired. Claude can self-select the next bounded source-backed review from the ledger or hardening backlog.
Supported docs agents	First batch published / historical	research-catchup-synthesis-default-supported, relevance-pruning-and-archive-default-supported	Earlier account-default helper chats produced catch-up and pruning/archive work. Relaunch or resume only for a fresh narrow lane; they are not live dashboard blockers.
Read-only pruning scouts	Returned / harvested	ui-runtime-bloat-scout, wiki-navigation-chain-scout	UI/runtime lead is promoted; small navigation fixes are promoted; remaining archive-page caveat note is already satisfied by archive page headers.
Sub-agents	Returned / closed	navigation-parity-and-scout-wave-2026-06-04	Supports, UI, tooling and AI scouts returned; most findings confirmed existing owner pages. Economy scout was closed without output and is not evidence.
Shared docs	Live	GitHub wiki + docs mirror	Wiki and mirror should stay in parity after scoped validation; use event logs and git history for commit IDs.

One-Link Check

Need	Link
Human progress page	Progress dashboard
Sub-agent swarm board	Discovery swarm
Detailed coordination page	Coordination board
Machine progress file	agent-status.json
Active lanes and ownership	agent-collaboration.json
Agent-readable knowledge records	agent-knowledge.jsonl
Agent-readable hardening backlog	agent-hardening-backlog.jsonl
Compact machine index	agent-machine-index.json
Agent release readiness ledger	Agent release readiness ledger
Latest event stream	agent-events.jsonl
Dated narrative notes	Agent worklog
External report intake	External research reports
External report manifest	external-research-report-manifest.json
Pruning and relevance decisions	Wiki pruning and relevance ledger

Current Lanes

This table is only for active, autonomous-ready, watchlist or future owner lanes. Published documentation batches are recorded in Latest Batch, Agent worklog, agent-status.json, agent-events.jsonl and git history.

Lane	Owner	Status	Next action
documentation-finisher-loop	Codex	Active / ongoing	Use this dashboard, Coordination board, Wiki pruning ledger, Feature status, Pending owner decisions, machine status files and fresh source evidence as the live open-task route.
autonomous-claude-research	Claude	Autonomous-ready	Self-select the next bounded source-backed review from Codebase coverage ledger when Claude is active.
feature-status-reconciliation	Codex / future agent	Watchlist	Fold newly confirmed findings into Feature status, owner pages and machine records. No untriaged finding is blocking this dashboard.
indicator-exploration-backlog	Codex / future UI scout	Matrix seeded; status counters refreshed	Use the seeded indicator surface matrix to pick the next family after the status-counter split, then do branch/root validation, owner-page integration or pruning; do not restart a broad "all indicators" checklist.
implementation-hardening-from-backlog	Future code owner	Owner decision / code lane	Pick implementation work from agent-hardening-backlog.jsonl only when Steff asks for gameplay patches or a code owner claims the work.
testing-debugging-release-workflow	Codex / future tester	Published release gate	Use Testing workflow to distinguish source review, propagated source fixes and actual Arma smoke evidence.
source-propagated-smoke-pending	Future tester / release owner	Smoke pending	Client skill init, hosted FPS, supply scan, paratrooper markers and commander-built ARTY are tracked in owner pages and Feature Status; they are not dashboard cleanup blockers.
wasp-marker-wait-cleanup	Future code owner	Source needs code	WASP marker wait cleanup remains a tiny patch-ready opportunity, not an active docs lane.

July Update To-Do

#	Item	Dev branch	Scope	LOC estimate	Status	Validation gate
1	Hosted Server FPS Loop Fix	planned dev/july-update-hosted-server-fps-loop-fix	Adopt/verify the DR-19 hosted/listen busy-spin fix for the July update target. Choose the target branch shape deliberately: current stable origin/master@0139a346 already uses one guarded SERVER_FPS_GUI publisher, while docs/source keeps two guarded compatibility publishers.	~5-20 LOC for a two-publisher loop guard on old-shape refs; ~20-50 LOC if cleanup/consolidation is included.	Queued for July update, but no current remote origin/dev/july-update-hosted-server-fps-loop-fix head was found on 2026-06-22. Create or restore the branch before code work.	Target-branch-specific: current-stable-shaped branch keeps dedicated SERVER_FPS_GUI publishing and no monitor loop; docs/source-shaped branch keeps SERVER_FPS_GUI plus WFBE_VAR_SERVER_FPS. In all cases, hosted/listen runs do not spin FPS publisher loops and Chernarus/maintained Vanilla parity is named before release wording.
2	Takistan Airfield FPV Drone Bay	origin/dev/july-2026-update@e3f530ed planning route; no current origin/dev/july-takistan-airfield-fpv-drone head found on 2026-06-22	Add neutral captured-airfield objectives on Takistan. Use runway-edge capture placement plus a bunker/camp-gated Drone Bay near each hangar; unlock player-funded FPV drones with UAV/EASA progression, one active drone per player, side-wide cap, center-map boundary kill, no base sniping and AA/radar counterplay. Normal aircraft hangar use stays ungated.	~350-700 LOC prototype; ~1000-1800 LOC for a July-quality server-authoritative Takistan-only version, plus mission.sqm object edits.	Queued as planning only. Closed draft PR #21 routes dev/july-2026-update@e3f530ed to release/2026-06-feature-bundle; docs/july-2026-update.md is a roadmap scaffold and states no gameplay code yet. The old per-feature branch name is not a current remote head.	Create or restore an implementation branch before code work, then run Takistan boot/capture/JIP smoke; economy smoke for $50 per player per cycle; UAV/EASA gate smoke; server-side ownership/funds/cap/tier/range rejection tests; base-protection and AA/radar counterplay smoke.

Recently Closed / Reclassified Open Items

• AICOM deploy PR board route: PR cleanup and integration lab was refreshed on 2026-06-21. PR #35 and deploy-child PR #34/#36-#39/#41 are closed history, PR #29 and PR #31 merged on 2026-06-17, PR #40 remains open but stacked on a closed base, PR #43 is the current open master-target soak/proposals route and PR #9 remains the separate Zargabad map/content lane.
• Salvage payout/loop branch scope: Construction and CoIn systems, Feature status and Source fix propagation queue now treat salvage as inherited current-source/current-stable debt: docs branch fb8d4ebc, current stable origin/master@0139a346, current Miksuu b8389e748243, perf 0076040f and historical release commit a96fdda2 all keep the lowercase payout call, || loop and client-local deletion/reward shape; current origin has no live release/* or feat/*salvage* head.
• Camp flag texture branch scope: Towns/camps/capture, Feature status and Source fix propagation queue now distinguish stable/release independent-capture fixes from docs checkout/Miksuu/perf old-owner shapes; repair-side world-flag refresh remains code-owner work everywhere checked.
• Coverage Ledger navigation request: Home, _Footer.md, llms.txt and agent-context.json already linked it; _Sidebar.md now links it too, and the Coordination Board mailbox is marked done.
• Dead-code OA compatibility scan refresh: Dead/stale code register and docs/analysis/dead-code-oa-compatibility-scan.json now reflect the latest docs tree; the scan still reports 0 code-risk implementation hits.
• Final old-BE/current-Wasp FPS scout: old-be-current-wasp-fps-opportunity-scout-2 returned and was harvested into Old WarfareBE comparison, Performance sweep, Testing workflow and Feature status. It is no longer a live lane.
• Old FPS provenance cleanup: Old WarfareBE comparison already routes current Wasp truth through source paths and Current source status snapshot; it is no longer a Latest Batch row.
• OA object-lifecycle command addendum: the old Codex-2 active claim is closed into Arma 2 OA command version reference, covering createVehicle, createUnit, deleteVehicle, hideObject / enableSimulation and the A3-only *Global variants.
• Old BE/FPS helper windows are harvested and no longer live dashboard lanes. Their outputs route through Old WarfareBE comparison, Player AI caps, Performance sweep, Testing workflow, Feature status, Agent worklog and agent-events.jsonl.
• Old ready-for-review rows for PVF dispatch, victory/endgame and factory/purchase are no longer dashboard blockers. Their findings are published and integrated; next work is code-owner implementation or validation.
• Historic scout waves are closed, harvested or non-evidence until relaunched. Their detail belongs in Discovery swarm, Agent worklog and agent-events.jsonl, not in this live dashboard.
• Standing future work remains visible as watchlist/code-owner lanes instead of generic open dashboard spam.

Recent Published Work

Batch	Output	Details
AI commander branch-head refresh	AI commander audit, Current source snapshot, Quad AI Commander	Refreshed branch heads and kept branch/design evidence separate from shipped source.
HC upstream history	HC upstream history and lessons	Captured older headless-client branch/comment-message lessons for future HC work.
PR8 and drone lesson match	PR8 and Drone upstream lesson match	Mapped upstream lessons to PR #8 and drone-branch review gates.
Quad AI/support/lifecycle/UI/tooling scout harvest	Quad AI Commander, Support specials, Tools/build	Promoted source-backed non-duplicate deltas and left concept-only evidence clearly labeled.
Config/factory/UI/AI/cleanup/upstream scout harvest	Mission config graph, Factory/purchase, Client UI systems	Added version/runtime contract, latent AIBuyUnit wording, UI cleanup debt and loop-topology notes.
Town/respawn/upstream/performance scout harvest	Gameplay systems, Respawn/death, Performance sweep	Added respawn penalty, resource cap, capture reward and loop-topology refinements.
Commander vote/reassignment playbook	Commander vote/reassignment	Routed commander UI/PV/authority pages through one patch-ready playbook.
Economy supply commander audit	Economy authority first cut, Supply authority cleanup	Completed source-backed economy/commander/supply boundary map and handed implementation choices to code owners.

Update Ritual

Moment	Codex / Claude action	Human-visible result
Starting work	Update agent-collaboration.json and append a claim event.	This dashboard and the coordination board show who owns what.
Still working after a long pass	Append a heartbeat event.	You can see that an agent is alive and where it is reading.
Finding a source-backed issue	Append a finding event and add a short worklog note.	The finding is visible before the full page is integrated.
Finishing a lane	Append a complete event, update affected pages and note validation status.	The lane moves from active to ready/integrated.
Handing off	Append a handoff event with the exact next action.	The next agent can pick it up without chat memory.

Status Legend

Status	Meaning
active	Someone is working this lane now.
watchlist	Keep synchronized when new evidence appears; no standalone action is currently blocked.
owner decision / code lane	Documentation is ready; a gameplay/release owner must choose or implement.
published / validated	Published into the wiki/docs set and reflected in navigation/context.
blocked	Needs user input, missing access or an external state change.

For Agents

1. Load agent-status.json, agent-collaboration.json, agent-knowledge.jsonl, agent-events.jsonl and Agent collaboration protocol before claiming work.
2. Treat agent-events.jsonl as append-only.
3. Keep claims bounded by source scope.
4. Never overwrite another agent's page or navigation changes from a stale branch.
5. Publish human notes to Agent worklog and machine notes to the JSON files.

Continue Reading

Previous: Agent context | Next: Coordination board

Main map: Home | Fast path: Quickstart | Agent file: agent-context.json