Context
In the cloud cold walk for neomjs/neo#20114 (2026-10-26), every npm run server-start in a fresh npx neo-app workspace printed:
[dev-server] WARNING: development theme assets are missing, stale, invalid, or borrowed. Served CSS may trail current SCSS sources.
Recovery: npm run build-themes -- -n -e dev -t all
The app was fully styled. Running the suggested recovery (3.7 s, 509 files written) changed nothing.
The Problem
An agent reads a warning that comes with a recovery command as an instruction, so this creates an extra setup step that does nothing, on every start, for every workspace.
The Architectural Reality
buildScripts/webpack/webpack.server.config.mjs createDevelopmentThemeFreshnessHooks calls inspect() with no arguments (:70). inspect defaults to inspectDevelopmentThemeAssets, whose repoRoot defaults to REPO_ROOT = path.resolve(import.meta.dirname, '../..') (buildScripts/util/developmentThemeAssets.mjs:7, :184).
- In a workspace that resolves to
node_modules/neo.mjs, and dist/development/css is absent there. The cloud agent called the same check: the engine-package arm reported missing: 632, and the workspace arm reported invalidMap: "SCSS source tree contains no buildable theme files".
The Fix
Inspect the root the dev server actually serves, and treat a root with no buildable theme sources as "not applicable" (no warning) rather than "not ready". The engine repository's own dev server keeps today's behaviour.
Acceptance Criteria
Related
Parent: neomjs/neo#20114
Sweeps (2026-10-26T16:06Z): live latest-open, the 5 newest neomjs/neo issues since the 15:52Z full sweep, no equivalent; keyword developmentThemeAssets / "development theme assets" / "theme freshness", none open; A2A, latest 30 messages, no claim. This promotes the defect-note on the workspace theme false alarm with the exact mechanism.
Origin Session ID: 9853627c-2129-4d41-b905-0c74bec35a48
Retrieval Hint: "createDevelopmentThemeFreshnessHooks inspectDevelopmentThemeAssets REPO_ROOT node_modules/neo.mjs workspace false warning build-themes recovery"
Context
In the cloud cold walk for neomjs/neo#20114 (2026-10-26), every
npm run server-startin a freshnpx neo-appworkspace printed:The app was fully styled. Running the suggested recovery (3.7 s, 509 files written) changed nothing.
The Problem
An agent reads a warning that comes with a recovery command as an instruction, so this creates an extra setup step that does nothing, on every start, for every workspace.
The Architectural Reality
buildScripts/webpack/webpack.server.config.mjscreateDevelopmentThemeFreshnessHookscallsinspect()with no arguments (:70).inspectdefaults toinspectDevelopmentThemeAssets, whoserepoRootdefaults toREPO_ROOT = path.resolve(import.meta.dirname, '../..')(buildScripts/util/developmentThemeAssets.mjs:7,:184).node_modules/neo.mjs, anddist/development/cssis absent there. The cloud agent called the same check: the engine-package arm reportedmissing: 632, and the workspace arm reportedinvalidMap: "SCSS source tree contains no buildable theme files".The Fix
Inspect the root the dev server actually serves, and treat a root with no buildable theme sources as "not applicable" (no warning) rather than "not ready". The engine repository's own dev server keeps today's behaviour.
Acceptance Criteria
node_modules), the freshness hooks raise no warning when the served theme CSS is present (unit arm with a workspace-shaped fixture, red-first ondev).dist/development/cssstill warns with the recovery command (existing arms stay green).Related
Parent: neomjs/neo#20114
Sweeps (2026-10-26T16:06Z): live latest-open, the 5 newest
neomjs/neoissues since the 15:52Z full sweep, no equivalent; keyworddevelopmentThemeAssets/ "development theme assets" / "theme freshness", none open; A2A, latest 30 messages, no claim. This promotes the defect-note on the workspace theme false alarm with the exact mechanism.Origin Session ID: 9853627c-2129-4d41-b905-0c74bec35a48 Retrieval Hint: "createDevelopmentThemeFreshnessHooks inspectDevelopmentThemeAssets REPO_ROOT node_modules/neo.mjs workspace false warning build-themes recovery"