T

saqib mirandClaude Sonnet 5 a7216b7531 docs: plan and design artifacts for SaaS integration feature

/speckit-plan output for 002-saas-integration: technical context and
constitution gate check (all PASS), Phase 0 research (9 decisions:
signed-token format, replay resistance via Redis jti tracking, clock
skew tolerance, rotation via previous-credential transition window,
per-integration/per-user rate limiting, strict unknown-field
rejection, non-leaking error responses, and reconciling the
placeholder Prisma schema with docs/06's real Product shape), Phase 1
data model (Product revision, ProductIntegration, CustomerReference,
AuditLog reuse for auth events), the inbound request validation
contract (9 fixed steps + admin lifecycle endpoints), and an
8-scenario quickstart.

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

2026-08-21 17:45:02 +05:30

.claude/skills

chore: install GitHub Spec Kit tooling

2026-08-21 16:22:13 +05:30

.husky

first commit

2026-08-19 16:29:17 +05:30

.specify

chore: install GitHub Spec Kit tooling

2026-08-21 16:22:13 +05:30

docs

docs: add architect's additions doc (gaps & recommendations)

2026-08-21 17:35:32 +05:30

prisma

first commit

2026-08-19 16:29:17 +05:30

scripts

first commit

2026-08-19 16:29:17 +05:30

specs

docs: plan and design artifacts for SaaS integration feature

2026-08-21 17:45:02 +05:30

src

first commit

2026-08-19 16:29:17 +05:30

tests

first commit

2026-08-19 16:29:17 +05:30

.dockerignore

first commit

2026-08-19 16:29:17 +05:30

.editorconfig

first commit

2026-08-19 16:29:17 +05:30

.env.example

fix: stop tracking .env files with committed secrets

2026-08-21 16:10:32 +05:30

.gitattributes

first commit

2026-08-19 16:29:17 +05:30

.gitignore

fix: stop tracking .env files with committed secrets

2026-08-21 16:10:32 +05:30

CONTRIBUTING.md

first commit

2026-08-19 16:29:17 +05:30

docker-compose.development.yml

update compose

2026-08-20 11:52:46 +05:30

docker-compose.prod.yml

first commit

2026-08-19 16:29:17 +05:30

docker-compose.test.yml

feat: implement CI pipeline (Jenkinsfile) for 001-ci-pipeline

2026-08-21 17:25:46 +05:30

Dockerfile

update docker dependency issue

2026-08-20 11:27:15 +05:30

eslint.config.js

first commit

2026-08-19 16:29:17 +05:30

Jenkinsfile

feat: implement CI pipeline (Jenkinsfile) for 001-ci-pipeline

2026-08-21 17:25:46 +05:30

lint-staged.config.js

first commit

2026-08-19 16:29:17 +05:30

package-lock.json

add the build command and also added the docker commands

2026-08-19 18:31:34 +05:30

package.json

add the env

2026-08-19 19:03:45 +05:30

prettier.config.js

first commit

2026-08-19 16:29:17 +05:30

README.md

feat: implement CI pipeline (Jenkinsfile) for 001-ci-pipeline

2026-08-21 17:25:46 +05:30

tsconfig.build.json

first commit

2026-08-19 16:29:17 +05:30

tsconfig.json

first commit

2026-08-19 16:29:17 +05:30

vitest.config.ts

first commit

2026-08-19 16:29:17 +05:30

README.md

Development

docker compose --env-file .env.development -f docker-compose.development.yml up -d --build

Test

docker compose --env-file .env.test -f docker-compose.test.yml up --build

Production

docker compose --env-file .env.prod -f docker-compose.prod.yml up --build -d

Stop

docker compose -f docker-compose.prod.yml down

Local environment setup

.env.development, .env.test, and .env.prod are gitignored (they hold real credentials) — copy .env.example to the one you need and fill in real values before running any command above.

CI/CD

Every push/PR triggers the Jenkins pipeline defined in Jenkinsfile. Stage order: checkout → install → environment validation → typecheck → lint → format check → unit test → integration test → E2E test → build → Docker build → publish → deploy. Publish/deploy only run on branches with a configured deploy target (main → prod, develop/test → test); other branches validate and build only. Pipeline run status and per-stage logs are visible in the Jenkins UI for the relevant job — see specs/001-ci-pipeline/quickstart.md for how to validate the pipeline itself, and specs/001-ci-pipeline/contracts/pipeline-stage-contract.md for the guarantees each stage makes.

Required Jenkins credentials (see the header comment in Jenkinsfile for exact IDs): per target environment (test, prod) a Postgres password, Redis password, JWT secret, and AWS access key/secret, plus one shared Docker registry username/password. None of these are ever read from a file in this repository.