@lacodda/rigger 0.20.0 → 0.21.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 +40 -22
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -77,11 +77,37 @@ $ rigger open sample
|
|
|
77
77
|
Starting claude in C:\dev\sample with the packet for sample
|
|
78
78
|
```
|
|
79
79
|
|
|
80
|
-
|
|
80
|
+
The MCP server is how the assistant reads that packet and writes back to the record as it works - decisions, findings and pitfalls become events, not lines in a transcript nobody opens again. The installer registers it, along with the hook that closes a sitting when the assistant stops:
|
|
81
81
|
|
|
82
82
|
```console
|
|
83
|
-
$
|
|
84
|
-
|
|
83
|
+
$ irm https://raw.githubusercontent.com/lacodda/rigger/main/tools/install.ps1 | iex
|
|
84
|
+
...
|
|
85
|
+
Registered the rigger MCP server with claude.
|
|
86
|
+
Added the Stop hook: a sitting now closes itself.
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
And for you, rather than for the assistant, the project's own screen - what it is, where it stands, what it has written down:
|
|
90
|
+
|
|
91
|
+
```console
|
|
92
|
+
$ rigger show sample
|
|
93
|
+
sample
|
|
94
|
+
A sample product
|
|
95
|
+
|
|
96
|
+
path C:\dev\sample
|
|
97
|
+
gate cargo fmt --all --check && cargo clippy --all-targets -- -D warnings && cargo test
|
|
98
|
+
|
|
99
|
+
Last shipped v0.2.0 on 2026-09-03, 2 commits since
|
|
100
|
+
1 versions planned, 2 tasks open
|
|
101
|
+
|
|
102
|
+
Current stage: v0.3.0 · Search
|
|
103
|
+
> full-text index
|
|
104
|
+
a query language
|
|
105
|
+
|
|
106
|
+
Written down:
|
|
107
|
+
vision Vision of sample 2026-09-12 rigger doc show sample vision
|
|
108
|
+
|
|
109
|
+
Next step
|
|
110
|
+
Ship the importer next.
|
|
85
111
|
```
|
|
86
112
|
|
|
87
113
|
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:
|
|
@@ -141,32 +167,24 @@ sample v0.2.0 — aimed at 2026-W37, 2 weeks late
|
|
|
141
167
|
|
|
142
168
|
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`.
|
|
143
169
|
|
|
144
|
-
## What
|
|
170
|
+
## What you get
|
|
145
171
|
|
|
146
|
-
- **Projects, versions, tasks, sessions.** A project has a map of versions; a version is a stage that ends in a tag; a task is a unit of work inside a version (at home) or a ticket across several projects and branches (at work).
|
|
172
|
+
- **Projects, versions, tasks, sessions.** A project has a map of versions; a version is a stage that ends in a tag; a task is a unit of work inside a version (at home) or a ticket across several projects and branches (at work).
|
|
147
173
|
- **Facts from git.** A pushed tag means the version shipped, on that date. Commits since the last tag are activity. The plan cannot claim more than git confirms.
|
|
148
|
-
- **A context packet instead of a hub.** `rigger context <project>` prints what the assistant needs to start - state, current stage, open questions, last events, next step - within a fixed token budget.
|
|
149
174
|
- **An MCP server as the assistant's only pen.** Decisions, findings, pitfalls, changes and the next step are recorded as events through tools, not by editing markdown.
|
|
150
|
-
- **The owner's inbox
|
|
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.
|
|
175
|
+
- **The owner's inbox and a release calendar**, both derived from the same record rather than kept by hand.
|
|
152
176
|
- **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
|
|
177
|
+
- **Thin project skills.** The file an assistant reads first is one template filled from the record.
|
|
154
178
|
|
|
155
179
|
## Status
|
|
156
180
|
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
| Facts | 0.6 - 0.8 | tags and commits as truth, changes read from commits, search and "why" |
|
|
163
|
-
| Owner | 0.9 - 0.12 | inbox and digest, the release calendar, the Monday brief, retro |
|
|
164
|
-
| Sessions | 0.13 - 0.14 | sessions with an end-of-session journal, hubs exported from the database |
|
|
165
|
-
| Line | 0.15 - 0.16 | thin project skills, every project of a line recorded at once |
|
|
166
|
-
| Tasks | 0.17 - 0.21 | the ticket profile, task cards, activity from branches, incoming material, snooze and handoff |
|
|
167
|
-
| Stabilisation | 0.22 | `--json` everywhere, docs, a signed binary where needed |
|
|
181
|
+
The record, the context packet, the MCP server, facts from git, the owner's
|
|
182
|
+
inbox, the release calendar and thin project skills are in daily use across
|
|
183
|
+
the whole line. The rules a line and a project state about themselves, and
|
|
184
|
+
the gate a project runs, are documents in the record rather than pasted into
|
|
185
|
+
every project's skill.
|
|
168
186
|
|
|
169
|
-
|
|
187
|
+
Released versions and what landed in each: [CHANGELOG](https://github.com/lacodda/rigger/blob/main/CHANGELOG.md).
|
|
170
188
|
|
|
171
189
|
## Install
|
|
172
190
|
|
|
@@ -191,4 +209,4 @@ https://lacodda.github.io/rigger/ - getting started, concepts, and a reference p
|
|
|
191
209
|
|
|
192
210
|
## License
|
|
193
211
|
|
|
194
|
-
MIT
|
|
212
|
+
MIT (c) [Kirill Lakhtachev](https://lacodda.com)
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lacodda/rigger",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.21.0",
|
|
4
4
|
"rigger": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.21.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",
|