README: add Run report section — full report migrated from the site run page (run pages became compact cards). Pure insertion; data files and citable tags untouched.

README.md

@@ -72,6 +72,93 @@ gemini spent six days stuck pre-registration, then registered,
 completed three quests, and bought a level-31 kami 90 minutes before
 the wall.
 
+## Run report
+
+The run's full report, migrated here from the site's run page on
+2026-07-29 when run pages became compact cards
+([kamibench.ai/experiments/001-budget-boxed](https://kamibench.ai/experiments/001-budget-boxed));
+every number is frozen as originally published.
+
+### What happened
+
+The three arms diverged sharply. Haiku completed the entire onboarding
+chain on day one — registered, funded its operator, bought two kamis,
+finished five quests — and exhausted its budget in 17 hours.
+GPT-4o-mini ran the full week and never once called
+`register_account`: 166 sessions, all 24 of its game transactions
+reverted, zero quests. Gemini spent six days stuck pre-registration,
+was unblocked by a single legible validation error, then completed
+three quests and bought a level-31 kami 90 minutes before the wall.
+Cost per quest: haiku $2.15, gemini $3.00, gpt-4o-mini ∞.
+
+### Milestones
+
+First success per onboarding/economy milestone, against cumulative
+inference. These rows are the frozen baseline that stack iterations
+([Run 2](https://kamibench.ai/experiments/002-stack-delta) onward)
+are compared against at fixed milestones.
+
+| milestone | haiku-4.5 | gpt-4o-mini | gemini-2.5-flash-lite |
+|---|---|---|---|
+| bridge ETH mainnet→Yominet landed | 07-10 23:10 · h1.4 · s2 · 0.14M tok · $0.14 | 07-12 04:45 · h31.0 · s32 · 10.33M tok · $1.56 | 07-11 03:35 · h5.8 · s6 · 0.62M tok · $0.06 |
+| operator wallet funded | 07-10 23:30 · h1.7 · s4 · 0.65M tok · $0.67 | 07-12 22:40 · h48.9 · s49 · 17.58M tok · $2.65 | 07-11 15:30 · h17.7 · s17 · 5.84M tok · $0.59 |
+| account registered in game | 07-10 23:30 · h1.7 · s4 · 0.68M tok · $0.70 | — | 07-16 15:15 · h137.5 · s129 · 62.57M tok · $6.30 |
+| first quest completed | 07-10 23:30 · h1.8 · s4 · 0.87M tok · $0.89 | — | 07-16 15:16 · h137.5 · s129 · 63.01M tok · $6.35 |
+| first kami bought | 07-11 00:35 · h2.8 · s5 · 2.30M tok · $2.34 | — | 07-17 20:30 · h166.7 · s156 · 87.83M tok · $8.84 |
+| first MUSU harvest started | 07-11 01:40 · h3.9 · s6 · 3.14M tok · $3.20 | — | — |
+| first MUSU banked (harvest stop/collect) | 07-11 01:50 · h4.1 · s7 · 3.51M tok · $3.57 | — | — |
+
+Cell = first success: UTC time · hours since run start · session
+number · cumulative tokens (in+out) · cumulative USD at that moment;
+"—" = never happened.
+
+### What we learned
+
+- **Error legibility, not model capability, was the sharpest
+  differentiator.** The same model that ignored opaque chain reverts
+  for four days corrected a human-readable validation error in one
+  turn.
+- **A single missing step was the cleanest capability
+  discriminator.** Two arms completed every onboarding step *except*
+  registration, and neither ever identified it as the blocker.
+- **Cost structure dominated spend.** The 84-tool surface re-billed
+  on every call dominated token spend, prompt caching was never
+  engaged, and un-broken poll loops reached $0.55 per session —
+  making repetition detection a budget control, not just hygiene.
+- **Orientation speed and decision quality are different axes.**
+  Haiku moved fast and bought level-1 kamis; gemini moved slowly and
+  bought a level-31 kami near floor price.
+
+Most of what this run taught us was about the stack, not the models —
+which is what a stress test is for.
+
+### What it changed in the stack
+
+Each learning above became a concrete change, and the whole bundle
+was pinned and re-measured by the next run:
+
+- **Legible pre-transaction validation** — environment interface
+  v1.4.0 → v1.5.1. A blocked game action now fails with a factual
+  precondition error before any gas is spent, instead of an opaque
+  on-chain revert. Directly from the legibility finding and the
+  registration blocker.
+- **A repetition breaker** — scaffold v0.2.0. Looping sessions end
+  instead of billing; Run 1's un-broken poll loops made repetition
+  detection a budget control, not just hygiene.
+- **Session caps and agent-chosen wake scheduling** — scaffold
+  v0.2.0. Bounded session cost, and pacing left to the agent as an
+  explicit, logged choice.
+- **Cache-aware budget accounting** — scaffold v0.2.0. Prompt caching
+  engaged and priced into the budget math, against Run 1's uncached
+  84-tool re-billing.
+
+[Run 2 (Experiment 002)](https://kamibench.ai/experiments/002-stack-delta)
+re-ran this exact protocol with the same three models and the same
+$10 on that stack. Measured against the frozen rows above, the
+changes cut chain revert rates from 0.58 / 0.97 / 0.94 to
+0.048 / 0.000 / 0.011, got all three arms registered in-game, and
+lifted quests at fixed budget (haiku 5→8, gemini 3→5).
+
 ## Layout
 
 ```