@workscribe/cli 3.0.1 → 3.2.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@workscribe/cli",
3
- "version": "3.0.1",
3
+ "version": "3.2.0",
4
4
  "description": "Passive developer work journal — automatic terminal activity summaries",
5
5
  "homepage": "https://workscribe.co",
6
6
  "repository": {
@@ -37,7 +37,7 @@ Follow [references/summary-format.md](references/summary-format.md). In short:
37
37
 
38
38
  - Up to **7 bullets**, most important first: what was built, fixed, shipped or decided.
39
39
  - Build bullets from `commits` (cite the short hash, e.g. `(a1b2c3d)`), test and build results (`exitCode` 0 vs non-zero; `null` means unknown, never "failed"), `notes` (always include them), and `hint`s on unclassified events.
40
- - Describe outcomes, not commands or tools. Never name the AI tool used. Don't invent anything the data doesn't show.
40
+ - Describe outcomes, not commands or tools. Don't invent anything the data doesn't show.
41
41
  - Don't name the projects worked `alongside` — Workscribe adds that line under each saved summary itself. Never repeat their work.
42
42
  - Skip a session with nothing notable rather than padding it.
43
43