Quintine
5a76ae0410
Add an offline Ix initializer through the real setup pipeline, supporting Basic and Advanced play, base factions, Ixians and Tleilaxu with the full 47-card deck and 22-card spice deck. Preserve all normal start and publication gates. Add a reusable local prototype starter: back up the named fresh ready lobby, initialize it once by exact version/state comparison and preserve seat/recovery tables and other rooms. Update the existing checklist with a separate prototype stage and document functional scope, source interpretations and later refinement. Six new tests cover all-profile private setup, exact typed starting forces, Face Dancer/treachery custody, JSON continuation, two fixed-seed complete games and local SQLite write/rejection boundaries. Independent review caught a missing JSON version update, now fixed and covered; focused checking fixed one test typing error before the stable broad check. No new rule interpretation was introduced. Validation: types, lint and 4,211 offline tests passed (123.237s); production build passed (6.543s); all 40 HTTP tests passed (23.578s). Source-bound report: 20260913-ix-prototype-final/report.json, fingerprint 3b8f295593bcb314bb72308d81739006b11d949d1e5906dbf6ce0704b15ebd72. Browser W5LE6VFB: human Ixian + Medium Tleilaxu + Hard Atreides from genuine setup, private starting-card refresh, Weather Control, mobile stronghold placement, then owned Brutal autopilot. Atreides won on turn 1; this short complete journey is not proof of every card or faction interaction. Finished private hand restored at phone width; expanded Poison Tooth was readable. Fixed-seed offline games 2026091301 (Basic) and 2026091302 (Advanced) both completed with both Ix factions. All 64 opening room versions/hashes are unchanged. One browser room and 30 HTTP rooms were added, totaling 95. Reused the running server; no restart or automation. Aggregate goal counters: 59,524,858 to 59,976,567 at completed verification, 451,709 tokens before final Git overhead. Two bounded workhorse helpers handled inventory/tests and independent review; one stable full check/build/HTTP run. Full game scope remains active and unfinished; future work prioritizes missing functional prototypes before exhaustive refinement and final acceptance.
85 lines
6.8 KiB
Markdown
85 lines
6.8 KiB
Markdown
# Three-milestone efficiency pilot
|
||
|
||
Preserve the complete game scope and required checks. Use small relevant reads,
|
||
coherent feature batches, selective subagents and compact verification artifacts.
|
||
Git remains mandatory: review, verify, commit, push and confirm remote success at
|
||
each finished implementation checkpoint. Never force-push or commit credentials.
|
||
The removed recurring automation stays removed.
|
||
|
||
| Milestone | Deliverable | Measurement |
|
||
| --- | --- | --- |
|
||
| 1: setup | Current status, decision index, reusable checks, saved-game snapshots/backups and HTTP seat restoration | Accepted checkpoint `6e26ba5`. Aggregate counters 57,957,554 → 58,124,416: 166,862 tokens including planning, coordination and the user-requested save reset. Two bounded helpers. Fifteen added regressions; 4,177 offline tests passed. Three broad attempts: two stopped before tests on type/lint errors; final check passed in 130.147s. One cancellation defect found and fixed in review. |
|
||
| 2: core readiness batch | Typed Advanced reserve-shipment commitments without Guild or optional modules | Accepted checkpoint `32791ed`. Aggregate counters 58,124,416 → 58,695,053: 570,637 tokens. Two bounded helpers: regression implementation and independent rules/privacy review. Fifteen added tests; 4,192 offline and 40 HTTP tests plus build passed. One stable broad run; focused checks resolved setup mistakes and two review findings before it. Two browser rooms verified distinct AI and human paths. Pending Guild settlement remains explicit. |
|
||
| 3: next dependency batch | Truthtrance total hand size and primary-role counts, controls, bots and recovery | Accepted checkpoint `7454456`. Aggregate counter 58,695,053 → 59,144,653 at completed verification: 449,600 tokens, before final Git/push overhead. Two workhorse-model helpers for regression implementation and independent review. Reused count panel and SQLite fixtures; eight added tests and expanded recovery cases. Two copy issues fixed before the single stable broad run: 4,200 offline tests, build and 40 HTTP tests passed. One browser room covered combined roles, total size, invalid input and phone refresh. |
|
||
|
||
The aggregate counter may update only between turns. Record a confirmed endpoint
|
||
when available rather than estimating missing usage. It includes coordination and
|
||
conversation overhead and is not a dollar-cost meter. Different capability sizes
|
||
limit direct comparisons; do not promise a savings percentage from this setup.
|
||
Do not count tests alone as accepted faction or mode completion. Scripts consolidate
|
||
existing checks; broad checks still run once source/review is stable and repeat if
|
||
subsequent changes or failures justify them. Browser fixtures remain feature-specific;
|
||
the reusable HTTP restoration helper does not automate browser setup or visual QA.
|
||
|
||
Milestone 2 cost more than the tooling baseline and cannot establish a saving.
|
||
Its larger rules/interaction scope, browser setup and context recovery contribute
|
||
to that total. Milestone 3 was smaller and reused more existing structure; its lower
|
||
count cannot isolate the effect of model choice or establish a savings rate.
|
||
Avoid repeatedly loading old audits. Three different deliverables alone cannot
|
||
support a reliable percentage estimate.
|
||
|
||
For initial planning, allow roughly **450,000–575,000 aggregate tokens for a
|
||
similarly sized reviewed gameplay batch**, based on milestones 2 and 3. This is a
|
||
low-confidence planning estimate, not a dollar quote, token-budget setting or a
|
||
reason to stop required work. Larger interaction sets need a revised estimate.
|
||
The tooling baseline was about 167,000 and is not a gameplay cost target. Reassess
|
||
after the next few comparable batches, including defects found after acceptance.
|
||
|
||
Next adjustment: use the owner plus one bounded helper for source research and
|
||
independent review when the existing implementation needs verification. Reuse
|
||
the same helper for its follow-up review, existing fixtures and applicable checks.
|
||
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. 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
|
||
|
||
The first batch starts at aggregate counter 59,524,858 and connects genuine Ix
|
||
setup to the existing faction/card gameplay and saved browser table. One bounded
|
||
helper inventoried existing work and implemented focused tests; a second reviewed
|
||
setup privacy and the local database writer. The owner integrates the prototype
|
||
entry, reusable backed-up starter, checklist and browser journey. Six added tests
|
||
include two fixed-seed complete games without a calibration study. A saved-version
|
||
review finding and a test typing error were fixed before the stable broad check;
|
||
final results and counter endpoint are recorded in the checkpoint commit.
|
||
|
||
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
|
||
unfinished when stopping for usage, preserve Git and subagent requirements, and
|
||
leave the removed recurring automation absent. After `32791ed`, usage was 3% used.
|
||
|
||
Use [current status](CURRENT_STATUS.md), [rule decisions](RULE_DECISIONS.md) and
|
||
[verification workflow](VERIFICATION_WORKFLOW.md) as short entry points. Historical
|
||
logs remain references, not mandatory full-context input on every turn.
|