@lacodda/rigger 0.5.0 → 0.7.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 +15 -3
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -19,7 +19,7 @@ rigger keeps the record as data, in a local SQLite file, and derives everything
|
|
|
19
19
|
|
|
20
20
|
```console
|
|
21
21
|
$ rigger init
|
|
22
|
-
Created C:\Users\you\AppData\Local\lacodda\rigger\data\rigger.db (schema version
|
|
22
|
+
Created C:\Users\you\AppData\Local\lacodda\rigger\data\rigger.db (schema version 3)
|
|
23
23
|
Next: rigger project add <path>
|
|
24
24
|
|
|
25
25
|
$ rigger project add C:\dev\sample
|
|
@@ -35,7 +35,7 @@ sample:
|
|
|
35
35
|
|
|
36
36
|
$ rigger doctor
|
|
37
37
|
database: C:\Users\you\AppData\Local\lacodda\rigger\data\rigger.db
|
|
38
|
-
schema: version
|
|
38
|
+
schema: version 3
|
|
39
39
|
projects: 1
|
|
40
40
|
versions: 3
|
|
41
41
|
tasks: 2
|
|
@@ -84,6 +84,18 @@ $ claude mcp add rigger -- rigger mcp
|
|
|
84
84
|
Added stdio MCP server rigger with command: rigger mcp to local config
|
|
85
85
|
```
|
|
86
86
|
|
|
87
|
+
What actually shipped is not taken on trust. `sync` reads the repository's tags and commits in-process and writes what they prove; where the plan says a version shipped and no tag agrees, the disagreement is reported rather than corrected:
|
|
88
|
+
|
|
89
|
+
```console
|
|
90
|
+
$ rigger sync claimed
|
|
91
|
+
claimed:
|
|
92
|
+
shipped v0.1.0 on 2026-09-04
|
|
93
|
+
read 2 changes from commit messages
|
|
94
|
+
no tag v0.2.0 is closed in the plan
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
Those changes come out of the commit messages themselves - `feat`, `fix` and anything breaking, dated by the commit rather than by the sync - so the chronicle stays current whether or not anyone opens a session.
|
|
98
|
+
|
|
87
99
|
A project is named after its directory - the name you call it by, not the one its manifest publishes under - and `--name` overrides. Every command that shows facts also prints them with `--json`.
|
|
88
100
|
|
|
89
101
|
## What it will do
|
|
@@ -98,7 +110,7 @@ A project is named after its directory - the name you call it by, not the one it
|
|
|
98
110
|
|
|
99
111
|
## Status
|
|
100
112
|
|
|
101
|
-
v0.
|
|
113
|
+
v0.7.0 keeps the record current without a session: `sync` reads changes out of commit messages, so the chronicle writes itself, and `resolve` finally closes a question or a wish. Before them: the database, projects, `import`, `backup`, `context`, `note`, `open`, the `mcp` server and facts from git. The road to 1.0 is twenty-two small releases in seven blocks:
|
|
102
114
|
|
|
103
115
|
| Block | Versions | What it delivers |
|
|
104
116
|
| --- | --- | --- |
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lacodda/rigger",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.7.0",
|
|
4
4
|
"rigger": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.7.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",
|