@rafinery/cli 0.8.2 → 0.8.3

package/bin/rafa.mjs

@@ -148,18 +148,15 @@ End to end — from zero to a queryable, working brain:
                 validates, bloom writes the improvement ledger. Then  rafa push
                 → webhook → the platform ingests it (the brain repo only).
   4. SEE IT     Open the repo on the platform: Overview (health), Brain (files),
-                Improvements (kanban), Plans, Activity (branch changes). "Agent
-                access" mints keys for more MCP clients (Slack, CI, incident.io).
+                Improvements (kanban), Plans, Reconciliations (merge runs).
   5. WORK       /rafa plan "<intent>" — prism-validated, brain-grounded; approval
                 pushes it to the platform (the plans channel). /rafa build —
                 execute it; statuses/journals + the branch WORKING SET sync at
                 checkpoints, so any teammate or session resumes where you stopped.
-  6. RECONCILE  rafa ci-setup (once) — your CI folds branch→branch merges
-                mechanically and DISTILLS merge-to-main into the org brain with
-                YOUR OWN LLM key. No CI? The next session offers the same.
-  7. QUERY      Any MCP client with a key can read the brain at <platform>/api/mcp:
-                get_brain_status · search_knowledge · get_rule/playbook/improvement ·
-                list_plans · get_plan · get_active_plan. Read-only, cited, per-repo.
+  6. MERGE      Just merge PRs — the platform detects the merge and distills the
+                branch's knowledge into the org brain automatically (watch the
+                Reconciliations tab). Teams that want the compute in their own
+                CI instead: rafa ci-setup (optional, org-CI adapter).
 
 Then, inside Claude Code:  /rafa scan · /rafa improve · /rafa plan · /rafa build
 

package/blueprint/.claude/commands/rafa.md

@@ -234,7 +234,7 @@ explicitly typed; an ACCEPTED boundary offer counts as the explicit invocation.
 | `insights` | spawn compass → bootstrap/refresh the dev's private user brain from their native `/insights` report + recent work; every candidate OFFERED, banked only on yes (`put_dev_insight`). Capture during normal work is §capture's job, not this command. | [rafa-insights](../skills/rafa-insights/SKILL.md) |
 | `leverage` | reason over the committed toolbox (`.claude/settings.json`, `.mcp.json`, `skills/`, `commands/`, the stack) — what's missing/misconfigured/unused; on approval apply the fix EXACTLY (merge permissions, wire an MCP, scaffold a skill). Merge, never clobber; show the diff. The CLI reports, you fix. | [rafa-leverage](../skills/rafa-leverage/SKILL.md) |
 | `sage` | explicit OVERRIDE of the implicit observer pass (below) | [rafa-sage](../skills/rafa-sage/SKILL.md) |
