kami
09e572f11e
Found by reading .orchestra/launch.md on the first burn-in task. The rendered context said `Acceptance: Not stated.` and carried the issue title as the whole goal, because Gitea.event parsed the issue body and then dropped it from the TaskCreated payload. The body is the task's own statement of what it wants, which every rendered context ranks above continuity and below only a human decision. The store already reads `description` from TaskCreated; only the provider was silent. Every Gitea-sourced task so far has therefore run on its title alone. Classify as an authority bug, not a model-following failure: no agent could have known what it was not told. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>