Scarp v0.0.6-alpha.2 — published prerelease

Published November 6, 2026 at 11:03:46 UTC. Published GitHub release · immutable source commit. This release is experimental, not stable.

Shipped changes

These are opt-in Rust embedding APIs, not new Scarp source syntax or additional CLI commands.

Capability	Behavior and limits
Module invalidation	Plans conservatively affected source identities from dependency graphs; current source still must be validated
Semantic cache	Reuses successful whole-graph resolution after exact source, import, identity, compiler-limit, label and revision validation; never masks failures with stale success
Token and syntax caches	Reuse successful lexing and parsed ASTs with correctly rebased source spans; import, syntax, type and resource checks remain required
Edit preflight and eviction	Validate bounded edit batches and discard affected cache entries; unknown identities invalidate conservatively, not securely wipe earlier returned objects
Native C11 scalar emitter	Shares stronger internal preflight; the restricted API and CLI availability remain unchanged

Read the tagged cache design contracts for exact Rust APIs: incremental-invalidation.md, semantic-cache.md, token-cache.md, syntax-cache.md, cache-edit-planning.md and cache-eviction.md. The binary archives do not bundle a separately compiled Rust library.

Official archives and checksums

Check the downloaded archive against its SHA-256 sidecar before extracting. Checksums are not digital signatures.

Existing CLI behavior

After extraction, from the directory containing examples/, the already supported commands include:

scarp version
scarp guide
scarp verify examples/hello.srp
scarp exec examples/hello.srp

For source-language examples, see alpha.6 symbols/CLI and alpha.6 numerical RMS. Those historical conformance examples remain pinned to v0.0.6-alpha.1; this newer Rust-only caching work does not justify repinning them.

Not shipped

There is still no scarp compile or scarp build, general native object writer, LSP server, file watcher, package registry or GPU/async runtime. Cached payload quotas are logical retention limits, not guaranteed heap bounds or speedups. Read the release feature matrix and version-aware Command Finder.