@lacodda/rigger 0.33.0 → 0.35.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.
Files changed (2) hide show
  1. package/README.md +14 -13
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -11,18 +11,17 @@
11
11
 
12
12
  ## Why
13
13
 
14
- Run more than a handful of projects and the record of them scatters: a plan in one file, a changelog in another, a session log the assistant writes for itself, a release calendar kept by hand. You stop reading it, because prose cannot be filtered or summed up across projects. The assistant reads it every session at full price. And what actually shipped lives in git, where nobody looks.
14
+ Run more than a handful of projects and the record of them scatters: a plan in one file, a changelog in another, a session log the assistant writes for itself, a list of what is next kept by hand. You stop reading it, because prose cannot be filtered or summed up across projects. The assistant reads it every session at full price. And what actually shipped lives in git, where nobody looks.
15
15
 
16
- rigger keeps the record as data, in one local SQLite file, and derives the rest from it: the packet an assistant starts from, the questions waiting for you, the calendar of what ships when - with git, not the plan, deciding what shipped.
16
+ rigger keeps the record as data, in one local SQLite file, and derives the rest from it: the packet an assistant starts from, the questions waiting for you, the order projects come round in - with git, not the plan, deciding what shipped.
17
17
 
18
18
  ## A day with rigger
19
19
 
20
20
  Plan a stage, and write down what was decided and what only you can answer:
21
21
 
22
22
  ```console
23
- $ rigger version add sample v0.1.0 --title "First light" --task "read a sheet" --task "write the report" --week 2026-W43
23
+ $ rigger version add sample v0.1.0 --title "First light" --task "read a sheet" --task "write the report"
24
24
  Added v0.1.0 to sample, with 2 tasks
25
- aimed at 2026-W43 - the week of 2026-10-23
26
25
 
27
26
  $ rigger note sample "Which file formats come first?" --kind question
28
27
  Asked the owner about sample; it waits in the inbox until answered
@@ -96,17 +95,18 @@ the work from the start of the record
96
95
  2026-10-07 change feat: write the report
97
96
  ```
98
97
 
99
- With nothing aimed at the week, it says which project to take up next, and why - here, a change landed from a neighbour's sitting that no sitting of its own has seen:
98
+ With a line of products, one command is the whole routine: it works out which project comes next, and starts your assistant on it. A turn left unfinished comes back before anything new begins:
100
99
 
101
100
  ```console
102
- $ rigger pick
101
+ $ rigger go
103
102
  Work on widget v0.2.0 · Plugins
104
- 1 change since the last release that no finished sitting has seen: feat(plugin): load plugins from a folder
105
- 1 question waits on the owner · 1 order from neighbours
103
+ not finished: 1 change since the last release
104
+ Starting claude in C:\dev\widget
106
105
 
107
- Then, by the same rule
108
- gadget v1.0.0 last sitting 2026-10-27
109
- sample v0.2.0 last sitting 2026-10-27
106
+ ...the session...
107
+
108
+ widget v0.2.0 went out.
109
+ Next: gadget v1.0.0 - `rigger go`
110
110
  ```
111
111
 
112
112
  The whole first week, command by command: [Your first week](https://lacodda.github.io/rigger/guides/first-week/).
@@ -116,13 +116,14 @@ The whole first week, command by command: [Your first week](https://lacodda.gith
116
116
  - **Projects, versions, tasks, sessions.** A version is a stage that ends in a tag; a task is work inside it - or, at work, a ticket across several repositories and branches. A project needs no repository: a folder of texts is worked on like any product, and git is never asked about it. A project taken out of the work is retired: it leaves every screen that looks ahead, and its history stays readable.
117
117
  - **Facts from git.** A tag means the version shipped, on that date; the plan cannot claim more than git confirms, and `doctor` names where they part.
118
118
  - **An MCP server as the assistant's only pen**, and a context packet held to a token budget.
119
- - **Your inbox, a weekly brief, a release calendar and a pick** - which project to work on now, and the one reason it comes first - derived from the same record rather than kept by hand.
119
+ - **`rigger go`** - which project to work on now, the one reason it comes first, and your assistant started on it; nothing new starts while a tag is not out.
120
+ - **Your inbox and a queue with weights** - `rigger queue` puts every project in the order it gets a turn, `rigger priority` sets how often one comes round - derived from the same record rather than kept by hand.
120
121
  - **`--json` on every command**, each field held by a test to its reference page.
121
122
  - **Hubs as an export.** Markdown notes are written from the record and kept that way: the end of each sitting writes again what nobody touched, and `doctor --hubs` names what somebody did. A hand-kept hub [moves into the record](https://lacodda.github.io/rigger/guides/from-a-hub/) in one command, every note in it.
122
123
 
123
124
  ## Status
124
125
 
125
- In daily use across a line of eighteen products and a library of texts, with one retired: the record, the packet held to its budget on the real record, the MCP server, facts from git, the owner's screens and the pick of what comes next, task cards at work, hubs kept as a view of a record that holds every file in them, and a JSON contract for every command ahead of 1.0. Released versions and what landed in each: [CHANGELOG](https://github.com/lacodda/rigger/blob/main/CHANGELOG.md).
126
+ In daily use across a line of eighteen products and a library of texts, ahead of 1.0: one command takes the next project to a release, and every field of `--json` is held by a test. What landed in each release: [CHANGELOG](https://github.com/lacodda/rigger/blob/main/CHANGELOG.md).
126
127
 
127
128
  ## Install
128
129
 
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@lacodda/rigger",
3
- "version": "0.33.0",
3
+ "version": "0.35.0",
4
4
  "rigger": {
5
- "binary": "v0.33.0"
5
+ "binary": "v0.35.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",