docs(changeset): correct the residue account — a copy edited name, and a later commit edited the adjacent url

The shipped changeset claimed the stale `repository.directory` survived two
pure renames and that "nothing rewrote the field". Measured, that is false in
three ways, and the true account is a stronger argument for a mechanical check
rather than a weaker one.

  f15d6f6  NOT a rename: a 26-file copy, +2222/-19, with all four
             trigger directories briefly coexisting. Each copied manifest
             differs from its original in exactly one line -- `name` -- so
             this commit edited the manifest and left `directory` stale.
  290c625  deleted the originals five minutes later.
  ea4941a  the only pure rename: 16 files, 0 insertions, 0 deletions.
  9a43e04  six weeks later, rewrote `repository.url` and `bugs` in both
             of these manifests. The stale `directory` line sits as
             unchanged context ONE LINE BELOW the edited `url`.

The last point is the one worth the correction. "Nothing rewrote the field"
reads as the field never having been in anyone's way; in fact an author edited
its immediate neighbour inside the same JSON object and the dead line was on
screen in a reviewed hunk. A rule is more clearly needed when a human looked at
the line and still missed it, so this strengthens the case on the gate card.

No code change: the four-line metadata fix is unchanged and its verification
still stands. This commit corrects prose only, in the file that ships to
release notes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XpTx2tbq3pZRYAdoGt6E6Y

Author: claude

.changeset/trigger-packages-repository-directory-15478.md

@@ -14,6 +14,6 @@ Both manifests declared a path under `packages/plugins/` that no longer exists i
 
 `repository.directory` is what npm uses to build the **Repository** deep link on a package page, and what tooling uses to locate a monorepo package's source from its tarball. Pointing it at a path that does not exist sends a reader to a 404 instead of to the source — on packages published today at `17.3.0`. The value ships inside the tarball, so this correction only reaches npm by being published; that is why it carries a changeset rather than `skip-changeset`.
 
-The residue is from two renames landed the same day, not one: `plugin-trigger-*` → `trigger-*` inside `packages/plugins/` first made the declared value wrong, and the later promotion of `packages/plugins/trigger-*` to a first-class `packages/triggers/` directory made it wrong in a second segment. Both were pure directory renames that changed no file contents, so nothing rewrote the field.
+The residue came from a three-commit sequence on 2026-06-12, and only one of those commits was a pure rename. `f15d6f6f6` **copied** the two packages to `packages/plugins/trigger-*` (26 files, +2222/-19, with all four directories briefly coexisting) and edited exactly one line of each copied manifest — its `name` — leaving `directory` pointing at the path it was copied from; `290c62514` deleted the originals five minutes later; and `ea4941ad8` then promoted `packages/plugins/trigger-*` to a first-class `packages/triggers/` directory as a pure 16-file rename with zero content changes, which made the declared value wrong in a second segment. Six weeks after that, `9a43e042f` (#3380) rewrote `repository.url` and `bugs` in both of these manifests, with the stale `directory` line sitting as unchanged context one line below the edited `url`. So the field was not merely never in anyone's way: one commit edited its immediate neighbour inside the same object, and a later reviewed hunk had the wrong line on screen. Nothing caught it because nothing reads it.
 
 Scope of this change, stated as a measured set rather than a general claim: over all **81** tracked `package.json` files in the repository, **57** declare `repository.directory`; before this change **55** resolved to the manifest's own directory and **2** did not — the two above. After it, **57 of 57** resolve. No other manifest field is edited, and no package's code, exports or behaviour is touched. The remaining **24** manifests declare no `repository.directory` at all; that population is deliberately left alone here and is reported separately, because whether declaring the field is mandatory is a policy question rather than a correction.