Ticket graphs

Self-repopulating successor (the #196 pattern: append-only governance means a ticket cannot reopen, so the work perpetuates by spawning its successor). UNIT KEY : go-port:successor:tag::g2 CHAIN : tag: GENERATION : 2 21 congruency-go port unit(s) matching --subset tag: are still un-ticketed. Run the decomposer again to file the next batch of at most 12, in dependency order (db #224 -> server #225 -> tags #226): python3 checkouts/current/congruency/tools/go_port_decomposer.py --file-tickets --batch 12 --gen 2 --subset tag: The `--gen 2` pins the run to THIS ticket's generation, so it will not mistake this very ticket for a successor someone else already filed; it then spawns generation 3, and the chain continues after this ticket settles. DROPPING THE FLAG DOES NOT KILL THE CHAIN (it used to — see #245). With no --gen the decomposer DERIVES its generation from the queue: the highest OPEN successor of this chain is normally this very ticket, so a plain `--file-tickets --batch 12` reaches the same conclusion and spawns the next generation anyway. Keep the flag regardless — it is what makes a run started from a STALE copy of this line (one the chain has already moved past, because a NEWER successor is open) correctly DECLINE, instead of adding a redundant successor. It is idempotent: it re-files nothing already ticketed. Run it with no flags first (and no --file-tickets) to see the enumeration without writing anything. A stop ticket aimed at this chain is the brake. Filed mechanically by checkouts/current/congruency/tools/go_port_decomposer.py under ticket #230.

— browse congruency source (forge-parked tree)