0.43.0

Configured thinking effort now reaches interactive dispatches

Per-agent effort in dev-team-config.json only ever took effect on the scheduled Index pipeline, which passes --effort on the CLI. A sub-agent dispatched from a live conversation took its effort from the calling session, and the configured value did nothing. The Agent tool exposes no per-invocation effort parameter, so the setting had no way through.

Agent frontmatter is the lever that reaches both paths. Verified against the Claude Code 2.1.268 binary: the agent frontmatter schema accepts an effort field, and the enum its runtime checks is low|medium|high|xhigh|max.

What changed

• Lestrade, Holmes, and Watson carry their configured effort in frontmatter.
• Setup gains a step that stamps the values from dev-team-config.json into the installed plugin's agent frontmatter. It runs whether or not you register the scheduler.
• Removing an effort key from the config removes the frontmatter line, so the CLI path and the frontmatter path are never left holding different values.
• An unrecognized value is refused rather than written. The harness normalizes it to "no override", so writing it would configure nothing while looking configured.
• The orchestrate skill and the README no longer tell the reader that effort cannot reach interactive dispatch.

Upgrade note

Re-run /workbench-dev-team:setup after updating. The stamping happens at setup time, so the configured values do not reach your installed copy until you do.

The shared JSON config stays canonical for the values. One edit still moves both paths: the scheduled one on the next tick, the interactive one at the next setup run.