Add verified Truthtrance hand inventory questions

Players can ask total-hand and primary-role card-count comparisons using the
existing count controls and compound facts. Component presentation shares the
same default-role classification, including canonical Richese cards, Ix alternate
uses, and Ecaz slot-only specials. Only the respondent receives the verified
aggregate answer; current facts do not impose future custody promises.

Eight new tests cover all 60 catalog cards, real engine actions, malformed input,
private worlds, all four bots, JSON continuation, and a legal custody transfer.
Expanded production-room SQLite cases cover restored total/category/compound
facts, suspended auction state, and one winning concurrent answer/discard.
Independent review's two copy issues were fixed before broad verification.

Validation: types, lint and 4,200 offline tests passed; production build passed;
40 HTTP tests passed. One stable broad run (check 123036 ms, build 6505 ms,
integration 23467 ms). Browser room LC3E55GY verified combined role counts,
total hand size, invalid-input feedback and refresh at 390px phone width.
All 33 pre-integration rooms preserved unchanged; HTTP checks added 30 rooms.
No complete-mode, full-game or publication gate opened.

Private report: 20260913-hand-inventory-final/report.json
Source fingerprint: c6a69a9e69941cdd1e5734d92afedbf10d31fda36c91d26ca7e15f4fb7c59b18
Efficiency pilot milestone 3: aggregate counter 58,695,053 to 59,144,653 at
completed verification = 449,600 tokens, including context/coordination overhead.
Two bounded workhorse-model helpers, reused UI and SQLite fixtures, one browser
room. Counter is not monetary cost and this differently sized batch does not
establish a savings percentage. Final Git/push overhead follows this sample.

docs/EFFICIENCY_PILOT.md

@@ -9,8 +9,8 @@ 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. |
+| 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 | Start aggregate counter 58,695,053. Two bounded helpers on the cheaper workhorse model for regression implementation and independent review. Reuses the existing count panel and persisted-room fixtures; eight added tests and expanded SQLite cases. Two copy issues resolved before broad verification. One isolated browser room covers combined role counts, total size, invalid input and phone refresh. Confirmed endpoint and final results are recorded in the checkpoint commit. |
 
 The aggregate counter may update only between turns. Record a confirmed endpoint
 when available rather than estimating missing usage. It includes coordination and
@@ -21,6 +21,18 @@ existing checks; broad checks still run once source/review is stable and repeat
 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. Keep the third batch bounded, reuse fixtures and avoid repeatedly
+loading old audits. Compare concrete capabilities and reopened defects alongside
+token counts before choosing the next budget; three different deliverables alone
+cannot support a reliable percentage estimate.
+
+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.