@lacodda/rigger 0.7.1 → 0.9.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 +33 -3
  2. 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 3)
22
+ Created C:\Users\you\AppData\Local\lacodda\rigger\data\rigger.db (schema version 4)
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 3
38
+ schema: version 4
39
39
  projects: 1
40
40
  versions: 3
41
41
  tasks: 2
@@ -96,6 +96,36 @@ claimed:
96
96
 
97
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
98
 
99
+ Once there is a record, it answers questions - which is the point of keeping it as data:
100
+
101
+ ```console
102
+ $ rigger find budget
103
+ sample 2026-09-04 decision The budget is a gate, not a suggestion.
104
+ sample 2026-09-04 pitfall A wide window hides what the budget dropped.
105
+
106
+ $ rigger why sample v0.3.0
107
+ v0.3.0 — shipped 2026-09-04
108
+ the work after v0.2.0 (2026-09-04)
109
+
110
+ 2026-09-04 decision The budget is a gate, not a suggestion.
111
+ 2026-09-04 pitfall A wide window hides what the budget dropped.
112
+ 2026-09-04 change feat: rank what a person wrote above a commit
113
+ ```
114
+
115
+ And it answers the question the notes never could - what is waiting on you, across everything at once:
116
+
117
+ ```console
118
+ $ rigger inbox
119
+ 6 questions in 3 projects
120
+
121
+ alpha [ 1] 2026-09-04 Place in the release calendar
122
+ [ 2] 2026-09-04 Sign the binaries?
123
+ beta [ 3] 2026-09-04 Place in the release calendar
124
+
125
+ Asked by several projects - one answer settles each group:
126
+ Place in the release calendar — alpha, beta, gamma
127
+ ```
128
+
99
129
  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`.
100
130
 
101
131
  ## What it will do
@@ -110,7 +140,7 @@ A project is named after its directory - the name you call it by, not the one it
110
140
 
111
141
  ## Status
112
142
 
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:
143
+ v0.9.0 opens the first two screens meant for you rather than the assistant: `inbox` gathers every question waiting on your answer across all projects - grouping the ones several projects are asking at once - and `digest` says what moved, five lines per project. Before them: the database, `import`, the context packet, the `mcp` server, facts from git, a chronicle that writes itself, and search. The road to 1.0 is twenty-two small releases in seven blocks:
114
144
 
115
145
  | Block | Versions | What it delivers |
116
146
  | --- | --- | --- |
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@lacodda/rigger",
3
- "version": "0.7.1",
3
+ "version": "0.9.0",
4
4
  "rigger": {
5
- "binary": "v0.7.1"
5
+ "binary": "v0.9.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",