replen 1.2.0 → 1.2.1

package/dist/init.js

@@ -166,13 +166,20 @@ export async function runInit() {
     const { runFirstIngest } = await import("./first-ingest.js");
     await runFirstIngest({ token: exchange.token, base: exchange.base, savedAt: "" });
     console.log("");
-    console.log("  All set. Restart Claude Code and try:");
-    console.log("    /replen       → triage today's candidates against this repo,");
-    console.log("                         in-session, using your subscription tokens");
-    console.log("    (no LLM API keys needed — the agent does the reasoning)");
+    console.log("  All set. Restart Claude Code, then do these two — IN THIS ORDER:");
     console.log("");
-    console.log("  Other MCP hosts (Codex / Cursor / Aider):");
-    console.log("    \"use replen_match\" — same tool, no slash command");
+    console.log("    1. /replen-onboard   ONE-TIME, FIRST. Reads your repos and builds a");
+    console.log("                         tailored profile so matches are relevant, not");
+    console.log("                         generic. Runs in the background — kick it off,");
+    console.log("                         then just keep working.");
+    console.log("");
+    console.log("    2. /replen           ANYTIME after that. Triages the candidates for");
+    console.log("                         the current repo, in-session, on your own");
+    console.log("                         subscription tokens — no LLM API key needed.");
+    console.log("");
+    console.log("  (Onboarding is once per project. After that, it's just /replen.)");
+    console.log("");
+    console.log("  Other MCP hosts (Codex / Cursor / Aider): \"use replen_match\" — same tool.");
     console.log("");
     console.log(`  Dashboard: ${exchange.base}`);
     console.log("");

package/dist/inject-instruction.js

@@ -33,12 +33,25 @@
 import { readFileSync, writeFileSync, existsSync } from "node:fs";
 import { join, basename } from "node:path";
 import { createInterface } from "node:readline";
-export const INTEGRATION_VERSION = "9";
+export const INTEGRATION_VERSION = "10";
 const SECTION_HEADER = "## Replen integration";
 const MARKER_RE = /<!--\s*replen-integration:\s*v(\d+)\s*-->/;
 const SECTION_BODY = `<!-- replen-integration: v${INTEGRATION_VERSION} -->
 
-On your **very first response** of each session:
+**FIRST, on your first response in a repo: check onboarding.** Call
+\`replen_onboard_state\` once. If it reports this repo (or the user's
+portfolio) is NOT yet onboarded/grounded, do NOT run the footnote flow
+this turn. Answer the user's message normally, then offer this VERBATIM
+as a new paragraph at the end:
+
+> Replen isn't set up for your repos yet — want me to do that now? Replen builds a profile so matches are relevant. Onboarding runs in the background, ~a few minutes.
+
+If they accept, invoke the \`replen-onboard\` skill. If they decline, carry
+on and do NOT re-offer for the rest of this session. Once \`replen_onboard_state\`
+shows the repo is onboarded, SKIP this check entirely and use the footnote
+flow below.
+
+Once onboarded, on your **very first response** of each session:
 
 1. **Skip the whole flow ONLY if** the user's first message is a
    pure trivial greeting with no content ("hi", "hey", "yo",

package/extras/skills/replen/SKILL.md

@@ -40,7 +40,10 @@ Parse the JSON response. Note:
 
 - `filterMode` — `tags`, `zero-knowledge`, or `fingerprint`
 - `scopedTo` — confirms the project context the user has open
-- `candidates[]` — the actual list to triage
+- `candidates[]` — the actual list to triage. Each carries `solid: true|false` —
+  the ones Replen counts as genuinely worth your time (clear domain-fit + posture +
+  not-already-covered, or a dependency-maintenance match). The footnote's count is
+  the number of `solid` ones; the rest are "worth a glance" laterals.
 
 If `candidates.length === 0`, tell the user "No new candidates today for
 `<owner/name>`. Calm-cadence working as designed — 1-3 actionable
@@ -50,8 +53,11 @@ If 1+ candidates, continue.
 
 ### Step 3 — Per-candidate analysis
 
-**Cap at 5 candidates.** If the inventory returned more, take the top 5
-by `whyShortlisted` strength + stars + recency, defer the rest.
+**Triage the `solid` candidates first** (cap at 5). If there are more than 5
+solid, take the top 5 by `whyShortlisted` strength + stars + recency. The
+non-`solid` "worth a glance" entries are optional — skim them only if the solid
+set is thin or the user asks. A low-domain-fit lateral there can still be a real
+port/cherry-pick, so don't dismiss them blindly, but they're not the headline.
 
 For each candidate, do this loop:
 
@@ -210,9 +216,15 @@ For tech-news-site:
 
 (Triaged 9 candidates; surfacing the 2 worth acting on + 1 idea worth keeping.)
 
-What would you like to do with each? (star / hide / handoff)
+What would you like to do with each? — star (save it for later; won't
+re-surface), hide (dismiss; never show again), or handoff (open a pull
+request against your repo for it). Or skip and decide later.
 ```
 
+Always present the options WITH that one-line gloss the first time in a
+session — never the bare "(star / hide / handoff)". A new user doesn't know
+what they mean, and the calm-cadence promise dies if the user has to ask.
+
 The one-line "(Triaged N…)" footer is the *only* acknowledgement that skips
 happened — honest, but it doesn't parade them.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replen",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "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": {