@brainervirus/workit-codex 1.0.9 → 1.0.10

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": "@brainervirus/workit-codex",
3
- "version": "1.0.9",
3
+ "version": "1.0.10",
4
4
  "private": false,
5
5
  "description": "Workit Codex CLI/desktop plugin — shared MCP transport, hooks, and fourteen method skills",
6
6
  "keywords": [
@@ -38,8 +38,8 @@
38
38
  "build": "bun scripts/build.ts"
39
39
  },
40
40
  "dependencies": {
41
- "@brainervirus/workit-core": "^1.0.9",
42
- "@brainervirus/workit-mcp": "^1.0.9"
41
+ "@brainervirus/workit-core": "^1.0.10",
42
+ "@brainervirus/workit-mcp": "^1.0.10"
43
43
  },
44
44
  "engines": {
45
45
  "node": ">=24"
@@ -22,9 +22,21 @@ selects requirements; do not wait for a rule that can only exist after assess.
22
22
  needed, owner, and next action. Keep the plan against the existing system.
23
23
  3. If policy separately requires a durable specification, record that behavior
24
24
  agreement; otherwise do not invent a spec. A plan without a spec is valid.
25
- 4. Update the shared task progress at meaningful boundaries. Reassess when facts,
25
+ 4. Present before asking: show durable artifacts as a complete digest plus the
26
+ exact path and inline plans as their content. Never ask the user to approve
27
+ something they have not seen, and keep the question to one short scoped
28
+ sentence.
29
+ 5. Execute an approved plan continuously: one atomic commit per task after its
30
+ checks pass, no "continue?" prompts. Stop only for a new product decision, a
31
+ failed safety or verification gate, a conflicting concurrent edit, or missing
32
+ authority.
33
+ 6. Record the plan's commit list once through the plan-scoped action approval
34
+ (`git.commit` with `plan_steps` and `plan_branch`) so each listed commit runs
35
+ without a new question; an unlisted message, a branch change, or any change to
36
+ the plan needs a fresh exact approval.
37
+ 7. Update the shared task progress at meaningful boundaries. Reassess when facts,
26
38
  dependencies, or scope change; preserve unresolved blockers and decisions.
27
- 5. On steering (new instructions mid-task): apply `workit-steer` — park state
39
+ 8. On steering (new instructions mid-task): apply `workit-steer` — park state
28
40
  verbatim, classify same-task / new-task / quick-question, handle, re-anchor.
29
41
 
30
42
  Use shared task/progress and evidence operations. Do not create a universal