Migrating from an older Scarp alpha? First check the executable's version, then choose commands that exist in that exact published release. This guide compares published releases through v0.0.6-alpha.3. It is a documented command migration guide—not a promise that every program, manifest or Rust API works unchanged between versions.
Which commands shipped in each version?
| Published release | Execute file | Check file | New / notable capability | Evidence |
|---|---|---|---|---|
| v0.0.5-alpha.13 website fixtures in current CI | scarp run hello.srp | scarp check hello.srp | Relative .srp imports and explicit public source declarations | Published releaseSource commit |
| v0.0.5-alpha.2Release-documented; not in current CI fixtures | scarp run hello.srp | scarp check hello.srp | Checked module inventory and structured module metadata | Published releaseSource commit |
| v0.0.5-alpha.3Release-documented; not in current CI fixtures | scarp exec hello.srp | scarp verify hello.srp | guide, diagnose, exec, verify FILE and nested inspect | Published releaseSource commit |
| v0.0.5-alpha.4Release-documented; not in current CI fixtures | scarp exec hello.srp | scarp verify hello.srp | scarp create DIRECTORY, verify DIRECTORY and launch DIRECTORY | Published releaseSource commit |
| v0.0.5-alpha.5Release-documented; not in current CI fixtures | scarp exec hello.srp | scarp verify hello.srp | Project module inspection via CLI; restricted scalar C11 generator for Rust embedding only (no compile CLI) | Published releaseSource commit |
| v0.0.6-alpha.1Release-documented; not in current CI fixtures | scarp exec hello.srp | scarp verify hello.srp | Static symbol/reference inspection and rms(vector); no LSP or native compile CLI | Published releaseSource commit |
| v0.0.6-alpha.2Release-documented; not in current CI fixtures | scarp exec hello.srp | scarp verify hello.srp | Retains rms(vector) and symbol inspection; opt-in token/syntax/semantic Rust caches, edit planning and eviction (no LSP or native compile CLI) | Published releaseSource commit |
| v0.0.6-alpha.33 website fixtures in current CI | scarp exec hello.srp | scarp verify hello.srp | Adds topk(vector,integer), topk_values, softmax_temp and logsoftmax_temp; retains rms(vector), read-only symbol inspection and opt-in Rust caches (no LSP or native compile CLI) | Published releaseSource commit |
"CI-tested" here means only the 3 website fixtures passed their exact-output and version-specific validation checks under that version. Alpha.2 through alpha.5 entries are based on their published source and release history, not this website's current executable fixture tests. The alpha.4 fixtures passed in an earlier website CI run; the current suite tests the baseline and alpha.6.
Translate old commands carefully
| Earlier command | Current command | Important difference |
|---|---|---|
scarp run hello.srp | scarp exec hello.srp | Execute a file with the Scarp interpreter; the legacy run spelling remains temporarily accepted. |
scarp check hello.srp | scarp verify hello.srp | Not equivalent: check can evaluate selected runtime paths without printing; verify statically checks names and types without running ordinary statements.Do not automatically substitute one for the other. |
scarp tokens hello.srp | scarp inspect tokens hello.srp | Inspect lexer tokens rather than execute the program. |
scarp modules --json hello.srp | scarp inspect modules --json hello.srp | Inspect checked module metadata. The older standalone modules command began in alpha.2, not alpha.1. |
Check versus verify: legacy check evaluates selected runtime operations in fresh storage while suppressing printed output; verify performs static validation without executing ordinary runtime statements. For a runtime behavior test, execute the program and inspect its exit code and output instead. Do not assume a successful static verification guarantees successful runtime execution.
A safe file-to-project upgrade
- Run
scarp --versionon the executable you intend to use. Keep the old binary available while checking programs against the published prerelease. - If you are using alpha.1 or alpha.2, start with legacy
runandcheckcommands. For alpha.3 or later, preferexecto run a file andverify FILE.srpfor static checking. - In alpha.4, create a new project directory;
createrefuses an already-existing destination. Review itsScarp.projectmanifest before moving existing source files into it. - Use
verify PROJECT_DIRECTORYto statically check its entrypoint, thenlaunch PROJECT_DIRECTORYto actually execute it. Both commands require the explicit directory argument.
Published alpha.4 project commands
scarp version
scarp create hello-world
scarp verify hello-world
scarp launch hello-worldThese project commands were introduced in alpha.4 and remain available in v0.0.6-alpha.3; alpha.3 does not offer project-directory execution. Since alpha.5, you can additionally use scarp inspect modules --json hello-world to inspect the project's modules without running it. Since alpha.6, read-only inspect symbols --json and inspect references --json accept source files or explicit project directories. The manifest is experimental: there is no package registry, dependency lockfile or native .srp executable generator. Read the release-pinned project workflow and CLI reference source.
Published alpha.6 symbol navigation
Alpha.6 retains opt-in static source indexing; neither command executes ordinary runtime statements. JSON schema-v1 snapshots are compilation-local, not durable editor databases.
scarp inspect symbols --json hello-world
scarp inspect references --json hello-worldThese commands are absent from alpha.5 binaries. Check the release-pinned CLI reference for exact options and errors; there is still no LSP or native scarp compile command.
What needs testing after migration?
- Program output, runtime failures and execution-budget behavior.
- Imports and filesystem paths, particularly inside a new project.
- Editor/CLI integrations that invoke the older command vocabulary.
- Syntax, manifest and embedding APIs: none have a stable v1 guarantee.
The compatibility evidence names the exact three programs tested under the original baseline and v0.0.6-alpha.3. For binaries and checksums, use Downloads. See the complete release comparison or official release notes.