A workflow stage's question reached Decisions with `Workflow run: <uuid>; stage: <uuid>` appended. The question is the card's bold title, so every card ended with two UUIDs that pushed the choice out of view. Members can't do anything with those ids, and Chat's run card already shows which run is waiting on Decisions.

## What changes

- `apps/server/src/harness/atomic/human-input.ts`: cards show the question exactly as asked. Pause holds still use the run id, so a paused run keeps its answer until it resumes. - `human-input.test.ts`: the label test now checks that cards carry no run or stage id. The length-limit test checks that a near-limit question is stored as asked. - `docs/hosted-agent.md`: describes the new card text.

## Verification

- `bun test apps/server/src/harness/atomic`: 52 pass, 0 fail. - `bun run types`: all workspace checks pass. - `bun run ci`: dprint, oxlint, tokens, design contract, design record, and Impeccable pass, with no new findings. - Not run: a live workflow question in the browser.

Assistant-workflow: inline Assistant-duration: 4m converged, estimated 15m Assistant-verification: bun test passed: apps/server/src/harness/atomic (52 pass, 0 fail) Assistant-verification: bun run types passed: all workspace checks Assistant-verification: bun run ci passed: no new findings User-preference: Workflow questions in Decisions should not show run or stage ids Co-authored-by: Alex Lavaee <lavaman131@github.com>