fix(tools): inline dotenv.parse in generate-config — kill canary CI breakage from layout sweep

[joelteply]

What

Replace import * as dotenv from 'dotenv' in tools/generator/generate-config.ts with an inline 15-line parseEnvText function. Removes the dotenv dep entirely from this script.

Why

The layout sweep (PR #1557, task #214) moved generate-config.ts from src/generator/ to tools/generator/. Node's module resolution walks ancestors of the script location, not process.cwd(). From tools/generator/, the upward walk goes tools/generator/ -> tools/ -> / and finds no node_modules/dotenv — that module only lives at src/node_modules/dotenv (a sibling of tools/, not an ancestor).

Every TS-validation CI job has been failing on canary since the layout sweep merged:

Error: Cannot find module 'dotenv'
Require stack:
- /home/runner/work/continuum/continuum/tools/generator/generate-config.ts

Surfaced via PR #1561's failing checks (validate / ts-eslint-baseline-ratchet / verify-architectures / verify-after-rebuild). NOT caused by that PR — pre-existing canary infrastructure regression.

How

dotenv was only ever used for its .parse(text) function (pure string-to-KV transform). Inlined as parseEnvText with the same semantics:

• KEY=value lines
• Optional surrounding double or single quotes around the value
• # comments + blank lines ignored

The .config() side-effect path (which mutates process.env) was never used here. Like-for-like behavioral replacement.

Doctrinal bonus

Generator scripts now have a Node-stdlib-only footprint, matching generate-version.ts's shape. No upward-walk module-resolution surprises possible. Aligns with task #209 (Node deps trimming).

Test plan

• Local: cd src && npx tsx ../tools/generator/generate-config.ts -> "shared/config.ts unchanged" (idempotent re-run), ports + active_example resolved correctly
• CI: validate / ts-eslint-baseline-ratchet on this branch should now produce a real signal instead of the dotenv-missing module error

Generated with Claude Code