nitrix/fete
1
0
Fork 0
Code Issues 1 Pull Requests 10 Actions Packages Projects Releases 13 Wiki Activity

Track completion of T-1 and T-2 health endpoint, add progress tracking rule

Browse Source 
Check off all T-1 acceptance criteria (retroactively) and the health-check
criterion of T-2. Add methodology rule to CLAUDE.md requiring acceptance
criteria to be checked off when tasks or stories are completed.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
nitrix
2026-03-04 18:10:22 +01:00
parent 5ad6a08b72
commit 958222d0c0
2 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
CLAUDE.md
View File

@@ -21,6 +21,7 @@ These are the non-negotiable principles of this project. Every decision — arch
- Refactoring is permitted freely as long as it does not alter the fundamental architecture. - Refactoring is permitted freely as long as it does not alter the fundamental architecture.
- No vibe coding. Every line of code must be intentional and traceable to a requirement. - No vibe coding. Every line of code must be intentional and traceable to a requirement.
- Document integrity: when a decision is revised (pivot), add an addendum with rationale — never rewrite or delete the original decision. Traceability over tidiness. - Document integrity: when a decision is revised (pivot), add an addendum with rationale — never rewrite or delete the original decision. Traceability over tidiness.
- When a setup task or user story is completed, check off its acceptance criteria in the corresponding spec file (`spec/setup-tasks.md` or `spec/userstories.md`) before committing. Progress must be tracked — no silent completions.
### Privacy ### Privacy

14
spec/setup-tasks.md
View File

@@ -10,12 +10,12 @@
**Description:** Set up the repository structure with separate directories for backend and frontend, scaffolded with the chosen tech stack. **Description:** Set up the repository structure with separate directories for backend and frontend, scaffolded with the chosen tech stack.
**Acceptance Criteria:** **Acceptance Criteria:**
- [ ] Single repository with `backend/` and `frontend/` directories - [x] Single repository with `backend/` and `frontend/` directories
- [ ] Backend: Java (latest LTS), Spring Boot, Maven, hexagonal/onion architecture scaffold - [x] Backend: Java (latest LTS), Spring Boot, Maven, hexagonal/onion architecture scaffold
- [ ] Frontend: Vue 3 with Vite as bundler, TypeScript, Vue Router - [x] Frontend: Vue 3 with Vite as bundler, TypeScript, Vue Router
- [ ] Shared top-level files: README, Dockerfile, CLAUDE.md, LICENSE (GPL), .gitignore - [x] Shared top-level files: README, Dockerfile, CLAUDE.md, LICENSE (GPL), .gitignore
- [ ] Both projects build successfully with no source code (empty scaffold) - [x] Both projects build successfully with no source code (empty scaffold)
- [ ] .gitignore covers build artifacts, IDE files, and dependency directories for both Java/Maven and Node/Vue - [x] .gitignore covers build artifacts, IDE files, and dependency directories for both Java/Maven and Node/Vue
**Dependencies:** None **Dependencies:** None
@@ -29,7 +29,7 @@
- [ ] Single multi-stage Dockerfile at repo root that builds backend and frontend and produces one container - [ ] Single multi-stage Dockerfile at repo root that builds backend and frontend and produces one container
- [ ] App connects to external PostgreSQL via environment variable (e.g. `DATABASE_URL`) - [ ] App connects to external PostgreSQL via environment variable (e.g. `DATABASE_URL`)
- [ ] All runtime configuration via environment variables: database connection, optional Unsplash API key, optional max active events - [ ] All runtime configuration via environment variables: database connection, optional Unsplash API key, optional max active events
- [ ] Health-check endpoint so Docker/orchestrators can verify the app is alive - [x] Health-check endpoint so Docker/orchestrators can verify the app is alive
- [ ] README documents setup with a docker-compose example (app + postgres) - [ ] README documents setup with a docker-compose example (app + postgres)
- [ ] Container starts and responds to health checks with an empty database (migrations run on startup or are documented) - [ ] Container starts and responds to health checks with an empty database (migrations run on startup or are documented)