@maind-dev/mcp-bridge 0.112.1 → 0.113.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -0
- package/build/index.js +291 -291
- package/build/meta.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -335,6 +335,14 @@ path and a 2,000-character preview.
|
|
|
335
335
|
channel (`session-start`). A hook you declined at the prompt is remembered
|
|
336
336
|
(`declined_hooks` in the bridge config) and not nagged about;
|
|
337
337
|
`install --hooks-only` asks again.
|
|
338
|
+
- **Any other core hook an update left unwired** (MAIND-869) — a hook that
|
|
339
|
+
did not exist when this machine ran `install`, such as the Stop
|
|
340
|
+
documentation-duty hook — gets the same treatment, less often: `doctor`
|
|
341
|
+
reports one `hooks` warning per missing core hook with the command, and
|
|
342
|
+
`on-session-start` adds one context line naming them, once per bridge
|
|
343
|
+
version (`~/.maind/guard/hook-wiring-notice.json` remembers). Until 0.112
|
|
344
|
+
that line went to stderr, which Claude Code shows only when a hook fails —
|
|
345
|
+
so it was printed at every start and seen by nobody.
|
|
338
346
|
|
|
339
347
|
## Cursor: conventions at session start
|
|
340
348
|
|