v0.8.1 — Trellis lifecycle integration
Changed
- MAWF now chains Trellis lifecycle operations explicitly:
mawf updateruns
trellis update, whilemawf upgraderunstrellis upgradeand the
applicable Trellis project update. mawf uninstallremains 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 through2026-09-12T23:59:59Z. No newly
released non-TUI host contract in that window required a MAWF code
adaptation.
Fixed
- Interactive
mawf initpreserves 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
head8f3e70656d4f103303f2ff27a634b9e7e424729b, 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.