v0.6

28 commits since v0.5. The theme is that content is opaque: the orchestrator routes and records what agents say and tools return, and never reads it.

Content is opaque. Norns.Runtime.Content is the one place content is handled, and it treats it as a blob. The orchestrator no longer composes prompts, parses responses, or decides what a run's output is — workers do, and report final_output. Adopted as decision-log.md § Content is opaque.

Keys stay on the worker. A tenant-level Anthropic key is no longer forwarded to workers. The worker owns the provider key; core never sees one.

Inbound webhooks. Token-addressed ingress with provider signature verification, so a GitHub or Slack event can start a run without a worker in the middle. nornsctl hooks manages them.

Clean shutdown. A drain event on the worker channel lets a worker finish its in-flight task and leave, instead of dying mid-call.

Smaller. GET /api/v1/workers; LLM dispatch is gard-strict, matching tools; a layout hook for embedding apps to add navigation; the provisioner is named volund and recorded as proprietary; a leading-indentation fix on run output.

Plans landed, not built: chains (ordered agent defs as tenant data) and the harness, sequenced as roadmap steps 7 and 8.

Workers want norns-sdk 0.5.0 (PyPI) or norns_sdk 0.2.0 (Hex).