v0.8.2 — Four-Tool Integration

MAWF v0.8.2 — Four-Tool Integration

Selective integration of write-notes-like-deepseek + CE Compound (durable knowledge), Trellis Card (desktop companion + transport seam), and Archify (locked diagram engine) into MAWF.

New capabilities

• Knowledge store (docs/knowledge/): dual-track Decision (write-notes-compatible header format) + Solution (CE-style YAML frontmatter + evidence-chain sections); CAS writes, advisory locks, sidecar provenance (lastVerified only moves on explicit verification), sealed+immutable archive, writer CLI (mawf knowledge get|create|update|archive|verify-doc), explainable CJK/latin retrieval with strict budgets, legacy→default migrator with dry-run + rollback
• Four-host skills: mawf-decision / mawf-compound / mawf-knowledge / mawf-archify (installed via mawf install)
• Bridge + SSH transport: typed read-only NDJSON protocol (no exec, no arbitrary file read), fixed MAWF-owned remote entry with strict charset gate, install-helper remote records, machineId-canonical workspace identity, stdin-hello workspace selection — verified live over a real SSH link (handshake/tasks/CJK-retrieval/tmux metadata/escape-rejection)
• Companion board service: loopback token-authed /rpc serving the vendored Notes Board with a workspace datasource (board stays byte-identical at rest)
• Archify adapter: raw-argv pass-through to the locked engine (commit-pinned; npm "archify" is an unrelated package), artifact registry (rebuildable), preview-state sidecar; visual-check verified with real Chromium
• Component manager: locked registry, digest-verified offline install, closure/entry validation, doctor-based promotion, rollback
• Observer: fail-open session hooks with precise ownership (never touches cost/permission guards)

Verification

• Suite: 534 tests / 524 pass / 0 fail / 10 skipped at tag commit
• CI: ubuntu Node 22/24 green at tag commit; Windows green at a7cb7a1/7c6057f, queued at release time due to GitHub runner congestion (no failures anywhere)
• A20 packed-install gate: PASS (tarball → isolated install → installed-CLI smoke)

Artifact

• multi-agents-workflow-0.8.2.tgz — SHA-256 0bfadd8ac2a014441ad2fd3675bbaf6fc125cbb4cca027b17f88f1f485b98e5b
• npm publish pending (owner will run npm publish from the tagged commit)

Notes

• PR #38 (base main) remains open; the tag points at the integration branch head per owner instruction
• write-notes/trellis-card upstreams lack LICENSE files; use is owner-authorized pending upstream license text (provenance + notices shipped)

v0.8.1 — Trellis lifecycle integration

Changed

• MAWF now chains Trellis lifecycle operations explicitly: mawf update runs
  trellis update, while mawf upgrade runs trellis upgrade and the
  applicable Trellis project update.
• mawf uninstall remains MAWF-only. It does not invoke Trellis uninstall and
  preserves Trellis-owned files.
• The fixed-cutoff compatibility ledger covers the five supported upstream
  hosts from after mawf v0.7.2 through 2026-09-12T23:59:59Z. No newly
  released non-TUI host contract in that window required a MAWF code
  adaptation.

Fixed

• Interactive mawf init preserves Trellis's native TUI when stdin and stdout
  are terminals: terminal streams are inherited and prompt-skipping and
  platform-selection flags are omitted. Redirected runs remain deterministic
  with -y, host-aware flags, and captured diagnostics.
• Lifecycle recovery remains deterministic after partial Trellis failures, and
  MAWF-managed blocks and the grill overlay are re-ensured after project
  updates.

Validation and evidence limits

• PR #36, original
  head 8f3e70656d4f103303f2ff27a634b9e7e424729b, was merged as
  2673b22160fcbe6f0a434f748e347441259ee0a5; its Ubuntu and Windows jobs on
  Node 22 and Node 24 all passed, as did the merge-triggered main CI run.
• Merged-main evidence records a successful Node 24 Windows publish dry-run
  (408 discovered, 404 passed, 4 expected skips, 0 failed) and successful npm
  pack and publish dry-runs with 138 files and no retained tarball. Package byte
  size is intentionally not treated as cross-platform invariant because Git
  checkout EOL policy can change compressed and unpacked sizes without changing
  the tagged tree or package file set.
• Linux adapter regressions are covered and the native Ubuntu/Windows CI matrix
  is green. This release does not claim fresh third-party ecosystem or live-host
  certification; third-party MCPs, skills, plugins, marketplaces, add-ons, and
  auxiliary harnesses were outside the fixed-cutoff audit.

