v0.4.2

What's Changed

• Preserve relay scan causes and isolate retries for v0.4.2 by @AngelMsger in #14

Full Changelog: v0.4.1...v0.4.2

v0.4.1

What's Changed

• Persist terminal relay failures and prepare v0.4.1 by @AngelMsger in #12

Full Changelog: v0.4.0...v0.4.1

v0.4.0

What's Changed

• Support direct Grok webhook delivery and local consumer claims by @AngelMsger in #11

Full Changelog: v0.3.0...v0.4.0

v0.3.0

What's Changed

• Use agent-cli-kit v0.6.0's shared READONLY_BLOCKED for the CLI session by @AngelMsger in #6
• Use agent-cli-kit v0.7.0 by @AngelMsger in #7
• Use agent-cli-kit v0.8.1 by @AngelMsger in #8
• Unify command responsibilities and add durable channel relay by @AngelMsger in #9
• Exclude self-bot observations and release v0.3.0 by @AngelMsger in #10

Full Changelog: v0.2.0...v0.3.0

v0.2.0

WeCom Channel CLI 0.2.0

Set up channel access with Bot ID and Secret before selecting a channel ID.

• Use the existing channel list --bot-id BOT_ID with the operator's
  WECOM_CHANNEL_BOT_SECRET to discover joined channel names and IDs without
  first creating a policy, broker or client context. Reads support bounded
  pagination and offline dry-run.
• Continue using channel list through the configured context/socket for normal
  operation. Credentials in the environment never select direct access or
  recover a failed broker call. Explicit bot/socket/context conflicts fail.
• Fill the policy template with config example --bot-id ... --channel ....
  Auth guidance, missing-ID recovery, README and companion Skill 0.1.6 now follow
  credentials → channel selection → policy → broker → client context.
• Match the first client context to the template's default name and socket.
• Make read-only enforcement structural: pkg/apiclient.Client combines the
  exported Reader and Writer interfaces, and missing write-blocking overrides
  fail compilation without changing the existing method signatures.
• Publish Linux/macOS amd64/arm64 binaries, checksums and the npm wrapper through
  the shared tag-triggered GitHub Actions workflow with npm OIDC provenance.

Upgrade

npm install -g @angelmsger/wecom-channel-cli@0.2.0
wecom-channel-cli skill install
wecom-channel-cli skill status

Reload the agent context after refreshing its Skill. Existing broker policies,
client contexts and agent socket restrictions remain valid. No migration or
credential re-entry is required for existing broker use.

The new credential-based setup path is tested with synthetic services. Earlier
live authentication, channel discovery and polling checks cover one test tenant;
live text/reaction writes, optional callbacks and actual production worker
isolation remain operator-specific verification. The connector does not sandbox
arbitrary agent tools or grant permissions from channel membership.

v0.1.0

WeCom Channel CLI 0.1.0

Initial release for the grayscale WeCom channel APIs, published on 2026-10-27
from 3a65bf9 with npm provenance.

• Named channel security contexts, with offline family-style configuration and
  independent socket, policy, inbox and approval boundaries.
• Shared token cache per bot deployment and optional verified callback ingress.
• Channel/member discovery, post/reply reads, scoped search and durable events.
• Bounded NDJSON watches for a whole channel or selected post threads, with
  explicit observation coverage, gap detection and context-bound checkpoints.
• Default HTTP polling without a public address: quiet baselines, atomic snapshot
  comparison, deduplicated changes and bounded request/record budgets. Callbacks
  retain the same watch command and output envelope.
• Immutable text proposals and independent exact-digest operator approval.
• Native emoji add/remove proposals for posts and replies, with type discovery,
  membership reads, independent reaction permission and the same approval boundary.
• Strict HTTP destinations, authenticated callbacks, replay protection, bounded
  output and secret-free untrusted-data envelopes.
• Linux/macOS amd64/arm64 binaries, mandatory SHA-256 verification in the npm
  installer, a companion Skill, and a static documentation site.

This connector does not sandbox arbitrary agent tools. Separate OS identities
and a restricted worker environment are required. Authentication and channel
discovery, whole-channel/thread polling, filtering and resume passed in one test
tenant. A synthetic Linux container verified distinct-user socket/file access
controls. Live text/reaction writes, optional callback delivery and the actual production
deployment still require operator verification. Polling may coalesce intermediate changes and never infers deletion
from absence. Media transfer, content edits/deletes,
Windows and channel long connections are outside this release.