docs: update plans and agent instructions
Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
This commit is contained in:
@@ -45,6 +45,8 @@ When driving browser tests via Chrome DevTools MCP, consult:
|
||||
- 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.
|
||||
- If a plan covers frontend interfaces, completion requires BOTH frontend functional testing of the impacted flows and backend `go test ./...`; only then may the plan be marked complete/archived.
|
||||
- Acceptance for frontend-involved work must be validated via frontend **page flows** (browser/UI) to confirm front-back integration. `curl`/API smoke is allowed only for quick backend checks and does **not** count as acceptance for frontend-related tasks.
|
||||
|
||||
## Commit & Pull Request Guidelines
|
||||
|
||||
|
||||
Reference in New Issue
Block a user