Publish work the executor committed itself, and gate when there is none

On the first live run the executor committed its milestone itself, as
its plan asked. The publisher only published a commit it made, found a
clean tree, reported "no changes to publish", and left the agent in
EXECUTING, where every message is answered "busy".

- publish(): with nothing left to commit, publish anyway when the branch
  has commits origin/<base> lacks; report no changes only when it has
  none.
- push_followup(): same for review fixes, comparing HEAD with what the
  remote branch holds (ls-remote; pushes go by URL, so there is no
  tracking ref).
- Nothing to publish now gates to AWAIT_INPUT, and the reply returns to
  the still-approved milestone plan.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE

nisse-dev/src/nisse_dev/control.py

@@ -743,7 +743,16 @@ class Orchestrator:
             )
             return
         if result.pull_request is None:
-            self._transport.send_message(result.note)
+            # Nothing left EXECUTING behind: the operator decides what next,
+            # and answering returns to the still-approved plan.
+            self._await_input(
+                cause=f"milestone {milestone}: {result.note}",
+                prompt=(
+                    f"milestone {milestone}: {result.note}. Reply to return to "
+                    "the approved plan."
+                ),
+                pending={"kind": "milestone_stopped", "milestone": milestone},
+            )
             return
         self._data["pr"] = {
             "number": result.pull_request.number,