v2.11.0

Fixed

• The kernel's method list opened with a permission and closed with an obligation, and the permission stood first. "Read only the guidance that materially helps the current request" asks a run to weigh what a method would add before opening it, which is a judgment nothing can make about a file it has not read. Version 2.5.0 had already added the obligation two paragraphs below it, on receipts showing methods going unread, and left the permission in place. The obligation is now the opening sentence and the permission is gone from both places it stood, the section itself and the skill description a host reads when it selects the skill: read the method that governs an act before that act, whether its trigger matches is the only question, and one whose trigger does not match stays unopened. No rule was added: one obligation replaced the permission and the restatement of that obligation below the list, and the section is sixteen words longer than it was.
• The rule sending a plan that spans several units to the project's tracker was conditioned on "an authorized change", which left out the other way a plan becomes a record: the owner asks for the plan itself, hands it to a later run, and authorizes no change at all. The destination now follows the plan — where the request authorizes recording it, as the record the owner asked for or as the state an authorized change needs to finish safely, it goes where the project keeps tracked work. decomposition carried the same rule for a split and the same looseness, conditioned on any authorized durable record, and it is corrected with it. The grant is unchanged: a request that authorizes no record still writes nothing, and a request whose record is something else is not permission to write a plan beside it.

Evidence

• The scan that prompted this release covers every session on the maintainer's own projects that loaded an installed package, and searches each installed reference file's own opening sentence rather than its path. It splits by major version: under 1.x, twelve of nineteen sessions carried at least one method's text into context; under 2.x, none of eighteen did, and only one of those touched the package directory at all, to measure the size of the plugin cache. The two most consequential 2.x runs in the period — a triage that opened twenty-two tracker items, and a three-and-a-half-hour run with twenty-eight delegates — opened none of tracked-work, continuity, decomposition, or delegation.
• The paired isolated runs do not reproduce that failure, and the release does not claim the change repairs it. On a throwaway fixture with the host's own built-ins and nothing else, 2.10.1 opened the matching method in three of three sessions, before acting in each, and opened nothing for the request that matches no trigger. The release candidate did the same: diagnosing-bugs on the defect, tracked-work and project-setup on the request to record findings, prioritization on the request to order competing work, and nothing on the plain question. So the non-loading is real in long installed sessions and absent in a clean one, which points at what those sessions carry rather than at the sentence changed here. The cause stays UNVERIFIED.
• What the change rests on is the contradiction itself, which is readable in the shipped text and needs no receipt. Whether removing it changes what a long session does is unmeasured, and the release candidate opened somewhat more methods per session than 2.10.1 on the same prompts, which one run per cell cannot separate from noise.
• The plan-destination correction has one observation behind it. An installed 2.10.0 session asked to record a batch of findings and extend the plan for the next agent opened twenty-two items in the project's tracker and wrote the plan and the launch brief into two ignored local files, beside two more the same project had already accumulated, none of them visible to the tracker holding the items. The owner's launch prompt for the next run then had to name that file by hand.
• Package checks: scripts/check.py passed, git diff --check clean, Claude package validation and isolated install passed. Codex package validation and isolated install are UNVERIFIED: this machine has no Codex plugin validator installed.