corrections: OpenTelemetry read-back adapter for the findings buffer #7564

Activity

1. kyle-sexton

   added

   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.

   on Oct 16, 2026
2. kyle-sexton

   added a parent issue on Oct 16, 2026

   • Epic: absorb Lauren Tan's and Matt Pocock's agent workflows (poteto-review) #7555
3. kyle-sexton

   added the

   Feature

   issue type on Oct 16, 2026
4. kyle-sexton

   set

   Work status

   to

   needs-spec

   on Oct 16, 2026
5. github-actions commented on Oct 16, 2026

   

   github-actionsBot

   on Oct 16, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   Proposed work class: none

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

   Understood: this is a parked Feature to add an OpenTelemetry read-back adapter for the findings buffer. It would implement the existing append.sh and read.sh contract. It is deferred (D61) until a team adopts OpenTelemetry as a buffer source. That trigger has not been cited in a comment yet, so there is nothing to build now. When it fires, cite it here and file the slices. I found no likely duplicates among the open issues.

   _{Automated triage. A maintainer reviews it.}
6. kyle-sexton

   added

   needs-specNeeds a Brief or plan before anyone can build it.Needs a Brief or plan before anyone can build it.

   on Oct 16, 2026
7. kyle-sexton

   removed

   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.

   on Oct 24, 2026
8. kyle-sexton commented on Oct 24, 2026

   

   kyle-sexton

   on Oct 24, 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.
9. github-actions

   added

   priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.

   on Oct 24, 2026
10. melodic-automation-lanes

    added

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

    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
11. 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.
12. kyle-sexton

    removed

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

    on Oct 26, 2026
13. 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.
14. 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

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

    

    melodic-automation-lanesBot

    on Oct 26, 2026

    Contributor

    More actions

    The work-resolve-issue lane did not start this issue: it needs a person to make it clearer first.

    Why, in the run's own words:

    This item is parked until a reopen trigger fires: 'A team adopts OpenTelemetry as a buffer source.' Its recorded decision (D61) defers the OpenTelemetry read-back adapter until that happens. Its first Done-when box is 'The trigger has fired and is cited in a comment.' No comment cites a team adopting OpenTelemetry. The two human comments only release the hold label for re-triage. The corrections plugin has no OpenTelemetry buffer source, only the local-file adapter under plugins/corrections/tools/findings-buffer/adapters/. Building the adapter now would go against D61. Filing the slices needs the adopting team's OpenTelemetry setup (backend, query API, auth), and the issue gives none of it; it also carries the needs-spec label. Question for a person: has a team adopted OpenTelemetry as a findings-buffer source? If so, cite it in a comment with the team's OTel backend and how its rows can be read back (the endpoint or API that read.sh --since would query). Otherwise keep this item parked and remove agent-ready.

    What the run says it did not do:

    • Did not implement the adapter or file slices. The reopen trigger has not fired, and D61 defers the work until it does.

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

    To retry, answer the question here, remove needs-human and add agent-ready again.
16. melodic-automation-lanes

    removed

    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