Env Bootstrap

---
name: env-bootstrap
description: Prove a project seam or execution environment before business logic is added. Use for CLI, API, service, Tauri command, library, FFI, subprocess, model/runtime, pipeline, or process boundaries that need smoke tests for parameters, returns, errors, logs, tracing, concurrency, resources, rollback, or disable routes.
---

# Env Bootstrap

Use this skill when a unit depends on a seam or environment that is not already
proven in the project.

## Scope

Bootstrap proves the boundary works. It does not implement business semantics.

Valid seams include CLI, HTTP/API, service facade, Tauri command, library API,
FFI, subprocess, worker queue, model loader, runtime process, or pipeline stage.

## Proof Matrix

Record the smallest useful proof:

```yaml
seam: cli | api | service | tauri | library | ffi | subprocess | model | pipeline
entrypoint: ""
inputs: []
outputs: []
errors: []
logs_or_traces: []
resource_paths: []
concurrency_or_cancellation: []
smoke_tests: []
rollback_or_disable: ""
owned_paths: []
```

## Workflow

1. Read project facts and current seam conventions.
2. Choose the existing boundary when one exists.
3. Add the thinnest adapter or fixture needed to call the seam.
4. Prove parameter passing, return shape, error projection, logs/traces, resource
   paths, and rollback/disable route.
5. Run a smoke test.
6. Record what later units may rely on.

## Non-Negotiables

- Do not put business logic in bootstrap code.
- Do not introduce a new seam when an accepted project seam already fits.
- Do not call a seam proven if errors and rollback are untested.
- Do not hide machine-specific credentials or paths in committed state.
- Do not broaden bootstrap into implementation work.