v0.30.0

iCode v0.30.0 brings background command management, new hook tools, clearer diagnostics, and improvements across the TUI, ACP, and session storage.

• Background shell commands: Commands that reach their timeout can keep running while the agent continues working. Quiet commands and commands with surviving child processes can also move to the background, with up to 32 running at once.
• Background task controls: Press Ctrl+T to background the main agent’s running commands. Inspect live output and stop commands from Tasks → Background Tasks. Session changes, quit, and relevant rollbacks ask before stopping them; startup can detect commands left behind after a crash.
• Hook inspection and validation: icode hook list shows which hooks would load. icode hook validate [path] reports configuration problems with file and line details without executing hooks. Both support --json.
• Consistent CLI commands: Help now uses singular names such as icode agent, model, approval, and workflow. Plural aliases remain supported, and these commands plus hook default to listing when no subcommand is supplied.
• Clearer trajectory insights: F12 findings explain causes and effects with concrete examples. Improved retry accounting, repeated-read detection, change verification, and sub-agent metrics reduce misleading findings and unresolved values.
• Terminal tab status: Workflow tabs now show the workflow title and progress. Chat and workflow tabs indicate approval or question waits (?), retry decisions (!), completion (✓), and failure (✗).
• Better request tracing: HTTP attempts and provider request IDs connect model replies to trajectory events and raw logs. Stable tool operation IDs connect recorded file changes to tool calls.
• More reliable input handling: A hook-rejected message submitted during a run returns to the input box while the agent keeps working. Arrow keys navigate wrapped prompt lines before recalling history, and cancelled questions no longer leave stale dialogs.
• Provider and ACP fixes: Chat Completions streams remain a single reply when gateways change chunk IDs. ACP approval requests now reference the main-agent tool call already displayed by the client.
• Broader file compatibility: Configuration readers support common legacy encodings and BOM-marked UTF-16/UTF-32. Configuration and session folders work through symbolic links, Windows junctions, and macOS exFAT storage.
  For consumers of trajectory exports, repeated-read replaces repeated-tool-fingerprint; findings also include additional detail fields.