← taskplaneCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to taskplane
Snapshot Sep 30, 2026 · 23:13 UTC · version 2.31.5
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "tp-status",
"description": "Show delivery progress, the responsible owner, actual outcomes, and available token usage without initializing a workflow.",
"included_files": [],
"skill_md_contents": "---\nname: tp-status\ndescription: Show delivery progress, the responsible owner, actual outcomes, and available token usage without initializing a workflow.\n---\n\n# Delivery status\n\nUse current task context first. For recorded delivery, invoke the installed\n`taskplane/tp.py flow report --workspace <checkout>` once. Show the orchestrator\nas owner, the latest meaningful milestone, actual verification, remaining work,\nand useful token or waste observations. An advisory is not a blocking gate.\nMissing usage means unknown, not zero. A recorded milestone is not proof that\nacceptance criteria passed; check the cited evidence when making that claim.\n\nDo not start a flow or mutate evidence to answer status. Distinguish work produced,\nevidence validated, human or policy approval, stale state and legacy unverified observations.\nShow workflow_available separately from authority_verified. Native workflow gates\ncan be active with host protections unavailable; capability_blocked applies to an\nexplicit protected_host request without a verified integration.\n\n## Shared delivery state\n\nFor an active delivery, follow [the shared flow](../tp-go/references/shared-flow.md).\nUse its existing run, task decomposition, dependency graph and dashboard. Return\nevidence to that run; the root orchestrator owns stage advancement.\n\nShow native discovery separately from protected storage, human origin, tool\ncontainment and process revocation. A plugin version or observed hook is not\nproof of those capabilities; an unavailable native owner stays unverified.\n\nSelect the current task’s run explicitly when available. Report approval mode, policy\nversion and pause reason, current visit versus run tokens, unknown/unallocated usage,\nsnapshot timestamp and graph freshness. Never equate old tab contents with current state.\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"
}SHA-256: 93e6a6b539accb03f595ed683358c5668f7cb924060ee194fd914ca142c1e9d2