npm status

At post-merge preflight, npm latest remains 0.8.0 and
multi-agents-workflow@0.8.1 is absent from the registry. npm authentication is
not available in the preparation environment (npm whoami returned E401),
so publication remains a separate maintainer-authenticated handoff. No npm
publication is claimed by these GitHub release notes.

More detail

• English changelog
• 简体中文更新日志
• 繁體中文更新日誌
• Upstream compatibility and audit limits

v0.8.0 — shared Linux/Windows core

Changed

• Maintain one shared application core with separate Linux and native Windows platform modules, selected automatically; both platforms use the same package/plugin version.
• Adapt command discovery and launching, native paths, process/port inspection, and plugin guard execution for Windows while retaining Linux behavior and existing policy/upgrade safeguards.
• Expand CI to Ubuntu and Windows on Node 22 and 24 without installing mawf or dependencies. Native CI and external-host verification remain release gates, not implied test results.
• Document source-only development, platform boundaries, prerequisites, and synchronized releases in Cross-platform development.

Fixed — upstream host compatibility

• Add required descriptions and names to the five shared mawf skills, with source and Pi installer/update regressions for both operating systems.
• Honor Pi's canonical agent directory and generate supported Agent role metadata; inventory configured package/MCP resources with provenance, filters, disabled/trust state, and redacted Git credentials.
• Emit Pi agent tool allowlists in the plain flow-list format consumed by pi-subagents-lite@1.13.1; live installed-runner validation now preserves exact native tool IDs.
• Read dsh versioned credential names and saved default selections correctly; report current DeepSeek adapter/model evidence, shadowed skills and staged presets without fabricated prices or live-readiness claims.
• Match Claude Agent and legacy Task spawns in the cost guard; quote watchdog Python advice for native Windows and Linux.
• Verify cc-switch schema 18 while preserving older schemas, cost attribution, future-version diagnostics and database write protections.
• Record current upstream contracts and explicitly deferred live checks in Upstream compatibility.

---

Changelog: English · 简体中文 · 繁體中文

v0.5.1

Fixed

• doctor: dsh profile list no longer misreports node_modules as a profile. The pnpm/dsh symlink farm that can appear under ~/.dsh/profiles/node_modules is now excluded by a dedicated listDshProfiles() reader (src/dshprovider.js): real profile directories only — node_modules and dot-entries skipped, missing profiles/ degrades to []. Regression-tested.

Verified

• Compatibility with DeepSeek Harness (dsh) 0.1.0-rc.8: agent-default-model dump row byte-identical to rc.6 (provider/model extraction intact); settings.yaml llm-pi-ai.providers schema unchanged; mawf inventory --verify clean over the enlarged everything-as-a-plugin table (no duplicates); mawf advise scoring intact; MAW never reads dsh's session store, so rc.8's incompatible SQLite format is a non-issue; wording complies with rc.8 brand guidelines (descriptive "DeepSeek Harness (dsh)" usage is explicitly permitted).

---

Changelog: English · 简体中文 · 繁體中文

v0.4.2

Fixed

• Upgrade refresh now inherits the installed host (0.4.2): the spawned bin/mawf.js update runs with MAW_HOST taken from ~/.maw/installed.json, so a bare mawf upgrade on e.g. a dsh-install machine that also has ~/.claude no longer re-detects as claude-code and lets the stale-asset cleanup purge the dsh skills.
• Installing a second special host no longer drops the first (union semantics): MAW_HOST=pi mawf install on a dsh install (or vice versa) now ships BOTH hosts' assets and records both dirs in the manifest — install never silently removes another host's assets; explicit removal stays uninstall. A bare mawf update on a multi-host machine likewise keeps every recorded host.
• npm pkg fix: repository.url normalized (no more publish warning).

---

Changelog: English · 简体中文 · 繁體中文

v0.4.1

Changed

• mawf upgrade now refreshes installed templates by default (npm and checkout modes): after a successful self-upgrade it spawns the NEW bin/mawf.js update, so host assets (commands/agents/skills/hooks) match the upgraded CLI without a manual follow-up. Opt out with --no-apply-templates; a refresh failure degrades to a warning — the upgrade itself stays successful.

Fixed

