TaskFlow v1.0.7

Added

• hooks/task next <todo-id> <next-action> [notes] — writes a Todo entry's - Next action: and - Updated: in one call, and appends notes at the end of the entry's Notes block. The fields it writes are templated from state the Agent already has, so writing them by hand only bought a full read of TaskFlowDocs/todo.md to change two lines. Missing fields are added rather than failing the write, matching hooks/archive.
• hooks/task get <todo-id> — prints one entry's field lines verbatim, so confirming an entry's state no longer means reading every entry. It is the read half of the same trade task next makes on the write side.
• hooks/repository-check — a read-only readiness summary: missing baseline governance documents and ambiguous branch/remote information are reported as needs-user-input, and any task artifact left uncommitted in the checkout is named. Opt-in; it is not attached to automatic hooks.
• A conflict rule in skills/taskflow/SKILL.md: when a merge or rebase the Agent runs hits a conflict, stop and put both sides in front of the user, who decides what to keep; the decision is recorded in the task plan.md before continuing. An automatic merge needs no action, and a conflict on a pull request merged in a hosting web UI is explicitly outside the rule.

Fixed

• The Claude Code SessionStart hook failed on every Unix installation. hooks/hooks.json invokes hooks/run-hook.cmd as a bare path, but the file was recorded in Git without its executable bit, so the host failed each session with Permission denied (exit 126) — a configured hook that could not run, and no plugin feature behind it. hooks/* and tools/fixture-compare now carry the executable bit in the index. This is the reason to update from 1.0.6.
• README.zh-CN.md said the release check compares "two plugin manifests" where hooks/release-check compares three. The count had been corrected once before, and a later conflict resolution reverted it — two sides that both read as valid Chinese, differing only in the number.
• The awk program in hooks/task could be broken by an apostrophe in a comment: macOS ships bash 3.2, whose parser rejects that shape inside a heredoc that is itself inside a command substitution, and it reports the failure against the end of the substitution rather than the comment.

Compatibility

• No runtime or installation change. The hook set, the plugin wiring, and the POSIX-shell-plus-awk floor are unchanged from 1.0.6; updating an existing installation needs no migration and no dependency installation.
• task next and task get are additions, not changes. They are new explicit subcommands; the existing intake / promote / state / progress / complete lifecycle is unchanged, and a task that never calls them behaves exactly as before.
• The conflict rule hands control back to the user. On a conflict you decide which side to keep, so a merge that hits one stops and waits. Only merges the Agent runs are covered; a pull request resolved in a hosting web UI is not.
• A release is two commits by construction. The marketplace pin names a commit that cannot exist before the tag does, so the pin lands as a second commit after the tag. Claude Code verifies the pin at install time and refuses a mismatch as sha_pin_mismatch; it clones by the pinned commit rather than by the tag, which is what keeps an installation on the reviewed release if the tag is ever moved.

Verification

• bash hooks/smoke-test — passed on Ubuntu, macOS, and Windows GitHub Actions runners.
• bash hooks/release-check . — passed.
• python3 evals/runner.py — passed.
• TaskFlow Skill validator — passed.