Skip to content

fix(instruction-placement): three surfaces still say path-scoped rules load only on read #6199

Closed

Description

@kyle-sexton

This was generated by AI during work-loop.

Context

PR for #6101 corrected the instruction-placement plugin's loading-mechanics claims within the operator-ratified scope: path-scoped rules trigger on Read, Write or Edit from Claude Code 2.1.288 (https://code.claude.com/docs/en/memory#path-specific-rules, changelog 2.1.288). A fresh-context verifier found three surfaces outside that scope that still describe the trigger as read-only:

  • plugins/instruction-placement/scripts/render-index.sh header comment (and the index preamble it renders, which consuming repos would need to re-render)
  • plugins/instruction-placement/skills/realign/SKILL.md ("the rule fires on read")
  • plugins/instruction-placement/evals/adherence-results.md and evals/adherence-experiment.sh

Proposed work

Bring those surfaces in line with the corrected verified-mechanics.md wording, keeping the creation deny's verdict (lifting it is #6193's).

Acceptance criteria

  • None of the three surfaces says path-scoped rules load only on read without the 2.1.288 version qualifier.
  • The rendered index preamble matches, and the plugin is bumped with a CHANGELOG entry.

References

Metadata

Filed by the work-loop lane (instance melo-worker-1) per the self-observation contract; not self-triaged.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 4, 2026
  2. github-actions commented on Oct 4, 2026

    @github-actions
    Contributor

    Thanks for the report. This describes a documentation-accuracy follow-up to #6101: three surfaces in the instruction-placement plugin still describe path-scoped rules as triggering only on read, without the Read/Write/Edit-since-2.1.288 qualifier that #6101 established. I checked the current repository state and confirmed the wording is still present in scripts/render-index.sh's header comment, skills/realign/SKILL.md, and evals/adherence-results.md (the adherence-experiment.sh reference appears to be a general "read" usage rather than the stale claim, worth double-checking during the fix). The acceptance criteria and scope (align wording with verified-mechanics.md, re-render the index preamble, bump version and CHANGELOG) are clear. I didn't find any duplicate open issues. No gaps that need clarification from here.

    Automated triage. A maintainer reviews it.

  3. added
    good first issueGood entry point for new contributors.
    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.
    on Oct 4, 2026
  4. kyle-sexton commented on Oct 4, 2026

    @kyle-sexton
    ContributorAuthor

    This was generated by AI during triage.

    Verified on origin/main 79abd80 (after #6201 merged): the plugin's verified-mechanics reference now says a path-scoped rule loads when Read, Write or Edit targets a matching file on 2.1.288 and later, Read only before. The surfaces below still say read only.
    Basis: verified, origin/main 79abd80: plugins/instruction-placement/scripts/render-index.sh:5 (header comment) and :259 (rendered preamble, "enters context automatically when Claude reads a file it covers"); plugins/instruction-placement/skills/realign/SKILL.md:211 ("the rule fires on read"); plugins/instruction-placement/evals/adherence-results.md:56; plugins/instruction-placement/evals/adherence-experiment.sh:71 (a copy of the preamble); this repository's AGENTS.md carries the same rendered preamble.

    Agent Brief

    Type: Bug
    Summary: Bring the instruction-placement plugin's remaining "loads on read" wording in line with its corrected loading-mechanics reference (Read, Write or Edit from Claude Code 2.1.288; Read only before).

    Current behavior:
    The index renderer's header comment, the preamble it renders into a repository's always-loaded index, the realign skill's gotcha about index regeneration, and the adherence experiment's script and results write-up all describe path-scoped rules as entering context only when Claude reads a covered file, with no version qualifier.

    Desired behavior:

    • Each of those surfaces describes the trigger as the plugin's loading-mechanics reference now does: Read, Write or Edit of a matching file on 2.1.288 and later, Read only before.
    • The rendered index preamble is updated, and this repository's own always-loaded index is re-rendered in the same change so the plugin's index-matches-disk check stays green.
    • The adherence experiment files record a measured past run: add the qualifier where they state the mechanism, and do not rewrite any measured result or the version it was measured on.
    • The creation-deny verdict is unchanged; lifting it is feat(instruction-placement): decide the write-trigger deny, path-scoped skill routing, and rule YAML validation (split from #6101) #6193's decision.

    Key interfaces:

    • The index renderer's preamble text (consumer repositories pick it up on their next re-render).
    • The realign skill's gotchas.

    Acceptance criteria:

    • None of the listed surfaces says path-scoped rules load only on read without the 2.1.288 qualifier.
    • This repository's rendered index matches the renderer's output (the instruction-placement check passes).
    • No measured result in the adherence write-up changes.
    • The plugin is version-bumped with a CHANGELOG entry.

    Out of scope:

    Routing: delegable. Work class scoped (bug fix): wording plus one re-render, bounded to one plugin and this repository's index. Priority low (documentation accuracy, no correctness gate depends on it).

  5. added
    agent-readyFully 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.
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    and removed
    good first issueGood entry point for new contributors.
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 4, 2026
  6. kyle-sexton commented on Oct 4, 2026

    @kyle-sexton
    ContributorAuthor

    This was generated by AI during work-loop.

    Ratify autonomous dispatch of this C3 bug-fix item?

    Classification: work-class: scoped (C3), bug-fix-shaped (confirmed at triage). Intended dispatch: the work-loop worker lane, through /work-items:work, to a draft PR the lane never merges. First drain is not complete and no item-level ratification exists, so it is queued here. Ratify through /work-items:attend-queue.

    Lane: work-loop, instance melo-worker-1, cycle 2.

  7. added
    needs-humanHuman-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.
    on Oct 4, 2026
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

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.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.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions