fix: align portal queries and super auth
This commit is contained in:
@@ -25,6 +25,15 @@
|
||||
- Go tests: `go test ./...` (some service tests exist under `backend/app/services/*_test.go`).
|
||||
- Frontend: build + lint are the main checks (`npm -C frontend/superadmin run build && npm -C frontend/superadmin run lint`).
|
||||
|
||||
## Planning Requirements
|
||||
|
||||
- Before any non-trivial development work, first produce a complete plan document (tasks, sequence, dependencies, and acceptance criteria) and get confirmation to proceed.
|
||||
- Plan format MUST follow spec-kit `plan-template.md` structure (Summary, Technical Context, Constitution Check, Project Structure, Plan Phases, Tasks, Dependencies, Acceptance Criteria, Risks). `docs/plan.md` MUST include a task breakdown list.
|
||||
- Use the local template `docs/templates/plan-template.md` as the source of truth (no web fetch required).
|
||||
- Use `docs/plan.md` as the active plan for the current phase.
|
||||
- When the phase completes, move `docs/plan.md` to `docs/plans/<date>.md` for archival.
|
||||
- After archiving, clear `docs/plan.md` to await the next plan.
|
||||
|
||||
## Commit & Pull Request Guidelines
|
||||
|
||||
- Commits generally follow a simple convention like `feat: ...` / `fix: ...` / `chore: ...` (keep subject short and imperative).
|
||||
|
||||
Reference in New Issue
Block a user