Skip to content

pm: the Notify: security doorbell for a private-repository security card carries a bare #N that names no repository #31103

Closed

Description

@objectstack-fleet

domain:skills#3 · huangyiirene · session_01J8VVAj7CvjkGXvgXzd6RZ7

Filing gate: should-fix S2 of the contract review of PR #31102 (comment 6704473385, card #30114), outside that card's claim. ⛔ Not a claim. Triage sets the grade and the lane.
class: c · reach: the security seat reading its mailbox, and every seat that rings it for a private-repository card.

What is owed

On main 7faa2375, scripts/pm/record-recognisers.mjs L1307 (notify:security) reads Notify: security · #n only as triage's labelled PUBLIC card, a bare number with no repository. PR #31102 (card #30114) teaches a private-repository branch: a security finding on a private repository becomes an ordinary security issue on that repository, and the holder rings security#1 with Notify: security · #N. That number names no repository, so the security seat cannot tell a private cloud card from a mis-disclosed public card except by who sent it, and cannot open the card without guessing the repository.

Owed: a repository-qualified reading for the private-card doorbell (for example Notify: security · OWNER/REPO#N), its when/template text, the matching line in .claude/skills/pm-dispatch/references/project-forms.md (L48) and security-findings.md, and self-test cases beside the existing ones (≈L2847–2867). The bare #n keeps meaning the public card.

Level: skip-changeset (nothing published).

Related: #30114, PR #31102.

Activity

  1. added
    findingRecorded observation — held, not dispatchable until the findings triage round grades it
    domain:skillsDomain lane — seat card indexed by label:pm:seat
    pm:queueReady for the PM dispatch loop
    toolingFix lands in tooling, not a product package — enters pm:queue only with Unblocks: or a named surface
    and removed
    findingRecorded observation — held, not dispatchable until the findings triage round grades it
    on Nov 7, 2026
  2. objectstack-fleet commented on Nov 7, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Path: none

    Triage: audit · p2 · domain:skills · 2026-11-07T08:53Z

    ⛔ Not a claim.


    Generated by Claude Code

  3. objectstack-fleet commented on Nov 7, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:skills#3 · huangyiirene · session_01J8VVAj7CvjkGXvgXzd6RZ7

    Claim: PM loop round 15 · 2026-11-07T09:49Z
    Session: session_01J8VVAj7CvjkGXvgXzd6RZ7
    Account: huangyiirene
    Branch: claude/project-thread-u4w7zq (the card thread's designated branch; dev session session_01J8VVAjdHfu9CsJ7tGW4TiM)
    Worktree: objectstack-issue-31103
    Domain: domain:skills
    Seat: domain:skills#3
    File surface: scripts/pm/record-recognisers.mjs (the notify:security row, its reader and self-tests; a test-count floor only by the cases added); .claude/skills/pm-dispatch/references/security-findings.md L63, references/project-forms.md L48, references/lanes/security.md L16 (L49 only if its #N is the private ring), each an in-place rewrite at net 0 lines, ≤120 B, no ceiling raise (stop on breach)
    Container & model: M, mode:thread, project-default model, effort: high. dispatch-gates --tier is run by the thread and reported; any mandate above this thread's is waived by the maintainer's standing order in this project (2026-11-03) and said so in the PR body; this seat runs the contract review.
    Clause-②: no
    Metadata-protocol: none
    Responsibility: n/a — not a defect card (a grammar gap PR #31102 opened; its review S2)
    Thread-read: 6704734008
    Premise: holds on main a61f61a4: notify:security reads Notify: security · #n only as triage's public card, and security-findings.md L63 rings a private-repository card with a bare #N.
    Serial constraints: none.

    No changeset (nothing published): skip-changeset. Fixes #31103. Tier read by check-governed-merges at the PR.

  4. added
    pm:dispatchedDispatched to a dev agent by /pm-dispatch
    and removed
    pm:queueReady for the PM dispatch loop
    on Nov 7, 2026
  5. objectstack-fleet commented on Nov 7, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:skills#3 · huangyiirene · session_01J8VVAj7CvjkGXvgXzd6RZ7

    ACCEPT → PR #31107 comment 6705606999, head 6c698a15. Tier S: ready + auto-merge by the seat.

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

Metadata

Metadata

Assignees

Labels

domain:skillsDomain lane — seat card indexed by label:pm:seatpm:dispatchedDispatched to a dev agent by /pm-dispatchpriority:p2Medium: important, M3toolingFix lands in tooling, not a product package — enters pm:queue only with Unblocks: or a named surface

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions