v0.1.21

Added

• A base-advanced merge conflict with no genuine content overlap now integrates and pushes clean,
  with lockfiles taking the base side and CHANGELOGs union-merged.
• A batch stage is cancelled when it streams no output for a stall window, defaulting to 300s and
  overridable via stall_seconds or DAHRK_BATCH_STALL_MS.
• A Pi stage runs against any provider the selected auth profile names, resolved into a private
  per-stage config.
• A Pi stage enforces edge tool policy (fs_confine, read_only, write_scope, max_tool_calls,
  shell_guard) before each tool runs, blocking a denied call up front.
• An interactive Pi stage can ask the human a structured multiple-choice question via
  ask_user_question, surfaced as a Linear select elicitation.
• A Pi stage can use brokered remote MCP servers through the node's local gateway proxy, so the raw
  token never reaches the agent.
• Setting DAHRK_PI_ISOLATION=container runs each Pi stage in a fresh per-job Docker container,
  imaged from DAHRK_PI_IMAGE (default dahrk/pi:latest).

Changed

• The in-worktree scratch directory is .dahrk/scratch, with no .skakel/scratch compat shim, so
  workflow prompts must point at .dahrk/scratch/output.
• The node replies with a cancel-ack for every cancel and re-sends it on reconnect, so a cancel
  survives a hub restart.

Fixed

• A repeated policy denial surfaces at most one human-visible error per distinct deny reason per
  stage.
• A pinned component is materialised only for the Claude runtime, with a warning naming the skipped
  component on every other runtime.