What Replume checks
Rules and evidence for a change, with clear limits.
Protected files
Auto contracts protect existing tests, test support, CI configuration, lockfiles, .env files and Replume state. The test script is protected by default. New tests may be added, but changing an existing test can be blocked or flagged.
Tests made easier
After a write, Replume looks for removed assertions, skips, relaxed expectations and narrowed test commands. These checks are patterns, not proof that a test is meaningful.
Claims against evidence
At Stop, it compares “tests pass” or file-change claims with recorded commands and file events. A missing or stale test run is called out. The ledger is local and editable, so this is observed evidence, not an audit guarantee.
Scope and dependencies
It compares changed paths with the contract’s allowed paths and inspects dependency file changes. Registry lookups are off unless you explicitly use replume verify --check-registry.
Runtime, like a user
With Docker, Replume can probe a detected CLI or HTTP app and compare it with the base. Web checks use Chromium only when its image is already ready in auto mode; auto.runtime: web allows the one-time image download. Without a runnable target or Docker, the runtime result is missing; read that limit before treating the report as complete.