@mindrian_os/cli 1.16.0-beta.9 → 2.0.0-beta.1

package/CHANGELOG.md

@@ -1,3 +1,95 @@
+## [2.0.0-beta.1] - 2026-08-10
+
+### Fixed
+- **Binding this session to a room now actually sticks, and `room_bind` finally tells you the
+  truth about whether it worked.** Before this, nine separate copies of the same room-lookup
+  logic were scattered across the MCP tool files, and every one of them only checked your
+  session's chosen room when a feature flag (`MINDRIAN_MCP_FIRST`) happened to be on, which it
+  is not by default on any install. So binding to a room reported success, and the very next
+  read silently used whatever room some OTHER session on your machine had last activated, not
+  the one you just picked -- `room-bind-mcp-first-off-falls-back-to-stale-global-active-room`.
+  All nine copies are now one shared resolver, and it consults your session's binding
+  unconditionally: a room you bind to is now authoritative for the rest of that session,
+  flag or no flag. A session that never binds anything keeps behaving exactly as before, byte
+  for byte. On top of that, `room_bind` itself used to report `{ok:true, bound:true}` even when
+  you named a room that does not exist on disk -- an honest-sounding lie about an effect that
+  never actually happened. It now round-trips through the same shared resolver right after
+  writing, so the response tells you what the NEXT read will actually see: `effective`,
+  `resolved_dir`, `resolved_source`, and, when the bind did not take, why not
+  (`room_not_on_disk` for a room with no directory on disk). The short-term fix this could have
+  taken instead -- writing your bind straight into the shared, machine-wide "active room"
+  pointer -- was deliberately rejected, because that would let one session's bind clobber every
+  other concurrent session on the same machine, reintroducing the exact race a prior fix
+  already closed. A standing test asserts that pointer never moves.
+- **Larry can read the Brain again. Every single Brain call was failing before this, and nothing
+  told you so.** If you asked Larry anything that needed the teaching graph -- which framework fits
+  your problem, what the corpus says, a grade, a chain recommendation -- the call died before it
+  reached him, with a host error that looks like a network fault: `e.reduce is not a function`.
+  Nothing was wrong with the network. Nothing was wrong with the graph. The Brain was up the whole
+  time, serving 28,325 nodes and 23,014 relationships in a perfectly correct response, and the
+  plugin's own connection to it was healthy too. What broke it was a hook this plugin ships to
+  sanitize Brain responses before they reach the conversation, and it broke them in two ways at
+  once. It looked for the response text in a field the protocol never puts it in, so it found
+  nothing and sanitized an empty string. Then it handed back that empty string in the wrong
+  container shape -- a bare object where an array of content blocks belongs -- so the host tried to
+  measure the length of something that was not there and threw. Every Brain response, replaced with
+  nothing, in a shape nothing could read. The reason this ran for weeks without anyone noticing is
+  the more uncomfortable half: the Brain layer was under standing instructions to fall back silently
+  and never mention failures to you. So a total outage of the single most valuable thing in the
+  product looked, from the outside, exactly like a Larry who simply had less to say. Both defects
+  are now pinned by tests that feed the hook a real protocol-shaped response and assert the text
+  survives with the container intact, so an empty-string regression fails the suite instead of
+  reaching your session. The doctrine that hid it is being revisited separately, because a fix that
+  only works until the next silent failure is not a fix.
+- **Asking the Brain about a framework by name no longer gets blocked as a possible data leak.** The
+  guard that stops your private venture content from ever reaching the shared Brain was refusing
+  ordinary methodology questions too. Asking about "jobs to be done" -- a framework name, the kind
+  of generic handle the Brain exists to answer about, and the exact query the deployment's own
+  verification step uses -- was classified as content that might leak and stopped before it left
+  your machine. Content-free graph introspection now classifies as allowed, and the guard is
+  covered from both directions: a test proves the framework-name case gets through, and a companion
+  test proves real venture content is still blocked on the same paths. The boundary did not get
+  looser; it got accurate.
+
+## [1.16.0-beta.11] - 2026-08-06
+
+### Added
+- **`/mos:grade-grant` scores a pasted grant-application draft before you submit it, instead of
+  you finding out what a reviewer would flag only after you've already sent it in.** Starts with
+  Tnufa (Israel Innovation Authority pre-seed): paste a draft, get it checked against 18 real
+  eligibility/budget/legal/market criteria pulled from the actual Tnufa guide, each with the
+  specific "here's what people usually get wrong" line reviewers already use. The rubric lives
+  locally as its own reference pack, not in the shared Brain, and the schema is built to take the
+  other 7 Israel Innovation Authority programs the same way once their criteria get filled in.
+- **`/mos:grade-grant` now grades your room directly, hands back a build roadmap, and can run
+  the whole thing in reverse.** Your room already holds what a Tnufa application needs, so you
+  no longer have to paste a draft: room-mode reads every populated room section and grades the
+  room itself (paste-mode stays for anyone without a room yet). Every rubric criterion now knows
+  which of the 8 room sections its evidence lives in, so the grade is no longer just a score --
+  it is an offer: "build this in room/financial-model/, and here is what a strong entry looks
+  like", weakest section first, with pure submission/reporting items kept as an honest checklist
+  instead of being forced into a fake section. The same map runs backwards: hand over a finished
+  application and it gets decomposed into a NEW dedicated room (never your live venture room, so
+  grant prose cannot pollute real venture data) and then graded as a room. And the map is real
+  graph structure now, not just JSON: criterion nodes wired to section nodes through the one
+  governed graph door, so Brain can be asked for STRATEGIC advice about the room's shape (which
+  sections are covered, partial, or missing) without a single line of your content ever leaving
+  the machine.
+- **`/mos:grade-grant` can now convene a full reviewer panel instead of one holistic read --
+  and the panel actually argues.** The opt-in "Reviewer panel examination" mode fans out seven
+  adversarial reviewer personas, one per rubric category (eligibility / process / budget /
+  legal / reporting / market / ip), each reading ONLY its own criteria and asking the question
+  a real committee member asks: would I accept this section on its own? It rides the same BONO
+  fan-out and debate machinery the plugin already ships (no second engine), with a discipline
+  per seat: budget claims must show their arithmetic, market claims must cite a reason to doubt
+  before crediting demand, IP claims must name their protection mechanism and budget line. The
+  debate has teeth: a later reviewer who reads an earlier reviewer's argument can challenge its
+  finding downward (never upward -- the panel is at least as strict as its strictest reviewer),
+  a sustained challenge changes the score before it is computed, and every disagreement is
+  shown at the ruling gate instead of being averaged away. One rule survives everything: an
+  application that fails ANY eligibility criterion is rejected no matter how strong its
+  aggregate score, and the rejection reason lands in the graph as data, not as a footnote.
+
 ## [1.16.0-beta.9] - 2026-08-05
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindrian_os/cli",
-  "version": "1.16.0-beta.9",
+  "version": "2.0.0-beta.1",
   "description": "Install MindrianOS into Claude Code with one command -- `npx @mindrian_os/cli`. Ships the MindrianOS plugin (Larry + PWS methodology + Data Room) plus a setup/diagnostics CLI (install/doctor/update).",
   "scripts": {
     "mcp": "node bin/mindrian-mcp-server.cjs",
@@ -23,6 +23,7 @@
     "@ig3/markdown-it-wikilinks": "^1.0.2",
     "@modelcontextprotocol/ext-apps": "^1.5.0",
     "@modelcontextprotocol/sdk": "^1.29.0",
+    "ajv": "^8.18.0",
     "asciichart": "^1.5.25",
     "chokidar": "^4.0.3",
     "chrono-node": "^2.9.1",