v3.0.0 to v3.0.0

4 added, 0 removed. Audit A to A.

---

name: cf-sync

description: "Synchronize process-first task Status and inline Receipts without inventing proof. Use when: Invoke after implementation or verification changes a task's real state, or to audit a feature packet for drift."

user-invocable: true

when_to_use: "Invoke after implementation or verification changes a task's real state, or to audit a feature packet for drift."

category: utilities

keywords: [sync, state, tracking, consistency]

metadata:

author: haposoft

version: "3.0.0"

---

# Sync — file-state synchronization

Synchronize only observed state. For the primary process-first layout, the single `Status:` field and inline `## Receipt` in each flat task file are the state. Never infer proof, approval, review independence, or product readiness.

## Commands

```text

$cf-sync <feature> <task-NN-slug.md> in_progress

$cf-sync <feature> <task-NN-slug.md> blocked "reason"

$cf-sync <feature> <task-NN-slug.md> done

$cf-sync <feature> <task-NN-slug.md> sync-finalize

$cf-sync audit <feature>

$cf-sync rebind <feature> [<task-NN-slug.md>]

$cf-sync

```

Resolve one regular direct-child task inside `specs/<feature>/`. Reject path escape, symlink, ambiguity, missing `plan.md`, duplicate Status fields, and unsupported status values.

## Task synchronization

- Read the task Outcome, Acceptance, Dependencies, Verification Plan, current Status, and Receipt before editing.

- Starting or resuming changes only Status to `in_progress`. Update only checkboxes whose implementation is real.

- Blocking changes Status to `blocked` and records a concrete blocker; it does not create proof.

- Done requires a current inline Receipt with `Verification: PASS`, exact Command, `Exit: 0`, runtime-bound Base/Head, non-empty fenced output, and any required negative/reachability/artifact proof.

- Write or replace the Receipt before changing Status to `done`. Missing, stale, contradictory, placeholder, failure, or zero-test evidence keeps the task `in_progress` or `blocked`.

- Re-read the file after the surgical edit and confirm exactly one Status and one Receipt section.

`sync-finalize` is the only promotion path for `FLASH_UNVERIFIED`. It requires fresh canonical PASS proof, revalidates Base/Head and artifacts, clears the flash blocker, then derives `done`. Caller-supplied promotion booleans and a marker alone have no authority.

## Audit

Scan only `specs/<feature>/task-*.md` beside `plan.md`. Compare plan task rows, task filenames, dependencies, Status, acceptance mapping, and Receipts. Report missing files, unknown rows, cycles, duplicate fields, done-without-proof, proof-on-unfinished-task, and overlapping ownership.

An audit writes nothing until the user confirms the named changes; then repair deterministic formatting drift only and never pick a winner in a semantic conflict. Read `references/rebind-and-audit.md` before a rebind, a bare call, or a file report, and `references/sync-protocols.md` for surgical update and audit rules.

## Docs impact

When a task becomes done, report `Docs impact: none|minor|major`. Create no docs work for `none`; update only affected existing docs for minor or major.

+ ## Gotchas

+ - **`provenance` fails on a done task after a small edit.** A done task file that matches its committed copy, or was never committed, has its Receipt checked on structure alone; changing a committed file afterwards, even a typo or a checkbox, binds the Receipt to the live Base and Head again, which a Receipt written before that commit usually no longer matches. Leave committed done tasks as they are, or run `$cf-sync rebind <feature> <task-NN-slug.md>` after the edit.