Reference · public release record
Changelog
This log starts with the current public contract. It does not reconstruct private development history.
Every entry records what changed, whether an agent or supervisor needs to act, and the migration path when a public contract moves.
Dated public record
Product and contract changes
@postdom/mcp · v0.3.0
Direct media upload
- Published @postdom/mcp@0.3.0 with upload_media and get_media.
- Expanded the configured surface to thirteen tools over both stdio and hosted Streamable HTTP.
- Added media_handle as an alternative to video_url on publish_video; exactly one is required.
- Kept video bytes on a direct, short-lived PUT path into workspace-scoped storage.
Migration guidance: Reload the exact Accounts configuration to use @postdom/mcp@0.3.0. Existing video_url calls remain valid; local media now uses upload_media, an exact PUT, get_media until stored, then publish_video with media_handle.
@postdom/mcp · v0.2.0
Weekly learning evidence
- Published @postdom/mcp@0.2.0 with a Node.js 22 or newer runtime requirement.
- Expanded the configured surface to eleven tools with get_digest for append-only, availability-honest weekly evidence.
- Added workspace-scoped agent keys and a human-completed destination authorization handoff.
- Added versioned Workspace Brief guidance and the optional brief_version plan field.
- Documented L0 through L3 authority, including bounded-autonomy defaults and pause controls.
Migration guidance: Reload the exact Accounts configuration to use @postdom/mcp@0.2.0 and receive all eleven tools, including get_digest and get_best_posts. Existing plan calls remain valid; brief_version is optional.
Public documentation
Initial public contract
- Documented the five configured agent tools and their current callable fields.
- Published exact plan, post, destination, and availability state references.
- Published field-enforcement layers and the 27-cell modeled availability baseline.
- Separated configured adapter defaults from publish_video inputs.
- Published operating-brief placement for already-configured agent clients.
No migration required: No callable schema changed in this documentation release. Configured clients should keep inspecting their connected tool schemas.
Caller responsibility
Migration policy
Configured clients should inspect their connected tool schemas before acting. Documentation never expands a callable contract.
The changelog explains movement. The agent contract defines what is callable now. Read the agent contract.
Publication threshold
Evidence policy
Executable truth first
Schema and runtime behavior outrank marketing copy. Modeled availability and recorded platform guidance keep their labels.
A release appears here only when a deployed product surface, callable contract, migration path, or its public documentation changes.