Run the board reconcile twice, because adds and Status cannot land in one pass

[rocklambros]

Follow-up to #157, fixing a defect I found by testing the merged workflow rather than one a reviewer would have caught from the diff.

The defect

A reconcile run that adds items cannot also set their Status.

Adding an item triggers project 9's own Item added to project workflow, which stamps a default Status asynchronously. apply_governance.py builds its entire plan before executing any of it, so on a run that adds anything it has already decided the Status actions before those items exist on the board. The default lands after the run finishes and nothing corrects it until the next run.

Measured, not theorised

On the 2026-09-17 backfill the first pass made 40 adds and 1 Status change. A second pass run immediately afterwards found 5 more Status corrections waiting:

Item	Why the default was wrong
#135	status:accepted
#131	status:accepted
#126	open pull request, belongs in In progress
#113	open pull request
#112	open pull request

None of those five has the default as its correct Status, which is precisely the population a single pass strands. A third pass reported zero actions, so the tool converges, it just cannot converge in one run when it is also adding.

Nightly, that is up to 24 hours of a board reading Needs triage for work that is accepted or in flight. That is the failure the board exists to prevent, so shipping #157 without this would have left the automation quietly wrong in the one case it most needed to be right.

The fix

Run the board step twice under --apply. The dry-run path still runs once and returns, since printing the same plan twice helps nobody.

The reconciler is idempotent, so the second pass costs one API listing on a run that added nothing. Once Auto-add to project is enabled on the project, that is every run.

Note on review

I did not admin-merge this one. #157 was merged under the administrative authorisation given for it specifically, and extending that to a second change on my own judgement is the kind of thing that should be asked for rather than assumed. The workflow is inert until the App and environment exist, so there is no urgency in merging this ahead of a normal review.