replen 1.0.14 → 1.0.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -62,6 +62,13 @@ already onboarded (it already has capabilities/facets). Re-running is always
|
|
|
62
62
|
safe — pushing again just overwrites — so an interrupted sweep resumes cleanly by
|
|
63
63
|
re-running and skipping repos already done.
|
|
64
64
|
|
|
65
|
+
**"Done" includes a version report.** A repo that has capabilities but has
|
|
66
|
+
never reported versions is NOT done — give it the lightweight backfill pass:
|
|
67
|
+
skip the doc work and re-profiling entirely, just read the lockfile + runtime
|
|
68
|
+
pins and call `replen_set_versions` (Step 2e.4). This is how an existing
|
|
69
|
+
portfolio gets version-aware deadlines/security awareness after upgrading
|
|
70
|
+
Replen — a re-run backfills versions across every repo in minutes.
|
|
71
|
+
|
|
65
72
|
For each in-scope repo, do this contract:
|
|
66
73
|
|
|
67
74
|
### 2a. Read the code (not just the README)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "replen",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.15",
|
|
4
4
|
"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.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|