Redacted excerpt; full evidence withheld.

$ cd <host-path> && git log -1 --format=%H 2>/dev/null; ls -la; cat README.md 2>/dev/null | head -300
exit: 0
e top level (e.g. `open_store`, `SchemaPolicy`); may change in a future minor. |
| **Internal** | `power_loop.core.*`, `power_loop.runtime.store.*` internals; no compatibility promise. |

See the [API reference](docs/en/api/index.md).

---

## Honest scope

power-loop **orchestrates; it does not, by itself, isolate.** The built-in `bash`/file tools run in-process and inherit the host environment — convenient for trusted, local use, **not a security boundary**. For untrusted/model-authored commands, inject a sandbox via the `ShellBackend` seam (tool-level) or run leaves through `SubprocessExecutor` + `WorkerLauncher` (process-level). Keep secrets in your orchestrator. See [SECURITY.md](SECURITY.md).
[excerpt truncated]