Repository navigation
Context OS v1.3.0
Context OS 1.3.0 adds Autoposting to the integration catalog and lets a catalog
entry record an execution capability that cannot be established. The
1.x compatibility contract
is unchanged.
Autoposting in the integration catalog
Autoposting CLI MCP is a listed, generic-stdio catalog reference pinned to
0.4.0. The entry discloses publishing, delayed writes, uploads, deletion,
credential destinations and the unverified backend API bridge. Listing it
installs and authenticates nothing; see the
catalog entry.
Unknown execution scope
Integration catalog schema 3 permits arbitrary_execution: null when execution
scope cannot be established, with a required explanation in
capability_uncertainty.arbitrary_execution. Generated references show
Unknown instead of No, and an unknown entry carries the same execution
confirmation and risk gates as a known one. Boolean-only schema 2 catalogs
remain readable. The
integration guide
describes the contract.
Release assets and upgrades
Download all five attached assets from the immutable release. Begin with
agent-context-os-template-v1.3.0.OFFLINE-VERIFY.md. The attached template tar
is the canonical workspace; GitHub's generated source archives are repository
snapshots.
Release qualification adds the published 1.2.0 release to the pinned baselines
in scripts/qualify-release-migration.py, so it exercises 1.2.0 → 1.3.0
upgrades of full-template and selected workspaces installed by that kernel,
alongside the earlier baselines, schema-v1 and legacy migrations, personalized
file conflicts, rollback, lock exclusion, journal recovery, post-commit doctor
failure and fresh setup on Linux and Windows. These synthetic tests are separate
from native adapter evidence. Windows extraction cannot verify POSIX executable
bits.
Source version 1.3.0 remains a candidate until its immutable release is
published. Until then, use the published 1.2.0 assets or the source setup path.
Cursor IDE remains experimental.