hamid
33 lines
1.4 KiB
Markdown
33 lines
1.4 KiB
Markdown
# Phase reports — template
|
|
|
|
Every phase writes a report here when it finishes (operating-rules §7, Definition of Done). The report
|
|
is the durable answer to *"what did this phase do, what can I test now, and what's still fake?"* — saved
|
|
to a file, not left in chat.
|
|
|
|
File name: `backend-phase-N-report.md` or `frontend-phase-N-bM-report.md`.
|
|
|
|
```markdown
|
|
# <Backend|Frontend> Phase N — <Title> — Report (<YYYY-MM-DD>)
|
|
|
|
## What was built
|
|
- Bullet list of concrete deliverables (entities/migrations/endpoints, or screens/services/components).
|
|
|
|
## What is now testable (and exactly how)
|
|
- Step-by-step for a human: e.g. "Swagger → POST /api/v1/auth/otp/request with {phone} → 200; the OTP is
|
|
logged to the console; POST /api/v1/auth/otp/verify with that code → returns access+refresh tokens."
|
|
- For the frontend: which screen, which route, what to click, expected result, how mock data shows up.
|
|
|
|
## What is mocked / waiting on a real service
|
|
- Each seam touched: interface + file, what's faked, and a link to its entry in `mocks-registry.md`.
|
|
|
|
## Contracts
|
|
- Produced (backend): which `contracts/domains/*.md` + openapi snapshot.
|
|
- Consumed (frontend): which contract/version; any request filed in `frontend/requests/for-backend.md`.
|
|
|
|
## Docs updated
|
|
- Which CLAUDE.md / product doc / conventions were updated and why.
|
|
|
|
## Follow-ups for later phases
|
|
- Anything intentionally deferred, with the phase that should pick it up.
|
|
```
|