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: Progress-Dashboard.md in the GitHub wiki; repo mirror path is docs/wiki/Progress-Dashboard.md only on branches/checkouts that carry the mirror.
• 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
hosted-fps-status-current-b742-refresh-2026-06-24	Published / validated	Refreshed hosted server FPS publisher/status-counter branch wording across Hosted server FPS, Client UI systems, Feature status, Source Fix queue, Performance sweep, runtime/testing gates and machine rows. Repo docs branch HEAD@4a1bc13edde6 is unchanged from d0161083 / a27086cd for checked FPS paths and keeps two guarded publishers. Current stable/B74.1 origin/master@f8a76de34, current B74.2 origin/claude/b74.2-aicom@21b62b04, B69, B74, live client-fps, live ASR FPS and historical a96fdda2 use one guarded serverFpsGUI.sqf:4 publisher and no maintained-root monitor file; B74.2 only line-drifts source-Chernarus init/removal anchors for this lane. Miksuu/perf quick-wins remain old-loop-shaped. No gameplay source changed.
task-objective-ping-current-b742-refresh-2026-06-24	Published / validated	Refreshed old town TaskSystem / commander Objective Ping branch wording across Abandoned feature revival, Feature status, Commander/HQ lifecycle, Client UI systems, Networking/public variables and machine rows. Repo docs branch HEAD@c5937045f still keeps GUI_Menu_Command.sqf:335,337,343 SetTask sends commented plus Client_TaskSystem.sqf; current stable/B74.1 origin/master@f8a76de34, current B74.2 origin/claude/b74.2-aicom@21b62b04, B69, B74 and naval-HVT send targeted Objective Ping at GUI_Menu_Command.sqf:336,344 with SetTask registration at Init_PublicVariables.sqf:40 and remove the old town helper. Miksuu/perf/c20 remain old-shape; historical a96fdda2 has live ping sends but no live release/* head. No gameplay source changed.
pvf-dispatch-agent-context-current-b742-refresh-2026-06-24	Published / validated	Refreshed compact agent-context.json PVF dispatch wording so future agents route current stable/B74.1 through origin/master@f8a76de34 and current B74.2 through origin/claude/b74.2-aicom@21b62b04 instead of older 0139a346 wording. Repo docs branch HEAD@af208505c229 is unchanged from 925d56e01a1e/a0721301d4f5 for checked PVF init/dispatcher/send-helper paths and still dispatches with Spawn (Call Compile _script) at Server_HandlePVF.sqf:14 and Client_HandlePVF.sqf:22 in both maintained roots. Current stable/B74.1/B74.2/B69/B74 use missionNamespace getVariable plus CODE guards at server :14-15 and client :32-33; Miksuu/perf/historical a96fdda2 remain old-shape. Canonical hardening detail remains PVF Dispatch implementation playbook; no gameplay source changed.
wasp-marker-wait-agent-context-current-b742-refresh-2026-06-24	Published / validated	Refreshed compact agent-context.json WASP display-54 wait wording so future agents route current stable/B74.1 through origin/master@f8a76de34 and current B74.2 through origin/claude/b74.2-aicom@21b62b04 instead of older 0139a346/B69-only wording. 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/B74.2/B69/B74/client-fps carry sleep 0.1 before findDisplay 54; Miksuu, perf and historical a96fdda2 remain old-shape. Canonical detail remains WASP marker wait cleanup; no gameplay source changed.
duplicate-ui-idd-current-b742-head-refresh-2026-06-24	Published / validated	Refreshed UI resource parity cleanup, UI IDD collision repair, Client UI systems, Feature status, Dead/stale code and duplicate IDD machine rows so EASA/Economy/title-ID evidence routes current stable/B74.1 through origin/master@f8a76de34 and current B74.2 through origin/claude/b74.2-aicom@21b62b04 instead of older 0139a346-only wording. 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/B74.2/B69/B74 and historical a96fdda2 split EASA to 24000 while Economy stays 23000; title 10200 remains shared by RscOverlay/OptionsAvailable; no checked hard-coded findDisplay 23000/24000/10200 callers. 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	Hosted FPS/status-counter current B74.2 refresh is published; pick the next bounded source-backed documentation lane and claim before editing.
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	Latest wiki payload mirrored here	GitHub wiki + docs/wiki mirror	This workspace mirrored live wiki origin/master@4d4014a into docs/wiki for the latest reference pages, nav routes and context files. If another active gameplay branch lacks docs/wiki, work in a standalone wiki checkout and record that branch-specific caveat before parity claims.

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	Target-specific source/smoke work	WASP marker wait cleanup remains patch-ready on docs/source, current Miksuu, perf and historical old-shape refs; current B74-shaped, client-fps and live map refs need marker-dialog smoke rather than the one-line sleep reopened.

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/B74.1 origin/master@f8a76de34 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 current stable/B74.1/B74.2/B69/B74/release/naval independent-capture fixes from docs checkout/Miksuu/perf old-owner shapes; origin/fix/wildcard-w4w5-outer-capture@ead7e854 is marker/handler context only, and 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