-| `push` | `npx @rafinery/cli push` — commit `.rafa/` and push to the brain remote (the dev's own git auth), stamped `brain-for: <code sha>`. After a scan, or to re-sync a changed brain. Never without approval. | — |
+| `push` | `npx @rafinery/cli push --verb=<scan\|improve\|build\|update>` — commit `.rafa/` and push to the brain remote (the dev's own git auth), stamped `brain-for: <code sha>`. Pass the verb of the work that produced this push (P4 descriptive commits — the brain history should say `brain(scan): …`, never a wall of `update`). After a scan, or to re-sync a changed brain. Never without approval. | — |
 | `migrate` · `update` | brain-side schema migration — see below | — |
 | `help` (also no arg / unrecognized) | print this reference verbatim, then stop | — |
 

package/blueprint/.claude/rafa/hooks/brain-commit.mjs

@@ -61,6 +61,7 @@ try {
     join(rafa, "intent", `${short}.md`),
     `---\n` +
       `type: IntentRecord\n` +
+      `description: "per-commit intent trail (capture-engine P2) — provenance, consumed at merge, never org-brain truth"\n` +
       `code-commit: ${fullSha}\n` +
       `code-branch: ${branch}\n` +
       `timestamp: ${new Date().toISOString()}\n` +

package/blueprint/.claude/skills/rafa-scan/SKILL.md

@@ -254,7 +254,7 @@ pipeline; **`--brain-only`** stops after the brain is validated (step 5 PASS)
    spawn `bloom` → `.rafa/improve/`. It reads the *validated* brain as its index, so it only
    runs after PASS.
 7. **Push** — present the full summary (brain verdict/score + top improvements). **On the
-   dev's explicit approval**, `npx @rafinery/cli push` — commits `.rafa/` and pushes to the
+   dev's explicit approval**, `npx @rafinery/cli push --verb=scan` — commits `.rafa/` and pushes to the
    brain remote using the dev's own git auth, stamped `brain-for: <code sha>`. Never without approval.
 8. **The coach offer (founding scan only)** — if this was the repo's FIRST scan and the dev's
    user brain is empty (`list_dev_insights` → none), offer ONCE: *"the code side is mapped —

package/lib/ci-setup.mjs

@@ -121,6 +121,12 @@ export default async function ciSetup(args = []) {
   const ROOT = process.cwd();
   const target = join(ROOT, WORKFLOW_PATH);
 
+  console.log(
+    "OPTIONAL — the platform reconciles merges automatically (no CI, no repo secrets).\n" +
+      "This wires the org-CI ADAPTER instead: reconciliation compute runs in YOUR\n" +
+      "GitHub Actions on YOUR secrets. Most teams should skip this.\n",
+  );
+
   if (existsSync(target)) {
     const current = readFileSync(target, "utf8");
     if (current === WORKFLOW) {

package/lib/init.mjs

@@ -176,25 +176,12 @@ export default async function init(args) {
     );
   }
 
-  // CI reconciliation — OPT-IN at provisioning (owner feedback #5): the workflow
-  // runs on the ORG's own secrets (their LLM key never touches our platform), so
-  // it is offered, never silently installed. Non-TTY (CI/agent shells) skips the
-  // question entirely — explicit `rafa ci-setup` remains the path there.
-  if (isInteractive()) {
-    const a = await ask(
-      "  • Wire CI reconciliation now? (GitHub Actions: mechanical fold on branch merges,\n" +
-        "    distillation on merge-to-main — runs on YOUR CI secrets) [y/N] ",
-    );
-    if (a === "y" || a === "yes") {
-      const { default: ciSetup } = await import("./ci-setup.mjs");
-      await ciSetup([]);
-    } else {
-      console.log(
-        "  • skipped — wire it anytime with `rafa ci-setup`. Until then, the next dev\n" +
-          "    session offers the same reconciliation after each merge (nothing is lost).",
-      );
-    }
-  }
+  // Reconciliation runs on the PLATFORM (App-only era, owner call 2026-07-18):
+  // merged PRs are detected and distilled by the platform's own sandbox — no
+  // CI workflow, no repo secrets, nothing to wire here. The org-CI adapter
+  // stays available as an explicit opt-out for teams that want the compute in
+  // their own CI: `rafa ci-setup`. Init no longer asks — one fewer question,
+  // one fewer confusion.
 
   // Stamp the versions this repo was provisioned at — the compat anchor `update`/`migrate`
   // diff against. Carries platform identity too when provisioned via a setup URL.
@@ -224,8 +211,8 @@ export default async function init(args) {
       "     Joining an ALREADY-scanned repo: run  rafa pull  — never re-scan for existing knowledge.\n" +
       "  4. Open the repo on the rafinery platform — its Overview shows the brain once pushed." +
       (p?.mcpUrl
-        ? "\n  5. After the first push, any MCP client with a key can query this repo's knowledge\n" +
-          `     (endpoint: ${p.mcpUrl} · keys: repo → Agent access on the platform).`
+        ? "\n  5. Merge PRs as usual — the platform reconciles branch knowledge into the\n" +
+          "     brain automatically (watch the repo's Reconciliations tab)."
         : ""),
   );
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@rafinery/cli",
-  "version": "0.8.2",
-  "description": "rafa — the AI engineer CLI. Vendors the rafa blueprint into your repo (shadcn-style) and runs the deterministic contract gates.",
+  "version": "0.8.3",
+  "description": "rafa \u2014 the AI engineer CLI. Vendors the rafa blueprint into your repo (shadcn-style) and runs the deterministic contract gates.",
   "type": "module",
   "bin": {
     "rafa": "bin/rafa.mjs",