fix(cli): address Reviewer A/B consensus findings (round 1)

- Set HTTP 500 status code in the onError fallback in both
  cli/lucli/templates/app/public/Application.cfc and public/Application.cfc
  so monitoring tools and CDNs don't cache the Wheels-init failure as
  a successful response. Uses a plain struct for cfheader's
  attributeCollection per CLAUDE.md cross-engine invariant #10
  (Adobe CF 2023/2025 reject the arguments scope on built-in tags).
- Document the no-nested-braces assumption behind catchClosePattern in
  vendor/wheels/tests/specs/cli/OnErrorFallbackGuardSpec.cfc so a future
  edit that adds nested braces inside the outer catch knows why the
  silent fallback to scanFrom=1 is the safety net.
- Fix the contradictory recovery steps in the first-15-minutes guide
  (wheels reload requires a running server) at
  web/sites/guides/src/content/docs/v4-0-1-snapshot/start-here/first-15-minutes.mdx.
- Replace the speculative "pre-4.0.2" wording in
  .ai/wheels/troubleshooting/common-errors.md with "4.0.1 or earlier"
  since the fix is still in [Unreleased].

Signed-off-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>

Author: github-actions[bot]

.ai/wheels/troubleshooting/common-errors.md

@@ -27,7 +27,7 @@ Wheels failed to initialize. Check the server log for details.
 3. Verify the `/wheels` mapping resolves: on a fresh install, `vendor/wheels/Injector.cfc` must exist. If it doesn't, re-run `wheels new` or copy the framework files manually.
 4. Run `wheels reload` (or stop/start the server) to pick up the corrected mapping.
 
-**Note:** Before the #2774 fix, this failure cascaded into a second `[WO] does not exist` exception that hid the real cause. If you see the old cascade on a pre-4.0.2 app, the underlying cause is always a failed `onApplicationStart` — see above.
+**Note:** Before the #2774 fix, this failure cascaded into a second `[WO] does not exist` exception that hid the real cause. If you see the old cascade on a version that predates this fix (i.e. 4.0.1 or earlier), the underlying cause is always a failed `onApplicationStart` — see above.
 
 ## Common Association Errors
 

cli/lucli/templates/app/public/Application.cfc

@@ -280,6 +280,16 @@ component output="false" {
 		// cascading into "The key [WO] does not exist." (issue ##2773).
 		if (!StructKeyExists(application, "wo")) {
 			setting requestTimeout=30;
+			// Surface a real 5xx so monitoring tools and CDNs don't cache this
+			// failure as a successful response. Use a plain struct for
+			// attributeCollection — Adobe CF 2023/2025 reject the `arguments`
+			// scope on built-in tags (CLAUDE.md cross-engine invariant ##10).
+			try {
+				local.statusArgs = {statusCode: 500, statusText: "Internal Server Error"};
+				cfheader(attributeCollection=local.statusArgs);
+			} catch (any headerErr) {
+				// Header may already have been written; the body still renders.
+			}
 			WriteOutput("<h1>Application Error</h1>");
 			WriteOutput("<p>Wheels failed to initialize. Check the server log for details.</p>");
 			try {

public/Application.cfc

@@ -294,6 +294,16 @@ component output="false" {
 		// cascading into "The key [WO] does not exist." (issue ##2773).
 		if (!StructKeyExists(application, "wo")) {
 			setting requestTimeout=30;
+			// Surface a real 5xx so monitoring tools and CDNs don't cache this
+			// failure as a successful response. Use a plain struct for
+			// attributeCollection — Adobe CF 2023/2025 reject the `arguments`
+			// scope on built-in tags (CLAUDE.md cross-engine invariant ##10).
+			try {
+				local.statusArgs = {statusCode: 500, statusText: "Internal Server Error"};
+				cfheader(attributeCollection=local.statusArgs);
+			} catch (any headerErr) {
+				// Header may already have been written; the body still renders.
+			}
 			WriteOutput("<h1>Application Error</h1>");
 			WriteOutput("<p>Wheels failed to initialize. Check the server log for details.</p>");
 			try {

vendor/wheels/tests/specs/cli/OnErrorFallbackGuardSpec.cfc

@@ -88,6 +88,18 @@ component extends="wheels.WheelsTest" {
 						//    application.wo.* dereference. Find the position of
 						//    the first such call after the catch block closes,
 						//    and assert the guard appears before it.
+						//
+						// Assumption: the outer catch body has no nested
+						// braces. `[^\}]*` only matches catch bodies whose
+						// contents (after comment stripping) contain no `{`
+						// or `}`. If a future edit introduces a conditional
+						// or nested try inside the outer catch, this regex
+						// will fail to match and `scanFrom` falls back to 1
+						// (top of onErrorBody) — the spec still passes as
+						// long as the guard exists, but the "scan after the
+						// catch" precision is lost. Widen the pattern (e.g.
+						// a brace-counter like the one above) if that
+						// becomes necessary.
 						var catchClosePattern = "catch\s*\(\s*any\s+\w+\s*\)\s*\{[^\}]*\}";
 						var catchMatch = reFindNoCase(catchClosePattern, onErrorBody, 1, true);
 

web/sites/guides/src/content/docs/v4-0-1-snapshot/start-here/first-15-minutes.mdx

@@ -48,7 +48,7 @@ You'll see log lines ending with something like `Server started successfully`. O
 The dev server stays running in the background. Leave the terminal open.
 
 <Aside type="caution" title="Seeing an Application Error page instead?">
-  If the browser shows `Application Error — Wheels failed to initialize` rather than the welcome page, the error message on screen includes the underlying cause. Check the server log for the full stack trace. The most common cause on a fresh install is a stale `/wheels` CFML mapping — try stopping the server, running `wheels reload`, and restarting. If the mapping issue persists, the server log will point to the specific file that failed to load.
+  If the browser shows `Application Error — Wheels failed to initialize` rather than the welcome page, the error message on screen includes the underlying cause. Check the server log for the full stack trace. The most common cause on a fresh install is a stale `/wheels` CFML mapping. While the server is running, try `wheels reload` to pick up the corrected mapping. If that does not clear it, stop and restart the server. The server log will point to the specific file that failed to load.
 </Aside>
 
 ## 3. Add a page (5 min)