MultiEdit sweep: repo-wide leftovers outside guardrails and context-budget #5810

Activity

1. 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 2, 2026
2. kyle-sexton

   added a commit that references this issue on Oct 2, 2026

   fix: act on the Jev digest defects and route handoff versus compactio…

   ...

   81ec20d
3. kyle-sexton commented on Oct 4, 2026

   

   kyle-sexton

   on Oct 4, 2026

   ContributorAuthor

   More actions

   This was generated by AI during triage.

   Triage

   Routing: delegable, priority low (documentation and comment hygiene, no behavior change), work class scoped (each hit needs a classify-and-act judgment). The precondition has landed: #5806 closed via #5822 (merged 2026-10-02).

   Current hits on main (git grep -n MultiEdit excluding CHANGELOGs, at e3bef1210), beyond what the issue lists:

   • plugins/session-flow/skills/audit-sessions/scripts/collect.py:64, an edit-tool set naming MultiEdit with no pointer or check date.
   • plugins/guardrails/README.md:1050 and :1174, release-narrative mentions of the old Write|Edit|MultiEdit|NotebookEdit matcher.
   • Line numbers have shifted for the listed ones (for example the parser comment is now at parse_transcript.py:102-108, the criteria row at criteria.md:334).
   • No live hook matcher names MultiEdit (that acceptance item is already met; keep it as a regression check).
     Basis: verified, git grep -n MultiEdit origin/main -- . ':!**/CHANGELOG.md'.

   Agent Brief

   Type: Task
   Summary: Classify and tidy every remaining non-CHANGELOG mention of the legacy MultiEdit tool.

   Current behavior:
   After #5822 removed the live hook matchers, MultiEdit is still named in plugin READMEs, a performance reference, a permission-lint rule with its criteria row and test, transcript parsers and collectors with their tests, and a telemetry schema. Some carry an upstream pointer, check date and recheck trigger; some do not.

   Desired behavior:
   Every mention falls in exactly one class: dated record with a recheck trigger, upstream pointer, kept for legacy input (old transcripts, old telemetry rows), or removed. Every kept mention carries a permissions-docs or tools-reference pointer and a check date. Transcript parsers and collectors keep accepting MultiEdit because older transcripts contain it. CHANGELOG entries are release history and stay.

   Key interfaces:

   • The permission-plane lint's uncovered-path rule, its criteria row and its test: fetch the current permissions page first; retire all three only if that page no longer names legacy MultiEdit, otherwise keep them with a refreshed check date.
   • The edit-tool sets in the retro transcript parser, the audit-sessions collector and the discovery re-read counter.
   • The hook-telemetry schema for the drive-root temp guard (historical rows still carry the value).

   Acceptance criteria:

   • Re-run the grep on current main; the closing PR lists every non-CHANGELOG hit with its class.
   • No hook matcher anywhere names MultiEdit.
   • Every kept mention has a pointer and a check date; the audit-sessions collector's set gains one.
   • The repository's affected-tests run and the changelog parity bump check pass; each touched plugin is bumped with a CHANGELOG entry.

   Out of scope:

   • CHANGELOG entries.
   • Removing MultiEdit support from any transcript parser or collector.
   • Hook matcher changes beyond confirming none names MultiEdit.
4. kyle-sexton

   added

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

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

   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: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   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 4, 2026
5. kyle-sexton commented on Oct 4, 2026

   

   kyle-sexton

   on Oct 4, 2026

   ContributorAuthor

   More actions

   This was generated by AI during work-loop.

   Approve this for autonomous dispatch, or keep it for a human?

   Triage marked this delegable as a feature-shaped C3 (work-class: scoped). The work-loop admission gate human-gates feature-shaped C3 work, so the lane removed agent-ready and applied needs-human. To dispatch it, flip it back through /work-items:attend-queue.

   Lane: work-loop, instance melo-worker-1, cycle 1.
6. 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.

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