anchors done

Close claimed task(s) (moves to the .anchors/done/ history).

Marks task(s) as done: they leave the live queue and go to .anchors/done/.
The worker calls this AFTER finishing the step and 'anchors check' passing.

Closing in BATCH, because the real queue grows faster than the work:

  anchors done --file src/pricing.ts    every task of that file
  anchors done --kind spec              every task of one kind
  anchors done --all                    the whole queue

The watcher queues by CHANGE, and one stage touches several files: in a real round
the queue reached 26+ tasks for 8 deliveries, and closing them one by one made the
orchestrator give up — the queue became scenery, which is the opposite of what it
exists to be.

Uso

anchors done [id] [flags]

Flags

Flag	Padrão	O que faz
--all		close the entire queue
--file		close every task of this file
--kind		close every task of this kind (spec|code|feature|test|change…)
--root	.	project root

A fila de trabalho — família

Comandos da mesma família — o que distingue cada um:

Comando	O que faz
anchors next	Pull and claim the next item from the queue (the worker calls this)
anchors queue	List live tasks (the work the watcher queued)
anchors work	Emit the work prompt of a stage (spec|code|feature|test|review) for a target
anchors done	Close claimed task(s) (moves to the .anchors/done/ history)
anchors drop	Discard a task from the queue without completing it (removes; does not archive)
anchors reclaim	Return to the queue the tasks stuck in claimed (dead worker)
anchors deliver	Record the delivery of a stage — the review trigger
anchors decided	Release the card escalate --for-user stopped, once the decision is made
anchors discard	Take off the board the card that no longer makes sense, without deleting it
anchors unblock	Open the work card that unblocks a card stuck in needs-user
anchors escalate	Open the issue for a change needed in the plan or the spec
anchors report-bug	Report a bug in Anchors itself at github.com/co2-lab/anchors
anchors synthesize	Two PRs conflicting in CONTENT become a synthesis card
anchors watch	The background watcher: sees changes and QUEUES work
anchors monitor	Watch the project’s long processes: one line when one starts, stalls, dies or ends
anchors flow	Operate the work flows (the puzzle of actions and results)
anchors board	The project board — published by the pipeline, or served live