replen 1.0.5 → 1.0.6

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

@@ -217,9 +217,16 @@ that actually fit."* If the user agrees, run this checklist:
    app.replen.dev/projects.) Tags matter most right after onboarding, before the
    project has an embedding — without them a fresh project falls back to
    language-only matching and surfaces noise.
-4. **Re-run.** Once it has a remote + docs + tags, call `replen_match` again —
-   now it scopes to the project and matches against the real code. (Its embedding
-   lands on the next pipeline run; until then, tags carry the relevance.)
+4. **Embed it now (don't wait for the daily run).** A freshly-registered
+   project has no embedding yet, so matching falls back to language/tags only
+   (noise) until the next scheduled run. Trigger an immediate run with the
+   `replen_run` tool — it builds the project's summary + embedding + initial
+   candidates from the README/CLAUDE.md you just pushed. It's async: poll
+   `replen_status` until the phase reports inventory ready (~1–3 min). Tell the
+   user it's processing.
+5. **Re-run.** Once the run finishes, call `replen_match` again — now scoped
+   AND embedded, matching against the real code (a dev-tool that only shared the
+   project's language now scores low on cosine and gets floored out).
 
 Note on recording actions: always use the MCP tools — `replen_state` (star /
 hide / handoff), `replen_record_triage` (your verdict), `replen_set_tags` — for

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replen",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "description": "Make your AI coding tools smarter. One command, no API keys. Replen scouts the OSS firehose against your projects and surfaces drop-in libraries, ideas to port, and dead deps to swap — the match decision happens inside your AI tool's session on your subscription tokens. 1-3 actionable matches a month, by design.",
   "type": "module",
   "bin": {