Enforce event-driven repository monitoring

[rotnov]

What changed

• defines a checkpointed, event-driven repository monitoring policy in AGENTS.md
• excludes historical documentation references, closed issues, and completed PRs from recurring polling
• records the project-wide choice as D-078 and updates the specification map and governance documentation
• makes CI fail closed if the essential monitoring clauses disappear
• captures the process lesson in the project iEvo evolution overlay

Why

Historical references to issue #125 and PR #119 were incorrectly treated as live monitoring targets. The new policy separates durable historical evidence from repository events observed after an explicit checkpoint.

Impact

Agents on both Codex and Claude Code consume the same canonical AGENTS.md policy through the existing CLAUDE.md redirect. Monitoring is now bounded to new default-branch commits, new or changed PRs, and state changes on task-active PRs.

Validation

• python3 -B -m unittest discover -s scripts -p 'test_*.py' — 240 passed
• python3 -B scripts/validate_agent_assets.py
• python3 -B scripts/validate_agent_policies.py
• ruby scripts/test_check_roadmap_evidence.rb — 99 runs / 432 assertions
• ruby scripts/check_roadmap_evidence.rb
• ruff check scripts/validate_agent_assets.py scripts/test_validate_agent_assets.py
• cargo doc --workspace --no-deps
• pinned iEvo deep review — clean

[rotnov]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: f5bd5d49bc

ℹ️ 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".