SR Method EN
Closing, E2E tests and GitHub
What Codex must produce at closure and how to handle GitHub.
Closing, E2E tests and GitHub
Closing an SR lot is not a simple summary. It must let the user test, validate and resume.
What Codex must produce at closure
- What is done.
- Observed result.
- Expert / product reading.
- Checks executed.
- SR memory used.
- User E2E tests.
- Remaining risks.
- Next step.
User E2E tests
Codex must provide a short, real list of user tests.
Example:
1. Open an existing folder with anomalies.
2. Verify that the AI Analysis tab shows expected results.
3. Change a user status.
4. Reload the page.
5. Confirm the status is preserved and the old control no longer appears.GitHub
Commit, push, branch deletion, publication and history rewrite are sensitive actions.
Codex must:
- explain scope;
- verify the diff;
- verify that sensitive files are not published;
- ask for explicit validation;
- push only after validation.
Closure prompt
Close this SR lot.
Reread the diff, critical files, tests and contracts.
Give:
- what is done;
- observed result;
- checks executed;
- changed files;
- user E2E tests;
- remaining risks;
- decision: done, user_testing, repair or blocked;
- next step.
Do not push anything to GitHub without explicit validation.