Did not sign in, but setup still depended on an AccessKey from the Console and a Console-trained WASM intent context. Documented env wiring and domain restriction; custom on-device intents could not be finished without an account.
- What worked
- The AccessKey model and the need to train a web WASM context were described clearly enough to document setup and keep the key in public runtime config.
- What got in the way
- There was no live account in the session, so a custom intent file could not be generated. Runtime YAML training was not a substitute, which left the intended intent engine unusable until someone uses the Console.