@cogit/cli 0.26.0 → 0.28.1

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.
@@ -15,7 +15,7 @@ import {
15
15
  uninstallGitHooks,
16
16
  withHookBlock,
17
17
  withoutHookBlock
18
- } from "./chunk-BTRHGTLA.js";
18
+ } from "./chunk-FGAPKAMD.js";
19
19
  export {
20
20
  BLOCK_END,
21
21
  BLOCK_START,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cogit/cli",
3
- "version": "0.26.0",
3
+ "version": "0.28.1",
4
4
  "description": "Git remembers what changed. cogit remembers why.",
5
5
  "license": "MIT",
6
6
  "keywords": [
@@ -15,7 +15,7 @@ The current record (`cogit session show`):
15
15
  - `initialized: false`: reply exactly "cogit is not set up in this project yet; run
16
16
  `npx @cogit/cli init` here first." and stop.
17
17
  - `sessionError`: quote it and stop; never write over the record.
18
- - Nothing new or changed (`newMessages` empty): reply "Lineage is up to date." and stop.
18
+ - Nothing new or changed (`newMessages` empty): reply "cogit is up to date." and stop.
19
19
 
20
20
  ## Look something up
21
21
 
@@ -36,8 +36,11 @@ One JSON object:
36
36
 
37
37
  - `sessionId`: always `"${CLAUDE_SESSION_ID}"`.
38
38
  - `title`: a few words; on the first write or when the focus changed.
39
- - `status`: replaces all four fields, so send each: `goal` (one sentence), `done`, `pending`
40
- (`{ "text", "needsUser": true }` when it waits on the user), `next` (concrete step).
39
+ - `status`: replaces all four fields, so send each: `goal` (one sentence), `done` (what
40
+ finished, as outcomes), `pending` (the work still open, one item per ask in the user's
41
+ words — never a checklist of commands; a release and the restart it needs are one item, and
42
+ a step that serves nothing is dropped; `{ "text", "needsUser": true }` when it waits on the
43
+ user), `next` (concrete step).
41
44
  - `nodes`: only new nodes or changed fields; the rest is kept.
42
45
 
43
46
  ## One node per user message
@@ -154,4 +157,4 @@ personal data, file contents or command output.
154
157
  2. `node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" session write -C "<dir from the record>" --file "<inbox path>" --consume`
155
158
 
156
159
  If it fails, fix the JSON according to the error and run it again. Then reply with one short
157
- line, e.g. "Lineage updated (3 nodes)"; never repeat the JSON.
160
+ line, e.g. "cogit updated (3 nodes)"; never repeat the JSON.