LLM Agent Entry Pack

LLM Agent Entry Pack

This is the compact operating brief for Codex, Claude and other AI assistants working on rayswaynl/a2waspwarfare.

Use this page first, then jump into the canonical pages and machine files it names. Do not treat this as a substitute for reading source before making code changes.

Load Order

1. Read agent-entrypoint.json for the compact machine-readable bootstrap and status vocabulary.
2. Read llms.txt for the high-level map.
3. Read agent-context.json for the larger current repo rules and page inventory snapshot.
4. Read Feature status register for current risk/partial/broken-system triage.
5. Read agent-feature-status.jsonl for compact feature/risk status and canonical page routing.
6. Read agent-release-readiness.json before claiming any source fix is propagated, smoked or release-complete.
7. Read Progress dashboard, agent-status.json and agent-events.jsonl to avoid duplicating active lanes.
8. Read Arma 2 OA compatibility audit and agent-compatibility-audit.json before accepting docs or prompts that mention Arma 3-era APIs.
9. Read the subsystem atlas/playbook for the thing you intend to change.
10. Inspect source directly before patching. The docs are guidance; the worktree is authoritative.

Non-Negotiable Rules

Rule	Why
Start gameplay edits in Missions/[55-2hc]warfarev2_073v48co.chernarus.	This is the source mission.
Treat Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan as generated/copy output.	Propagation should happen through Tools/LoadoutManager, not hand-edited drift.
Do not claim Vanilla propagation unless LoadoutManager ran and generated diffs were inspected.	The tool now supports normal repo-root marker checkouts and can skip packaging with A2WASP_SKIP_ZIP=1; runtime smoke is still a separate gate.
Treat Modded_Missions/* as divergent/stubbed unless a tooling owner proves otherwise.	Current generation/package paths do not actively maintain modded missions.
Use Arma 2 OA scripting references and the compatibility audit.	Arma 3 behavior is not a safe assumption; existing Arma 3 mentions are usually warnings, not implementation advice.
Keep public-server hardening conservative.	PVF/direct PV/economy paths include client- or payload-authoritative legacy behavior.

Highest-Risk Work First

Lane	Read	Current posture
PVF dispatch trust boundary	PVF dispatch implementation, Networking/PV, Public variable channel index	P0. Replace sender-chosen dispatch compile with allowlist / namespace lookup.
ICBM/Nuke authority	ICBM authority, Server authority map	P0. Server must validate commander/upgrade/funds/side before damage.
Side-supply clamp	Economy authority first cut, Resistance supply scaffold, Server authority map	P0 first economy hardening slice; resistance economy is scaffolded but unsupported.
Upgrade request authority	Upgrades/research atlas, Economy authority first cut, Server authority map	P1. Client menu validates/debits; server worker owns timer/state but must accept/reject authoritatively.
Attack-wave authority	Attack-wave authority, Public variable channel index	P1. Direct PV must become server-derived request flow.
Economy/server-authority class	Server authority map, Economy authority first cut	P1 design lane. Do not patch build/buy/sell/gear/supply as unrelated one-offs.
Integration trust boundaries	Integration trust boundary audit, AntiStack database extension audit, External integrations, Player stats branch audit, Feature status	High local-write-gated DiscordBot JSON risk; separate from the in-repo extension writer, the absent AntiStack DB DLL and branch-only stats RPT/file integration gates.

Common Task Bundles

Task	Read these first
Startup, init, parameter or generated include change	Mission entrypoints, Lifecycle wait-chain, Join/disconnect lifecycle, Parameters/build inputs, SQF atlas
PublicVariable/PVF change	Networking/PV, Public variable channel index, PVF dispatch implementation
Economy, upgrade or purchase change	Economy/towns/supply, Resistance supply scaffold, Factory/purchase atlas, Upgrades/research atlas, Server authority map
Commander, HQ, MHQ or base-area lifecycle change	Commander/HQ lifecycle, Construction/CoIn atlas, Commander reassignment call shape, Server authority map, Public variable channel index
Town capture, camps or SV visibility	Towns/camps/capture atlas, Economy/towns/supply, Town AI vehicle safety, Testing workflow
Victory, endgame or match statistics	Victory/endgame atlas, Deep-review findings DR-11/DR-12/DR-13/DR-36, Hardening roadmap, Testing workflow
Supply mission or PR #1 work	Supply mission architecture, Supply mission authority cleanup, Current supply heli PR
Support/special/tactical module work	Support/specials/modules atlas, Server authority map, ICBM authority, Supply mission authority cleanup
Marker, cleanup or restoration work	Marker cleanup/restoration atlas, Client UI systems atlas, Server gameplay runtime atlas, Performance opportunity sweep
AI or headless change	AI/headless/performance, AI commander autonomy audit, HC delegation/failover, Town AI vehicle safety
UI/HUD/dialog change	Client UI systems atlas, Respawn/death lifecycle, UI IDD collision repair, Client UI/HUD/menus, Gear/loadout/EASA atlas, Gear template profile filter, Vehicle cargo equip loop bounds, Service menu affordability guards
Build/tooling/release change	Parameters/build inputs, Tools/build workflow, Source fix propagation queue, agent-release-readiness.json, Testing workflow, Content/maps, Knowledge platform roadmap
Discord/extension/AntiStack/BattlEye change	Integration trust boundary audit, AntiStack database extension audit, External integrations, agent-hardening-backlog.jsonl
Revival/removal decision	Abandoned feature revival, Pending owner decisions, Feature status

Current Truth Notes

• Paratrooper marker revival, client skill duplicate init removal, hosted server FPS loop exits, supply mission command-center scan narrowing and supply player-object list indexing are patched in Chernarus source and propagated to maintained Vanilla Takistan; Arma 2 OA smoke remains pending.
• The current source/Vanilla propagation ledger lives in Source fix propagation queue, with compact machine status in agent-release-readiness.json; update both before claiming release completeness.
• Machine-file contract: agent-entrypoint.json is the small canonical bootstrap file. agent-status.json, agent-collaboration.json, agent-context.json, agent-release-readiness.json and agent-compatibility-audit.json are snapshots. agent-events.jsonl, agent-knowledge.jsonl, agent-feature-status.jsonl and agent-hardening-backlog.jsonl are append-oriented evidence streams; do not assume event rows are timestamp-sorted, and prefer the newest explicit status/supersedes record when older rows disagree.
• WASP marker wait cleanup is an opportunity/playbook, not a completed code patch.
• Respawn/death lifecycle has a canonical atlas. Local MASH respawn is live for the audited deployer path; MASH marker synchronization is dead/orphaned; custom-gear penalty mode 5 has a patch-ready affordability/skip edge.
• Service menu affordability guards are a patch-ready local correctness lane for GUI_Menu_Service.sqf; do not confuse them with full gear/EASA/service server authority.
• Integration trust fixes are split: DiscordBot TypeNameHandling.All is the active JSON intake risk; a2waspwarfare_Extension is the in-repo status writer; AntiStack uses a separate absent A2WaspDatabase extension. AntiStack has a controlled ON/OFF parameter and disabled-mode guards, but enabled-mode DB return parsing still needs hardening.
• Commander reassignment, UI IDD collisions and resistance supply now have dedicated source-backed playbooks: Commander reassignment call shape, UI IDD collision repair and Resistance supply scaffold.
• Commander/HQ lifecycle now has a canonical atlas. It maps commander vote/reassignment, client commander affordances, HQ deploy/mobilize, HQ destruction, allied wreck markers, normal MHQ repair, WASP cash HQ recovery and base-area/JIP-sensitive risk edges.
• Victory/endgame now has a canonical atlas. It maps the default 80-second server victory loop, loser-side client payload semantics, all-towns winner inversion, same-tick double-fire, non-zero threeway no-detection, stale PVFunctions/LogGameEnd.sqf and smoke gates.
• Wave G scout outputs now have owner pages: Join/disconnect lifecycle, Marker cleanup/restoration atlas, Parameters/build inputs and Support/specials/modules atlas.
• Checked-in source has no tracked version.sqf; local ignored generated copies may exist, but clean checkout generation/pack inputs must supply it before source-mission boot or release packaging.

Agent Output Rules

• Put short status and dashboard rows in Feature status or Progress dashboard.
• Put detailed evidence in subsystem pages or playbooks.
• Put durable machine-readable findings in agent-feature-status.jsonl, agent-knowledge.jsonl or agent-hardening-backlog.jsonl.
• Put source-fix propagation, generated-target and smoke-gate status in agent-release-readiness.json.
• Put engine compatibility classifications in agent-compatibility-audit.json when new Arma 3-era terms are intentionally added to docs.
• If you discover a stale claim, correct the prose page and the machine file that would mislead future agents.
• If you patch source Chernarus but cannot run LoadoutManager, write source fix; propagation pending; if LoadoutManager runs with inspected generated diffs but no Arma smoke, write propagated; smoke pending.
• Before handoff, run docs/validate-wiki.ps1 from the repo root when you changed docs or machine files.

Continue Reading

Previous: Quickstart | Next: Feature status

Main map: Home | Machine entry: agent-entrypoint.json | Machine map: agent-context.json | LLM map: llms.txt