From 194471e90617aa55758e1a3e5d28070c2964737e Mon Sep 17 00:00:00 2001 From: Quintine <15965533+Quintine@users.noreply.github.com> Date: Sun, 13 Sep 2026 11:56:23 +1000 Subject: [PATCH] Prioritize rapid prototypes across the full game scope Record the user's new development order: working first versions of all remaining functions, followed by integrated play, refinement and final acceptance. Track missing/prototyped/integrated/verified/polished work in the existing checklist. Keep essential legality, privacy, custody and persistence checks; defer exhaustive combinations and final polish until broader functional coverage. Preserve selective subagents, independent review where required, automatic verified Git pushes, the 80%-used weekly stop and as-needed server restarts. Material rulings and final mode/publication gates remain explicit. The canonical goal file outside Git was updated with the same instructions. Validation: documentation-only follow-up to 4a0b1ee; local links and git diff --check passed. Runtime and tests are unchanged from its passing types, lint and 4,205 offline tests. No redundant broad check or server restart was needed. --- AGENTS.md | 17 +++++++++++++++++ docs/CURRENT_STATUS.md | 15 +++++++++++---- docs/EFFICIENCY_PILOT.md | 23 ++++++++++++++++++++++- 3 files changed, 50 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 4fd6978a..249a92ac 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -20,6 +20,23 @@ for the in-memory SQLite tests. `tsx` is a pinned development dependency. - Do not read `github.md` for routine development: it is ignored private local credential material. Do not put secrets in logs or tracked files. +## Prototype the remaining scope first + +- The user prioritizes working first versions of all remaining functions across + Basic, Advanced and every expansion, followed by integration, refinement and + polish. Reuse existing capabilities; batch related functions by dependency. +- Track missing, prototyped, integrated, verified and polished work in the + existing checklist. Prototypes need usable controls, a legal AI path and saved + continuation; placeholders and disconnected helpers are not completed features. +- Keep focused checks for crashes, deadlocks, legality, custody, privacy and save + integrity. Defer exhaustive combinations, AI calibration and visual polish + until broader functional coverage, unless current failures require them. +- Preserve required checkpoint checks, selective subagents and independent + review for complex rules/privacy/persistence. Commit and push verified + checkpoints under standing authorization; stop at 80% weekly usage consumed. +- Keep material rulings explicit and prototype independent work while pending. + Prototype evidence does not open mode or publication gates. + ## Implement and verify - Keep rule calculations/validation in focused `game/` modules; integrate them diff --git a/docs/CURRENT_STATUS.md b/docs/CURRENT_STATUS.md index 05dc2d99..324a14e3 100644 --- a/docs/CURRENT_STATUS.md +++ b/docs/CURRENT_STATUS.md @@ -6,6 +6,7 @@ Updated 13 September 2026. This is the short navigation dashboard; detailed evid - [Rules implementation checklist](../game/reference.ts): `RULE_TOPICS`, topic `implementation-checklist`, and each feature's implementation, controls, AI, documentation and verification entries. Coverage is per stated boundary, not an implicit whole-game certificate. - [Latest verified gameplay checkpoint](IMPLEMENTATION_STATUS.md): Truthtrance hand inventory, 13 September 2026 (`7454456`): types, lint, **4,200 offline tests**, production build and **40 HTTP tests** passed, with a phone/browser refresh journey and preserved saved games. These are recorded results, not checks rerun for this dashboard. +- Latest verification checkpoint `4a0b1ee`: genuine Advanced full-plan interaction tests; types, lint and **4,205 offline tests** passed. Private inspection restored after restart, with desktop/phone checks and all 64 saved games unchanged. No runtime change; prior build/HTTP evidence applies. - [Development guide](DEVELOPMENT.md) defines focused verification; [rule decisions](RULE_DECISIONS.md) locates settled contracts and pending interpretations. Read the newest checkpoint and relevant feature document before consulting older log entries. The user authorized a one-time local reset on 13 September: the 3,644 historical @@ -42,10 +43,16 @@ The [base/Advanced audit](BASE_ADVANCED_READINESS_20260907.md) includes historic Likewise, the [Truthtrance readiness audit](TRUTHTRANCE_NONBATTLE_READINESS_20260907.md) predates [spice facts](TRUTHTRANCE_SPICE_FACTS.md), [card-count facts](TRUTHTRANCE_CARD_COUNT.md) and [Basic shipment promises](TRUTHTRANCE_SHIPMENT_PROMISES.md). Current `TruthFact` already includes these facts; do not rebuild them. Typed preparation and BG conversion now support the active reserve-shipment scope in base Advanced without Guild or optional modules. Broader facts, earlier-phase promises, remaining Advanced/expansion commitment scope and freeform interpretation remain incomplete. -## Next milestone: core readiness +## Next milestone: rapid functional coverage -1. Reconcile the remaining base-only gaps against current helpers, consumers and tests, using the existing [Guild cancellation contract](GUILD_RATE_KARAMA_RULES.md) and [special-Karama findings](BASE_ADVANCED_READINESS_20260907.md#explicit-unresolved-base-interpretations). Keep already-asked interpretations pending; tests are not rulings. -2. Ordinary Guild cancellation remains the next dependent gameplay batch around an exact saved shipment intent. Keep discount, cross/return permission and income separate; preserve contributors, independent Karama rates and original typed forces. Establish the unresolved affordability/settlement contract before implementing those outcomes. Verify sufficient-funds paths, nested responses, rejected-action immutability, private controls, all four bots and saved continuations together. -3. Continue remaining core Truthtrance and Advanced timing gaps. The [full-plan interaction audit](ATREIDES_FULL_PLAN_TIMING.md) closes the named native card-interaction evidence gap while preserving unresolved timing interpretations. Run genuine Basic/Advanced setup-to-finish multiplayer and browser acceptance before reconsidering mode gates. Expansion completion remains a subsequent part of the same overall goal. +The user changed the development order on 13 September: get working prototypes +of all remaining functions into the game, then use integration and play to find +issues and refine them. Complete core certification no longer precedes independent +expansion prototyping. Final rules compliance and release requirements still apply. + +1. Reconcile the existing checklist with current helpers, controls, AI and saved-state paths. Mark remaining work as missing, prototyped, integrated, verified or polished; retain explicit blockers and reuse completed features. +2. Implement the next connected batch across Basic, Advanced, factions or modules according to dependencies. Include real actions, usable controls, a legal AI path and saved continuation. Keep fast checks for crashes, deadlocks, legality, custody, privacy and save integrity; avoid exhaustive refinement of each small feature before broad coverage exists. +3. Continue independent functions while [material rulings](RULE_DECISIONS.md) are pending. Ordinary Guild repricing/settlement and special Karama interpretations remain unresolved; do not invent their outcomes to fill the inventory. +4. Integrate prototypes and play complete games to discover issues, then deepen combination coverage, multiplayer recovery, AI calibration and visual polish. Required checkpoint checks, reviewed Git pushes, selective subagents and the 80%-used weekly stop remain in force. Keep unfinished modes and publication gated until acceptance. Consult [AI calibration](AI_CALIBRATION.md), [multiplayer audit](MULTIPLAYER_AUDIT.md), [autopilot](AUTOPILOT.md), [component inventory](COMPONENT_INVENTORY.md) and [visual playtest](VISUAL_PLAYTEST.md) for their measured scope and follow-ups. Use current code and later checkpoints to interpret historical results. Publication still requires the completion and integrated verification gates in [README](../README.md). diff --git a/docs/EFFICIENCY_PILOT.md b/docs/EFFICIENCY_PILOT.md index ff7f0d20..bae5d8d7 100644 --- a/docs/EFFICIENCY_PILOT.md +++ b/docs/EFFICIENCY_PILOT.md @@ -42,7 +42,28 @@ Avoid adding runtime code merely to make an audit appear to be implementation. The full-plan interaction audit starts at aggregate counter 59,151,671, uses that one-helper pattern and changes tests/documentation. It therefore requires the full offline check, but can reuse the unchanged application's earlier build; -browser/restart acceptance supplies direct recovery evidence. +browser/restart acceptance supplies direct recovery evidence. Checkpoint `4a0b1ee` +passed all 4,205 offline tests in one stable broad check. Its aggregate endpoint +was 59,509,237 at completed verification: 357,566 tokens before final Git and new +goal-steering overhead. It is an audit batch, not a new gameplay capability. + +## User-directed rapid prototyping, 13 September 2026 + +Prioritize functional coverage of the entire remaining game before exhaustive +per-feature refinement. Use the existing checklist to distinguish missing, +prototyped, integrated, verified and polished functions, and choose connected +batches by dependency across core and expansion systems. A prototype includes +a working action, usable controls, legal AI participation and saved continuation. +Track functions newly playable and issues discovered during integration, alongside +tokens and rework; do not count placeholders as delivered functions. + +Keep focused invariant and smoke checks during prototyping and required checks +at stable checkpoints. Use integrated games to find defects; defer exhaustive +combination testing, AI calibration and final visual polish to refinement unless +an active defect requires them sooner. Preserve material rule questions, mode +gates, selective subagents and automatic verified Git pushes. The earlier batch +estimates remain historical planning evidence and should be reassessed for this +broader prototyping workflow, without an assumed savings percentage. Check account usage after each verified checkpoint. The user explicitly confirmed the stop point as **80% weekly usage consumed (20% remaining)**. Keep the goal