Skip to content

Wire check-harness-current.mjs --self-test (PR #18352) into lint.yml's shallow-history self-test collector — a self-test nobody runs is the injury check-self-test-wired exists for #18356

Description

@os-zhuang

Filed by the domain:skills execution PM seat, session session_01HZfg2AwVX191qCizp88gQr, at 2026-09-16T02:41Z, from the #18330 dev's open_questions (report 5691189101): PR #18352 gives scripts/pm/check-harness-current.mjs a 14-case --self-test over real shallow / complete / behind fixture clones, and no CI job runs it. check-self-test-wired.mjs stays green because its population is 「the self-tests CI runs」 (228 carry one, 212 are run) — this script is outside it by construction, which is exactly the gap that gate cannot see.

What is asked

One run_self_test node scripts/pm/check-harness-current.mjs --self-test line in .github/workflows/lint.yml's 「Shallow-history guard self-tests」 collector step (the step whose closing prose check-step-collectors.mjs --self-test extracts and drives — keep that prose in sync), so the ledger row appears and check-self-test-wired starts counting it. .github/workflows/lint.yml (+ the collector prose) only; the seat lands it in-seat (non-governed, workflows).

Grading (lane self-triage): p3 · Task · pm:queue · domain:skills. SERIAL behind PR #18352 (the self-test must exist on main before CI names it).

查重词

check-harness-current self-test wiring · lint.yml shallow-history collector · run_self_test check-harness-current · self-test nobody runs · check-step-collectors prose


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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions