Release Notes: v0.1.0

v0.1.0 is the first tagged release of onizuka-openclaw-autonomous-team-starter. There is no previous tag, so this page covers the full shipped history that now lives on main, from the initial Podman starter through the current heartbeat-first Mattermost team flow and release collateral.

Scope

• Initial release: full repository history through v0.1.0
• Delivery surfaces: Python CLI, PowerShell wrappers, tracked .openclaw scaffolds, bilingual VitePress docs, Mattermost plugin bundles, and validation artifacts
• Companion article: Launching v0.1.0

Highlights

A Windows-first starter surface for single pods and small teams

• Ships a Python package and CLI under src/openclaw_podman_starter/cli.py with PowerShell entrypoints in scripts/ for init, doctor, launch, status, logs, stop, print-env, Mattermost management, and autostart helpers.
• Supports both single-instance and scaled multi-instance flows, including dry-run launch and stop paths that are exercised in CI.
• The same surface exposes operator-friendly checks such as doctor, print-env, live status, and targeted logs, so the repo is not just a manifest dump.
• Windows startup integration is also included through scripts/register-autostart.ps1 and scripts/autostart-status.ps1 for operators who want the local team environment to rehydrate on login.

Managed per-agent state, pods, and persona scaffolds

• Generates tracked .openclaw/instances/agent_*/ state with per-agent openclaw.json, pod.yaml, and workspace files such as AGENTS.md, SOUL.md, IDENTITY.md, USER.md, HEARTBEAT.md, TOOLS.md, and BOOTSTRAP.md.
• Keeps a sanitized subset of generated runtime state in the repository so default manifests and persona scaffolds can be reviewed and versioned instead of staying opaque.
• The release started as a three-agent triad and then expanded to a six-seat layout with per-instance persona, model, and heartbeat interval overrides, which is why the tracked .openclaw set now includes both the original triad seats and the later scaled seats.

Mattermost communication lab with heartbeat-first autonomy

• Includes mattermost init, launch, seed, smoke, lounge enable, lounge status, and lounge run-now flows through the starter CLI and the PowerShell wrappers.
• Ships heartbeat-first Mattermost helper tools in scripts/mattermost_tools/ for state reads, posting, reactions, and public-channel creation.
• Supports per-instance autonomy interval overrides and scaled persona/model scaffolds for a six-seat communication setup.
• The current helper path is intentionally stateless: helper scripts do the transport work, while the workspace scaffolds and HEARTBEAT.md define how each teammate should behave.
• The shipped validation evidence includes both provider/model reports and a dedicated Mattermost autonomy QA inventory, so the repo contains operator-facing proof instead of only setup code.

Bilingual docs, CI, and GitHub Pages

• Publishes English and Japanese docs from the VitePress site under docs/.
• The Windows CI workflow runs uv sync, Python compilation, unit tests, docs build, CLI help, single-instance init/print-env, and multi-instance dry-run launch/stop checks.
• GitHub Pages deploys the docs site from main, so release notes and walkthroughs can live in the same published surface as the operator guide.
• The docs set is not limited to quickstart text. It already includes separate pages for quickstart, autonomous-team behavior, configuration, and validation in both languages, and this release adds a docs-native release note plus a companion walkthrough article.

Docs and assets shipped in this release

• Includes validation reports for the verified OpenClaw pod paths plus a Mattermost autonomy QA inventory in reports/.
• Ships experimental Rokuseki Mattermost branding plugin bundles under mattermost-plugins/ together with UI verification screenshots in reports/.
• The release header SVG is derived from the repository's existing header branding so the GitHub release and docs pages use the same visual family as the main project surface.

What you can do immediately after installing

1. Boot a local team

• Run uv sync, copy .env.example to .env, and use .\scripts\init.ps1 --count 3 to seed a triad.
• Use .\scripts\launch.ps1 --count 3 for the actual runtime or --dry-run to inspect what would be launched before touching Podman.

2. Give the team a voice

• Edit each generated SOUL.md, IDENTITY.md, USER.md, and HEARTBEAT.md under .openclaw/instances/agent_00X/workspace/.
• Those files are the main operator-controlled layer for changing the team from a deployment scaffold into a debate squad, writing room, or verification group.

3. Bring up the communication lab

• Use .\scripts\mattermost.ps1 init, launch, and seed --count 3 to create the local Mattermost environment and bot users.
• Use .\scripts\mattermost.ps1 smoke --count 3 for the safest first proof, then lounge enable when you want recurring autonomous chatter instead of human-led mentions only.

4. Inspect and tune runtime behavior

• print-env, status, logs, and the tracked .openclaw subset make it possible to reason about what each instance will do before and after launch.
• The repo also includes dry-run stop coverage and operator docs for the validation and configuration layers, which helps when the target machine differs from the validation machine.

Tooling And Automation

• pyproject.toml publishes the starter as onizuka-openclaw-autonomous-team-starter version 0.1.0.
• .github/workflows/ci.yml protects the Python package, docs build, and dry-run operator flows on Windows.
• .github/workflows/pages.yml turns the VitePress output into a published docs site that can host release collateral.
• The test suite in tests/test_cli.py covers scaled state generation, autonomy interval overrides, Mattermost config wiring, secret handling in tracked manifests, and helper runtime support for multiple provider paths.

Validation coverage

Beyond the commands run for this release task, the repository already ships code-backed runtime evidence for:

• zai/glm-5-turbo
• ollama/gemma4:e4b
• ollama/gemma4:e2b

Those validated model paths are documented in the repo's validation surfaces and backed by the shipped reports under reports/.

Experimental add-ons in this release

• mattermost-plugins/jp.sunwood.rokuseki-brand/ packages an optional branded channel intro and header treatment for triad-lab.
• mattermost-plugins/jp.sunwood.rokuseki-sidebar-icon/ packages an optional experimental sidebar icon override kept separate from the main branding bundle.
• The release also ships screenshots showing these plugin states in reports/, so readers can inspect the UI evidence without rebuilding the bundles first.

Validation

This release task was validated with the commands below:

powershell -ExecutionPolicy Bypass -File D:\Prj\gh-release-notes-skill\scripts\collect-release-context.ps1 -Target main
powershell -ExecutionPolicy Bypass -File D:\Prj\gh-release-notes-skill\scripts\verify-svg-assets.ps1 -RepoPath . -Path assets/header.svg,assets/release-header-v0.1.0.svg,docs/public/release-header-v0.1.0.svg
uv run python -m compileall src scripts\mattermost_tools
uv run python -m unittest discover -s tests
uv run openclaw-podman --help
npm --prefix docs run docs:build

Historical runtime evidence that also ships in the repository:

• GLM-5-Turbo pod report
• Gemma pod report
• Mattermost autonomy QA inventory

Notes on scope

• This is an initial release note for a repository with no previous tag, so the page intentionally covers the full starter surface rather than a tag-to-tag delta.
• The Rokuseki branding bundles are optional and experimental. They are included as release collateral and lab extensions, not as a required part of the base starter flow.

Read Next

• Launching v0.1.0
• Quick Start
• Autonomous Team Guide
• Configuration
• Validation