# v1.7.0 — bounded commands and first use

Date: 2026-09-05.

Adds an optional executable helper inside the existing Sessions skill. The
fifteen-skill portfolio and client-neutral routing remain intact. Installation
now appears before architecture, with coding and everyday-task trials.

## Verification

- 140 deterministic tests pass, including 14 runner regression tests.
- Canonical structure and suite validators pass.
- An isolated copy installation includes the executable helper. Three actual
  runs verify completion, timeout (exit 124), and output limit (exit 125).
  [Machine-readable smoke receipt](artifacts/v1.7.0-copy-install.json) records
  the exact helper hash, platform, limits and observed results.
- Independent implementation and integration review covered process-group
  cleanup, closed pipes, signal-resistant children, fresh receipt publication,
  and fast-command deadline accounting.

The smoke ran on macOS with Python 3.14.5. CI separately verifies its advertised
matrix; local checks alone do not establish other client or platform support.
The timeout includes a finite cleanup grace, so elapsed duration can exceed the
configured execution deadline. Output forwarding occurs after child cleanup.

## Scope and limits

[Runner boundary](../BOUNDED_RUNNER.md), [first task](../TRY_IT.md), and
Trending decisions describe usage.
The research screened 435 discoveries across the collected views, then inspected
selected sources; it was not a source-code audit of every repository.

The helper requires POSIX and Python 3.11+. It bounds command execution time and
captured output, not model tokens, billing, memory, filesystem or network access.
Processes escaping the owned process group are outside its cleanup guarantee.
A blocked downstream output consumer can delay receipt publication.
No comparative model-quality, token-savings, universal client compatibility or
security-sandbox claim follows from these checks. Previous model evaluations
remain historical evidence and were not rerun or relabeled as v1.7.0 results.

The GitHub release record identifies the published source commit. Website and
scheduled-post publication require their own live readback after release.