Skip to content

v0.31.0 — Native emulator queries and durable incident evidence

Choose a tag to compare

@alextitov19 alextitov19 released this 11 Oct 05:54
48fe017

This release fixes Android emulator listing classification and improves diagnosis of queue waits, cancellations and compiler memory use.

  • Exact emulator listings remain lightweight. Real boots still require admission.
  • Agent feedback distinguishes explicit waits and compound heavy execution from independent inspection.
  • Private analytics retain bounded cancellation/action evidence and job checkpoints for up to 90 days, prioritize incident decisions, and support tool-call selection without publishing identifiers or commands.
  • Long waits include observed blockers and finite-slot occupants. Learning reports distinguish missing coverage from usable measurements; release comparisons include matching workloads.
  • Direct local Node/TypeScript invocations support bounded compiler profiles. Sampling-only retries are shorter without relaxing freshness or pressure checks.

Memory limits and termination policy are unchanged. A TypeScript process over the configured cap still needs a smaller workload; prediction is not an exemption. The initiating sender of historical cancellation #403 remains unknown and that issue stays open. New report #408 concerns Claude's worktree guard rejecting a managed heavy wrapper before execution. New report #410 describes a v0.30 heavy-work wait with recorded slot/headroom blocking. Both remain open and are not claimed fixed here.

Existing jobs keep their loaded runner until completion. Stable hooks use the new installation on subsequent calls. No profile edit or engine restart is required. If analytics is enabled, refresh its collector with launchctl kickstart -k gui/$(id -u)/com.memcap.analytics.

Validation: 658/658 Bats tests passed both normally and with isolated HOME/no Docker; grouped and individual shellcheck and all 27 Bash parse checks passed. The pre-release baseline is saved locally. Production performance gains will be assessed after comparable workloads run; this release does not claim a measured latency improvement yet.