@lacodda/rigger 0.18.0 → 0.20.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 +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -154,7 +154,7 @@ A project is named after its directory - the name you call it by, not the one it
|
|
|
154
154
|
|
|
155
155
|
## Status
|
|
156
156
|
|
|
157
|
-
v0.18.0
|
|
157
|
+
v0.20.0 puts the rules of the work into the record and makes the gate something the record witnessed. The rituals of a line and the ones a project states about itself were pasted into every project skill - seventeen copies of nearly the same text, about 390 KB read before every session, and a change to them was seventeen edits or, more often, one edit and sixteen skills quietly out of date. They are documents now: the line's hang off a project named after the profile, a project's off the project, and `rigger rules [<project>]` prints both. The skill that reads them is 1.3 KB and says three things - `context`, `rules`, `session end`. A project states its gate once (`rigger project set <project> --gate "..."`), the packet prints it on one line, and `rigger gate <project>` runs it: every run is kept with its verdict and how long it took, red exits non-zero so a hook can act on it, and `session end` names a gate this sitting left red. `import --answers <file>` reads the questionnaire an owner fills in before a plan is reworked - a fork becomes a decision naming the option taken **and the ones it beat**, an idea ticked becomes a wish, one left unticked a decision - so the page stops being the only place those choices live. The wishes file is read in once and then watched: `doctor` says when something has been left in it, since nothing reads it at every session any more. Found on the way, and fixed: a generated hub read back struck versions the export had simply scrolled past, and a hub directory that was not there was read as an empty one - each of which told the record to strike every stage of a project while exiting zero. Before it, v0.19.0 moves a project's handwritten texts into the record. The vision, the rituals a project states about itself, the preamble of its decisions journal and every research note used to live only as files in a hub - the reason a hub had to exist at all - and `rigger doc list|show|add|edit|remove` now keeps them where everything else is kept. `import` takes them in, `export --docs` writes them back out as an optional cache, and over MCP `doc_show` and `doc_write` let an assistant write a research note or correct a vision into the record rather than into a file somebody has to remember to import. Editing goes through `$EDITOR` - scheda when it is installed, since it takes the `--wait` an editor has to - and a new document starts from the questions its kind exists to answer, from a skeleton `doc template --write` makes yours. The record being one file made its insurance the first thing to build: `backup --keep` rotates the copies, `doctor` says how old the newest is, and `session end` takes one when the newest predates today. `export --check` now shows the lines that would change rather than only the names of the files, because the question it answers is whether something written by hand is about to be thrown away. Before it, v0.18.0 brought the desk its cards. A card is a ticket in the record - a key, the aliases it went by before it moved, a summary, the repositories it is worked in with a branch in each, and everything written against it. `rigger task find` takes a task exactly as it was handed over - an id, a title, two case numbers - and says whether to take a card, ask, or make a new one, with the matching a script ran a desk on for a year: an id is certain, a title is compared by bigrams and by the words it shares, a case number lifts a card, and a number mentioned only in what was written against another card is the trail of a task that moved. `task new`, `open`, `active`, `close`, `link`, `rename`, `note` and `context` are the card's day; over MCP, `task_find`, `task_context` and a `task` argument on every recording tool. Before it, v0.17.0 gave rigger a second way of working. A profile is a record of its own - its database, its roots, its way of naming work - and every command reads the current one without being told: `line` for the products of a line, `tickets` for the desk at work, where the unit is an id worked on branches across several repositories. The config is a TOML file a person edits; `profile add`, `set` and `use` write it. The database from before profiles is moved into the default profile on first use, with the old file kept. A task's status is a word from a vocabulary now - new, active, waiting-handoff, frozen, done - given by `task status` or `set_task_status` over MCP and shown in the packet; a hub's empty box means "not done" and no longer resets it. This is the release that changes the shape of the data before 1.0; the schema migrates itself, with a copy of the database taken first. Before it, v0.16.0 put a whole line through rigger. Every hub of a real line is now written from the record and every project skill is generated, and what that took was the other half of reading a hub: a hub kept by hand for a month is not the hub the first import read. A task struck from the plan is dropped rather than kept as open work for ever, a stage renumbered by hand leaves no ghost, a question the owner struck is withdrawn, a version known only from a tag is a fact rather than an empty changelog entry, and a diary entry read once without its date is one entry. A hub the record writes keeps growing without a hand: `session end` leaves its diary entry in the record, and `note --kind state` (`record_state` over MCP) puts a line at the top of the README's state block. `doctor --hubs` names the hubs still kept by hand. Before it, v0.15.0 made 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:
|
|
158
158
|
|
|
159
159
|
| Block | Versions | What it delivers |
|
|
160
160
|
| --- | --- | --- |
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lacodda/rigger",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.20.0",
|
|
4
4
|
"rigger": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.20.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",
|