@koda-sl/baker-bridge 0.112.0 → 0.114.0

package/README.md

@@ -254,6 +254,7 @@ variables nothing is registered. Content is sent in full; mask attributes with
 | `GET` | `/brand/entry?path=<sub-path>` | None | Return one file inside `src/brand/` by its path (e.g. `logos/logo.webp`). Markdown paths return `{ content, title }` (+ `baselineContent` with `?baseline=1`); every other asset (logos, fonts) streams raw bytes with its `Content-Type`. `?baseline=1` serves the version at the git merge-base (the "before"), used by the per-file Brand changes preview |
 | `GET` | `/knowledge/:collection/:entry` or `/knowledge/:entry` | None | Return knowledge entry as `{ content, title }`; title-only Chat Change slugs are resolved by matching entry ids/titles. `?baseline=1` also includes `baselineContent` from the git merge-base when available |
 | `GET` | `/documents/:slug` | None | Serve document binary (pdf, pptx, docx, xlsx) |
+| `GET` | `/checks/:slug` | None | Return a check as `{ slug, scope, manifest, readme, files, related }`: every file of `__tooling__/checks/extensions/<slug>/` (for a base check, only its `waivers.json`) with `content`, `baselineContent` from the git merge-base and a `status` (`added`, `modified`, `deleted`, `unchanged`), plus the `__tooling__/checks/sdk/` modules its scripts import |
 | `GET` | `/landings/:slug/definition` | None | Return landing `_definition.md` as `{ content, title }`; `?baseline=1` also includes `baselineContent` from the git merge-base when available |
 | `GET` | `/flows/:slug` | None | Read flow `_data.json` (decrypted). `?baseline=1` returns `{ flow, baselineFlow, baselineStatus }` — used by the dashboard's structural changes view. `baselineStatus` is `found` (baseline decoded, `baselineFlow` set), `new` (flow absent at the merge-base, i.e. not yet published), `unavailable` (no base ref / merge-base to compare against, or an unexpected git failure), or `undecodable` (baseline present at the merge-base but not readable — invalid JSON or not decryptable with the current key); the last two keep the UI from rendering a misleading full "added" diff |
 | `PUT` | `/flows/:slug` | None | Write flow `_data.json` (encrypts at rest) |

package/dist/hono/bridge-job.test.js

@@ -321,7 +321,7 @@ describe("isControlChannelDeny", () => {
         // Its block arrives as an is_error tool_result, so an envelope-substring
         // match counted it as a deny — three blocked spawns in one turn would have
         // tripped the breaker and errored a perfectly healthy turn.
-        expect(isControlChannelDeny(controlChannelDenyMessage("PreToolUse:Agent hook error: [node __tooling__/hooks/base/guard-background-commands.mjs]: " +
+        expect(isControlChannelDeny(controlChannelDenyMessage("PreToolUse:Agent hook error: [node __tooling__/checks/base/guard-background-commands/guard-background-commands.mjs]: " +
             "✗ guard-background-commands — blocked: subagent spawned in the background.\n" +
             "  A subagent that outlives the turn loses its permission channel and orphans\n" +
             "  any work it started (a render inside it fails 'Tool permission request failed')."))).toBe(false);