Skip to content

Progress Dashboard

rayswaynl edited this page Jun 5, 2026 · 908 revisions

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
pr8-release-head-evidence-refresh Published / validated Routed the current PR #8 / origin/release/2026-06-feature-bundle head 3282ff3f into PR cleanup lab and Testing workflow. The addendum covers WF menu player/town counts, service-point full/refuel QoL, shielded HQ walls and Tools/SmokeTests/Test-PR8StaticSmoke.ps1, while keeping the static smoke script explicitly Chernarus/source-only. No gameplay source changed.
community-upstream-head-note-refresh Published / validated Refreshed Community & Dev and Developer history so older miksuu/master 8bcc42b1 wording is clearly point-in-time provenance and the current upstream head 69e1958a / e4be1958 capture-state candidate routes through Upstream Miksuu commit intel. No gameplay source changed.
miksuu-town-capture-state-fix-intake Published / validated Source-checked new miksuu/master commit e4be1958 / merge 69e1958a: it clears previous-side active town-AI state on town capture in both Chernarus and maintained Vanilla Takistan. Routed it as an upstream candidate in Upstream Miksuu commit intel, Towns/camps/capture, Feature status, Developer history and Testing workflow. No gameplay source changed.
current-source-status-refetch Published / validated Refreshed Current source status snapshot with a 2026-06-05 refetch delta: docs mirror head advanced to a552060d, origin/release/2026-06-feature-bundle advanced to 3282ff3f, and miksuu/master advanced to 69e1958a. The page explicitly treats those as routing deltas, not proof that the newer release/upstream changes are reviewed or shipped. No gameplay source changed.
bottleneck-queue-validation-refresh Published / validated Refreshed Bottleneck removal queue so it no longer describes mirror/wiki parity as merely required from an old 2026-06-03 state. It now records recent docs batches as using docs/validate-wiki.ps1, JSON/JSONL parse, git diff --check, wiki-checkout checks and full SHA parity with full-diffCount=0. 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 Active documentation-finisher-loop Keeping PR/release, upstream and backlog status pages current as branch heads and helper reports move.
Codex-2 Ready None Pick a bounded source-backed lane from PVF dispatcher lookup, side-supply clamp first, commander reassignment call-shape repair or remaining supply authority hardening.
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 Keep the wiki current from source evidence after this pruning goal closes.
old-be-wasp-fps-archaeology Codex delegated window Active / read-only Compare old Benny Edition / WarfareBE against current Wasp for client/server FPS opportunities, player-AI cap options and matched 20-player/full-server test planning. Promote only source-backed deltas after review.
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.
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 and paratrooper markers 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 dev/july-update-hosted-server-fps-loop-fix Adopt/verify the DR-19 hosted/listen busy-spin fix for the July update target. Keep the low-risk early !isDedicated exit shape for FPS publisher loops; decide separately whether to consolidate the two FPS variables. ~5-20 LOC for the loop guard; ~20-50 LOC if cleanup/consolidation is included. Queued for July update. Remote dev branch created from origin/master. Dedicated server still publishes SERVER_FPS_GUI / WFBE_VAR_SERVER_FPS; hosted/listen runs do not spin the FPS publisher loops; Chernarus and maintained Vanilla parity are named before release wording.
2 Takistan Airfield FPV Drone Bay dev/july-takistan-airfield-fpv-drone 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 for July update. Remote dev branch created from origin/master; design captured from Steff questionnaire. 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

  • 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.
  • 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 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: Bottleneck removal queue

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

Sidebar

Clone this wiki locally