Huddle v0.5.0

Added

• /huddle-continue <n> (Issue #83): continues an Issue that was already started after the AI Manager answered it (a review or a decision).
  It enters the Issue's worktree, takes the pending request and follows it, so the developer no longer copies the prompt by hand.
  /huddle-start <n> now only starts (on an Issue that is already started it says so and continues it anyway, so old prompts keep working),
  and the first line of the AI Manager's prompts says First run /huddle-continue <n>. No new CLI command.

• huddle update and /huddle-update (Issue #81): bring a repo that already has Huddle to the installed version in one step, and ask
  only the questions a new release added. huddle.json gets setup_version; new questions come from a registry
  (lib/setup/questions.mjs, empty in 0.4.x) and are never asked twice. huddle update [--check] [--dry-run] [--json] [--answer key=value]
  needs no login and no network, changes nothing and exits 3 while a question is unanswered. huddle doctor has a setup line, and the
  update notice for the AI Manager now says /huddle-update.

Fixed

• in progress and in review no longer sit next to needs decision or changes requested from AI Manager (Issue #85). Those two are stop labels: while one is on, the labels job shows only it, and the usual status comes back by itself once the request is taken or the question is answered. A pending request now has no status label with or without an open PR.

• /huddle-setup no longer asks the initial questions again in a repo that already has a valid huddle.json (Issue #79). The skill
  now reads huddle.json first: a valid file means a refresh that asks nothing (the block and the templates are updated, and the report
  says what changed and which templates were kept because the project edited them); a missing or incomplete file is asked only for the
  fields that are missing; a first install still asks all five. The CLI already worked this way; only the skill's text was wrong.