@lacodda/rigger 0.13.0 → 0.14.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 +1 -1
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -153,7 +153,7 @@ A project is named after its directory - the name you call it by, not the one it
153
153
 
154
154
  ## Status
155
155
 
156
- v0.13.0 makes a sitting a thing the record knows. `session start` opens one and everything written until `session end` belongs to it - the assistant records as it always has, and the boundary is applied by the record rather than guessed from a window of days. `end` says what the sitting held, checks the two things the end-of-session ritual asks for by name, and can append a diary entry composed from the session's own sentences. As an assistant's `Stop` hook it needs no project name: it runs in the project, and the record knows every project by its path. The packet gained the line a returning session actually wants - where the last sitting stopped, and what has happened since. Before it: 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, and the cycle looked back on. The road to 1.0 is twenty-two small releases in seven blocks:
156
+ v0.14.0 turns the record back into notes. `rigger export` writes a project's hub - the plan, the changelog, the diary and the state block of its README - out of the database, and `import` reads them back: the circle closes with every counter at zero. Nineteen of the twenty hubs of a real line are reproduced byte for byte, which is the only way to know that generating them deletes nothing. A hub kept by hand is not overwritten because a command was typed: the first export refuses, `--check` says what would change, `--adopt` hands it over on purpose. `doctor --hubs` names a generated file somebody has edited since, and a project whose hub the record has never seen. The vision, the decision log's prose and the research notes are a person's writing and are never touched. Before it: 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
157
 
158
158
  | Block | Versions | What it delivers |
159
159
  | --- | --- | --- |
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@lacodda/rigger",
3
- "version": "0.13.0",
3
+ "version": "0.14.0",
4
4
  "rigger": {
5
- "binary": "v0.13.0"
5
+ "binary": "v0.14.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",