Add GitHub issue orchestration standard

[maniczko]

Summary

• Add the RSSmaster GitHub Issue orchestration contract.
• Add agent task issue template, PR evidence template, and .codex/orchestration.json.
• Add the repo-local AGENTS.md orchestration section without changing product logic.

Linked Issue

Closes #3

Evidence

• python C:\Users\user\.codex\skills\github-issue-orchestrator\scripts\codex_orchestrate.py doctor --repo-root . passed.
• npm run test:unit passed.
• Required gate labels satisfied: area:governance, gate:quick.

Agent Checklist

• One issue, one branch, one PR.
• No direct commit to main.
• No secrets, tokens, raw emails, or private documents in logs/comments.
• Residual risks stated.

Risks / Rollback

• The working tree still contains unrelated local changes from other tasks; this PR stages only the orchestration setup files for Apply GitHub Issue orchestration standard to RSSmaster #3.

[gemini-code-assist]

Code Review

This pull request establishes a structured orchestration framework for AI agents by introducing a JSON configuration for gate commands, standardized issue and pull request templates, and updated documentation for the GitHub issue workflow. The reviewer identified a verification gap in the gate:quick command, which lacked backend test execution, and suggested simplifying redundant gate commands by utilizing aggregate scripts for better maintainability.

[gemini-code-assist]

The gate_commands configuration contains redundancies and a verification gap for backend-related areas:

1. Backend Verification Gap: gate:quick is mapped to area:backend, area:data, and area:governance (lines 9-12), but it currently only runs web tests (test:unit:web). It should include npm run test:unit:api to ensure backend changes are actually verified in the fast loop.
2. Redundancy in gate:quality-critical: This command manually duplicates the logic of npm run check (which already includes build, test:unit, and check:contract). Using the aggregate script is more maintainable.
3. Redundancy in gate:corpus: This command runs python scripts/check_api.py twice (once via npm run check and once explicitly).

Simplifying these to use the aggregate scripts defined in package.json improves clarity and ensures all areas are correctly tested.

Suggested change

	"gate:quick": "npm run build && npm run test:unit:web",
	"gate:quality-critical": "npm run build && npm run test:unit && python scripts/check_api.py",
	"gate:browser": "npm run check:layout",
	"gate:runtime": "npm run health",
	"gate:release": "npm run check && npm run health",
	"gate:corpus": "npm run check && python scripts/check_api.py"
	"gate:quick": "npm run build && npm run test:unit:web && npm run test:unit:api",
	"gate:quality-critical": "npm run check",
	"gate:browser": "npm run check:layout",
	"gate:runtime": "npm run health",
	"gate:release": "npm run check && npm run health",
	"gate:corpus": "npm run check"

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4ca3c1f0b7

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

Require API checks for backend/data issue areas

area:backend and area:data are mapped only to gate:quick, but gate:quick runs npm run build && npm run test:unit:web (line 15), which does not execute the API verification commands required for FastAPI/repository changes (python scripts/test_api_unit.py and python scripts/check_api.py per docs/quality-gates.md). In practice, any autopilot issue labeled backend/data can pass with only web checks, allowing backend regressions to be merged without contract or API coverage.

Useful? React with 👍 / 👎.