@onlooker-community/ecosystem 0.43.2 → 0.43.4

package/.claude/settings.json

@@ -15,4 +15,4 @@
       }
     ]
   }
-}
+}

package/.claude/skills/writing-tests/SKILL.md

@@ -144,6 +144,24 @@ tail -n 1 "$ONLOOKER_EVENTS_LOG" \
 
 Production code must emit only through `scripts/lib/onlooker-event.mjs` (often via a plugin wrapper like `librarian_emit` / `assayer_emit_event`) — never by writing the log directly. New event types must be registered in `@onlooker-community/schema` before they validate.
 
+You no longer need a bespoke per-plugin test proving a payload validates. The
+suite gates every emission at once: `ONLOOKER_TEST_REPORT_DIR` is set during
+`test:bats` and `test:schema`, and `npm run test:bus` fails on any rejected
+emission. Write the test that drives the branch; the gate does the validating.
+
+What still matters is exercising the *rare* branches. A payload is only checked
+when some test makes the code emit it, so an enum bug on an error path stays
+invisible until a test reaches that path.
+
+If a test deliberately emits an invalid payload — proving a bad event type or
+malformed payload gets rejected — wrap the call in `expect_emission_rejected`
+(`test/helpers/setup.bash`) instead of calling it directly. It unsets
+`ONLOOKER_TEST_REPORT_DIR` for the duration of the call and restores it
+afterward, so the deliberate rejection never lands in `emissions.jsonl`. Skip
+this and Gate A fails: it counts every rejection in the report as a real
+regression, deliberate or not, and can't tell your negative test from schema
+drift.
+
 ### Seed fixtures and generate IDs
 
 Write fixtures with `jq -n` into the plugin's project-keyed directory, and generate IDs with the plugin's `*-ulid.sh` (ULIDs, not UUIDs — a repo-wide convention). A typical artifact seeder:

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ecosystem",
-  "version": "0.43.2",
+  "version": "0.43.4",
   "description": "Observability substrate for Claude Code. Provides the shared $ONLOOKER_DIR storage root (default $HOME/.onlooker), canonical schema-validated event emission, session and tool tracking hooks, and prompt rules. Required by all other Onlooker plugins.",
   "author": {
     "name": "Onlooker Community",

package/.release-please-manifest.json

@@ -1,5 +1,5 @@
 {
-  ".": "0.43.2",
+  ".": "0.43.4",
   "plugins/archivist": "0.3.1",
   "plugins/tribunal": "1.2.7",
   "plugins/echo": "0.3.1",

package/AGENTS.md

@@ -132,7 +132,10 @@ See `plugins/compass/docs/adr/001-evaluate-prompts-in-context.md` for the full d
 3. Store runtime artifacts under `${ONLOOKER_DIR:-$HOME/.onlooker}/<name>/<project-key>/`. Always use `$ONLOOKER_DIR` — never hardcode `~/.onlooker` — so the test suite's isolated temp home is respected.
 4. Derive the project key via `tribunal_project_key` (or equivalent) — first 12 hex chars of SHA256(`remote:<origin-url>`), falling back to SHA256(`root:<repo-root>`) for repos without a remote. See `plugins/tribunal/scripts/lib/tribunal-project-key.sh`.
 5. Register event types in `@onlooker-community/schema` before emitting them. The runtime emitter is dependency-free and **fails open**: it validates against the schema package only when that package is resolvable (dev, CI, tests) and emits unconditionally otherwise, because installed marketplace plugins ship no `node_modules`. Schema drift is caught in CI against the published schemas at `schema.onlooker.dev`. See [ADR-005](docs/adr/005-runtime-emitter-fails-open.md).
-6. Fail-soft when `~/.onlooker/` is absent — plugins must not block a session they were not invited to.
+6. Triage every new event type into `test/bus-coverage.json` — `expected` when
+   a test drives the branch that emits it, `excluded` with a reason when not.
+   `npm run test:bus` fails on any registered type that appears in neither list.
+7. Fail-soft when `~/.onlooker/` is absent — plugins must not block a session they were not invited to.
 
 ## Development
 
@@ -163,6 +166,16 @@ Workflow:
 - ULIDs everywhere for IDs (not UUIDs). Each plugin ships its own `*_ulid` helper (e.g. `archivist-ulid.sh`, `tribunal-ulid.sh`); there is no shared ecosystem helper. Copy `plugins/tribunal/scripts/lib/tribunal-ulid.sh` as a starting point and rename the function prefix.
 - Config defaults live in `config.json`. User overrides go in `~/.claude/settings.json` (global) or `.claude/settings.json` (per-project) under the plugin's namespace key (e.g. `"compass"`, `"tribunal"`). See ADR-004.
 
+<!-- Every `bd`-generated block is fenced by markdownlint-disable/enable pairs.
+     `bd setup` rewrites whatever sits between BEGIN and END verbatim, so any
+     fix `npm run lint` applies inside a block is undone the next time anyone
+     regenerates it. CI runs `lint:check`, which reports but never rewrites, so
+     the churn lands as a red build unrelated to whatever that person was doing.
+     The pairs sit *outside* the markers so `bd` does not clobber them.
+     MD012 (consecutive blank lines), MD024 (duplicate headings) and MD034
+     (bare URLs) are the rules the generated text trips. See ecosystem-55g.
+     scripts/lint/check-managed-blocks.mjs enforces that every block is fenced. -->
+<!-- markdownlint-disable MD012 MD024 MD034 -->
 <!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:970c3bf2 -->
 ## Beads Issue Tracker
 
@@ -218,13 +231,13 @@ This protocol applies when ending a Beads implementation workflow. It is subordi
 - Do not commit or push without clear authority from the active profile or the current user request.
 - If a required sync or push is blocked, stop and report the exact command and error.
 <!-- END BEADS INTEGRATION -->
+<!-- markdownlint-enable MD012 MD024 MD034 -->
 
 <!-- The Codex block below repeats the "Beads Issue Tracker" heading from the
      integration block above. Both are generated and re-synced by different `bd`
      subcommands, so neither heading can be renamed by hand without breaking
-     idempotent regeneration. These comments sit outside the BEGIN/END markers
-     so `bd` does not clobber them when it rewrites the block. -->
-<!-- markdownlint-disable MD024 -->
+     idempotent regeneration. -->
+<!-- markdownlint-disable MD012 MD024 MD034 -->
 <!-- BEGIN BEADS CODEX SETUP: generated by bd setup codex -->
 ## Beads Issue Tracker
 
@@ -246,6 +259,6 @@ bd prime                # Refresh Beads context
 - Run `bd prime` when Beads context is missing or stale. Codex 0.129.0+ can load Beads context automatically through native hooks; use `/hooks` to inspect or toggle them.
 - Keep persistent project memory in Beads via `bd remember`; do not create ad hoc memory files.
 
-**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See <https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md> for details and anti-patterns.
+**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See https://github.com/gastownhall/beads/blob/main/docs/core-concepts/sync-concepts.md for details and anti-patterns.
 <!-- END BEADS CODEX SETUP -->
-<!-- markdownlint-enable MD024 -->
+<!-- markdownlint-enable MD012 MD024 MD034 -->

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.43.4](https://github.com/onlooker-community/ecosystem/compare/ecosystem-v0.43.3...ecosystem-v0.43.4) (2026-08-22)
+
+
+### Bug Fixes
+
+* **events:** route prompt_rule emission through the canonical emitter :relieved: ([#196](https://github.com/onlooker-community/ecosystem/issues/196)) ([c233bfa](https://github.com/onlooker-community/ecosystem/commit/c233bfa466cf400e767f4673e0143081618314a7))
+
+## [0.43.3](https://github.com/onlooker-community/ecosystem/compare/ecosystem-v0.43.2...ecosystem-v0.43.3) (2026-08-22)
+
+
+### Bug Fixes
+
+* **ci:** fence bd-managed blocks against lint churn :relieved: ([#194](https://github.com/onlooker-community/ecosystem/issues/194)) ([e09fcb6](https://github.com/onlooker-community/ecosystem/commit/e09fcb6836645999feb831a7494236d4a54ed318))
+
 ## [0.43.2](https://github.com/onlooker-community/ecosystem/compare/ecosystem-v0.43.1...ecosystem-v0.43.2) (2026-08-21)
 
 

package/CLAUDE.md

@@ -79,7 +79,10 @@ See `plugins/compass/docs/adr/001-evaluate-prompts-in-context.md` for the full d
 3. Store runtime artifacts under `${ONLOOKER_DIR:-$HOME/.onlooker}/<name>/<project-key>/`. Always use `$ONLOOKER_DIR` — never hardcode `~/.onlooker` — so the test suite's isolated temp home is respected.
 4. Derive the project key via `tribunal_project_key` (or equivalent) — first 12 hex chars of SHA256(`remote:<origin-url>`), falling back to SHA256(`root:<repo-root>`) for repos without a remote. See `plugins/tribunal/scripts/lib/tribunal-project-key.sh`.
 5. Register event types in `@onlooker-community/schema` before emitting them. The runtime emitter is dependency-free and **fails open**: it validates against the schema package only when that package is resolvable (dev, CI, tests) and emits unconditionally otherwise, because installed marketplace plugins ship no `node_modules`. Schema drift is caught in CI against the published schemas at `schema.onlooker.dev`. See [ADR-005](docs/adr/005-runtime-emitter-fails-open.md).
-6. Fail-soft when `~/.onlooker/` is absent — plugins must not block a session they were not invited to.
+6. Triage every new event type into `test/bus-coverage.json` — `expected` when
+   a test drives the branch that emits it, `excluded` with a reason when not.
+   `npm run test:bus` fails on any registered type that appears in neither list.
+7. Fail-soft when `~/.onlooker/` is absent — plugins must not block a session they were not invited to.
 
 ## Development
 
@@ -110,7 +113,17 @@ Workflow:
 - ULIDs everywhere for IDs (not UUIDs). Each plugin ships its own `*_ulid` helper (e.g. `archivist-ulid.sh`, `tribunal-ulid.sh`); there is no shared ecosystem helper. Copy `plugins/tribunal/scripts/lib/tribunal-ulid.sh` as a starting point and rename the function prefix.
 - Config defaults live in `config.json`. User overrides go in `~/.claude/settings.json` (global) or `.claude/settings.json` (per-project) under the plugin's namespace key (e.g. `"compass"`, `"tribunal"`). See ADR-004.
 
-<!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:6cd5cc61 -->
+<!-- Every `bd`-generated block is fenced by markdownlint-disable/enable pairs.
+     `bd setup` rewrites whatever sits between BEGIN and END verbatim, so any
+     fix `npm run lint` applies inside a block is undone the next time anyone
+     regenerates it. CI runs `lint:check`, which reports but never rewrites, so
+     the churn lands as a red build unrelated to whatever that person was doing.
+     The pairs sit *outside* the markers so `bd` does not clobber them.
+     MD012 (consecutive blank lines), MD024 (duplicate headings) and MD034
+     (bare URLs) are the rules the generated text trips. See ecosystem-55g.
+     scripts/lint/check-managed-blocks.mjs enforces that every block is fenced. -->
+<!-- markdownlint-disable MD012 MD024 MD034 -->
+<!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:46cd31e7 -->
 ## Beads Issue Tracker
 
 This project uses **bd (beads)** for issue tracking. Run `bd prime` to see full workflow context and commands.
@@ -130,7 +143,7 @@ bd close <id>         # Complete work
 - Run `bd prime` for detailed command reference and session close protocol
 - Use `bd remember` for persistent knowledge — do NOT use MEMORY.md files
 
-**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See <https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md> for details and anti-patterns.
+**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See https://github.com/gastownhall/beads/blob/main/docs/core-concepts/sync-concepts.md for details and anti-patterns.
 
 ## Agent Context Profiles
 
@@ -154,6 +167,7 @@ This protocol applies when ending a Beads implementation workflow. It is subordi
 
    # Team-maintainer opt-in only, unless current instructions forbid it:
    git pull --rebase
+   bd dolt push
    git push
    git status
    ```
@@ -164,3 +178,4 @@ This protocol applies when ending a Beads implementation workflow. It is subordi
 - Do not commit or push without clear authority from the active profile or the current user request.
 - If a required sync or push is blocked, stop and report the exact command and error.
 <!-- END BEADS INTEGRATION -->
+<!-- markdownlint-enable MD012 MD024 MD034 -->

package/biome.json

@@ -42,5 +42,11 @@
         "organizeImports": "on"
       }
     }
-  }
+  },
+  "overrides": [
+    {
+      "includes": [".claude/settings.json"],
+      "formatter": { "enabled": false }
+    }
+  ]
 }

package/docs/architecture.md

@@ -93,7 +93,49 @@ Every observable event flows through `onlooker-event.mjs` before being written t
 
 The schema is versioned independently and published to npm. Plugin shell scripts invoke `onlooker-event.mjs` at runtime so schema validation always reflects the installed version.
 
-> **Note:** Not all events in the JSONL log are schema-validated. `prompt_rule.*` events are currently emitted outside the canonical schema pipeline (the event types are not yet defined in `@onlooker-community/schema`). Schema-first emission is the goal for all future event types.
+> **Note:** Every emission path that fires in normal operation routes through `onlooker-event.mjs`. `prompt_rule.*` was the last routine exception — `prompt_rules_emit` hand-built its envelope with `jq` and wrote straight to `$ONLOOKER_EVENTS_LOG`, so those lines carried none of the required `id`/`schema_version`/`runtime`/`machine_id`/`sequence` fields and added a `turn` field the envelope forbids. It now goes through the emitter like everything else.
+>
+> One hand-built envelope remains, in the `safe_emit` fallback in `scripts/lib/validate-path.sh`. It is reached only when `$ONLOOKER_EMIT` is missing, which does not happen in a normal checkout or install, so it is latent rather than live — but if it ever fires it writes the same unvalidatable shape. Route new event types through the emitter rather than writing to the log directly: an envelope assembled anywhere else will drift from the schema without anything noticing.
+
+### Emission gates
+
+Payload drift used to be invisible. The emitter validates against
+`@onlooker-community/schema` wherever it resolves and rejects a bad event with
+a non-zero exit, but hooks fail soft and exit 0, so the rejection was destroyed
+and the event simply never appeared.
+
+Two CI gates close that hole. During the test suite `ONLOOKER_TEST_REPORT_DIR`
+is set, and the emitter appends one line per emission to `emissions.jsonl`
+recording whether validation ran (`validated`) and, if so, whether it passed
+(`valid`). `npm run test:bus` (`scripts/lint/check-bus-coverage.mjs`) reads
+that report and runs two gates against it, after `test:bats` and `test:schema`
+have populated the report:
+
+- **Gate A** fails if the report is empty, if nothing in it was actually
+  validated (the schema package never resolved — usually a missing
+  `npm ci`), or if any recorded emission was rejected, naming the type and
+  its ajv errors.
+- **Gate B** checks every event type in `@onlooker-community/schema`'s
+  `ALL_EVENT_TYPES` against `test/bus-coverage.json`, and fails when:
+  1. an `expected` type never produced a validated emission during the
+     suite;
+  2. a registered type is missing from both `expected` and `excluded` (or
+     the manifest names a type the schema doesn't register);
+  3. an `excluded` type carries an empty reason; or
+  4. an `excluded` type *did* emit and validate during the suite — without
+     this check, moving a genuinely-emitted type into `excluded` with any
+     non-empty reason would satisfy the other three, so coverage could be
+     silently under-claimed while CI stayed green.
+
+Gate B only runs when Gate A found at least one validated emission in the
+report. A merely non-empty report where nothing validated would otherwise
+bury the one real failure under one "expected type never emitted" line per
+expected type — 82 lines of noise for 1 real cause, measured against the
+current manifest.
+
+Adding an event type therefore requires triaging it into
+`test/bus-coverage.json` — as `expected`, meaning a test exercises the branch
+that emits it, or as `excluded` with a stated reason.
 
 ## Project keying