feat(verification): call /app-control:map refresh for touched features #9586

Activity

1. kyle-sexton

   added

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

   on Oct 24, 2026
2. kyle-sexton

   marked this as blocked by 3 issues on Oct 24, 2026

   • refactor(testing): retire map-features and refresh-feature-map for /app-control:map #9585
   • feat(app-control): add /app-control:map refresh #9583
   • feat(app-control): route lessons to map refresh or /corrections:codify #9584
3. kyle-sexton

   added a parent issue on Oct 24, 2026

   • feat(app-control): discover-and-interview setup that generates and maintains a control skill #9507
4. kyle-sexton

   added the

   Feature

   issue type on Oct 24, 2026
5. kyle-sexton

   marked this as blocking on Oct 24, 2026

   • feat(testing): resolve grouped feature ids in run-e2e #9587
6. github-actions commented on Oct 24, 2026

   

   github-actionsBot

   on Oct 24, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

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

   Size: Medium
   Complexity: Medium
   Uncertainty: Known
   Flags: none
   Blocked by: none

   I understood this as slice A6 of #9507. /verification:confirm and /testing:run-e2e would map changed files to features through the index's sources: globs. If app-control is installed, they would call /app-control:map refresh <feature>. If it isn't, they would report the drift and name it in ## Next. Four evals and two changelog fragments are included.

   The body says it is blocked by A4, A5, A7 and B1, but I couldn't match those labels to open issue numbers. Please add the issue numbers so the blocked-by edges can be set. I found no clear duplicates among the open issues.

   _{Automated triage, applied by the lanes App.}
7. 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: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   and removed

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

   on Oct 24, 2026
8. melodic-automation-lanes commented on Oct 24, 2026

   

   melodic-automation-lanesBot

   on Oct 24, 2026

   Contributor

   More actions

   Not admitted to the issue lane: a Feature needs an open parent issue a listed human filed that awaits no decision. A recorded decision does not change these rules (.github/actions/resolve-config/admission-rules.json); a person who wants it worked adds agent-ready.
9. kyle-sexton

   removed

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   on Oct 26, 2026
10. kyle-sexton commented on Oct 26, 2026

    

    kyle-sexton

    on Oct 26, 2026

    MemberAuthor

    More actions

    Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.

    To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.
11. melodic-automation-lanes

    added

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

    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued capReady for the issue lane; work-unblock admits it when queued work is under the queued cap

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

    and removed

    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued capReady for the issue lane; work-unblock admits it when queued work is under the queued cap

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

    on Oct 26, 2026
12. melodic-automation-lanes commented on Oct 26, 2026

    

    melodic-automation-lanesBot

    on Oct 26, 2026

    Contributor

    More actions

    The work-resolve-issue lane stopped partway through this issue and needs a person.

    Why, in the run's own words:

    Blocked by B1, which has not merged. The issue lists 'Blocked by: A4, A7, A5, and poteto's B1', and the owner adopted the merge order on ＃9507 (kyle-sexton, 2026-10-24): A6 (＃9586) and A8 'start after B1 merges and rebase onto the shrunk file', because B1 removes run-e2e's driving and its Feature map section, which is the text this issue's run-e2e edit would change. On main (checkout 857822e, and the raw file on main read during this run), plugins/testing/skills/run-e2e/SKILL.md still has its own '＃＃＃ Feature map' driving section and never mentions /app-control:drive, so B1 has not landed. The other blockers are cleared: A4 (refresh is in plugins/app-control/skills/map/reference/refresh.md, including feature-id refresh), A5 (merged as 2640984 per ＃9507), and A7 (replaced by the owner's lesson-routing amendment). Building against the pre-shrink run-e2e would go against the owner's adopted order and conflict with B1. Requeue this issue after B1 merges. No files were edited.

    What the run says it did not do:

    • The whole issue (the refresh call in confirm and run-e2e, the four evals, the testing and verification fragments) is left undone until B1 merges, per the owner-adopted merge order on ＃9507
    • The review, build/test and lint steps were skipped because no change was made

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40262037307

    To retry, remove needs-human and add agent-ready again.