WeClaw Dev v0.1.7-alpha

Highlights:

• Enable default background logging to ~/.weclaw/weclaw.log.
• Add automatic log trimming around the default ~20 MB limit while preserving newer complete log lines in chronological order.
• Allow weclaw start <profile> resume to omit the session ID and use the most recent ACP/Codex session for that profile.
• Preserve explicit resume <session-id> behavior.
• Make weclaw start ... idempotent when a managed WeClaw process is already running.
• Report already-running status instead of stopping or replacing the current process.
• Fix Codex ACP resume by calling stable app-server thread/resume before turn/start.
• Remove experimental excludeTurns from the default thread/resume request, avoiding the experimentalApi capability requirement.
• Keep the user-visible ACP session/thread ID stable after successful resume.
• Improve /now and /status consistency by resolving the default profile/session through a shared path.
• Avoid unknown context-window used/left values in /status where configured context-window data is available.
• Label Codex turn IDs as last turn id to avoid confusing per-turn IDs with ACP session/thread IDs.
• Improve weclaw upgrade --alpha for rebuilt pre-release tags by comparing release commit metadata, not only the public version string.
• Preserve running managed sessions during upgrade when possible: download and install first, then stop the old process and restart the new version with the previous profile and ACP session.
• Increase upgrade download timeout and retry budget for slower VM network paths.
• Document upgrade runtime migration in README and README_CN.
• Make weclaw stop explicit and verifiable: it reports stopped PIDs or not-running state, clears stale PID state, and verifies that no managed WeClaw process remains.
• Keep weclaw stop aligned with weclaw start and weclaw status by using the same managed-process runtime inspection path.

Validation:

• Focused resume, runtime-state, start/profile, status/now, upgrade, and messaging tests passed across the p5a20-p5a25 line.
• p5a28 stop-semantics tests passed, including focused command tests, go test ./cmd, and full go test ./....
• git diff --check and bash -n install.sh passed before release asset rebuild.
• Five release assets were built and uploaded: Linux amd64, Linux arm64, macOS amd64, macOS arm64, and Windows amd64.
• Linux amd64 release asset was smoke-tested for public/internal version metadata: v0.1.7-alpha | 31fa432 and v0.1p5a28-stop-semantics | 31fa432.
• VM validation confirmed weclaw upgrade --alpha can detect a rebuilt same public tag, install the new asset, stop the old managed process, and restart with the prior deepseek-thinking profile and ACP session.
• VM WeChat validation confirmed natural-language resume no longer fails with thread/resume.excludeTurns requires experimentalApi capability.
• VM stop-semantics validation confirmed an intentionally leftover old v0.1.6-alpha managed process is detected after installing the new v0.1.7-alpha asset, and the new weclaw stop prints weclaw stopped, Stopped PIDs: ..., and Verified: no managed weclaw process remains.
• VM validation also confirmed a second weclaw stop prints weclaw was not running and still verifies that no managed process remains.

Notes:

• This Release currently points to commit 31fa432.
• turn/last turn id is not the same as the ACP session/thread ID. A turn ID is per user request. The session/thread ID is the persistent Codex ACP conversation container.
• Token attribution by user message, history, tool schemas, environment context, and system/runtime prompt is not yet implemented in WeClaw. It requires dsproxy to expose a request-payload attribution interface.