PR_26179_OWNER_036-reports-are-tracked-source

[ToolboxAid]

PR_26179_OWNER_036-reports-are-tracked-source

Summary

This governance PR clarifies that dev/reports/ contains the authoritative Codex reports for the repository and that reports committed to main are the official record. Reports generated during a PR are expected to be committed as part of that PR, while repository authority remains the report state committed to main.

Scope

• Updated Codex artifact/reporting governance.
• Updated canonical repository structure wording for dev/reports/.
• Updated PR workflow clean-main guidance for intended report updates.
• Preserved the existing PR277 post-merge closeout report artifacts instead of deleting them.
• No runtime code changes.
• No auth changes.
• No Local API changes.
• No .gitignore changes.

Policy Added

• dev/reports/ contains the authoritative Codex reports for the repository.
• Reports committed to main are the official record.
• Reports generated during a PR are expected to be committed as part of that PR.
• Once merged into main, those report versions become the canonical repository history.
• Do not delete report files solely to obtain a clean worktree.
• Do not add dev/reports/ to .gitignore.
• Continue storing ZIPs under dev/workspace/zips/.

Validation

PASS:

• git diff --check
• npm run validate:canonical-structure

[chatgpt-codex-connector]

💡 Codex Review

HTML-JavaScript-Gaming/dev/reports/codex_review.diff

Lines 9 to 11 in ca8af9e

	+## Tracked Report Governance
	+
	+`dev/reports/` is an authoritative repository report location and is tracked by Git.

Regenerate the checked-in review diff

This committed codex_review.diff is stale: it records an earlier draft adding ## Tracked Report Governance, while the actual committed document now adds ## Codex Reports with different wording. Since this PR also makes dev/reports/ the official report record, keeping a review artifact that does not match the committed change will mislead future audit/review workflows that rely on these tracked reports.

ℹ️ 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]

Clarify how post-merge reports get committed

When APPLY_PR/post-merge closeout generates required reports after the PR has already been merged and the runner is back on main, this rule leaves no valid path to close the same PR: the new reports cannot be committed “as part of that PR”, while direct commits to main are prohibited unless OWNER explicitly approves. That makes post-merge closeout runs either leave dev/reports/ dirty or require an undocumented follow-up PR, so the workflow should explicitly exempt/route post-merge closeout reports.

Useful? React with 👍 / 👎.