replen 1.0.29 → 1.0.31

package/extras/skills/replen/SKILL.md

@@ -43,6 +43,22 @@ Parse the JSON response. Note:
 
 - `filterMode` — `tags`, `zero-knowledge`, or `fingerprint`
 - `scopedTo` — confirms the project context the user has open
+- `projectThesis` — what this project is trying to BE (`purpose`) and where it's
+  heading (`goals`). **This is your primary relevance lens.** Judge every
+  candidate against the mission, not just the capability match: a library can fit
+  a tech slot and still NOT advance what the product is trying to be (a generic
+  charting lib for a decision-support platform), and a candidate that advances a
+  `goal` is worth surfacing even if it doesn't map to an existing capability.
+  Lead your writeups with mission-fit, not just tech-fit. (Null until the project
+  is onboarded with a thesis — then fall back to capability-fit alone.)
+- `keystoneUpgrades` — task-scoped `better_than` upgrades for solutions this
+  project already uses (from Keystone, the comparative-knowledge ontology): each
+  is `{current, better, betterKind, task, margin, source}`. A deprecated/inferior
+  dependency has a maintained/stronger replacement. The footnote may surface one;
+  if the user wants it, DO the swap (update the dep, adjust call sites). Always
+  cite the `task` — "better" is task-relative (e.g. text-embedding-3-large beats
+  3-small for general retrieval but NOT for short-label matching). Don't push an
+  upgrade the user didn't ask about beyond the one calm line.
 - `candidates[]` — the actual list to triage
 - `candidates[].priorContext` — server-attached MEMORY: the user's earlier
   verdicts on this repo, and whether the matched capability is already

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

@@ -216,6 +216,30 @@ into the report or the descriptors — the capability is the signal; the
 application is exactly what stays local. When in doubt, describe it as the
 public README does.
 
+### 2c-thesis. Capture the product THESIS (what it's trying to BE)
+
+Capabilities say what a project technically *does*; the **thesis** says what it's
+trying to *be* and where it's *heading* — and that's a far better relevance test
+than any capability slot ("does this advance a contested-airspace decision-
+support platform?" beats "does this do OSINT?"). Replen now matches and triages
+against it, so capture it:
+
+- **First, look for an explicit thesis the user already keeps** — `goals.md`,
+  `GOALS.md`, `handover.md`, `HANDOVER.md`, `ROADMAP.md`, `PRD.md`, `vision.md`,
+  `docs/product*.md`, or the "what it is / active areas" sections of CLAUDE.md.
+  These are the user's own words for the mission — use them as the primary
+  source (same adapter spirit as the knowledge-graph step 2a-pre).
+- **Derive two things:**
+  - `purpose` — 1–2 sentences: what the product is trying to be and what makes
+    it distinct. The mission, not a feature list.
+  - `goals` — a few outcome directions it's heading toward (e.g. "real-time
+    multi-sensor fusion", "sub-second COA ranking").
+- **Respect the cover** exactly as for the report: the thesis describes intent
+  and tech direction, never a sensitive codename / end-user / operational target.
+  Follow the framing the user's own docs use.
+
+Pass both to `replen_set_capabilities` (`purpose`, `goals`) in 2e.
+
 ### 2d. Derive grounded capabilities
 
 From the report + code, produce 8–15 **grounded** capability objects — NOT bare
@@ -244,10 +268,11 @@ specific — `cloudflare bypass`/`proxy rotation`, not just `web scraping`.
    sidesteps the shadow. Ensure each repo has a GitHub remote so it scopes by
    `owner/name`.
 2. **Set domain tags** with `replen_set_tags` — broad domain labels.
-3. **Set capabilities + report** with `replen_set_capabilities`, passing the
-   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`.
+3. **Set capabilities + report + thesis** with `replen_set_capabilities`, passing
+   the grounded `capabilities` array, the `report` from 2c, AND the `purpose` +
+   `goals` from 2c-thesis. The server builds the facet vectors immediately, stores
+   the report as grounding, and hands the thesis to the triage agent so candidates
+   are judged against the mission. 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

package/package.json

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