pog-mcp 0.9.6 → 0.9.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pog-mcp",
-  "version": "0.9.6",
+  "version": "0.9.7",
   "type": "module",
   "description": "MCP server that lets an AI agent play Proof of Goal — wallet, sign-in, squad building, and matches as typed tools.",
   "license": "MIT",

package/skill/reference/measurements.md

@@ -2549,12 +2549,41 @@ that was an artefact of an unattainable +4 buff and is withdrawn.
 **This section does NOT close C-2.** An earlier version said it did; that was wrong. `τ` was
 never measured — the probe's 24h default was simply used — and the neutral point was left
 unchosen between its two branches. An F-1 implementer following that decision would have made
-a probe default the production recovery rate. And `τ` cannot be measured from this data: F-1
-does not exist, so production has no fatigue and there is no observed recovery curve to fit.
-What measurement CAN do is price the choices, which is what the τ sweep does. A third product
-choice sits beside τ and the neutral point: F-1 has not selected predicate C versus D. The
-published values are conditional on C; switching to D moves τ=24h median/p95 `L` by
-−5.3%/−10.4%. That measures the price of the choice, not which workload meaning the product wants.
+a probe default the production recovery rate. And `τ` cannot be measured from this data: at the
+time of this measurement F-1 did not exist, so production had no fatigue and there was no observed
+recovery curve to fit. What measurement CAN do is price the choices, which is what the τ sweep
+does. Predicate C versus D was the third product choice at publication; it was subsequently
+resolved as **D** on 2026-09-04. The published values remain conditional on C; switching to D
+moves τ=24h median/p95 `L` by −5.3%/−10.4%. That measures the price of the choice, and selecting D
+does not retroactively relabel C-conditioned calibration as D-conditioned evidence.
+
+### F-1 implementation status — predicate D is now durable
+
+F-1 persists version `f1-d-growth-neutral-v1`: actor plus responder selections minus only the
+actor/responder selections produced by a zero-weight `weightedPick` fallback. Legitimate direct
+defender selections, fixed set-piece/post-play actors, and penalty keepers remain counted. This
+keeps the measured defensive participation while preventing the known all-zero ZP table from
+turning the first non-GK slot into a fatigue lever.
+
+The engine instrumentation is opt-in and consumes no RNG. The existing growth-buffed simulation
+still decides the real result; one separate engine instance projects `total` back to the public
+attribute sum and emits only unsigned slot counters. Scheduled processing claims the complete due
+batch before either real or shadow simulation, freezes one external batch epoch into
+`MatchInputSnapshot v3.capturedAt`, and reuses it on retries. A first locked transaction commits the
+snapshot and durable per-player reservation; a second commits the real result, replay events,
+`match_workloads` root, 11/22 `player_workload_events`, and reservation release. Interactive ladder
+play holds the same player locks from snapshot through both simulations and the durable write.
+
+Cup classification is structural (`tournament_id IS NOT NULL`) and credits both sides. Ladder
+credits home, plus away only when the shared `isAI || isSystemOwnedWallet` rule identifies a bot;
+human away produces no workload rows. Durable players retain `playerId`; daily cup fill-bots use a
+separate salt over cup date, team and slot. Listing, fixed purchase, auction settlement, custody
+activation/delivery finalization, and shared ownership transfer all participate in the same lock
+and reservation fence. Recovery discovers exactly
+`(tournament_id IS NOT NULL OR match_type='playoff') AND status='complete' AND completed_at > cursor`,
+never filters on kickoff, and records explicit legacy exemptions. Friendly, paid trial and sandbox
+write no workload and pin both route-local engine copies to `cond=5`. EWMA decay, neutral point and
+actual condition derivation remain F-2; F-1 alone changes no competitive input.
 
 ### Growth-leak gate: use a zero-growth shadow, not the real action trace
 
@@ -2578,7 +2607,7 @@ stored seed and `gameFlg`. F-1 consumes unsigned engagement counters only from t
 The real result still uses the growth-buffed input; the shadow cannot change its score, events,
 ratings or growth. It is therefore a **zero-growth counterfactual workload**, never the action
 record of the match that happened. Runtime cost is one extra pure simulation per competitive match;
