PR_26177_OWNER_011-codex-zip-and-next-pr-standard

[ToolboxAid]

Summary

Adds governance that every Codex execution produces required reports and a repo-structured ZIP, and that completed PR ZIP review automatically drives the next logical PRs.

Scope

• Documentation/governance only.
• Active Project Instructions updated only.
• No runtime, UI, API, database, or start_of_day changes.

Validation

• PASS: staged whitespace validation with generated codex_review.diff excluded.
• PASS: documentation/governance-only changed-file check.
• PASS: ZIP-on-every-result rule exists.
• PASS: hard stops require ZIP/report output.
• PASS: next logical PRs plural wording exists.
• PASS: automatic next PR planning is tied to completed PR ZIP review.
• PASS: SOD/EOD, Product Owner testable, and page-level Playwright rules remain present.

Artifact

• tmp/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_delta.zip

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 090163bf1d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Replace placeholder node validations with runnable checks

In this validation lane, the listed node -e entries are prose labels rather than executable JavaScript. I checked node --help (-e evaluates the argument as a script), and this command fails with a SyntaxError/exit 1, so the recorded Result: PASS cannot be reproduced by anyone rerunning the documented validation commands for this PR.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Index the new completed-ZIP workflow rule

This new completed-PR ZIP automation lives only in addendums/pr_workflow.md, but I checked the active Project Instructions indexes (README.txt and PROJECT_INSTRUCTIONS.md) and they do not list that addendum by path; only release_gate.md mentions it as a protected file. For agents following the documented read-first/index workflow, the detailed requirements to generate each next PR with a Codex command, Playwright scope, and manual validation can be missed, leaving only the shorter backlog note in the indexed team backlog standard.

Useful? React with 👍 / 👎.