starcoach-hackathon/zarinpal-analytics-frontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(sdd): authorize frontend implementation

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 19:17:49 +03:30
parent a5173d1601
commit e1e4ed8467
7 changed files with 28 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
tasks/todo.md
View File

@@ -1,15 +1,15 @@
# Phase 3 Task List — Merchant Analytics Dashboard
- Status: Approved task list — implementation explicitly paused
- SDD phase: 3 — Tasks approved; Phase 4 not authorized
- Status: Approved — Phase 4 implementation authorized 2026-08-20
- SDD phase: 4 — Tasks approved and ready to execute
- Source plan: [`plan.md`](plan.md)
- Implementation authorization: Not granted
- Implementation authorization: Granted by user on 2026-08-20
- Approved by user: 2026-08-20
- Last updated: 2026-08-20
Tasks are ordered by dependency. Each implementation task must satisfy its acceptance criteria plus the Definition of Done in `tasks/plan.md`. Likely files are planning targets and may be adjusted before work begins, but a task must be split if it would exceed approximately five files or one focused session.
Approval of this task list closes the SDD Phase 3 review gate only. It does not authorize starting any task, scaffolding the application, installing dependencies, editing application code, or otherwise entering Phase 4. Implementation begins only after a separate explicit user instruction.
The user approved this task list and explicitly authorized Phase 4 implementation on 2026-08-20. Execute tasks in dependency order and stop at their named review checkpoints.
Commands named below are established by Task 4. Before then, verification uses the scaffold's generated commands and read-only contract checks.
@@ -21,7 +21,7 @@ Commands named below are established by Task 4. Before then, verification uses t
**Acceptance criteria:**
- [ ] Backend `API-SPEC.md` and `openapi.yaml` identify an approved matching version.
- [ ] Approved CSV defaults, 30-day analytics/export audit retention, opaque terminal reference, and stable Problem Details base URI are recorded by the provider.
- [ ] Approved CSV defaults, 90-day analytics/export audit retention, 30-day demo-authentication audit retention, opaque terminal reference, and stable Problem Details base URI are recorded by the provider.
- [ ] A checksum or immutable commit hash is recorded for frontend generation.
**Verification:**