xmlsquishsource. compose. build.
中文
Release log

v1.0.1 · Historical

Publication boundaries become product contracts

Build outputs now carry typed, project-relative locators instead of exposing publisher storage paths. Raw artifact inspection validates digest and size before any bytes reach stdout.

· Machine protocol 3.0· 6 native archives
Get this versionGitHub ReleaseRelease metadata

01

Changes

Typed publication catalog

  • Published targets expose target and generation identities plus typed artifact records.
  • Every artifact carries an immutable id, kind, stable locator, size, and digest.
  • Manager code no longer constructs or scans private generation directories.

Capability-lazy runtime

  • One invocation-scoped production runtime is injected at the composition boundary.
  • CAS, action index, target publisher, and catalog publisher initialize independently and only when required.
  • An initialization failure in one capability does not poison unrelated capabilities.

Protocol 3.0 migration

  • Automation must decode PublishedArtifact rather than the protocol 2.1 Artifact shape.
  • Keep and pass the stable locator instead of reading a physical uri.
  • Use inspect artifact LOCATOR --format=raw when exact bytes are required.

02

Get this version

Native archives

Choose the archive matching your operating system and processor. Verify its exact filename against SHA256SUMS before extraction.

Windows

Windows 10/11 · ZIP

Linux

glibc 2.35+ · tar.gz

macOS

macOS 11+ · tar.gz
SHA-256 manifest

Native archives are unsigned and not Apple-notarized. Checksums establish byte integrity, not publisher identity.

Pinned source install

cargo install --git https://github.com/kleedaisuki/prompt-squish --tag v1.0.1 --locked

03

Compatibility

  • The XML DSL namespace, vocabulary, and semantics are unchanged.
  • The six direct commands, manifest, locked/offline modes, exit codes, and artifact roles remain stable.
  • Machine-event consumers must migrate from protocol 2.1 to 3.0 together with the CLI.