Skip to content

feat(session-flow): retro reads delivery metrics from measure-delivery #11884

Description

@kyle-sexton

Problem

Q521 names retro as a caller of the metrics skill.

Origin: Q521.

Fix

/session-flow:retro trends mode calls /work-items:measure-delivery when work-items is installed,
and says so when it is not.

Done when

  • The retro skill names the call and the absent-plugin path; check-skill over plugins/session-flow/skills/retro and a session-flow changelog fragment pass.

Parent: #7578

Activity

  1. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Nov 1, 2026
  2. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 1, 2026
  3. github-actions commented on Nov 1, 2026

    @github-actions
    Contributor
    No description provided.
  4. melodic-automation-lanes commented on Nov 1, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41318699661, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-01T15:23:51Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.

  5. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 1, 2026
  6. github-actions commented on Nov 1, 2026

    @github-actions
    Contributor
    No description provided.
  7. github-actions commented on Nov 1, 2026

    @github-actions
    Contributor
    No description provided.
  8. melodic-automation-lanes commented on Nov 1, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue lane stopped on this issue (check-failed): a check the runner ran on the branch failed or could not be read, so the next run continues the branch.
    It keeps agent-ready, and work-unblock starts it again (retry 1 of 2).

    In the run's words:

    The run reported done, but a check the runner ran on the branch failed or could not be read, so it is not finished.

    What the run says it did not do:

    • scripts/check-changelog-fragments.sh --check failed (exit 1)
    • new-changelog-fragment wrapper refused (HEAD is not on a branch), so I wrote the fragment by hand in the same shape as its siblings; check-changelog-fragments validates it
    • tidy pass 5 (ai-slop:audit fix): the deterministic detector detect.sh cannot run under this lane's Bash allowlist, so only the rubric read ran over the changed markdown lines (no findings); passes 1-3 had nothing to do in evals.json (JSON data, no comments)
    • the eval cases were not executed against a model here; evals-quality passed on their shape
    • check-affected's CI-only checks (evals-schema, lychee-offline, purged-em-dashes and the rest) are left to the PR's CI
    • the untracked dotfiles at the checkout root (.bashrc, .bash_profile, .gitconfig, .idea, .mcp.json, .profile, .ripgreprc, .vscode, .zprofile, .zshrc) were not created by this run and are not part of the change

    Partial work is on the branch work-resolve-issue/issue-11884-41322370630-1. The next run continues from it while it is not behind the default branch, and otherwise starts fresh.

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

  9. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 1, 2026
  10. added
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Nov 1, 2026
  11. github-actions commented on Nov 1, 2026

    @github-actions
    Contributor
    No description provided.
  12. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    on Nov 1, 2026
  13. github-actions commented on Nov 1, 2026

    @github-actions
    Contributor
    No description provided.
  14. melodic-automation-lanes commented on Nov 1, 2026

    @melodic-automation-lanes
    Contributor

    This run started fresh from the default branch instead of resuming work-resolve-issue/issue-11884-41322370630-1, which is behind it. That branch keeps the earlier run's commits until the next run on this issue deletes it, when no pull request uses it.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.

    Fields

    No fields configured for Feature.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions