Skip to content

gate-proposal: retro #2001 repair 1: skill-audit-disclosure CI check failed shortly after PR #1984 was opened for a references/**-only file #2002

Description

@tvna
Criterion Interpretation Planned ops Proof method Residual risk
skill-audit-disclosure CI check failed shortly after PR #1984 was opened for a references/**-only file Task 1's diff touched skills/evaluating-skill-quality/references/skill-metadata.schema.json, which independently triggers skill-audit-disclosure's applicability per issue #1796's own references-only-trigger rule, but the PR body's initial Skill audit evidence section did not yet disclose it; CI caught the gap after the PR was already open. A batched review-persona read of hooks/check-pr-skill-audit-disclosure.sh confirmed the create-time hook is capable of reproducing this exact CI verdict when it fires with an explicit base, but executing-a-branch-plan opens the PR before later waves' task commits land, and those land via a plain main-thread git push, never a second create/update_pull_request call -- so nothing re-fires the hook against the PR's growing diff until CI reacts. This is the same underlying gap open umbrella issue #1800 (skill-audit-disclosure post-push re-check gap) already tracks, and closed-duplicate #1626 already named for this PR's own creation-time variant of it. See #1800's own Planned ops (a post-push/re-open re-check of the PR body's Skill audit evidence section against the diff's current touched-file set, run locally before CI has to catch it). implementing PR adds the check plus a regression test; confirm it fails against a reintroduced instance of the original defect, then passes None beyond what #1800 already discloses.

Refs #2001

Dedup-sweep: 125 open gate-proposal issues at 2026-09-14T03:57:29Z; verdict DUPLICATE-OF #1800

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions