ci/woodpecker/push/woodpecker Pipeline was successful
CI / fmt + clippy + test (Linux x86_64) (push) Canceled after 0s
CI / schema instance validation + consumers (push) Canceled after 0s
CI / runtime contract (macos-latest) (push) Canceled after 0s
CI / runtime contract (windows-latest) (push) Canceled after 0s
CI / release candidate artifact (macos-latest) (push) Canceled after 0s
CI / release candidate artifact (ubuntu-latest) (push) Canceled after 0s
Capture the strict child through launch_strict_capture and classify the outcome before writing anything. In --json mode a control-plane failure now emits exactly one error document with a stable code instead of forwarding bubblewrap stderr and leaving stdout empty; a verified child's valid JSON is forwarded unchanged with its own exit code. Empty, partial or non-JSON child output becomes strict.child_invalid. Route the remaining run --json error paths (mode, grants, missing entry, trace) through the same contract, classify sandbox launch failures with StrictFailureKind so probe/spawn/timeout/resource failures stay distinguishable, and add deterministic routing tests plus forged-marker CLI coverage. Document the decision in ADR-0053 and spec/security.md 1.2. This is step 2 of the CI/security RFC (B02/B03).
32 lines
601 B
Plaintext
32 lines
601 B
Plaintext
/target
|
|
/.cache
|
|
**/*.rs.bk
|
|
*.profraw
|
|
.DS_Store
|
|
|
|
# Built plugin artifacts
|
|
examples/plugin-demo/solver.so
|
|
examples/plugin-multi-export/solver.so
|
|
|
|
# Local cargo home used on hosts with a read-only $HOME
|
|
.cargo-home/
|
|
# Local rustup home used for cross-target `cargo check` verification
|
|
.rustup-home/
|
|
|
|
# Generated plugin fixture manifests/artifacts
|
|
examples/plugin-demo/build/
|
|
examples/plugin-multi-export/build/
|
|
|
|
# Release artifacts
|
|
dist/
|
|
|
|
# Local VM/QEMU tooling and disk images
|
|
.tools/
|
|
|
|
# Local-only credentials and environment files
|
|
.secrets/
|
|
.env.local
|
|
|
|
# stdlib product test output
|
|
stdlib/tests/out/
|