fix(triggers): point repository.directory at the directory the trigger packages actually live in

`@objectstack/trigger-record-change` and `@objectstack/trigger-schedule` both
declared a `repository.directory` under `packages/plugins/` that does not exist
in this repository, so the "Repository" deep link on their npm pages resolves to
a 404 instead of to their source. Both are published at 17.3.0.

    @objectstack/trigger-record-change
      was packages/plugins/plugin-trigger-record-change
      now packages/triggers/trigger-record-change
    @objectstack/trigger-schedule
      was packages/plugins/plugin-trigger-schedule
      now packages/triggers/trigger-schedule

Residue of two same-day renames, not one: `plugin-trigger-*` -> `trigger-*`
inside `packages/plugins/` broke the first segment, and the later promotion of
`packages/plugins/trigger-*` to a first-class `packages/triggers/` directory
broke the second. Both were pure directory renames with zero content changes, so
nothing rewrote the field.

Scope as a measured set, not a general claim: across all 81 tracked package.json
files, 57 declare `repository.directory`; 55 resolved to the manifest's own
directory before this change and 57 of 57 resolve after it. The 24 manifests
that declare no `repository.directory` at all are untouched here.

ADR-0041's `## References` section carried the same dead path as a source
pointer and is corrected with it. The rename table earlier in that record
(`plugin-trigger-record-change` -> `@objectstack/trigger-record-change`) is the
decision's own history and is deliberately left as written.

The corrected value ships inside the npm tarball, so it reaches readers only by
being published: a patch changeset accompanies the fix rather than
`skip-changeset`.

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

@@ -0,0 +1,19 @@
+---
+"@objectstack/trigger-record-change": patch
+"@objectstack/trigger-schedule": patch
+---
+
+`@objectstack/trigger-record-change` and `@objectstack/trigger-schedule` now declare a `repository.directory` that resolves to the directory they actually live in.
+
+Both manifests declared a path under `packages/plugins/` that no longer exists in the repository:
+
+| package | declared | actual |
+|---|---|---|
+| `@objectstack/trigger-record-change` | `packages/plugins/plugin-trigger-record-change` | `packages/triggers/trigger-record-change` |
+| `@objectstack/trigger-schedule` | `packages/plugins/plugin-trigger-schedule` | `packages/triggers/trigger-schedule` |
+
+`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.
+
+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.

docs/adr/0041-flow-trigger-family.md

@@ -191,8 +191,8 @@ other contract-ahead-of-runtime surfaces.
 
 - Engine seam: `packages/services/service-automation/src/engine.ts`
   (`FlowTrigger`, `registerTrigger`, `activateFlowTrigger`)
-- Shipped triggers: `packages/plugins/plugin-trigger-record-change`,
-  `packages/plugins/plugin-trigger-schedule`
+- Shipped triggers: `packages/triggers/trigger-record-change`,
+  `packages/triggers/trigger-schedule`
 - Reserved surface: `FlowSchema.type` enum (`packages/spec/src/automation/flow.zod.ts`)
 - Auto-wiring: `packages/cli/src/commands/serve.ts` (trigger `nameMatch` table)
 - Related: ADR-0018 (descriptor pattern this extends), ADR-0030 (outbox),

packages/triggers/trigger-record-change/package.json

@@ -42,7 +42,7 @@
   "repository": {
     "type": "git",
     "url": "https://github.com/objectstack-ai/objectstack.git",
-    "directory": "packages/plugins/plugin-trigger-record-change"
+    "directory": "packages/triggers/trigger-record-change"
   },
   "homepage": "https://objectstack.ai/docs",
   "bugs": "https://github.com/objectstack-ai/objectstack/issues",

packages/triggers/trigger-schedule/package.json

@@ -41,7 +41,7 @@
   "repository": {
     "type": "git",
     "url": "https://github.com/objectstack-ai/objectstack.git",
-    "directory": "packages/plugins/plugin-trigger-schedule"
+    "directory": "packages/triggers/trigger-schedule"
   },
   "homepage": "https://objectstack.ai/docs",
   "bugs": "https://github.com/objectstack-ai/objectstack/issues",