Changelog
Changes users can see and verify.
Capability, safety, reliability, compatibility, and retirement changes belong here. Internal review notes, roadmap details, and implementation scoring do not.
Controlled-live hardening and release-state alignment shipped.
Production routing, provider-health gates, MCP exposure, authority copy, SDK/CLI release state, and operational proof were aligned for controlled beta without changing public-launch status.
- The production server migration is complete, old-server cleanup is complete, and direct app ports remain closed.
- Provider health now gates controlled-live arming and keeps degraded or unavailable source states explicit.
- Default public MCP exposure no longer includes agent_execute; scoped clients use tools/list as the advertised capability source.
- Authority copy separates wallet sign-in, walletless setup, runtime mode, approval, and execution boundaries.
- Runtime warning and Redis URL log-marker hardening reduced noisy or sensitive operational signals.
- SDK and CLI remain on 0.3.11; no new package surface is shipped by this changelog entry.
- Controlled-beta proof assets were captured for review, while public launch, fresh CI/security evidence, and offsite proof remain parked.
Shadow-first control became the default public explanation.
Public product guidance now separates wallet sign-in, agent funding, live arming, approval, submission, and reconciliation.
- New operators can inspect the product before connecting a wallet.
- Unavailable or degraded evidence is described explicitly.
- Submission is no longer described as a completed financial outcome.
Hub consolidated autonomous trading-agent operations.
Hub became the active web product for agents, rules, runtime, wallets, activity, Signal Sources, Revenue, and access.
- Studio remains only as a retirement and migration route.
- Telegram and Discord are presented as Signal Sources, not chat-bot products.
- Explorer remains the public evidence and discovery surface.
External-agent onboarding gained clearer access boundaries.
CLI, SDK, MCP, walletless onboarding, and browser wallet sign-in are documented as distinct paths with different scopes.
- Builders can prove a read-only integration before adding privileged access.
- Walletless onboarding no longer depends on opening the Hub UI.
- Public records preserve raw technical identifiers as secondary metadata.
Need the technical record?
Public package source and documentation carry the implementation detail.
