replen 1.0.39 → 1.1.0

package/README.md

@@ -72,7 +72,7 @@ Every data command accepts `--json` for scripting.
 Three layers, defence-in-depth — at least one will fire:
 
 1. **SessionStart hook** runs `npx replen check-new --hook` at the start of every Claude Code session. If there's anything new, the JSON output appears in the agent's opening context.
-2. **MCP tool** `replen_check_new` is exposed to the agent at all times. The instructions in `CLAUDE.md` tell it to call this tool early in each session.
+2. **MCP tool** `replen_match` is exposed to the agent at all times. The instructions in `CLAUDE.md` tell it to call this once early in each session (it returns the footnote + the candidate inventory).
 3. **CLAUDE.md / AGENTS.md instruction** (idempotent, marker-versioned) is injected into every tracked repo on setup. This is the most reliable layer — survives Claude Code version churn.
 
 Calm-cadence by design: most days are silent. 1-3 actionable matches a month per project.

package/dist/commands.js

@@ -335,7 +335,7 @@ export async function runCheckNew(argv) {
             console.log(`    ${m.oneLine}`);
     }
     console.log("");
-    console.log("Call replen_today for the full writeups.");
+    console.log("Open /replen (replen_match) for the full writeups.");
 }
 // Watch for new matches in the background. Polls /api/mcp/today, diffs against
 // the matchIds seen on the previous poll, prints anything new, and rings the

package/dist/inject-instruction.js

@@ -81,11 +81,6 @@ On your **very first response** of each session:
 - The user directly asked for Replen output ("anything from replen
   today?", "what\'s new from replen?"). Just answer.
 
-**Do NOT use \`replen_check_new\` for the conversational footnote.**
-That tool is cursor-based and meant for SessionStart shell hooks.
-\`replen_match\` queries inventory state directly and is the right
-primitive here.
-
 **Don\'t call \`replen_match\` again on subsequent turns** — once
 per session at start only. The user explicitly types
 \`/replen\` if they want a fresh triage mid-session.

package/dist/mcp-setup.js

@@ -55,19 +55,21 @@ const CODEX_CONFIG = join(homedir(), ".codex", "config.toml");
 const GEMINI_CONFIG = join(homedir(), ".gemini", "settings.json");
 // Read/triage replen MCP tools that are safe to auto-allow so the proactive
 // footnote (replen_match) and in-session triage don't trigger a permission
-// prompt every session. Deliberately EXCLUDES replen_run / replen_handoff /
-// replen_feedback — those trigger pipeline runs / open PRs and should keep
-// prompting for explicit consent.
+// prompt every session. Deliberately EXCLUDES replen_handoff — it opens PRs and
+// should keep prompting for explicit consent.
 const REPLEN_AUTO_ALLOW = [
     "mcp__replen__replen_match",
-    "mcp__replen__replen_check_new",
-    "mcp__replen__replen_analyze",
-    "mcp__replen__replen_state",
     "mcp__replen__replen_record_triage",
-    "mcp__replen__replen_today",
-    "mcp__replen__replen_search",
-    "mcp__replen__replen_starred",
-    "mcp__replen__replen_status",
+    "mcp__replen__replen_state",
+    "mcp__replen__replen_capture_insight",
+    "mcp__replen__replen_recall",
+    "mcp__replen__replen_leaps",
+    "mcp__replen__replen_queue",
+    "mcp__replen__replen_onboard_state",
+    "mcp__replen__replen_set_tags",
+    "mcp__replen__replen_set_capabilities",
+    "mcp__replen__replen_set_versions",
+    "mcp__replen__replen_set_product",
     "mcp__replen__replen_help",
 ];
 // ============================================================================
@@ -99,7 +101,7 @@ export async function setupMcp(token, base) {
     installSkills();
     // CLAUDE.md / AGENTS.md / GEMINI.md inject is the proactive-surfacing
     // mechanism for each host. Without it, the agent doesn't know to
-    // call replen_check_new at session start. Idempotent + versioned.
+    // call replen_match at session start. Idempotent + versioned.
     console.log("");
     const { injectInstructions, summariseOutcome } = await import("./inject-instruction.js");
     const outcome = await injectInstructions();

package/dist/project-init.js

@@ -25,12 +25,11 @@ Total length target: 200-500 words, bullet points over paragraphs.
 
 Also append a short "## Replen integration" section with this exact guidance:
 
-  At the start of every session, if the \`replen_check_new\` tool is
-  available, call it once before asking the user what to work on.
-  If \`hasNew\` is true, summarise the count + repos in 1-2 lines and
-  ask if the user wants the full writeups (which they get via
-  \`replen_today\`). If \`hasNew\` is false, say nothing — silence is
-  the correct response, not "no new matches found".
+  At the start of every session, if the \`replen_match\` tool is
+  available, call it once (no repo arg — it defaults to the cwd repo)
+  before asking the user what to work on. Relay the USER-FACING MESSAGE
+  block it returns VERBATIM if it's non-empty; if it's empty, say
+  nothing — silence is the correct response, not "no new matches found".
 
 This instruction is a fallback for AI tools that don't run Claude Code's SessionStart hooks (e.g. Codex, Cursor, Aider). For Claude Code users the hook calls \`replen check-new\` automatically and Claude Code injects the result into the opening context — but the CLAUDE.md guidance is durable across tools and survives hook misconfiguration.`;
 export function runProjectInit() {

package/extras/skills/replen-onboard/SKILL.md

@@ -297,6 +297,12 @@ typed properties, computed properties as rows", never the entity names).
      `military-drones`, `counter-uas`). The COLLECTIVE pins the meaning: a
      candidate that hits one term but none of its neighbours is a different
      world and scores low.
+   - QUALIFY AMBIGUOUS HEAD-NOUNS. If a tag's core noun is ambiguous ACROSS
+     fields (`agent`, `carry`, `model`, `pipeline`, `driver`, `mission`),
+     prefix it with the domain so the compound carries the meaning —
+     `estate-agent-matching` NOT `agent-matching`, `funding-carry` NOT `carry`.
+     A bare head-noun like `agent-matching` decomposes in embedding space toward
+     the wrong field (AI agents) and drags the whole project's centroid with it.
    - GROUNDED ONLY — every tag supported by code you actually read; never
      aspirational (don't add `scraping` if it doesn't scrape).
    - EXCLUDE: stack / framework / language (`next.js`, `react`, `firebase`,
@@ -329,10 +335,11 @@ If several repos are one product (e.g. `aegis-web`/`aegis-api`/`aegis-cv`), grou
 them with `replen_set_product` so Replen unions the whole product's capabilities
 when the user is in any one of them.
 
-## Step 4 — Warm + close out
+## Step 4 — Close out
 
-1. Trigger an embedding/inventory pass so everything's ready: `replen_run` (it's
-   async; the per-project facets you set are already live regardless).
+1. Nothing to trigger — the per-project facets, capabilities, and versions you
+   set are live immediately, and the next scheduled run refreshes the candidate
+   inventory automatically.
 2. Summarise what you did, calmly:
 
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replen",
-  "version": "1.0.39",
+  "version": "1.1.0",
   "description": "Make your AI coding tools smarter. One command, no API keys, free. Replen watches what your projects actually do and surfaces a few things worth bringing in each month. Use one as is, port a piece of another, cherry pick an idea, or build it clean room. The match happens inside your AI tool's session. A few actionable matches a month, by design.",
   "type": "module",
   "bin": {