v0.4.2 — the skill asks which template

Fixed

• The skill never asked which template to use. Three templates besides
  next have shipped since 0.3.0, and the skill documented all four — but only
  as an optional --template flag on scaffold, with next as the stated
  default and nothing telling the agent to raise the choice at all. Its
  description named Next.js and nothing else. Both together meant every run
  scaffolded next silently, whatever the surrounding project was.

  Choosing the template is its own step now, ahead of agreeing the page, with
  the trade-off spelled out per template — because the choice decides which
  files every later step touches, and is expensive to change afterwards.
  scaffold is documented as taking --template explicitly, even for next.

  Skill file only. The CLI already accepted all four names and still does.

• Three version numbers disagreed about which release this is. The plugin
  manifest still said 0.3.0 and the skill's own metadata still said 0.1.0, both
  left behind while package.json moved. All three read 0.4.2 now, and a
  release bumps all three from here.

  The package.json inside each template stays at 0.1.0 on purpose: that is the
  version of the site somebody scaffolds, not of the tool that scaffolded it.