From 37feaa555d18d10e0ec9ed1734713f068e05f737 Mon Sep 17 00:00:00 2001 From: saagpatel Date: Sun, 7 Jun 2026 17:48:55 -0700 Subject: [PATCH] docs: remove stale Codex AGENTS labels --- AGENTS.md | 38 +++++++++++++------------------------- 1 file changed, 13 insertions(+), 25 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 9e8e717..88631e9 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,28 +1,16 @@ -# codex-os-managed -# Repo AGENTS baseline generated by global Codex OS bootstrap. - -## Definition of Done (Git + Performance) -- Work on non-default branch only. -- Branch must match `codex//`. -- Commit messages must follow Conventional Commits. -- Commits must be atomic by concern. -- Run reviewer/fixer loop before final completion: - - `reviewer-findings-v1` - - `fixer-apply-findings-v1` - - re-run reviewer until no P0/P1 remain -- PR must include sections: What, Why, How, Testing, Performance impact, Risk / Notes. -- If lockfile changed, include lockfile rationale in PR body. -- Required checks before done-state: - - git hygiene - - bundle delta - - build delta - - performance budgets (profile-dependent) - - assets/memory checks -- Required gates block completion when `fail` or `not-run`. - -## Verification Contract -- Canonical commands are in `.codex/verify.commands`. -- Use `.codex/scripts/run_verify_commands.sh` for deterministic execution. + + +## Communication Contract + +- Inherit global Codex communication and reporting rules from `/Users/d/.codex/AGENTS.override.md` and `/Users/d/.codex/policies/communication/BigPictureReportingV1.md`. +- Repo-specific instructions below add project constraints only; do not restate global voice or status-reporting rules here. + + +## Inherited Operating Rules + +- Inherit global git, review/fix, testing, docs, skill-use, and reporting gates from `/Users/d/.codex/AGENTS.md` and active session instructions. +- Use `.codex/verify.commands` and `.codex/scripts/run_verify_commands.sh` as this repo-local verification authority when present. +- Keep the project-specific portfolio constraints below as the source of truth for runtime, privacy, and release risks. # Portfolio Context