snipara-companion 4.2.4 → 5.0.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/CHANGELOG.md CHANGED
@@ -2,6 +2,12 @@
2
2
 
3
3
  Release notes for `snipara-companion`, newest first.
4
4
 
5
+ ## 5.0.0
6
+
7
+ - Remove the swarm and htask commands, --swarm-id flags, related doctor checks and routing hints, and featureTitle/workstreams handoff inputs.
8
+ - Forward memory sources, preserve workflow session boundaries and record outcomes; update commit guards and stuck-session handling.
9
+ - Migration: remove deleted commands, flags and handoff fields from scripts; use the retained workflow and collaboration commands.
10
+
5
11
  ## 4.2.4
6
12
 
7
13
  - Keep routine Team Sync handoffs and status reads continuity-only, preventing repeated handoffs from adding durable pending memories. Preserve explicit durable Why Capture and phase/final decisions.
package/README.md CHANGED
@@ -197,3 +197,27 @@ prepared dependency image described above. A documentation review alone does
197
197
  not qualify runtime behavior or publish a package.
198
198
 
199
199
  MIT licensed. See [package metadata](package.json) for repository and support links.
200
+
201
+ ### Quiet command defaults
202
+
203
+ `init --with-hooks` and `automations install` make Companion pre-tool hooks quiet
204
+ for Claude, Cursor and Codex bundles. `post-tool` emits a short rescue hint only
205
+ after repeated identical failed results or empty searches. `query` defaults to 800
206
+ source tokens; use `--max-tokens` and opt in with `--answer-pack` when needed.
207
+
208
+ `workflow start`, `workflow phase-start` and `workflow phase-commit` print compact
209
+ receipts and save the full payload to the returned detail path. Add `--detail` to
210
+ print it. JSON stdout stays machine-readable. FULL phase commits enforce
211
+ `workflow efficiency`, including cached input tokens. Unavailable usage coverage
212
+ blocks this enforcement check and does not establish zero usage.
213
+
214
+ `workflow start --plan-file plan.json` takes the plan's top-level id/goal by default.
215
+ `workflow resume` can use local state without hosted configuration.
216
+ `agent-context resolve --task "Implement change"` selects the configured/code agent
217
+ unless `--agent` overrides it. `memory list --limit 20 --offset 0 --json` provides
218
+ a bounded, paginated inventory instead of repeated recalls.
219
+
220
+ Pre-commit collaboration checks use the selected staged index, including linked
221
+ worktrees. Memory Guard passes docs-only changes and unavailable guidance; strict
222
+ destructive-action and contradiction confirmation rules remain in force. Failed
223
+ hook steps identify themselves on stderr. See [full reference](docs/FULL_REFERENCE.md).