Security-relevant behaviour (development tokens, loopback HTTP, inline
checkpoints, raw provider keys, optional verification profiles) was
keyed off NODE_ENV === 'production', so any deployment that forgot
NODE_ENV silently ran with development rules.
- @wishforge/contracts exports deploymentMode/isProduction/
requireDeploymentMode. WF_DEPLOYMENT_MODE wins; misspelled values and
development combined with NODE_ENV=production are rejected; NODE_ENV
remains a fallback only for libraries and tests.
- All API, runtime, artifact, Git service and operator-script checks use
isProduction.
- The API, worker, Git service and Runner refuse to start without an
explicit WF_DEPLOYMENT_MODE; the IDE gateway treats anything other
than an explicit development mode as production.
- The development seed loads .env.local before checking the mode.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds prettier 3.9.8 (exact) with a shared config (single quotes,
120 columns, trailing commas), .prettierignore, .editorconfig and the
`format` / `format:check` scripts, then formats all TypeScript,
JavaScript, CSS, JSON and YAML sources.
Purely mechanical: no behaviour change. Typecheck passes, the vitest
suite and the 74 IDE node tests produce the same results as before
(socket-binding tests still cannot run inside this sandbox).
Previously the longest source line was ~3000 characters; reviewing the
following semantic changes now produces readable diffs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Imports the previously untracked working tree as-is so that the review
changes that follow (requirements -> design -> implementation) can be
reviewed as diffs and reverted if needed. No content changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>