v0.9.0

Added

• /craftsman:orchestrate <task>: a slash command for the full pipeline. The orchestrator was the
  only major entry point without one, so it never appeared in the / menu — every other command
  (init, quick, doctor, review, security) did. It runs the orchestrator's discipline in
  the main thread rather than dispatching the agent as a subagent, for two reasons:
  orchestration is subagent dispatch and nesting that is unreliable, and the ideation gate needs
  interactive Q&A that a subagent cannot hold (as a subagent, orchestrator must bounce
  underspecified features back to its caller). @craftsman:orchestrator still works for running
  the pipeline in its own context.

Fixed

• Agent invocation is documented as @craftsman:<name> throughout. Plugin agents are namespaced,
  so the bare @<name> form the docs taught — @orchestrator in both READMEs, docs/use-cases.md,
  and the ideation-first skill — matches nothing in the agent picker, making the orchestrator look
  like it wasn't installed. Note: craftsman-demo.svg still shows @orchestrator in its rendered
  terminal text; correcting it requires regenerating the asset.