• Stale assets from older installs are now cleaned up. install/update diff the previous v2 manifest against the files the current version writes and remove exactly the leftovers (no prefix scanning — user-added files are never touched), then prune emptied dirs. Fixes the 2026-08-18 incident where a 0.1.0-era install left maw-* skills/commands on disk next to the new mawf-* set, with a hooks.json pointing at a dead bin/maw.js, after the CLI itself had upgraded to 0.4.0. Legacy manifests without files[] are skipped (uninstall's prefix fallback still covers those).

---

Changelog: English · 简体中文 · 繁體中文

v0.2.1

Fixed

• --version / -v now prints the version; upgrade --dry-run no longer reports "upgraded".

---

Changelog: English · 简体中文 · 繁體中文

v0.2.0

Breaking / Rename

• npm name multi-agent-workflow → multi-agents-workflow (the old unscoped name is an unrelated third-party package); bin maw → mawf (deprecated maw shim kept for one release); GitHub repo renamed with 301 redirects.

Added

• maw upgrade self-upgrade command (git fork-first and npm global modes).
• Complete uninstall across all hosts with manifest-driven removal, optional config retention (--keep-config / --purge-config), and a prefix-scan safety net.
• DeepSeek Harness (dsh) host support: detection, provider/model reader, config generation, installer routing, doctor, docs.
• Model price gate (pause + human approval when a model is expensive); GitHub Actions tracker for @mindfoldhq/trellis updates; cc-switch project feature decoupled (code kept, disabled).

---

Changelog: English · 简体中文 · 繁體中文

v0.1.0

Added

• Initial MAW release: portable dynamic multi-agent workflow system for complex codebases — reads cc-switch config, selects architecture (loop / orchestrator-workers / multi-agent / graph / dynamic / ultracode), generates per-agent configs, enforces per-agent and total cost-rate limits via a PreToolUse guard, integrates Codex review.
• Capability-aware model selection, cc-switch read-only policy + pre-init snapshots, trellis-init chain, multilingual READMEs (en / zh-Hans / zh-Hant), agent-oriented install docs.
• Pi Agent host support: host detection, provider/model reader without cc-switch, config generation, installer routing, doctor, docs, tests.

---

Changelog: English · 简体中文 · 繁體中文

v0.7.3

Fixed

• codex 0.152.0 MCP-name atomicity in mawf inventory — quoted TOML server names ([mcp_servers."tools.calendar"]) have been atomic server names since codex 0.152.0 allowed : @ / . in server names; they are no longer misclassified as dotted-child config detail when a same-prefix server exists (with server tools configured, "tools.calendar" stays its own server). Genuine TOML sub-sections ([mcp_servers.<srv>.env]) are still dropped; package-style names (: @ / .) are covered by regression tests.

Added

• Upstream round-2 host-changelog adaptation: dsh 0.1.2-alpha.2→0.1.2-rc.1 + the 2026-09-05 plugin-rename wave / codex 0.151.0→0.153.3 / pi 0.84.4→0.85.0 / claude-code 2.1.251→2.1.260 (audit since the 2026-08-31 baseline; full matrix in the task tracker).
  • dsh 0.1.2-rc.1: --dump-config anchor row re-verified byte-identical; plugin delta (-dsh-tool-subagent-report, superseded by two-way send_message; +dsh-session-turn-outline; tool-web.config.fetch default flip) covered by a NEW 630-line real capture tests/fixtures/dsh-dump-0.1.2rc1.txt. The 0.1.2a2 fixture is KEPT as the legacy pre-rename plugin-name regression — parse tests run over BOTH.
  • dsh plugin rename wave: @noob-stupid/dsh-plugin-console / @changfenhuang/dsh-genui / dsh-drag-and-drop (git deps → npm registry packages) + @linxin666/dsh-web-all@0.3.14 sub-plugin namespacing (@linxin666/dsh-web-all/<x> ids with nested config.plugin) — tests cover renamed bundle origins, zero old-name residue, and namespaced ids; live-verified on the real machine (171 plugins, 0 dupes; doctor / inventory --verify / advise all exit 0).
  • codex 0.153.0: remote-marketplace plugin installs keep the [plugins."name@market"] config shape (verified against codex-rs config/src/plugin_edit.rs); [marketplaces.*] tables are not a plugin surface — regression tests document both.
  • configgen: dsh host notes gain the rc.1 headless output contract (progress streams to stderr; stdout carries only the final result).
  • pi 0.85.0 / claude-code 2.1.251→2.1.260: corpus-audited with code-cited evidence — no mawf impact (TUI/SDK/session-management and permission-rule entries only).
  • Tests 316→321; README ×3 badge 321.

---

Changelog: English · 简体中文 · 繁體中文