Release v0.2.0

[delexw]

Release v0.2.0, cut with the cut-release skill (baseline v0.1.0, 11 commits since; highest tier feat: → minor bump).

Version bump (lockstep, version-only diff)

• package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json → 0.2.0
• package-lock.json, src-tauri/Cargo.lock regenerated

CHANGELOG ## [0.2.0] — 2026-06-16

Added — inline assistant commentary (#116), image file paths from Codex v0.138.0 (#129), archived-session awareness from v0.136.0 (#132).
Fixed — raw exec output no longer fakes tool-call metadata (v0.133.0, #133); JSON-object function_call arguments no longer dropped (v0.139.0, #130); --output-schema final answers display (v0.132.0, #131); versioned memory summaries parsed (v0.132.0, #128); close_agent→interrupt_agent recognized (v0.139.0, #127).
Changed — detail-view fonts use fixed px (#116).

All 11 source PRs were authored by the maintainer (delexw), so no contributor attribution lines were added. chore(deps) PRs (#117–#119) were skipped per skill rules.

Verification

npm run check green (tsc + oxlint + oxfmt + clippy + cargo fmt + vitest + cargo test). The CHANGELOG heading matches the exact ## [X.Y.Z] — YYYY-MM-DD format the release pipeline's notes job requires.

How to publish after merge

This session can't push tags/main (sandbox restriction), so the tag isn't pushed here. Once merged:

• Tag-driven (full build): push v0.2.0 → runs guard → notes → macOS/Linux/Windows build → publish; or
• Manual (no artifacts): run the Release workflow via workflow_dispatch with version 0.2.0 — the manual-release job tags v0.2.0 at main and publishes the GitHub release from the CHANGELOG. I can trigger this for you via the GitHub API once merged.

https://claude.ai/code/session_01FLcTQTp5efCHTgWrpbYf64

---

Generated by Claude Code