docs(discovery): reword trace-intent's evidence categories #9788

Activity

1. kyle-sexton

   added a parent issue on Oct 24, 2026

   • docs: reword nine pre-existing passages that track upstream pstack and mattpocock text #7052
2. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 24, 2026
3. 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: Small
   Complexity: Low
   Uncertainty: Known
   Flags: none

   Understood: a copy check flagged the four-category list in the trace-intent evidence-categories doc as matching an upstream source. The fix is to confirm it with the fingerprint compare. If it fires, reword the doc in a new structure with this repository's own examples, keeping every directive and eval expectation, and make sure the upstream credit row exists. Nothing is missing. The done-when checks need network access to fetch the upstream file, which a maintainer may need to run. I found no likely duplicates.

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

   added

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

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 24, 2026
5. github-actions

   added the

   Task

   issue type on Oct 24, 2026
6. 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.

   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 24, 2026
7. melodic-automation-lanes commented on Oct 24, 2026

   

   melodic-automation-lanesBot

   on Oct 24, 2026

   Contributor

   More actions

   The work-resolve-issue run that agent-ready started ended over 3 hours ago with no report and no pull request. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. It does this once per version of those files, so if this run fails the same way, a person looks at it.
8. melodic-automation-lanes

   added

   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

   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 24, 2026
9. melodic-automation-lanes commented on Oct 24, 2026

   

   melodic-automation-lanesBot

   on Oct 24, 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:

   The issue's first step is to confirm the finding with fingerprint.mjs compare against cursor/plugins12d587dfb2 pstack/skills/why/SKILL.md. This run cannot fetch that file (gh api to github.com needs approval and is not an allowed host), so the finding is neither confirmed nor refuted. The issue says to rewrite only if the check fires. The local file also lists three categories, not the four the finding describes, so a rewrite on the issue's word alone would be a guess. Nothing was changed.

   What the run says it did not do:

   • fingerprint.mjs compare against the upstream pstack why/SKILL.md: the upstream file could not be fetched (gh api refused, github.com not an allowed host). A person or a run with GitHub access should run the issue's compare command; if separation.fired is false, record that and close, otherwise rewor
   • Check that docs/upstream/cursor-pstack.md has a credit row for pstack/skills/why: not done because no rewrite was made
   • PR body before/after longest_span_words and containment: not produced because the comparison was not run

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

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

    added

    host-runNeeds a host or attended run; the host runner takes it, not a person or the issue lane.Needs a host or attended run; the host runner takes it, not a person or the issue lane.

    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.

    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 27, 2026