anchors synthesize

Two PRs conflicting in CONTENT become a synthesis card.

Opens the card that asks for the synthesis of two conflicting PRs, and closes both.

A content conflict is not resolved by automation: two agents wrote different things
about the same rule, and picking a side is choosing without reading both.

What this command does is give the wait an OWNER. The new card asks for what neither of the
two PRs delivers alone: the best of each, in a result better than both.

    anchors synthesize --pr-a 693 --pr-b 556 --files Dashboards.spec.md

TRACEABILITY is the point: the card cites both issues and both PRs; the issues
get a comment pointing to it; the PRs are closed saying where the work
continued. Nothing is lost.

Usage

anchors synthesize [flags]

Flags

Flag	Default	What it does
--dry-run		show the card without opening or closing anything
--files		the files where the conflict is, comma-separated
--pr-a		the first PR in conflict
--pr-b		the second PR in conflict
--root	.	project root

The work queue — family

Commands of the same family — what tells each apart:

Command	What it does
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