docs: correct REVIEW.md inaccuracies flagged by automated review

[anandgupta42]

Summary

Follow-up to #983 — corrects a wording inaccuracy in REVIEW.md flagged by automated review (CodeRabbit).

• REVIEW.md stated the Marker Guard / altimate_change marker check is "CI-enforced at compile time." It isn't — it's a dedicated marker-guard job in ci.yml (bun run script/upstream/analyze.ts --markers), separate from the typecheck step. The old wording overstated the guarantee and could mislead reviewers about when marker failures actually surface. Fixed to describe it as a CI job, not a compile-time check.

Test plan

• Verified via .github/workflows/ci.yml (marker-guard job, line 448) that the marker check runs as its own CI step, not during typecheck/compile.
• wc -m REVIEW.md → 9603 (under the 10,000 char budget).

🤖 Generated with Claude Code

---

Summary by cubic

Corrected REVIEW.md to fix an inaccuracy about Marker Guard enforcement. Clarifies the check is handled by a dedicated CI job (marker-guard in ci.yml), not at compile time.

^{Written for commit 5199576. Summary will update on new commits.}

Summary by CodeRabbit

• Documentation
  • Clarified the “Marker Guard” guidance to reflect that marker checks are enforced by a dedicated CI job.
  • Kept the existing rule to avoid guessing missing markers and to continue flagging incorrect usage.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 8361ec3f-e74d-4ec4-9e3c-cd3b7e4422f1

📥 Commits

Reviewing files that changed from the base of the PR and between 6b1dd22 and 5199576.

📒 Files selected for processing (1)

• REVIEW.md

---

📝 Walkthrough

Walkthrough

Updated a single line in REVIEW.md's Marker Guard section, changing the enforcement mechanism description from "compile time" to a dedicated CI job named "marker-guard", while preserving existing guidance on marker handling.

Changes

Documentation update

Layer / File(s)	Summary
Marker Guard wording change REVIEW.md	Rewords enforcement description for altimate_change marker presence/format from compile-time to the marker-guard CI job.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• AltimateAI/altimate-code#983: Prior PR established the initial REVIEW.md guidance on altimate_change marker presence and misuse that this PR further revises.

Poem

A tiny tweak, a single line,
"Compile time" gives way to CI's shine.
The marker-guard now stands on watch,
No missing tags will pass the notch.
Hop along, docs are aligned! 🐇✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers Summary and Test Plan, but it omits the required PINEAPPLE header and the Checklist section from the template.	Add PINEAPPLE at the very top, then include a Checklist section with the requested items; keep the existing Summary and Test Plan details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the change: a docs-only fix to REVIEW.md correcting the Marker Guard wording.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/review-md-fixes

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)

• REVIEW.md

---

_{Reviewed by glm-5.2 · Input: 24.7K · Output: 2.4K · Cached: 134.1K}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}