/claim and a new forge's home load with no console errors #11345

Replaces part of #11278. The production probe on 2026-11-11 (forge probe-qxkv, 0.7.533) saw one console error on /claim and one on the new forge's home.

Done:

• [ ] Reproduce both by loading /claim and a spawned forge's home in the preview (or reading their page scripts against the CSP), name each cause in the pull, and fix it.
• [x] A test that would have caught each (e.g. the inline script hash in the CSP, or the element the script looks up exists).

If a cause cannot be reproduced, say so in the pull and fix the one that can.

Reviewed pull #11358 at its head: ticked A test that would have caught each (e.g. the inline script hash in the CSP, or the element the script looks up exists).. left open: Reproduce both by loading /claim and a spawned forge's home in the preview (or reading their page scripts against the CSP), name each cause in the pull, and fix it. — Neither error was reproduced or its text confirmed. Only a likely cause (interest-cohort) is fixed, so the issue stays open until the probe text confirms it..

Left open after pull #11358 landed: 1 unticked item remains (Reproduce both by loading /claim and a spawned forge's home in the preview (or reading their page scripts against the CSP), name each cause in the pull, and fix it.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

Split: the open box is #11397; the landed pull's work stays.