Task payload and coverage

Create TSK with status backlog. Example input slots must be replaced by discovered IDs:

{"workspaceId":"<workspace-uuid>","type":"TSK","title":"Show an acknowledged offline edit","status":"backlog","body":"## Outcome\nA queued title change becomes one applied revision after reconnect.\n\n## Scope\nCommand receipt, local write acknowledgement and resulting UI state.","links":[{"id":"<spec-uuid>","relation":"specification"}],"data":{"kind":"feature","priority":"Normal","baseRef":"main","acceptanceCriteria":["Offline state remains Pending device","Reconnect applies one Markdown revision","Repeated delivery does not duplicate the write"],"checkCommands":[{"file":"pnpm","args":["test","--","replay"]}],"timezone":"Europe/London"}}

Only include a check command that the actual repository supports. Keep agent selection absent until supplied. For manager-created tasks, store dependency task IDs in data.dependsOn, the assigned role in data.role, and the target task ID in data.targetTaskId for reviewer/qa. managerThreadId and planId preserve origin. Plan proposals use local refs until approval. Also link dependencies using depends_on and attachment/selected-artifact records using appropriate relations.

Coverage ledger: spec criterion → task ref → dependency → verification → readiness. A complete plan has no requested criterion silently omitted and no cyclic dependency. Record a blocked choice in the task body/data while leaving it in Backlog.