Quintine
32791ed5e2
Extend the existing reserve-shipment promise pipeline to base Advanced games without Guild or optional modules. Share scope between parser, save validation and UI. Reuse canonical Ghola normal/elite revival eligibility and retain live BG conversion responses while proving conditional private feasibility. Hide future-price guidance until pending responses finish. Show exact Sardaukar/Fedaykin allocation in private executable steps. Validation: types, lint and all 4,192 offline tests pass; production build and all 40 HTTP tests pass. 41 focused shipment tests include 15 new cases covering genuine Advanced setup, all five non-Guild factions and four bot profiles, typed Ghola quota, BG allowance/cancellation/alternatives, private views, saved continuations and production SQLite duplicate races. Independent review found and resolved optional-module scope and pending price-guidance issues. Browser rooms EUZZ8D4M and GWNCVCAP verified an AI No route and human Yes with four-force/one-Sardaukar Ghola then six-force shipment. Phone settlement controls and refresh passed. Both existing browser room hashes/versions preserved through HTTP tests; 30 rooms added. Full source-bound report: 20260913-advanced-shipment-final; fingerprint 6c2f29d9b3e61bf6b9544ee3a95c47538abfb05e1c3b2ae9d0a603ef0cef38dd Broad checks ran once after focused fixes/review. No full-game AI study or complete Advanced mode acceptance is claimed; all existing release gates and pending Guild settlement questions remain intact.
2.4 KiB
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 | Remaining Basic/Advanced capabilities with rules, controls, bots and recovery together | Start aggregate counter: 58,124,416. Batch: typed Advanced reserve-shipment commitments without Guild or optional modules. Two bounded helpers: regression implementation and independent rules/privacy review. Final counts belong to the verified checkpoint; pending Guild settlement remains explicit. |
| 3: next dependency batch | Next core or connected expansion capability selected from current evidence | Repeat measurements; compare cost per accepted capability and investigate repeated work. |
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.
Use current status, rule decisions and verification workflow as short entry points. Historical logs remain references, not mandatory full-context input on every turn.