Fix stalled workflows and integrate development on devel

[d3cker]

Targets devel. Merging this PR does not publish a release. Merge #13 before #14.

Development and publication flow

Feature PRs now target devel, with CI on every new PR revision. When a release is wanted, a reviewed same-repository devel → release PR starts the existing automatic patch/tag/publication pipeline. Other feature branches targeting release are rejected by CI and cannot start automatic publication.

After stable publication, the publisher commits the versioned README on release, opens/updates the main promotion PR, and automatically merges the published release head into devel without a synchronization PR. Normal Git merges/pushes preserve newer development commits, retry concurrent updates, and fail visibly on conflicts or denied pushes. Retries reuse the published version and assets. main remains PR-only.

The release pipeline has 18 integration tests, including real Git remotes, protected-main rejection, devel fast-forward/divergence, conflict recovery, denied writes, and a concurrent push. README, release documentation/diagram, installation notes, AGENTS and changelog describe the new flow. The release diagram and all eight runtime diagrams parse successfully.

Problem and behavior

A session timeout or manual interruption left the durable task blocked/running forever. Completing that session in the TUI did not notify the dispatcher, so it never verified/published the work and newly discovered issue comments remained queued across service restarts.

Recheck stopped sessions, including legacy checkpoints, and return successful sessions to normal validation, configured checks, and publication. Preserve the existing branch/worktree/PR and process pending feedback only after that publication completes.

Add /restartworkflow, opencode2-automation restartworkflow owner/repo#123, and the corresponding RPC. Recovery persists its intent, reconnects to existing execution, and continues the same stopped session when necessary. It does not duplicate prompts after uncertain responses, interrupt active work, bypass checks/questions/permissions, or clear saved work. Verification/publication failures retry their saved stage.

Validation

• npm run check: lint, typecheck, 157 tests, and build passed.
• New regressions cover legacy/typed stops, manual completion, owner restart, queued follow-up processing, recovery admission, lost prompt responses, pending permissions, failed checks, and the TUI command.
• npm run package:check: archive installation, loaders, SDK entrypoints, TUI, and CLI passed.
• Feature release validation confirms Unreleased notes for the next patch.
• All eight workflow Mermaid diagrams validated with the Mermaid parser.

Earlier server verification (recovery code only)

Installed the tested feature archive at commit d9eb0d1 on the affected host, backed up Git refs and session/queue state, and reloaded both configured owners while sessions were idle. No queue repair or manual publication was used. The dispatcher automatically reconciled the legacy timeout for issue #18, completed verification/publication of round 3, and started round 4 for pending comment 5679024617, preserving thirst-for-levels, its saved worktree, and PR #19. Both automation plugins were active and both schedulers reported zero failures. The new implementation round remains in progress.

Documentation

Reviewed all eight issue-to-PR diagrams against the implementation and updated their ordering, phase/status transitions, saved worktree behavior, automatic/manual recovery, media failure paths, verification/publication gates, merge polling and tab cleanup. Updated README and architecture/runtime/advanced/configuration/installation references, including command scope and the distinction between queued feedback and execution.

AGENTS.md and the bundled bot prompt now require affected descriptions, examples and diagrams to be updated in the same change, with documentation impact reviewed before completion. This requirement is an agent instruction; it is not an additional runtime gate.

Documentation validation: all eight diagrams passed the Mermaid parser, 66 local links (including section anchors) passed, Markdown diff checks passed, and three existing prompt/branch tests passed. The server verification above used code build d9eb0d1; this later documentation/instruction commit is included in the PR for release.