@maind-dev/mcp-bridge 0.111.0 → 0.112.0

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 CHANGED
@@ -304,13 +304,20 @@ path and a 2,000-character preview.
304
304
  via …`), never cut silently. It runs on `startup`, `clear` and `compact` (a
305
305
  compaction summarises the earlier block away); `resume` and `fork` keep the
306
306
  earlier one.
307
- - **Where it comes from.** The same cache-first ladder as the guard: the
308
- local cache `~/.maind/guard/briefing-cache.json` (fresh for 12 h, for the
309
- same project), else
310
- one fetch from mcp.maind.dev with a 3-second budget (API key, device id,
311
- project key, client family — never paths or file contents), else the stale
312
- cache with a note. With nothing at all, one line tells the model to call
307
+ - **Where it comes from.** The same ladder as the guard: the local cache
308
+ `~/.maind/guard/briefing-cache.json` (fresh for 5 minutes, for the same API
309
+ key, project and stack, and only when the server delivered your org's
310
+ conventions), else one fetch from mcp.maind.dev with a 3-second budget (API
311
+ key, device id, project key, client family and the repository's stack —
312
+ slugs such as `nextjs,typescript`, read from the tracked `package.json` and
313
+ marker files; never paths or file contents), else the stale cache of the
314
+ same API key with a note — a copy made for another repository without its
315
+ conventions. With nothing at all, one line tells the model to call
313
316
  `get_session_briefing` itself.
317
+ - **The stack.** Conventions can be scoped to a stack; a session that declares
318
+ none receives none of those. The hook and the live connection therefore
319
+ declare the stack they detect (`x-maind-stack`). A `?stack=` in your MCP URL
320
+ is yours and wins: the live connection then sends no header.
314
321
  - **Delivery, not enforcement.** It is a core hook: `install` offers it with
315
322
  its own consent, `install --full` (the dashboard's One-Click path) wires it,
316
323
  and it works with the guard off. The guard pack's `guard-inject` delivers
@@ -656,7 +663,7 @@ enables it without asking.
656
663
  | `~/.maind/guard/agents-md-refresh.json` | When a team block in `AGENTS.md` was last checked, per file (path hashed; mode 0600) |
657
664
  | `~/.maind/guard/rules-refresh.json` | When each user-level rule file was last checked, for which repository, with which content (all hashed; mode 0600) |
658
665
  | `~/.maind/guard/repo-blocks-notice.json` | Repositories the session-start line already told about their old maind blocks (hashed; mode 0600) |
659
- | `~/.maind/guard/briefing-cache.json` | The last session briefing + conventions, for the session-start hooks, the rule files and the team block (12 h; mode 0600) |
666
+ | `~/.maind/guard/briefing-cache.json` | The last session briefing + conventions, for the session-start hooks, the rule files and the team block (5 min, bound to the API key; mode 0600) |
660
667
  | `~/.maind/context/<session>/` | Once-per-session markers of the context hooks: one empty file per delivered item, named by a hash; swept after 7 days |
661
668
  | `~/.maind/cursor/deliveries.jsonl` | What the Cursor sessionStart hook delivered: conversation id, transcript path, size (local, pruned; mode 0600) |
662
669