sentryagent-idp/openspec/changes/archive/2026-04-02-engineering-docs/specs/dev-environment-setup/spec.md at af630b43d45165891a82ec690704a96e308b3246

Files

SentryAgent.ai Developer f1fbe0e29a chore(openspec): archive all completed changes, sync 14 new specs to library

Archived 4 completed OpenSpec changes (2026-04-02):
- phase-3-enterprise (100/100 tasks) — 6 Phase 3 capabilities synced
- devops-documentation (48/48 tasks) — 3 new + 1 merged capability
- bedroom-developer-docs (33/33 tasks) — 4 new capabilities synced
- engineering-docs (superseded by 2026-03-29 archive) — no tasks

Main spec library grows from 21 → 35 capabilities (+14 new):
federation, multi-tenancy, oidc, soc2, w3c-dids, webhooks,
database, operations, system-overview, api-reference, core-concepts,
developer-guides, quick-start + deployment (merged additive requirements)

Active changes: 0 — project board is clear for Phase 4 planning.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-02 03:50:47 +00:00

2.2 KiB

Raw Blame History

ADDED Requirements

Requirement: Development environment setup guide

The system SHALL include a document (docs/engineering/07-dev-setup.md) that takes a new engineer from zero to a fully running local stack in under 30 minutes, with no prior knowledge of the project assumed.

Scenario: Prerequisites listed completely

WHEN a new engineer reads 07-dev-setup.md
THEN they SHALL find a complete prerequisites list: Node.js 18+, Docker Desktop, Git, a PostgreSQL client (optional), and links to install each — with no undocumented dependencies

Scenario: Repository clone and setup steps complete

WHEN a new engineer follows the clone and setup steps
THEN they SHALL be able to: clone the repo, copy .env.example to .env, run npm install, and have all dependencies installed with zero manual configuration

Scenario: Docker Compose local stack starts successfully

WHEN a new engineer runs docker-compose up -d
THEN all services (PostgreSQL, Redis, API server) SHALL start, migrations SHALL run automatically, and the guide SHALL show how to verify each service is healthy

Scenario: Smoke test confirms working stack

WHEN a new engineer follows the smoke test section
THEN they SHALL run a curl command to POST /oauth2/token with the seed credentials and receive a valid JWT — confirming the full stack is operational

Scenario: Common setup errors documented

WHEN a new engineer encounters a setup error
THEN the guide SHALL include a troubleshooting section covering the 5 most common errors: port already in use, migration failure, Node version mismatch, Docker not running, and missing .env variables

Scenario: Running tests locally documented

WHEN a new engineer wants to run the test suite
THEN the guide SHALL show: npm test (unit tests only, no services needed), npm run test:integration (requires Docker stack), and how to run a single test file

Scenario: Web dashboard local development documented

WHEN a new engineer wants to run the web dashboard
THEN the guide SHALL show how to start the Vite dev server (npm run dev in dashboard/) and which port it runs on, and confirm it connects to the local API server

2.2 KiB Raw Blame History