Skip to content

Commit 5199576

Browse files
anandgupta42claude
andcommitted
docs: correct REVIEW.md inaccuracies flagged by automated review
- 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 <[email protected]>
1 parent 6b1dd22 commit 5199576

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎REVIEW.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ CI here enforces type-safety and marker presence, not runtime correctness of asy
99
## Don't duplicate CI — never flag
1010

1111
- **`bun turbo typecheck` / `tsc`** — pure type errors, unused type imports. If it compiles, don't relitigate types.
12-
- **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.
12+
- **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.
1313
- **`anti-slop.yml`** — advisory only (made non-blocking after #741 auto-closed legitimate PRs); don't treat its output as a merge gate.
1414
- **PR title/standards (`pr-standards.yml`)** — conventional-commit-style title checks are automated; don't nitpick title format.
1515
- Pre-existing issues in code the diff doesn't touch.

0 commit comments

Comments
 (0)