Actspan release notes

Review the available downloads and their known limitations before installing or updating Actspan. Start with one documented workflow and keep the version of its CLI, plugins and examples explicit.

Before you begin

These notes describe the public CDN's Actspan 0.2.0 CLI as of October 22, 2026. Private release assets can share a version label while having different build identities. Check the supplied artifact and its verification record before applying results from another build.

Expected result: you can choose an available download, identify its limits and follow the relevant setup or approval instructions.

Public 0.2.0 download

The current public native bundle is for Apple Silicon macOS. It includes Python and requires no product-repository account. The installer verifies the archive checksum before activating the command. Follow the installation guide for the exact download and published checksum.

The executable is ad-hoc signed, without Apple Developer ID signing or notarization. Fresh-machine Gatekeeper acceptance has not been qualified. See the macOS opening instructions.

Linux AMD64/ARM64 and musl ZIPs are attached to the separately distributed private release. They are not in the current public installer catalog. See download availability for the distinction between channels and the reported absence of Mac release attachments.

Workflows and verification

• Start with the two-file first prompt. Initialization, validation and preview make no model calls; a live request uses your provider account and incurs its normal charges.
• The refund walkthrough records the public OpenAI $75 automatic, $250 local-review and $750 blocked paths with synthetic sandbox payments. It explains which decisions belong to the service and which are enforced by Actspan.
• Provider and framework coverage depends on the named runtime and workflow. Read the verification matrix for the exact scope. The portal screenshots remain labelled as historical core 0.1.2 evidence.

Known limitations in the public 0.2.0 CLI

Approval tool-source binding

If a same-named Python package and .py module coexist, public 0.2.0 can fingerprint the file while execution imports the package. A package edit may then leave an earlier pending approval valid. Use explicit file entrypoints for the documented refund rehearsal, keep reviewed code and configuration fixed while paused, and start a fresh run after changing them. Imported helpers are also outside that release's binding.

The approval guide retains the detailed issue, scope and safeguards. The source correction and explicit dependency manifest need their own qualified release; an existing download is not updated by changing repository source.

Failed direct-prompt receipt checks

A failed receipt check in a direct prompt can have an unreliable outer success flag or exit code in the public 0.2.0 build. Inspect the nested runtime status and same-run error evidence. The optional receipt exercise checks those signals and the sandbox ledger. It does not imply rollback of a write already committed by the service.

Cost estimates

Token estimates depend on the selected model and supported pricing. The current flat-rate catalog intentionally leaves context-tiered Claude Haiku 5.5 unpriced. Read the cost-limit guide before relying on a budget estimate. Missing cost evidence is not proof of zero cost.

Updating safely

Retain the downloaded archive and checksum, record the CLI and independent plugin versions, and repeat the checks for the workflow you use. New GitHub attachments do not update the public CDN installer. Check these notes and the installation guide when a separately verified public build becomes available.

Packaging and publication notes

GitHub binary jobs run when a GitHub Release is published or the workflow is started manually; a tag push alone does not trigger that binary workflow. Mac release upload requires its signing/notary configuration and completed checks. Private release attachments and the public CDN catalog are separate channels. A release filename/version does not establish identical bytes or qualification.

The current immutable public2 example README uses older “unsigned” wording; the verified public executable is ad-hoc signed without Developer ID/notarization. The archive README also promises a per-file manifest that is not included. Its published checksum covers the whole archive. Corrected README generation is for a new immutable revision, not replacement bytes under public2's existing URL. The published installer help also names a future branded download root; its actual selected default remains the CloudFront endpoint in the install guide. A local help correction is not a CDN update.