test(prerequisites): merge probe on a fleet host for the five plugins' reworded degrade commands #13072

Activity

1. kyle-sexton

   added

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   host-runNeeds an agent run or builder session on a host; not a person or the issue lane.Needs an agent run or builder session on a host; not a person or the issue lane.

   on Nov 4, 2026
2. github-actions commented on Nov 4, 2026

   

   github-actionsBot

   on Nov 4, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   Proposed work class: work-class: read-only
   Basis: automated intake triage; the lanes App applied this class.

   Size: Small
   Complexity: Low
   Uncertainty: Known
   Flags: none
   Blocked by: #12570

   Understood: this is a follow-up to #12570. Once that change merges, a merge probe on a fleet host should confirm that the reworded degrade commands in discovery, rate-limit-guard, multi-agent, review and context-guard run as written when a hook dependency is missing. The probe needs a host, so it is routed to the host-run path and an unattended lane can't do it. The issue already has the host-run label. No duplicates found.

   _{Automated triage, applied by the lanes App.}
3. github-actions

   added the

   Task

   issue type on Nov 4, 2026
4. melodic-automation-lanes

   added

   status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   work-class: read-onlyAudits, research, reports. No repository mutation; tracker and queue writes only.Audits, research, reports. No repository mutation; tracker and queue writes only.

   on Nov 4, 2026
5. melodic-automation-lanes

   marked this as blocked on Nov 4, 2026

   • refactor(prerequisites): five plugins' notices have no emitter, and degrade text prints a literal <plugin root> #12570
6. melodic-automation-lanes

   set

   Work status

   to

   ready

   on Nov 4, 2026
7. melodic-automation-lanes

   added

   status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.A maintainer confirmed the item is real and in scope; ready to be worked.

   and removed

   status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   on Nov 4, 2026
8. melodic-automation-lanes commented on Nov 4, 2026

   

   melodic-automation-lanesBot

   on Nov 4, 2026

   Contributor

   More actions

   Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 1 (a run on a host the lane is not: "A person whose hook dependency is missing in one of these plugins can reach a..."); no done-when item is left for the lane, so it goes to the host queue (host-run); it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
9. melodic-automation-lanes commented on Nov 4, 2026

   

   melodic-automation-lanesBot

   on Nov 4, 2026

   Contributor

   More actions

   The latest triage verdict holds nothing: admission moved the issue to status: confirmed; its comment says why.
10. melodic-automation-lanes

    changed

    Work status

    to

    confirmed

    on Nov 4, 2026
11. kyle-sexton commented on Nov 4, 2026

    

    kyle-sexton

    on Nov 4, 2026

    MemberAuthor

    More actions

    Delivered: closing as completed.
    Agent choice, not an owner answer.

    Merge probe on a fleet host (WSL), on origin/main at 55f8a62, after #13108 merged. Each plugin tree was exported from that commit; one hook dependency was hidden (PATH=/usr/bin:/bin, which holds no node, with the checker's node invoked by absolute path; or a stub claude reporting 2.1.100 put first on PATH); <node> lib/prerequisites.mjs check <root> ran from and against that root; then the command its line names ran exactly as written, from that root, first with the dependency still missing and then with it resolved (node v24.21.0, claude 2.1.318). No check line printed a literal <plugin root>.

    • discovery: FAIL node line names bash scripts/check-hook-registration.sh; it ran as written: exit 1 with node missing (node FAIL, hook not run), exit 0 with node resolved (node, registration, hook PASS). 55f8a62
    • multi-agent: FAIL node line names bash scripts/check-hook-registration.sh; it ran as written: exit 1 with node missing, exit 0 with node resolved (node, registration, gate PASS). 55f8a62
    • review: WARN node line (node is optional here, so the checker exits 0) names bash scripts/check-hook-registration.sh; it ran as written: exit 1 with node missing, exit 0 with node resolved (node, registration, hook PASS). 55f8a62
    • context-guard: FAIL claude line (2.1.100 below the 2.1.287 floor) names bash scripts/check-mod-load.sh; it ran as written: exit 1 at 2.1.100 (mods-floor FAIL), exit 0 at 2.1.318 (mods-floor PASS). 55f8a62
    • rate-limit-guard: FAIL claude line names bash scripts/check-mod-load.sh; it ran as written: exit 1 at 2.1.100 (mods-floor FAIL), exit 0 at 2.1.318 (mods-floor PASS). 55f8a62

    The node lines print only when node is installed but absent from the PATH the checker sees (the case the notice names: hooks read Claude Code's PATH, not your shell profile); with node absent outright the checker cannot start, which is the emitter gap #12570 accepted as is. The named command also runs with node missing and reports the gap. The five READMEs still spell these commands with a <plugin root> placeholder for the reader to fill in; that is documentation, not a notice or check line.
12. kyle-sexton commented on Nov 4, 2026

    

    kyle-sexton

    on Nov 4, 2026

    MemberAuthor

    More actions

    Closing as completed on the delivery record above: the probe passed for all five plugins at main 55f8a62.
13. kyle-sexton

    closed this as completedon Nov 4, 2026