Huddle 0.4.0

Added

• A notice when a newer Huddle exists, and auto-update (Issue #65). The SessionStart hook compares the installed version
  (.claude-plugin/plugin.json in the plugin folder) with the latest GitHub release (releases/latest, unauthenticated,
  3 s timeout, cached 24 h in Claude Code's data folder). When the release is newer (a pre-release never counts) it prints
  one block, at most once a day, that tells the session to say it first in the person's language: the two commands, or
  «pull your clone» when running with --plugin-dir, and the link to the release. The AI Manager's block adds «run
  /huddle-setup on a branch in each repo». Any failure (no network, HTTP error, bad JSON, slow answer) is silent.
  huddle doctor has a version line (✔ latest, ⚠ behind with the commands, ⚠ could not check). A new test fails when
  the newest released section of CHANGELOG.md is not the version of plugin.json, package.json and marketplace.json.
  Docs: «Updating Huddle» in the team guide, and a «turn on auto-update» step (🙋 Only you) in the first-day guide.
  /huddle-setup does not write autoUpdate in the project settings: it could not be proven in a sandbox (see the PR).

• The website home as a parallax scrolling landing page (Issue #61). site/index.html tells the story in eight scenes: a hero with
  depth layers, five sessions that drift apart and snap into order, the pinned label flow (one Issue card travels ready,
  assigned, in progress, in review and merged and takes both side roads), the four steps scrolling sideways, the two
  roles, GitHub and GitLab, a terminal that types the install commands with a Copy button, and the FAQ with a final call.
  Motion comes from GSAP 3.15.0, ScrollTrigger 3.15.0 and Lenis 1.3.27, vendored in site/vendor/ with their licences
  (no CDN, no npm dependency) and one deferred script, site/js/landing.js. All text stays in the HTML: with no JavaScript
  or with prefers-reduced-motion: reduce the page is a normal readable document, and on a phone the effects are lighter.
  Only transform and opacity are animated. Lighthouse on the home page, mobile: Accessibility, Best Practices and SEO 100,
  Performance 95. The site test checks the vendored files, local deferred scripts, the eight scenes and the reduced-motion rule.

• Design Issues, worked in a Claude Code session with Claude Design (Issue #58). A new Design Issue template for GitHub
  (.github/ISSUE_TEMPLATE/design.md) and GitLab (.gitlab/issue_templates/Design.md), installed by the setup skill, with the
  design label (created by huddle labels when missing). It keeps every section the labels job reads, so a Design Issue
  goes ready / assigned / in progress / in review like a task, and adds Screens, For whom, Visual guide, Content and
  Deliverable; its allowed files are always design/<issue number>-<slug>/. /huddle-issue writes it; /huddle-start
  creates the design with Claude Design, polishes it only through the chat, and on «ready» saves README.md, design.html
  and screens/ in design/<n>-<slug>/, opens the PR and closes, with each round a new commit; /huddle-review checks a
  design PR (screens, content, visual guide, contrast, phone width, never tests) and offers the follow-up «Build
  from design #N» Issue. Docs: «If you are a designer» in the first-day guide and «Design tasks» in the team guide.

• The Huddle website on GitHub Pages (Issue #56), at https://srprofessional.github.io/Huddle/. A static site in site/
  with no build step and no dependencies: home (the problem, the four steps, the label-flow diagram as inline SVG, GitHub
  and GitLab, the install and a FAQ), «Get started», «How it works» and a 404. Each page has its own title and
  description, a canonical link, Open Graph and Twitter tags; the home page has JSON-LD SoftwareApplication. The site
  also has sitemap.xml, robots.txt, a favicon and the 1200 × 630 share image og.png with its source in site/og/.
  Light and dark, readable on a phone, keyboard focus visible, no trackers. .github/workflows/pages.yml deploys it from
  main when site/** changes, and on a manual run, with pinned actions. test/site/site.test.mjs checks every page. The
  README opens with the words people search for and links the website with a badge.

• Bugs are their own Issue type, and the skill /huddle-bug writes them (Issue #55). /huddle-setup installs a Bug template
  (bug.md on GitHub, Bug.md on GitLab: a bug block, then every Task section) and, on GitHub, a Bug report form
  (bug-report.yml) for people who are not the AI Manager. huddle labels creates the labels bug and needs triage.
  An Issue with needs triage never gets ready or an assignee, and a blocking Bug is assigned before every other ready
  Issue. /huddle-bug (AI Manager only) takes a plain description or #N of a raw report, investigates without changing
  anything, checks duplicates, sets the severity and waits for the AI Manager's OK. The team guide has a «Reporting a bug»
  section.

Fixed

• The four steps on the home page had no side margin on a phone, with prefers-reduced-motion: reduce or with JavaScript off
  (Issue #63): only the pinned wide-screen rule gave the list a margin. The plain .steps rule now uses --gutter like
  .wrap; the pinned sideways scene is unchanged. The site test checks that rule and that every block of a scene outside
  .wrap has a --gutter rule, so the next section cannot repeat the bug.