The publisher switched branches in place and carried its own file into a bee branch #4499

What is wrong

#4338 passed every required check and could not merge:

CONFLICT (add/add): Merge conflict in tools/queen/publish.py

Its issue's boundary named one spec. The publisher ran from a checkout carrying its own copy of publish.py, git checkout -B switched branches in place, and the file travelled into the bee's branch.

A second trap turned up on the next publish (#4498): the bee's branch adds a workflow, and a new workflow moves the census and the gate-topology ledger — both have turned master red before (#4303, #4319).

Acceptance criteria

• 1. grep -c 'worktree' tools/queen/publish.py prints at least 2 (today: 0)
• 2. grep -c 'adds_workflow' tools/queen/publish.py prints at least 2 (today: 0)
• 3. python3 tools/queen/publish.py --self-test prints a line beginning ok:

Boundary

tools/queen/publish.py