anchors backfill-labels

Write into open issues the links the new version began to mark.

Recovers the link `anchors:blocked-by-<n>` on the cards that stopped before
it existed.

The `escalate --for-user` marks the origin card with `blocked-by-<n>`, and the ones that
stopped before only have the `needs-user`: the board says they are waiting and does not say for whom.

The link is recoverable because the NEW card always carried `anchors:under-<n>` with the
number of the origin card — the relation exists in the opposite direction, and this
command writes the one that was missing.

A card in `needs-user` with nobody pointing at it is NOT touched: inventing a
blocker would make the claim hold the card for a decision nobody linked to it.

    anchors backfill-labels --dry-run    # shows what it would do
    anchors backfill-labels

Usage

anchors backfill-labels [flags]

Flags

Flag	Default	What it does
--dry-run		show what it would do, without touching anything
--root	.	project root

Changelog and pull requests — family

Commands of the same family — what tells each apart:

Command	What it does
anchors changelog	Build the technical changelog from the commits, release by release
anchors commit-msg	Confront the commit message with the format the changelog will read
anchors pr-body	Write the lines linking this work’s cards, in the platform’s syntax
anchors backfill-labels	Write into open issues the links the new version began to mark
anchors report	Generate reports in docs/ by perspective (cuts of what Anchors measures)