io-cli 0.2.0 — release

[aakashpawar1999]

Release PR for io-cli 0.2.0. develop is byte-identical to the sealed feat/0.2.0 tree — verified with git diff --quiet feat/0.2.0 develop immediately before opening this, because a dependency merge landing above the feature merge has twice shipped a tree the record did not describe.

What ships

The operator can see the boundary the agent is working under, change it, and answer it when it asks. Through 0.1.0 and 0.1.1 the approver handed to io-harness was DenyAll, so the ask before writes posture declined every write and every command it was named for. That dead end is closed.

• An interactive approver, an overlay that cannot scroll away, three answers on keys and on arrows.
• Shift+Tab cycles the permission posture; the status line names the one in force.
• A refusal prints its rule and its layer — and says the tier default decided when no rule named the action.
• Three more status fields: tokens, context pressure, containment as mode and backend.

Gates

• cargo test — 140 passing, 0 failing, 7 ignored by design, across 25 test binaries.
• cargo fmt --all -- --check, cargo clippy --all-targets -- -D warnings, cargo build --release — all exit 0.
• All 8 CI checks green on the sealed commit 3044736, across macOS, Linux and Windows.
• A sabotage arm for every functional criterion, each failing only its own criterion's tests.
• F10 completed by the owner at a real terminal: a write approved, verdict working! approved.
• Live rehearsal against a real provider: the approve path lands the write, the deny path leaves the file byte-identical, and allow this session collapses three questions into one inside a turn.

Recorded, not hidden

The record carries twelve known limitations. The two that change what the release promised:

Spend against the tree ceiling is not in the status line. EventKind::SpendDraw is emitted only by a contained turn, and io-harness's contained entry point takes no steer inbox — rendering spend would have cost Ctrl+C. The roadmap moved it to 0.8.0, the fleet release, which is contained by definition.

The overlay shows a write's proposed content plainly, not as a diff. The harness hands an approver the resulting file rather than a patch, so the diff is io-cli's to compute and 0.3.0's to design.

The sealed record and its lock pin ride the feature branch and merged with the code, so the seal precedes the tag that cuts the Release. mode: published describes the channel this product has: a GitHub Release with four cross-compiled artifacts and SHA256SUMS, and no registry.