docs: remove mandatory tracker and checkpoint bureaucracy

Merged
RM
14d ago
+6-6

User description

Summary

Survivor for RM-1712. #213 is the overlapping implementation of the same issue and is left open.

Current main already removed mandatory Beads setup, GitHub issue twins, and checkpoint hard-stops (#221 / RM-1956) and pointed AGENTS.md at that contract (#222). This branch is updated onto that main. It does not restore bd prime session hooks.

The remaining contradiction was traceability guidance that still required a GitHub issue:

  • REVIEW.md identifies the task already in hand (Linear id, existing GitHub issue, or the pull request). No issue twin, child issue, or Beads record is required.
  • SKILL.md discovery includes an existing pull request. A merge-ready claim names cargo fmt --all -- --check, cargo clippy --workspace --all-targets -- -D warnings, and cargo test --workspace. Checkpoints stay on focused checks with honest status.
  • Both handoff workflows accept one existing record. An existing pull request is updated instead of duplicated.

Task

Linear: RM-1712

No GitHub issue twin. Milestone M1 and the existing docs and size:L labels are unchanged. Not merged.

Validation

Docs only. Head c35cb9ed957e519c9f87b3b103b7ef880c7be3cd.

GitHub checks on this head passed: fmt/clippy, test (ubuntu, macOS, Windows), cargo audit, CodeQL, Codacy, CodeScene, codecov/patch, qlty check, qlty fmt, Devin Review, and Kilo Code Review. CodeRabbit completed as success with review skipped. Local cargo test --workspace was not re-run for this docs edit; the workspace tests above are the hosted run.

Review threads on this head are resolved. No changes-requested review.

Linear Issue: RM-1712

Open in Web Open in Cursor 

Summary by cubic

Removes the mandatory tracker and checkpoint bureaucracy from the contribution docs so a pull request can act as the task record and checkpoints are no longer treated as merge readiness.

  • Maintainer work uses a Linear task; contributor work uses a GitHub issue or an existing pull request. No issue twin, child issue, or Beads record is required.
  • REVIEW.md no longer requires the PR to link a GitHub issue, and the discovery and handoff workflows reuse an existing PR instead of creating a duplicate.
  • A merge-ready claim must name the cargo fmt, cargo clippy, and cargo test --workspace gates; drafts and checkpoints publish with their honest test status.

The branch was brought onto current main, which removes the Beads startup hooks entirely, so this PR carries the doc changes only.

CodeAnt-AI Description

Allow pull requests to replace required issue records

What Changed

  • A Linear task, an existing GitHub issue, or the pull request itself can identify the work; no duplicate issue, child issue, or Beads record is required.
  • Handoff workflows update an existing pull request instead of creating a duplicate.
  • Merge-ready guidance now names formatting, lint, and workspace test checks; draft checkpoints are not treated as merge readiness.

Impact

✅ Fewer duplicate GitHub issues
✅ Work can start from an existing pull request
✅ Clearer merge-readiness checks

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.