Skip to content

[finding] dispatch-gates' population markers accept // and # only, so a declaration written inside a BLOCK comment parses as NOTHING — two live gates' examined-and-explained status is dropped with no tell #18661

Description

@os-justin

Filed by the domain:skills execution seat (session_01Gqi43smmqjJ5sUrhfoPeKu, seat post #7623) out of the #18422 round (PR #18660), from the dev's out-of-scope findings, re-measured by the seat before filing. ⛔ Filed bare: finding only, domain:* / type / priority are triage's (lane self-triage exception noted — the seat did not grade its own filing).

Dedupe words: block comment marker · no-path-population unparsed · symbol-anchors declaration · release-verify-npm population · comment form alternation.

The reading, on origin/main 14d254411

scripts/pm/dispatch-gates.mjs's three population markers (no-path-population, whole-tree-population, wide-population) match a line whose comment form is // or # — and only those two. PR #18660 keeps that grammar in one spelling (populationMarkerPattern) and adds the wholeness refusal; it does NOT widen the form set, and this card is the leg it names as out of scope.

Two live gates declare a population inside a block comment, and both parse as nothing:

file line how it is written declaredNoPathPopulation
scripts/symbol-anchors.mjs :180 /* dispatch-gates: no-path-population -- this module is the shared resolution … null
scripts/release-verify-npm.mjs :110 * dispatch-gates: no-path-population -- the self-test drives synthetic package maps … (inside a /** … */ docblock) null

Seat's own control: the same regex over the same two sources — marker text present in both, the //-or-# form matches in neither. So both families sit in the derivation's undetermined listing with hints=0, i.e. in the exact bucket the marker exists to split them out of, and their authors' examined-and-explained status is dropped with no tell: nothing is refused, nothing is printed, the row reads like a gate whose population was never examined.

Class

A metadata-authoring trap: the author wrote the declaration in the file's own comment idiom (a JSDoc block), passed every refusal, and shipped a row that says less than they wrote. Same class as #18422 (a declaration the consumer silently drops), one comment form further out.

Shape (⛔ a proposal, not a prescription)

Either refuse the block-comment spelling at author time (the marker text is present but no recognised form carries it ⇒ RED, naming the file and the line — the shape #18422 chose for the wrapped reason), or admit * / /* as a third comment form in populationMarkerPattern with the same continuation/termination rules. ⚠️ A block form has its own wholeness question (the docblock's next * line is a continuation by construction), so admitting it is not free. Not graded here.

⛔ Not measured

Refs: #18422 · PR #18660 · scripts/pm/dispatch-gates.mjs populationMarkerPattern (after PR #18660)

domain:skills execution seat · seat post #7623 · readings taken on origin/main 14d254411


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions