opencode-setup-system 0.0.88

Install, update, back up, restore and remove complete OpenCode configurations. Built by NDDev.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

# Validate

For a setup, follow the builder's ai-stp lifecycle validation: native component
checks, exact composition, evaluation, disposable install/readback/restore and
the intended product tasks. Document capabilities and evidence gaps.

For provider implementation changes, also run this checkout's checks:

```bash
cargo fmt --all --check
cargo clippy --locked --all-targets -- -D warnings
cargo test --locked --all-targets
```

If a command here is not present, say so rather than working around it.

Then a lifecycle smoke against a disposable target, never a live home:

```bash
target="$(mktemp -d)/opencode-target"
mkdir -p "$target"
opencode-setup-system install baseline    --target "$target"
opencode-setup-system status              --target "$target"
opencode-setup-system select full-auto    --target "$target"
opencode-setup-system diff                --target "$target"
opencode-setup-system backups             --target "$target"
opencode-setup-system restore             --target "$target"
opencode-setup-system remove              --target "$target"
```

Then, where a change touched the wire surface or the harness facts, run the
consumer's conformance against the built binary. Ask
`opencode-setup-system provider-info` for `harness_id`; that is the value
`--harness` takes. Report the verdict **with the consumer version that gave
it** — the same command answers differently on a released CLI and on a
development one, and a verdict without its version is not a verdict.