replen 1.0.16 → 1.0.17

package/dist/inject-instruction.js

@@ -33,7 +33,7 @@
 import { readFileSync, writeFileSync, existsSync } from "node:fs";
 import { join, basename } from "node:path";
 import { createInterface } from "node:readline";
-export const INTEGRATION_VERSION = "8";
+export const INTEGRATION_VERSION = "9";
 const SECTION_HEADER = "## Replen integration";
 const MARKER_RE = /<!--\s*replen-integration:\s*v(\d+)\s*-->/;
 const SECTION_BODY = `<!-- replen-integration: v${INTEGRATION_VERSION} -->
@@ -89,6 +89,16 @@ 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.
+
+**PORTFOLIO-FIRST RULE (any turn, not just the first).** Before you
+(a) add a new dependency, (b) pick a library/stack for a task, or
+(c) build a capability from scratch (scraping, auth, OCR, queues,
+charting, …), call \`replen_recall\` with the capability first. The
+user\'s OTHER projects may already have a settled way to do it — a
+chosen library, or an implementation file (\`paths\`) you can port.
+If recall returns a convention, FOLLOW IT (or name it and ask)
+instead of introducing a parallel stack. The user should never have
+to say "you know I use scrapling elsewhere" — knowing is your job.
 `;
 // Find candidate project directories using the same layered discovery
 // as `npx replen sync-projects` — explicit --root flag → REPLEN_PROJECT_ROOTS

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

@@ -135,6 +135,11 @@ specific — `cloudflare bypass`/`proxy rotation`, not just `web scraping`.
    grounded `capabilities` array AND the `report` from 2c. The server builds the
    facet vectors immediately and stores the report as grounding for its own
    summarization. Use the MCP tools, not hand-rolled `curl`.
+   **Include `paths` on each capability** — up to 5 file paths that implement
+   it (e.g. `{tag: "computer vision", …, paths: ["src/cv/transformations.py"]}`).
+   Paths only, never code. You just read these files; recording WHERE each
+   capability lives lets Replen point another of the user's projects straight
+   at the implementation worth porting ("aegis solved this — see src/cv/…").
 4. **Report pinned versions** with `replen_set_versions` — the resolved DIRECT
    dependency versions from the lockfile (package-lock.json / poetry.lock /
    uv.lock / Cargo.lock), plus runtimes under canonical keys (`node` from

package/package.json

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