@grifhinz/logics-manager 2.7.0 → 2.8.0

package/README.md

@@ -111,14 +111,36 @@ Useful commands:
 
 ```bash
 logics-manager flow list
+logics-manager flow show req_001_example
 logics-manager flow promote request-to-backlog req_001_example
 logics-manager flow promote backlog-to-task item_001_example
 logics-manager flow finish task task_001_example
-logics-manager sync context-pack req_001_example --format json
+logics-manager sync read-doc req_001_example --max-chars 6000
+logics-manager sync context-pack req_001_example task_001_example --format json
+logics-manager sync refresh-mermaid-signatures task_001_example
+logics-manager flow closeout task_001_example --validation-command "pytest tests" --validation-result passed --lint --audit
 logics-manager view --open
 logics-manager view --focus req_001_example --read --open
 ```
 
+### Agent workflow cookbook
+
+For bounded workflow inspection, prefer `logics-manager flow show <ref>` or
+`logics-manager sync read-doc <ref>` before reading Markdown directly. Both
+commands include useful body content in text mode and keep JSON output available
+with `--format json`.
+
+For linked context, use `logics-manager sync context-pack <refs...>` with a
+small set of request, backlog, or task refs. The command deduplicates each
+ref's direct neighborhood and supports `--mode diff-first` when recent changes
+matter.
+
+For targeted hygiene repair, use
+`logics-manager sync refresh-mermaid-signatures <refs-or-paths...>` or
+`--changed-only` to avoid unrelated workflow diffs. For end-of-delivery cleanup,
+use `logics-manager flow closeout <task>` with validation evidence plus
+`--lint --audit` when you want the command to run the gates before reporting.
+
 ### Local Browser Viewer
 
 Use the CLI viewer when you want to inspect the Logics corpus outside VS Code:
@@ -127,7 +149,19 @@ Use the CLI viewer when you want to inspect the Logics corpus outside VS Code:
 logics-manager view --open
 ```
 
-The viewer starts a localhost-only, read-only browser UI on `127.0.0.1:8765` by default. It shows the same workflow board/list experience as the extension, with search, filters, document previews, corpus insights, lint/audit health, Mermaid rendering, auto-refresh, and an edit shortcut that opens the selected Markdown file in the system editor.
+The viewer starts a localhost-only browser UI on `127.0.0.1:8765` by default. It shows the same workflow board/list experience as the extension, with search, filters, document previews, corpus insights, lint/audit health, Mermaid rendering, auto-refresh, and an edit shortcut that opens the selected Markdown file in the system editor.
+
+The CDX missions panel includes guarded workflows for audits, release reviews,
+turning a free-form wish into a structured Logics request, preparing a corpus
+plan, and preparing a guarded pre-release from an editable `vX.X.X` version.
+For full-audit and release-review, the main write checkbox allows CDX to write
+the mission corpus/report; direct repository fixes require the separate `Fix
+directly` checkbox and skip the corpus/report artifact. Write-capable missions
+must report changed files and validation evidence. The corpus-ready mission asks
+CDX for allowed corpus actions first; the corpus is updated when those returned
+actions are applied explicitly. The pre-release mission may update release
+metadata and create the matching changelog, but must not tag, push, publish,
+upload assets, or create a GitHub release.
 
 Useful options:
 
@@ -139,7 +173,7 @@ logics-manager view --focus logics/tasks/task_001_example.md --read --open
 logics-manager view --no-open
 ```
 
-Use `--port 0` when the default port is already taken. The viewer is intentionally read-only; use the canonical CLI commands such as `flow promote`, `flow finish`, `lint`, and `audit` for workflow mutations.
+Use `--port 0` when the default port is already taken. Direct Logics workflow mutations still route through canonical CLI commands such as `flow promote`, `flow finish`, `lint`, and `audit`; guided CDX missions may edit repository files only when the mission's file-write checkbox is enabled.
 
 Focused viewer links can point directly at a corpus item:
 

package/VERSION

@@ -1 +1 @@
-2.7.0
+2.8.0