Release notes

Release notes without release-shaped promises

Separate approved releases from development progress and internal builds.

Pre-release. Reviewed October 23, 2026. This review covers code behavior, not a packaged release or provider certification.

No public release is announced here

The public release remains in preparation. This is a dated development summary, not a downloadable version announcement.

October 4, 2026: website launch work

  • Catalog freshness and clipboard failure are made explicit rather than reported as success.
  • Dedicated guides separate accounts, Saved Views, verified runs, local collaboration and reviewed handoff.
  • Capability and research pages expose unavailable, degraded and unadjudicated states.
  • Commandem Journal prepares substantive Development and Research articles with an RSS feed.

These describe website source work. They do not claim the production site or installed application includes it.

What an approved release entry must contain

  1. Exact version/date and matching artifact identities.
  2. Changes that matter to users, known limitations and affected providers/platforms.
  3. Upgrade or migration steps, preserved state and rollback instructions.
  4. Named verification evidence and unresolved acceptance.
  5. Security fixes disclosed through the established private reporting process.

Routine internal commits belong in development updates, not fake release announcements. See the Journal and release hub.