@lacodda/rigger 0.9.0 → 0.10.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 +15 -2
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -126,6 +126,19 @@ Asked by several projects - one answer settles each group:
126
126
  Place in the release calendar — alpha, beta, gamma
127
127
  ```
128
128
 
129
+ And it lays the releases out over the weeks, comparing what you aimed at with what the tags say happened:
130
+
131
+ ```console
132
+ $ rigger calendar --from 2026-W37 --weeks 5
133
+ 2026-W37 2026-W38 2026-W39 2026-W40 2026-W41
134
+ sample *v0.1.0 >v0.2.0 ·v0.3.0 A
135
+ widget +v0.1.0 ·v0.2.0 B
136
+
137
+ + shipped as planned > slipped ! overdue * unplanned · planned
138
+
139
+ sample v0.2.0 — aimed at 2026-W37, 2 weeks late
140
+ ```
141
+
129
142
  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`.
130
143
 
131
144
  ## What it will do
@@ -135,12 +148,12 @@ A project is named after its directory - the name you call it by, not the one it
135
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.
136
149
  - **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.
137
150
  - **The owner's inbox.** Every question waiting for your answer, across all projects, in one list.
138
- - **A release calendar** with tiers and rhythm, derived from the same data.
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.
139
152
  - **Hubs as an export.** The markdown files you keep in Obsidian are generated from the database, not written by hand.
140
153
 
141
154
  ## Status
142
155
 
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:
156
+ v0.10.0 puts the release calendar in the database. A project gets a tier and a rhythm, a version gets the week it is aimed at, and `calendar` lays the two against the tags: what shipped on time, what slipped and by how far, what is past its week with no tag at all. `next` reads one week in full, and names the projects that have quietly stopped releasing at the pace their tier asks. Before it: the database, `import`, the context packet, the `mcp` server, facts from git, a chronicle that writes itself, search, and the owner's inbox and digest. The road to 1.0 is twenty-two small releases in seven blocks:
144
157
 
145
158
  | Block | Versions | What it delivers |
146
159
  | --- | --- | --- |
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@lacodda/rigger",
3
- "version": "0.9.0",
3
+ "version": "0.10.0",
4
4
  "rigger": {
5
- "binary": "v0.9.0"
5
+ "binary": "v0.10.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",