-F-1 still has to persist its counters atomically with completion. The workload timestamp must be
+F-1 persists its counters atomically with the computed result. The workload timestamp must be
 growth-invariant too: fix every due match's first-condition-snapshot (claim-start) time before ANY
 real or shadow engine in that scheduler batch runs, then use that match's one stored value for both.
 A sequential loop that timestamps match B only after simulating match A would carry A's
@@ -2604,8 +2633,8 @@ projection to the synthetic variations above and got byte-identical candidate-F-
 **1,201/1,201 matches and all 2,402 sides**. Unit tests pin erasure, preservation, non-mutation and
 idempotence; `match-growth.test.ts` pins that the real `applyMatchGrowth` producer projects exactly
 back to its innate team, and the existing squad-hash test independently pins that `total` is outside
-the hash. This closes only the §3-5 prerequisite, not F-1/F-3/G-1/F-4's own implementation and
-exposure contracts.
+the hash. That closed the §3-5 prerequisite; F-1 now uses it and G-1 is complete, while F-3 and F-4
+retain their own implementation and exposure contracts.
 
 **The gate is not a per-mode ceiling — it is defined on the exposure-weighted mix.**
 `band-worstcase.mts` holds the canonical statement (`01-engine-expansion.md:319-329` puts
@@ -2765,7 +2794,8 @@ counts; on expected rates it is 14%. Within-match noise had been read as between
 structure. The argument survives in a different form.
 
 The keeper still accrues almost nothing — it enters a contest only at the A0 one-on-one and
-at penalties — so no rule here makes one tired, and F-1 has to fill that blank deliberately.
+at penalties. F-1 deliberately accepted that limitation when it selected D rather than adding a
+separate goalkeeper source; whether it yields usable rotation belongs to F-2.
 
 Predicate D now subtracts fallbacks on BOTH sides of the contest: zone press picks its ACTOR
 through the fallback too, and an earlier version recorded only the responder's, so "C without
@@ -3007,8 +3037,9 @@ conversion.
 
 ### τ cannot be measured — only priced
 
-`τ` is the recovery rate §6 C-2 asks for. F-1 does not exist, so production has no fatigue
-and there is no observed curve to fit: `τ` is a DESIGN choice, not a measurement. What
+`τ` is the recovery rate §6 C-2 asks for. This measurement window predates F-1 and fatigue,
+so there is no observed curve to fit. The later F-1 ledger still does not derive condition;
+`τ` remains a DESIGN choice, not a measurement. What
 measurement can do is re-run everything at each candidate and report what follows. Each row
 below re-integrates the timeline, re-runs that τ's full cell set, and re-searches for the safe
 amplitude (one run, one snapshot).
@@ -3126,7 +3157,7 @@ it leaves open — does an opponent outside the basket exceed? — is asked sepa
 only **62 distinct XIs**. The old pool held 95 objects, of which only **47** were distinct
 lineups — 48 were duplicates. And **35 of the 95 teams fielded more than one XI** inside the
 window, every later one discarded. The new pool CONTAINS the old one and adds 15 lineups.
-(Snapshot `cond` is 5 for everyone in this window — F-1 does not exist yet — so "fielded XI"
+(Snapshot `cond` is 5 for everyone in this historical window — it predates F-1 — so "fielded XI"
 is squad identity here, not condition.)
 
 **Taking only the top three was arbitrary — all 13 teams that played are measured.** Two
@@ -3537,8 +3568,8 @@ understated. Engine changes are input-dependent, so interspersed failures are a
 possibility rather than a clean release boundary.
 
 `LOAD_PRED` selects the integration predicate (default `C`). C is published, and the probe also
-integrates at D at every τ and prints the difference — F-1 has not chosen, so the calibration
-has to carry which predicate it is conditional on.
+integrates at D at every τ and prints the difference. F-1 subsequently selected D, but the
+published figures remain C-conditioned: calibration must always carry the predicate it used.
 
 Without `TAU_SWEEP` only `TAU_H` runs. **Calling a single-τ run a "decision" makes a probe
 default the production recovery rate** — that is why the sweep exists.