Skip to main content

Module sample

Module sample 

Source
Expand description

Try the sample: a small project and a run of it recorded with a real model, bundled into release builds, copied into speccoder’s own state directory (never the person’s workspace) and verified by strict replay — no model, no key, no network. A run this build cannot reproduce is reported as such, never shown as if it had worked; a build without the recording says so (SAMPLE-MISSING), never shows an empty playback.

The recording is made by the maintainers with just record-sample (scripts/record-sample.sh), never in CI.

Structs§

Asset
A sample: the project’s history as a git bundle, the journal, the manifest.
Manifest
The recording’s manifest (manifest.toml).

Functions§

available
Whether this build has the sample.
bundled
The sample bundled into this build, if it has one.
copy
The copy of the project, if one was made.
home
Where the sample’s copies live.
missing
The sample is missing from this build.
missing_tool
The tool the sample’s checks need that is not on the PATH, with how to get it (None: they can run here).
open
speccoder sample [--fresh]: the bundled sample, copied and replayed.
open_from
open for asset: a copy under <state>/sample/<version>/ (an existing one is reopened unless fresh), its journal placed in the copy’s project state, every recorded run replayed strictly.
run_checks
Run the checks yourself: the sample’s own fast checks, in its copy, confined like a run’s (no network). Refused anywhere but the sample.