New on the blog: wheels console — The Debugging Move You're Not Using. <https://blog.wheels.dev/posts/wheels-console-debugging/> The rails-console move, for Wheels: a REPL evaluated INSIDE your running dev app. Models resolve, scopes chain, service() answers, get() reads the real merged config. What it covers: - The three-line validation session that replaces form-submit-dump archaeology: new() -> valid() -> errorsOn() - Scope-chain verification before you touch a view; DI resolution checks before the 500 three requests later - The slash-commands: /models, /routes (which pattern wins, from the dispatcher's own data), /env, /reload - console vs repl — same look, different tools: full app context + running server vs bare CFML calculator - Two habits: verify state after migrations/seeds instead of trusting memory, and respect that deleteAll() at the prompt is real - The honest boundary: dev-workflow tool; production questions belong to observability, not a REPL on a prod box