Retry PR publication while GitHub catches up with the pushed commit

[d3cker]

After a successful push, GitHub can still report the previous commit in the PR response. Publication previously treated that mismatch as a permanent description conflict, leaving an open PR with pushed changes and a blocked bot task.

Compare the remote branch ref with the verified commit before reconciling the description and again before PATCH. When the branch matches but the PR view lags, retry the saved publishing phase using the existing backoff and attempt limit. Closed PRs, changed branch commits, and manual description edits remain blocking conflicts with distinct messages.

Persist successful pushes as pushedCommit, so retries and owner restarts reuse the saved report and commit without repeating a confirmed push. Clear that checkpoint for each new feedback round. Unacknowledged pushes retain the existing non-force reconciliation behavior.

Documentation: update architecture, runtime guidance, publication recovery, changelog, and workflow diagrams 3, 6, and 8. Review the remaining diagrams for impact.

Validation:

• npm run check: lint, typecheck, 213 tests, native TUI rendering, and build passed.
• Regression coverage for PR propagation, branch changes, closure, pre-PATCH rechecks, restart recovery without another push, and exhausted retries.
• All 8 Mermaid diagrams parsed; 91 local documentation links checked.
• Read-only verification of the GitHub branch-ref endpoint against the affected repository.

Targets devel; no package release or server deployment is included.