From 51995765ad21651fcb5fea0b76afb36113e16452 Mon Sep 17 00:00:00 2001 From: anandgupta42 Date: Sun, 5 Jul 2026 08:40:45 -0700 Subject: [PATCH] docs: correct REVIEW.md inaccuracies flagged by automated review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Marker Guard is enforced by a dedicated CI job (`marker-guard` in `ci.yml`), not "at compile time" — fixed wording that overstated when marker failures actually surface. Co-Authored-By: Claude Opus 4.8 --- REVIEW.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/REVIEW.md b/REVIEW.md index 7498c650d..e87f13cdb 100644 --- a/REVIEW.md +++ b/REVIEW.md @@ -9,7 +9,7 @@ CI here enforces type-safety and marker presence, not runtime correctness of asy ## Don't duplicate CI — never flag - **`bun turbo typecheck` / `tsc`** — pure type errors, unused type imports. If it compiles, don't relitigate types. -- **Marker Guard** — presence/format of `altimate_change` marker comments is CI-enforced at compile time (see #872, #904). Don't flag a *missing* marker as a guess; CI will fail the PR. Do still flag *misuse* (see Focus Areas below) since Marker Guard checks presence, not correctness. +- **Marker Guard** — presence/format of `altimate_change` marker comments is enforced by a dedicated CI job (`marker-guard` in `ci.yml`, see #872, #904), not at compile time. Don't flag a *missing* marker as a guess; CI will fail the PR. Do still flag *misuse* (see Focus Areas below) since Marker Guard checks presence, not correctness. - **`anti-slop.yml`** — advisory only (made non-blocking after #741 auto-closed legitimate PRs); don't treat its output as a merge gate. - **PR title/standards (`pr-standards.yml`)** — conventional-commit-style title checks are automated; don't nitpick title format. - Pre-existing issues in code the diff doesn't touch.