Skip to content

feat(app-control): route lessons to map refresh or /corrections:codify #9584

Description

@kyle-sexton

Slice A7 of #9507. poteto's draft routed lessons through instruction-placement; the owner routed non-feature lessons to /corrections:codify instead (amendment).

Problem

Nothing says where a lesson learned while driving goes.

Fix

  • map refresh and create put a one-feature lesson into that feature's Gotchas; a lesson for every feature goes into the control skill's contract section.
  • /verification:confirm lists lessons in its report and names /app-control:map refresh <feature> and /corrections:codify in its ## Next. It names no instruction-placement or write-for-agents call.
  • Evals: one per scope (feature, every feature, non-feature). Fragments: app-control minor, verification minor.

Done when

  • grep -n '/corrections:codify' plugins/verification/skills/confirm/SKILL.md plugins/app-control/skills/map/SKILL.md matches in both.
  • The three evals pass; confirm's existing evals are non-inferior.

Blocked by: A2.

Activity

  1. github-actions commented on Oct 24, 2026

    @github-actions
    Contributor

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

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

    Understood: slice A7 of #9507. It adds routing for lessons learned while driving an app. A one-feature lesson goes to that feature's Gotchas through map refresh or create. A lesson for every feature goes to the control skill's contract section. Non-feature lessons go to /corrections:codify. /verification:confirm lists lessons and names both next steps. The work also needs three evals and two minor fragments. The done-when checks are clear. The issue says it is blocked by A2, so it can't start until that lands. I found no likely duplicates.

    Automated triage, applied by the lanes App.

  2. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    status: needs-decisionAwaiting a human or maintainer judgment call.
    and removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Oct 24, 2026
  3. melodic-automation-lanes commented on Oct 24, 2026

    @melodic-automation-lanes
    Contributor

    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.

  4. self-assigned this
    on Oct 24, 2026
  5. kyle-sexton commented on Oct 24, 2026

    @kyle-sexton
    MemberAuthor
    No description provided.
  6. kyle-sexton commented on Oct 25, 2026

    @kyle-sexton
    MemberAuthor
    No description provided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: mediumReal value, no hard deadline; normal backlog flow.status: needs-decisionAwaiting a human or maintainer judgment call.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

Fields

No fields configured for Feature.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions