DoGaMa/DoGaMa-serv
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: require milestone push and web UI validation

Browse Source
This commit is contained in:
codex
2026-08-07 20:09:14 +00:00
parent 9eb4fe2cd8
commit 92c5e11bbc
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+8 -2
View File
@@ -43,7 +43,10 @@ Stop and report any request that would weaken these boundaries.
- Work only on a non-`main` feature branch. If the task starts on `main`, create or request a working branch before editing. - Work only on a non-`main` feature branch. If the task starts on `main`, create or request a working branch before editing.
- Never modify, commit on, merge into, rebase, reset, delete or push `main`. - Never modify, commit on, merge into, rebase, reset, delete or push `main`.
- Commit or push a working branch only when the task requests delivery. Never approve or merge a Gitea pull request. - Develop each milestone on its own dedicated working branch.
- After a milestone's validations and commits, always push its working branch to Gitea using the `codex` account. The milestone is not complete until the remote branch exists.
- After pushing, create a pull request from the working branch to `main` when the available tools permit it. If automatic creation is unavailable, provide the URL or exact information needed to open it immediately.
- Never approve or merge a Gitea pull request.
- Do not alter remotes, credentials or repository-wide Git configuration unless explicitly requested. - Do not alter remotes, credentials or repository-wide Git configuration unless explicitly requested.
- Never use destructive recovery commands such as `git reset --hard`, `git clean`, or checkout-based restoration without explicit approval and a verified target list. - Never use destructive recovery commands such as `git reset --hard`, `git clean`, or checkout-based restoration without explicit approval and a verified target list.
- Before committing, review `git status`, `git diff --stat`, the complete relevant diff and `git diff --check`. - Before committing, review `git status`, `git diff --stat`, the complete relevant diff and `git diff --check`.
@@ -58,7 +61,8 @@ Stop and report any request that would weaken these boundaries.
6. Run targeted tests first. 6. Run targeted tests first.
7. Run the applicable global validations. 7. Run the applicable global validations.
8. Update `docs/PROJECT-STATE.md` with the new baseline, delivered behavior, durable decisions, limitations and next work. 8. Update `docs/PROJECT-STATE.md` with the new baseline, delivered behavior, durable decisions, limitations and next work.
9. Review and report the final diff and validation status. 9. Review the final diff and validation status, then commit the completed milestone.
10. Push the working branch to Gitea with the `codex` account and create, or provide the exact link to create, a pull request to `main`.
## Validation ## Validation
@@ -86,6 +90,8 @@ git diff --check
Use installed tools and pinned dependencies. Do not silently install missing tools; report the exact blocker. Keep caches under `.cache/codex/` or an OS temporary directory and remove only artifacts created by the current task. Use installed tools and pinned dependencies. Do not silently install missing tools; report the exact blocker. Keep caches under `.cache/codex/` or an OS temporary directory and remove only artifacts created by the current task.
For changes that affect the web interface, exercise the relevant screens and states in a real browser when the environment permits it. Capture screenshots and use them to check at least the overall rendering, alignment, overflow, labels, primary states, relevant responsive behavior and obvious visual regressions. Screenshots are local validation artifacts and must not be committed unless explicitly requested or another project rule requires it. If browser validation or screenshots are technically unavailable, state that explicitly in the completion report.
## Completion report ## Completion report
- Summarize behavior and contract changes. - Summarize behavior and contract changes.