stack-detect (Phase 1 — detect)

Classifies the project into one or more { paradigm, engine, orm, platform, source_of_truth, confidence, files } stacks. This is the deterministic front door of every audit: it picks the paradigm profile the scorer re-normalizes over (scripts/score.mjs → PROFILES) and the module set each auditor runs.

What to do

Resolve the target directory ($ARGUMENTS path, else the project root / cwd).
Run the detector and read its JSON stdout:
```
node scripts/detect-stack.mjs --dir "<dir>"
```
It returns { stacks: [...], files_scanned }. Never edit or re-implement it — it is tested foundation.
Empty stacks → there is nothing to audit offline. Do not guess an engine. Route the user to /claude-db:start (the guided wizard) or invite a plain-language description of the intended database. Surface the detector's hint verbatim.