Skip to content

Drop the lesson-router comments that failed the comment gate. - #1330

Merged
EdbertChan merged 1 commit into
stack/EdbertChan/reflect/lesson-route-already-covered/route-restated-existing-rules-already-covered--bb2d3e90from
stack/EdbertChan/reflect/lesson-route-already-covered/drop-lesson-router-comments-failed-comment-gate--0a048d4d
Oct 11, 2026
Merged

EdbertChan merged 1 commit into
stack/EdbertChan/reflect/lesson-route-already-covered/route-restated-existing-rules-already-covered--bb2d3e90from
stack/EdbertChan/reflect/lesson-route-already-covered/drop-lesson-router-comments-failed-comment-gate--0a048d4d

Conversation

@EdbertChan

@EdbertChan EdbertChan commented Oct 11, 2026 •

Copy link
Copy Markdown
Owner

Summary

The lesson router failed its check because the new file explained itself in comments. Those comments are gone. The mark that tells the text checker a line is a real parser stays, and the comment checker now treats that mark as a machine instruction.

Review Claim

A lesson router can keep the mark that allows a text parser, and the comment checker accepts that mark.

Review Lane

behavior

Review Unit

engine-runtime

Safety Invariant

Prose comments stay banned. Only the existing allow mark for a text parser is recognized, beside the marks the checker already allows. This does not merge.

Non-goals

  • Does not change how a restated rule is bucketed.
  • Does not allow prose comments.
  • Does not merge.

Slice Rationale

The router and the comment checker change together. Leaving the mark while the checker rejects it keeps the check red. Deleting the mark makes the text checker warn on the parser lines.

Measured

Command: python3 scripts/ci/check_no_new_comments.py --base origin/main

  • base: fail 20 new comment line(s); comments are banned in code
  • head: ok no new comments

Test Plan

Test Plan
  • python3 scripts/ci/check_hook_test_coverage.py engine/hooks/no-comments — check_hook_test_coverage: OK (1 hook(s) checked)
  • python3 scripts/ci/check_skill_test_coverage.py --base HEAD~1 --head HEAD — ok skill test coverage
  • ruff check --select E9,F on the four changed files — All checks passed!
  • python3 scripts/ci/check_skills_three_harnesses.py — ok skills four-harness check
  • python3 scripts/ci/check_ecosystem_boundaries.py — ok ecosystem boundaries
  • python3 scripts/ci/check_skill_file_refs.py — ok skill file refs
  • python3 scripts/ci/check_skill_trigger_mechanism.py — ok skill trigger mechanism
  • python3 scripts/ci/check_skill_trigger_policy.py — ok skill trigger policy
  • python3 scripts/ci/check_subagent_scope_contract.py — ok subagent scope contract
  • python3 scripts/ci/check_no_new_comments.py --base origin/main — ok no new comments
  • python3 -m unittest engine.hooks.no-comments.tests.test_hooks.TestAllows.test_allows_directives_and_shebang engine.skills.reflect.scripts.tests.test_lesson_route -q — Ran 11 tests / OK

Revert Plan

Revert Plan

Revert this commit. The comment checker again rejects the parser allow mark, and the router file is back to the prose comments that failed the check.

The boundary-parser allow mark stays, and the comment checker treats that mark as a machine directive so the two gates agree.

Co-authored-by: Cursor <cursoragent@cursor.com>
Change-Id: I0a048d4d387df53de81d2638521a5198de499b36
@EdbertChan

Copy link
Copy Markdown
Owner Author

This pull request is part of a Mergify stack:

# Pull Request Link
1 Route restated existing rules to already-covered, not automate-me #1324
2 Drop the lesson-router comments that failed the comment gate. #1330 👈

@cursor

cursor Bot commented Oct 11, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 74537e1e-af6f-4a23-97d5-d79b30cbe415)

@EdbertChan
EdbertChan merged commit cfbdf1a into stack/EdbertChan/reflect/lesson-route-already-covered/route-restated-existing-rules-already-covered--bb2d3e90 Oct 11, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant