Update to taskplane

{
  "name": "tp-build",
  "description": "Build a requested feature through to verified output. Reuse existing product decisions and use optional alternatives only when requested or needed.",
  "included_files": [],
  "skill_md_contents": "---\nname: tp-build\ndescription: Build a requested feature through to verified output. Reuse existing product decisions and use optional alternatives only when requested or needed.\n---\n\n# Build a feature\n\nBefore substantive work, resolve this installed plugin's runtime and run\n`flow activate --workspace <checkout> --phase tp-build --request-reference <actual-user-request>`.\nInspect `flow report`: reuse the matching active visit or initialize the appropriate\nscoped run before continuing. This requirement includes standalone work and resumed\nstages; loading a skill alone grants no phase approval. See the shared flow for\nbootstrap, native dashboard handoff and legitimate user waits.\n\nRead [delivery](../tp-go/SKILL.md) and execute its flow. The root orchestrator\nowns completion. Clarify the outcome, inspect the existing implementation, make\nthe smallest sufficient design, build, verify, and deliver.\n\nUse a visual when it helps settle a UI decision; do not require one for backend\nwork. Discuss alternatives when a consequential trade-off needs a decision.\nBuild A/B variants only when requested, in separate checkouts, and let the user\nselect before integrating mutually exclusive variants. Do not create multiple\nimplementations or review waves by default.\n\nReuse authorization already given. Missing telemetry or a\nreview quota must not block authorized implementation. Native host permissions\nremain in force.\n\n## Shared delivery state\n\nFollow [the shared flow](../tp-go/references/shared-flow.md) for every execution.\nUse the shared run, task decomposition, dependency graph and dashboard, including\nwork originating in a standalone phase. Return evidence to that run; the root\norchestrator owns stage advancement.\n\nThe shared flow defaults to explicit human approval at each phase checkpoint.\nA recorded, explicit run policy may authorize automatic approval as described there. Use\nthe dependency graph with source component decomposition, task DAG and shared\ndashboard throughout. Unsupported host authority must be reported, never bypassed.\n\n## Consume bounded context\n\nAfter activation, start, advancement or resumption, use the installed runtime's\n`flow context --workspace <checkout> --run <run>` and consume the returned\nhandoff with `--consume <handoff-ref-sha256>`. Use `--task <current-task-id>` for\nfocused work. Read every omitted required input using `--read <ref-sha256>`;\nfollow index children and page cursors until all required bodies are returned.\nA fresh consumer receives these bodies, scoped source and relevant findings;\ndo not copy the predecessor conversation or tool history into its instructions.\nNo context operation authorizes dispatch or a phase transition.\n\nFor phase submission, obtain a current whole-phase receipt (without `--task`)\nand include the returned `context_receipt` object in the phase output. Renew it\nafter source, scope, revision or accepted input changes. New bounded/v1 runs\nreject missing, partial, foreign or stale receipts. Legacy runs keep their\noriginal evidence contract. A receipt proves returned data, not model attention.\n\nRoutine command summaries preserve the current gate and reference full details.\nExpand specific references when needed; request `--full` only for a consumer that\nrequires the complete legacy report. Native dashboards retain complete evidence.\nReuse a prior passing check only when its verification record matches current\nsource/dependency, tests, runtime, environment, command and criteria fingerprints.\nRetain failed/unknown results and findings; reuse never transfers approval.\n\n## Scoped native workers\n\nWhen authorized, use the installed native dispatch protocol: root prepares a run-bound\ntask grant, the observed worker claims its identity and consumes its own task context,\nand root verifies the joined result before satisfying dependencies. Fill observed\ncapacity with useful independent work; two is only the minimum live acceptance test.\nWorkers return evidence and cannot operate root phase controls or publish task definitions.\nRequire actual loaded-runtime and native execution evidence for live claims.\n"
}