Documentation is organized by document type and responsibility so architecture, API docs, setup guides, reference material, roadmaps, plans, tasks, runbooks, and checklists are easy to distinguish.
../README.md - repository quick start and canonical command surface../LICENSE - canonical public-use terms and attribution notice for the repository../CHANGELOG.md - canonical release history from the documented baseline forwardarchitecture/ARCHITECTURE_OVERVIEW.md - five-layer architecture contract and system viewsplanning/roadmaps/ROADMAP.md - main development roadmap, sprint status, and canonical progress trackingplanning/roadmaps/PLATFORM_MICRO_ROADMAP.md - scoped platform and DevOps roadmap companionenvironment/setup/ENVIRONMENT_SETUP.md - local, Docker, and deploy setup flowgovernance/RELEASE_VERSIONING.md - semantic versioning and release bookkeeping processarchitecture/ARCHITECTURE_OVERVIEW.md - layer boundaries, architecture contract, and Mermaid system viewsarchitecture/ADR-0002_FRONTEND_STATE_ARCHITECTURE.md - accepted frontend state-management decision recordapi/API_DOCUMENTATION.md - API contract and examplesapi/openapi/ - OpenAPI reference specs for roadmap phasesproduct/FRONTEND_ROUTES.md - route mapproduct/features/ - feature-level behavior notesproduct/features/DesignSystem.md - cross-app UI primitive contract and reuse inventoryproduct/guides/ - end-user quick guides for citizen, agent, and manager rolesenvironment/reference/ENV.md - current source of truth for env rules, browser origins, and the port contractenvironment/reference/ENV_INVENTORY.md - env variable inventory reference snapshotenvironment/reference/ENV_CONFLICTS.md - historical conflict matrix and normalization notesenvironment/reference/ENV_CANONICAL_DECISIONS.md - decision history behind the canonical env modelenvironment/setup/ENVIRONMENT_SETUP.md - local, Docker, and deploy environment setupenvironment/setup/DOCKER_SETUP.md - compose workflow and expected service statesplanning/roadmaps/ROADMAP.md - strategic and sprint roadmapplanning/roadmaps/PLATFORM_MICRO_ROADMAP.md - platform lane roadmapplanning/plans/landing-plan.md - scoped landing-page execution planplanning/tasks/PR_TASKS.md - active deployment rollout task trackerplanning/tasks/PRODUCT_HARDENING_10_10_TASKS.md - Development-only product hardening and quality task trackergovernance/RELEASE_VERSIONING.md - release bookkeeping and versioning policygovernance/CODE_ANNOTATION_CONVENTIONS.md - TSDoc and JSDoc expectations for shared and exported codegovernance/SECURITY.md - secret-management and leakage safeguardsgovernance/QUALITY_SCORECARD.md - Development-only release quality thresholds and evidence contractgovernance/checklists/DOD_CHECKLIST.md - definition-of-done and quality checklistdata/DB_SCHEMA_NAMESPACE_PLAN.md - approved namespace migration and additive-entity designdata/DB_SCHEMA_NAMESPACE_STATUS.md - preserved implementation status for the DB namespace rolloutoperations/observability/ELK.md - observability stack notesoperations/runbooks/ - incident, rollout, quality, and platform runbooksoperations/runbooks/EXTENDED_QUALITY_GATES.md - K6, Stryker, Percy, and Lighthouse execution pathsoperations/runbooks/ACCESSIBILITY_RESPONSIVE_AUDIT.md - explicit accessibility and responsive release checklistoperations/runbooks/MOBILE_PRODUCT_READINESS.md - mobile release-readiness lane and evidence mapoperations/runbooks/DEPLOYMENT_PLATFORM_ROLLOUT_PLAN.md - phased Cloudflare Pages, Render, and Neon rollout planoperations/runbooks/NEON_MANAGED_POSTGRES_BASELINE.md - current managed Postgres baselinespecs/README.md - entry point for source specs and planning inputsspecs/SOURCE_OF_TRUTH.md - executable-spec governance, scope, and update workflowspecs/source-of-truth.dev.json - machine-readable source-of-truth contractspecs/cdc-traceability-matrix.dev.json - machine-readable Development-specialty CDC matrixspecs/cdc-traceability-matrix.dev.md - human-readable Development-specialty CDC matrixspecs/mobile-platform-integration-contract.md - platform and mobile integration contractspecs/mobile-layer-rollout-plan.md - architecture-first mobile rollout planspecs/inputs/ - canonical source documents used by specs and traceability and kept local-only via Git ignore rulesspecs/source-of-truth.dev.json separates repo-enforced canonical files from localInputArtifacts, which stay local-only and are validated through .gitignore coverage rather than repo file existencebaselines/ - captured validation outputs used during remediation phasesInstall:
npm ci --include=dev
Develop:
npm run dev
npm run dev:doctor
npm run dev --workspace=ecotrack-app
npm run dev:mobile
npm run dev --workspace=ecotrack-api
Cleanup:
npm run clean:artifacts
Validate:
npm run lint
npm run lint --workspace=ecotrack-mobile
npm run typecheck
npm run typecheck --workspace=ecotrack-mobile
npm run test
npm run test --workspace=ecotrack-mobile
npm run validate-doc-sync
npm run validate-sonar-coverage-alignment
npm run test:api
npm run test:e2e
npm run test:coverage
npm run test:coverage:api
npm run quality:mobile-readiness
npm run quality:product-hardening
npm run validate-env:all
npm run validate:workspace-toolchain
npm run validate-specs
node infrastructure/scripts/ci/generate-cdc-summary.mjs
npm run ci:release:manifest
npm run ci:release:quality-scorecard
npm run ci:release:deploy-hooks
npm run ci:release:smoke
npm run ci:quality:k6
node infrastructure/scripts/ci/run-mutation-gate.mjs
node infrastructure/scripts/ci/run-visual-gate.mjs
node infrastructure/scripts/ci/run-visual-snapshots.mjs
node infrastructure/scripts/ci/run-lighthouse-gate.mjs
Build:
npm run build
npm run build --workspace=ecotrack-app
Frontend bundle budgets are enforced during ecotrack-app builds via app/scripts/check-bundle-size.mjs.
Use the route-aware budget overrides ECOTRACK_INITIAL_ROUTE_SHELL_GZIP_BUDGET_KB, ECOTRACK_LANDING_ROUTE_GZIP_BUDGET_KB, ECOTRACK_LOGIN_ROUTE_GZIP_BUDGET_KB, ECOTRACK_DASHBOARD_ROUTE_GZIP_BUDGET_KB, ECOTRACK_ADMIN_ROUTE_GZIP_BUDGET_KB, ECOTRACK_MAPPING_VENDOR_GZIP_BUDGET_KB, and ECOTRACK_LOGO_BUDGET_KB when CI or local runs need non-default caps.
UI theme contract checks are enforced during ecotrack-app lint via app/scripts/validate-theme-contract.mjs.
Doc-sync checks are enforced via npm run validate-doc-sync and the managed local pre-commit hook that repo-root installs generate under .githooks/ through the root prepare script. .githooks/ is ignored and remains local-only.
Database:
npm run db:generate
npm run db:migrate
npm run db:seed
npm run db:migrate:seed
Infrastructure:
npm run hooks:install
npm run infra:up
npm run infra:health
npm run smoke-test
npm run infra:down
docs/operations/runbooks/.docs/specs/inputs/ paths and out of Git.tmp/; avoid root-level timestamped temp folders and root temp-*.log files.