Add beta verbose progress controls

[zeolenon]

Summary

• Adds beta/experimental verbose progress support for CAS, defaulting off via config.
• Adds /cas_verbose [on|off|status] as a persisted runtime override and shows Verbose: on/off in /cas_status immediately after Plan mode.
• Emits reduced progress labels only (Working, Reasoning, Tool, Command, etc.) from app-server notifications, without exposing raw command text.
• Updates a single progress message where possible, falls back to replace-and-delete when edit fails, and cleans the progress message at turn completion.
• Uses the OpenClaw Telegram runtime API from plugin-runtime-deps for edit/delete when available, with raw API fallbacks.

Beta validation notes

• This was tested against the current beta CAS/OpenClaw Telegram flow.
• Verified /cas_verbose on, /cas_verbose off, edited progress updates, and final cleanup behavior in Telegram.

Tests

• npm test
• npx tsc --noEmit --module NodeNext --moduleResolution NodeNext --target ES2023 --lib ES2023 --skipLibCheck index.ts index.test.ts src/*.ts

[huntharo]

Thank you for your contribution!

Unfortunately there are still changes needed to support such an ambitious plugin in OpenClaw. Some of this functionality is now being included directly in OpenClaw.

I have made a new project, https://github.com/pwrdrvr/PwrAgent, that gives you a Codex Desktop replacement app (uses Codex) but also integrates with messaging with openclaw-codex-app-server-like functionality.

In that project I have coalescing of tool invocations, rate limit budgeting (particularly important for Telegram SuperGroups), and a control for how many tool invocation messages you get. I think you'll like it.

Please give it a try!