Updated both passages in all six locales and rebuilt dist/. Other site text, styles, addresses and game rules are unchanged.

Build, locale typecheck and Chromium interaction checks passed. Existing design findings and unavailable WebKit testing are documented in DESIGN.md.

The builder made both wording changes exactly as asked, in all six locales, and the rebuild changed nothing else. I found one problem, and it is in the requested wording itself: the live contract contradicts it. I logged that as an info finding for the requester to decide, not as a defect for the builder to fix. .imd-findings.json holds that one finding.

Area	Count
Brief requirements	4: 4 met, 0 missing, 0 faked
Broken features	0
Product on first screen at 390	yes
taste@1 checks passed	7 of 16 (none of the 9 failures is a finding, see below)
Copy findings	1 (info, needs the requester)
Share card	no (og:title and og:image missing)

Requirements

1. "faq.a3: replace … with: 'The garden contract reads SqueekCore directly, with no oracle. The only owner switch is …'": met. It is word for word at web/src/locales/en.js:341, translated in tr.js, es.js, zh.js, hi.js and ar.js, and appears on the guide page in en, ar and zh at 390 px. The old leading "No." is gone; the brief's new text replaces that whole answer, so I counted this as correct.
2. "guide.intro: replace … with 'so nobody can speed a plant up by hand'": met. It is at en.js:283 and in the five translations, and the guide page shows it.
3. "and rebuild": met. dist/assets/nav-BgoFB5g8.js contains all the new strings, and none of the old ones are left in dist/.
4. "Change nothing else: no other text, styles, contract addresses or game rules": met. I compared the old and new bundles directly: the only differences are the 12 locale strings and the renamed bundle file references. The commit also adds a DESIGN.md, which is documentation the site does not load.

The finding: info, fidelity, needs the requester. The new wording says no one can speed a plant up by hand and that plants simply keep their progress when the owner switches cores. The contract says otherwise:

• setCoreFrom (contracts/SqueekGarden.sol:517) checks only that the readings the owner supplies are not lower than before. There is no upper limit, and it works on the same core.
• So an owner call with inflated readings pushes every growing plant forward at once.
• There are also ten owner-only functions, so "the only owner switch" holds only if it means growth.

I put the exact call that shows this, and a suggested wording that matches the code, in the finding. The builder followed the brief, so this is the requester's decision.

Not reported as findings. The brief says "Change nothing else: no other text, styles", and that outranks the probe. The failures were already there before this change:

• Layout: at 320 px, "+380" and "Unlocks for everyone" are cut off by 18 px, and the readout labels are truncated.
• Type: 11 type sizes and 4 font families.
• Text styling: all-caps, widely spaced labels.
• Contrast: 3.4:1 on the price tags.
• Emoji in the seed packets.
• Surfaces: borders and shadows on the same element, and one card inside another.
• Share card: no og:title or og:image.

The first screen at 390 px shows the name, Connect wallet, the live hamster scene with its readings, and the garden plots.

Idea: a pixel farming game whose plots grow only from the live hamster's on-chain wheel runs, carried by the moonlit hamster-wheel scene.

How I checked

• I ran the taste probe after installing Playwright in a temp folder outside the repo.
• I rendered dist/guide.html at 390 px in en, ar and zh with Chromium. The edited text shows, Arabic lays out right to left, and nothing scrolls sideways.

Not done

• No WebKit pass. This change is text only, and time was short.
• No Foundry proof. The finding is info and the project uses Hardhat.
• No repository files were changed. git status is clean.