Node-target automation display and control issues

Found while driving Task 9901's live checks on dev (Org B, win-t8703) through a node-target automation. - A task the automation has just filed in the Nodes system project shows "Waiting · Its slot could not be built" on the board for its first seconds, before it starts normally. Show "Queued" (or the real dispatch state) until a slot build has actually failed. - "Run now" is disabled while the automation is paused, so a one-off manual run means Resume → Run now → Pause, and a scheduled run can slip in between. Allow Run now on a paused automation. - A runner in the system Nodes project cannot file the follow-up it finds (`task_create` 422: system project is automation-only), so its findings are left as prose. Let a runner there file the draft in the org's default project, or name where it should go. Out of scope: placement rules, the slot builder itself, automation scheduling semantics. Done means: - A freshly filed node-target task never shows "Its slot could not be built" unless a build failed (web/API test). - Run now works on a paused automation and leaves it paused (test + live check on dev). - Required checks: Jaah Deploy

Merged #6902 and #6904. Run now works on a paused automation and leaves it paused (verified live on dev). A retried slot refusal no longer shows "could not be built" until parked or 90s old. A Nodes-project runner now files its follow-up as a draft in the org's oldest own project. Quick gate green; #6902 Jaah Deploy passed; #6904's deploy was superseded.