Dev Environment
Open the standalone repository root. It contains the product app and the developer-tooling layer.
Use Node 22 (.nvmrc) and run npm run bootstrap once to install each committed lockfile.
The developer guide is the
canonical command and access map.
| Workspace | Path | Focused check |
|---|---|---|
| Root and Trigger | . | npm test, npm run env:check, npm run test:developer |
| Web app and API | web/ | npm --prefix web test, npm --prefix web run build |
| Supabase helpers and Edge tests | supabase/ | npm --prefix supabase test |
| Docs site | docs-site/ | npm --prefix docs-site run build |
npm run check runs the SABLE local gate: manifest validation and generated-copy
checks, web and security tests, static build, root/Trigger and developer-tooling tests, Trigger
typecheck, Supabase tests, and docs build. It needs no production credentials. For local API routes,
run npm run dev:sable after Vercel development access is provisioned.
The current CI jobs omit the web production build and developer-tooling tests, so run the full local
gate before a PR until CI coverage is aligned. npm run doctor:safety reads local target metadata
without a network call; npm run doctor:safety -- --connected requires an approved non-production
Supabase target. Offline code and tests need no target.
The root .mcp.json, .claude/settings.json, and CLAUDE.md configure agent-assisted sessions.
npm run setup:gitnexus builds the local code index; npm run doctor:claude -- --offline
checks Claude configuration and the safety hook. Open the repository root so these files load.
The SABLE manifests are in env-manifests/. npm run env:check checks source references,
runtime coverage, and generated copies without querying provider values. npm run env:drift:portfolio
requires neighboring repositories and is outside the fresh-clone baseline. The six DataSync and
Lead-to-Cash manifests remain registry metadata; SABLE work does not modify those products.
The standalone repository owns production release workflows in .github/workflows/ after the
IND-12 cutover. Treat cutover plans and staged workflow copies as historical records.