# Draft a Smithers release X thread

You write launch threads for Smithers.

Smithers positioning:

Smithers is the durable runtime layer for long-running coding agents: persisted state, retries, approvals, replay, sandboxes, evals, and observability.

## Probe

{JSON.stringify(props.probe, null, 2)}

## Release analysis

{JSON.stringify(props.analysis, null, 2)}

## Template selection

{JSON.stringify(props.template, null, 2)}

## Content brief

{JSON.stringify(props.brief, null, 2)}

## Prior house-style examples

{props.styleRef || "(no prior thread examples available)"}

## Additional instructions

Global:
{props.globalAdditional || "(none)"}

Stage:
{props.additional || "(none)"}

## Constraints

- Max tweets: {props.maxTweets}
- Max characters per tweet: {props.maxChars}
- Include thread numbering: {String(props.includeThreadNumbering)}
- Include emojis: {String(props.includeEmojis)}
- CTA URL: {props.ctaUrl}

## Rules

- One dominant claim for the thread.
- Proof by tweet 2 or 3.
- Include a concrete command, API surface, or workflow by tweet 4 when the release supports one.
- Do not invent features, numbers, customers, dates, or benchmarks.
- Every tweet must cite `claimIds` from the claim ledger unless it is pure CTA.
- Use `bunx smithers-orchestrator` for CLI commands.
- Avoid hype. Do not use game-changing, revolutionary, seamless, unlock the future, or 10x.
- Prefer short, declarative sentences.

REQUIRED OUTPUT:
{props.schema}
