docs: restore comprehensive AGENTS.md with governance and technical s… - #189
Conversation
…ections - Governance & process rules (master-staging, gates, proposals) - Complete technical documentation (tokei stats, 28 tools, CI/CD) - Navigation hierarchy, core projects, development workflow - Methodology evolution, troubleshooting, 15 AI agent guidelines - References to DATA_FLOW_MANIFEST.md, SYSTEM_MAP.md
|
Mention Blocks like a regular teammate with your question or request: @blocks review this pull request Run |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Deployment failed for project termux-monorepo with the following error: Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit |
github-project-automation
Bot
moved this to Todo
in @timerloggedout-spec's untitled project team planning
|
Warning Review limit reached
Next review available in: 5 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@jules Auto-resolve (heyVern lane / GHA agent-review-auto-jules) — do not wait for a human ping. Feedback excerptInstructions
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR More tips ↗ | Customize Qodo ↗ | Qodo docs ↗ |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| ## Debate & close | ||
|
|
||
| - Debate: MANIFEST Review log, optional DEBATE.md, linked PR/issue. | ||
| - Close: all items terminal + Review log outcome + move `active/` → `closed/` + registry update. | ||
| - Full rules: `docs/proposals/PROCESS.md` §§ consensus / closing. | ||
|
|
There was a problem hiding this comment.
🔍 Governance "Debate & close" rules dropped from AGENTS.md
The rewrite removes the "Debate & close" block (debate via MANIFEST Review log / DEBATE.md; closing requires terminal items, Review log outcome, moving active/ → closed/, registry update). The PR describes itself as "restoring comprehensive" governance, but this section is net-deleted while nothing in the new text covers closing procedure. docs/proposals/PROCESS.md:51 still instructs agents to read AGENTS.md first, so agents relying on this file lose the close checklist. Worth confirming the deletion is intentional.
Was this helpful? React with 👍 or 👎 to provide feedback.
| - **Indices:** Stored in `workspace/llm_map/`, `archwiz/`, `cli-synthegration/workspace/` | ||
| - **Configuration:** Project-specific configs in respective directories | ||
| - **Backups:** `.bak` files created automatically, large JSONL indices backed up externally | ||
| - **Ignore Patterns:** Respect `.gitignore` and `.bobignore` (see root `.bobignore` for exclusions) |
There was a problem hiding this comment.
🔍 Referenced ignore file .bobignore does not exist in the repo
The new conventions instruct agents to "Respect .gitignore and .bobignore (see root .bobignore for exclusions)", but there is no .bobignore at the repo root (verified by directory listing). Agent guideline 9 repeats the same reference at AGENTS.md:559. This will send agents looking for a nonexistent file.
Was this helpful? React with 👍 or 👎 to provide feedback.
| ### Commit Practices | ||
| - Use feature branches (`feature/*`) for all changes | ||
| - Never commit directly to `master` without review | ||
| - Reference task IDs in commit messages when applicable | ||
| - Keep commits focused and atomic | ||
| - Follow conventional commit format when possible |
There was a problem hiding this comment.
🔍 Branch conventions in new section contradict the Hard Rules
The new "Commit Practices" and agent note 3 (AGENTS.md:553) say to use feature/* branches and never commit to master, while the Hard Rules above state integration work must target master-staging, and the Preferred Execution Loop says to branch from master-staging. The two sets of instructions are not reconciled, which can lead agents to open PRs against the wrong base branch.
Was this helpful? React with 👍 or 👎 to provide feedback.
| ## Hard Rules | ||
|
|
||
| - Target **`master-staging`**, not raw `master`, for integration work. | ||
| - Both gates must pass before merge: |
There was a problem hiding this comment.
🔍 Gate scripts cited in Hard Rules are absent from the repo
The retained Hard Rules require python3 scripts/ci/repo_gate.py and python3 scripts/ci/termux_smoke.py before merge, but scripts/ci/ currently only contains calculate_lag_index.py. Pre-existing, but since this PR is a documentation restoration it would be a good moment to either add the scripts or correct the paths.
(Refers to lines 21-23)
Was this helpful? React with 👍 or 👎 to provide feedback.
| ### Active PRs (as of 2026-08-01) | ||
| 1. **PR #1 `critical-proposal`** - Critical eval + roadmap (mergeable as docs) | ||
| 2. **PR #2 `timerloggedout-spec-patch-1`** - GHA Rust (narrow scope before merge) | ||
| 3. **PR #3 `agent/repository-hygiene`** (draft) - Untrack session stores (**priority security**) | ||
|
|
There was a problem hiding this comment.
📝 Info: Hard-coded statistics and "active PR" snapshot will go stale quickly
Tokei counts, file-count figures in the workspace tree, and the "Active PRs (as of 2026-08-01)" list are point-in-time snapshots baked into the guidance file. Agents are told to treat this file as authoritative first reading, so stale numbers/PR states may drive incorrect decisions. Consider marking these sections as generated/snapshot with a regeneration command.
Was this helpful? React with 👍 or 👎 to provide feedback.
PR Summary by QodoDocs: restore comprehensive AGENTS.md (governance + technical guide)
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
|
head_sha: d0c128f Peer review gate (ready for second-pass agents)External reviewers polled: CodeRabbit, Devin, Aikido, Sentry, Copilot. Peer activity (truncated): Downstream: |
github-project-automation
Bot
moved this from Todo
to Done
in @timerloggedout-spec's untitled project team planning
1 participant
reference #188
…ections