@grifhinz/logics-manager 2.7.0 → 2.8.1

package/README.md

@@ -2,10 +2,10 @@
 
 [![CI](https://github.com/AlexAgo83/logics-manager/actions/workflows/ci.yml/badge.svg)](https://github.com/AlexAgo83/logics-manager/actions/workflows/ci.yml)
 [![License](https://img.shields.io/github/license/AlexAgo83/logics-manager)](LICENSE)
-![Version](https://img.shields.io/badge/version-v2.5.2-4C8BF5)
+![Version](https://img.shields.io/badge/version-v2.8.1-4C8BF5)
 ![VS Code](https://img.shields.io/badge/VS%20Code-1.86.0-007ACC?logo=visualstudiocode&logoColor=white)
 ![TypeScript](https://img.shields.io/badge/TypeScript-5.3.3-3178C6?logo=typescript&logoColor=white)
-![Vitest](https://img.shields.io/badge/Vitest-2.1.8-6E9F18?logo=vitest&logoColor=white)
+![Vitest](https://img.shields.io/badge/Vitest-4.1.2-6E9F18?logo=vitest&logoColor=white)
 
 `logics-manager` is a local workflow runtime for projects that keep their delivery memory in Markdown.
 
@@ -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,29 @@ 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.
+
+Viewer preferences are stored locally in the browser profile. Auto-refresh
+restores the interval chosen in the viewer unless the launch command explicitly
+sets `--refresh-interval`, in which case that launch value controls only the
+current session. The CDX status table has compact controls for column visibility
+and provider filtering; `BLOCK` and `CR` are hidden by default, and provider
+filtering defaults to all providers so newly discovered providers remain visible.
+When workspace inspection is available, the topbar shows an `Explorer` view
+before `Git`; it provides a read-only file tree and bounded previews for text,
+directories, images, oversized files, and unsupported binary files.
+
+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 +183,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:
 
@@ -554,20 +598,25 @@ If the current plugin version is already published, `logics-manager assist next-
 - Logics docs lint: `npm run lint:logics`
 - Logics workflow audit + docs lint: `npm run audit:logics`
 - Strict Logics governance audit: `npm run audit:logics:strict`
+- README metadata drift check: `npm run docs:check`
 - Local browser viewer smoke: `logics-manager view --port 0 --open`
 - Fast extension-focused local check: `npm run ci:fast`
 - Full CI-equivalent local check: `npm run ci:check`
 - Security audit policy gate: `npm run audit:ci`
 
-`npm run audit:logics` uses the default active-work profile. It blocks correctness and traceability failures, but reports early companion-doc polish such as missing overview Mermaid diagrams as warnings so drafting and agent handoffs can continue.
+`npm run audit:logics` uses the default active-work profile. It blocks correctness and traceability failures with a nonzero process exit, but reports early companion-doc polish such as missing overview Mermaid diagrams as warnings so drafting and agent handoffs can continue.
+
+`npm run audit:logics:strict` uses the strict governance profile. Use it before release or governance review when companion docs must be complete and warning-class findings should be resolved. Strict governance findings are advisory to active implementation until you choose the strict command; the standard audit remains the mandatory day-to-day gate.
+
+`logics-manager audit --format json` and `logics-manager lint --format json` expose `issue_count`, `warning_count`, `strict_count`, `finding_count`, `can_continue`, and `release_ready`. Agents should treat `issue_count > 0` or `can_continue: false` as blocking active work. Treat `release_ready: false` as a signal that cleanup remains before release-grade validation, not as a standard-audit process failure when there are warnings only.
 
-`npm run audit:logics:strict` uses the strict governance profile. Use it before release or governance review when companion docs must be complete and warning-class findings should be resolved.
+`npm run ci:check` mirrors the blocking repository CI contract, including Logics strict-status lint, request auto-close sync verification, workflow audit, README badge drift detection, Python tests, CLI smoke checks, TypeScript validation, extension tests, local viewer smoke, and VSIX packaging.
 
-`logics-manager audit --format json` and `logics-manager lint --format json` expose `issue_count`, `warning_count`, `strict_count`, `finding_count`, `can_continue`, and `release_ready`. Agents should treat `issue_count > 0` as blocking active work, and `release_ready: false` as a signal that cleanup remains before release-grade validation.
+`npm run audit:ci` enforces the repository audit policy locally. It runs `npm audit --json` against the configured npm registry, blocks new actionable vulnerabilities, and only allows the explicitly documented temporary exceptions tracked in the backlog. If the registry is unreachable, the command fails as `registry unavailable` rather than reporting a clean advisory state. `npm run package:ci` is local-only package validation and does not require registry access after dependencies are installed.
 
-`npm run ci:check` mirrors the blocking repository CI contract, including Logics strict-status lint, request auto-close sync verification, workflow audit, Python tests, CLI smoke checks, TypeScript validation, extension tests, and VSIX packaging.
+`npm run test:viewer-smoke` writes `artifacts/local-viewer-smoke/summary.json`. A localhost socket bind denial is recorded as an explicit skipped result. CI still has non-skipped coverage for the viewer path: Linux/macOS-capable environments exercise Chrome or the JSDOM fallback, while Windows CI runs a server/API smoke that proves the shell and `/api/items` path without launching a browser.
 
-`npm run audit:ci` enforces the repository audit policy locally. It blocks new actionable vulnerabilities and only allows the explicitly documented temporary exceptions tracked in the backlog.
+Oversized runtime, viewer, and test files are tracked through `logics/architecture/adr_020_split_the_oversized_plugin_and_workflow_surfaces_into_focused_modules.md`. The decomposition rule is correctness-first: extract pure helpers and API contracts before cosmetic file-size work, keep entrypoints thin, and cover each seam with targeted Python, Vitest, or smoke tests before moving on.
 
 CI runs compile, lint, tests, Logics docs lint, and VSIX packaging validation on every `push` and `pull_request` via `.github/workflows/ci.yml`.
 

package/VERSION

@@ -1 +1 @@
-2.7.0
+2.8.1