@lacodda/rigger 0.13.0 → 0.15.0
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.
- package/README.md +2 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -150,10 +150,11 @@ A project is named after its directory - the name you call it by, not the one it
|
|
|
150
150
|
- **The owner's inbox.** Every question waiting for your answer, across all projects, in one list.
|
|
151
151
|
- **A release calendar** with tiers and rhythm, derived from the same data - the plan is a week, the fact is a tag, and the gap between them is named.
|
|
152
152
|
- **Hubs as an export.** The markdown files you keep in Obsidian are generated from the database, not written by hand.
|
|
153
|
+
- **Thin project skills.** The file an assistant reads first is one template filled from the record, not sixteen kilobytes of ritual kept by hand per project.
|
|
153
154
|
|
|
154
155
|
## Status
|
|
155
156
|
|
|
156
|
-
v0.
|
|
157
|
+
v0.15.0 makes moving a project onto rigger two commands. `rigger adopt <dir> --hubs <dir>` walks a directory of checkouts, records each one that has a hub, imports the hub and reads the tags - the three commands a project used to take, once for a whole line, and the command to run again when the line has grown. `rigger skill <project> --install` writes the project's skill from one template and the record, so a change to the ritual is one edit rather than seventeen; a line writes its own template, a project keeps what only it can say in a file of its hub, and a skill somebody wrote by hand is not replaced until asked. Found on the way: a second import of a hub put the hub's release date back over the one the tag proved, and every sync after it reported the version shipped anew - a fact from git now stays. Before it, v0.14.0 turned the record back into notes: `rigger export` writes a project's hub out of the database and `import` reads it back, nineteen of the twenty hubs of a real line byte for byte, and a hub kept by hand is not overwritten until `--adopt` hands it over. Before that: the database, `import`, the context packet, the `mcp` server, facts from git, a chronicle that writes itself, search, the owner's inbox and digest, the release calendar, the week as a brief and a shopfront queue, the cycle looked back on, and sittings the record knows. The road to 1.0 is twenty-two small releases in seven blocks:
|
|
157
158
|
|
|
158
159
|
| Block | Versions | What it delivers |
|
|
159
160
|
| --- | --- | --- |
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lacodda/rigger",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.15.0",
|
|
4
4
|
"rigger": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.15.0"
|
|
6
6
|
},
|
|
7
7
|
"description": "One seat for all your projects and tasks: a local record of what is done, what is next and when it ships - read by you and your coding assistant",
|
|
8
8
|
"license": "MIT",
|