manage-issue-execute

Automating issue solution execution involves dispatching the planned fix via a central server, falling back to local CLI delegation if the server health check fails. This dual-mode workflow ensures robust, auditable executions while updating issue status.

Dual-mode issue execution is a dispatch mechanism that posts solutions to a central server when available, or delegates locally as a fallback. It is needed to ensure planned issue solutions execute reliably even when server connectivity fails.

Executing a planned issue solution with a dry-run preview requires invoking the command with the issue ID and dry-run flag. This validates the planned steps and prompts without performing actions, ensuring the solution is correct before dispatch.

Yes, issue execution requires a planned solution to be present before dispatch. The workflow enforces a safeguard validating issue.solution presence, ensuring a concrete plan exists before routing to server dispatch or local delegation.

After issue solution execution succeeds, the status updates to resolved and routes to next steps like close or verify. If execution fails, the workflow routes to debug, appending history entries for auditability and status tracking.

Yes, you can route issue execution to verify or debug after dispatch. The workflow provides explicit next-step routing paths to close, verify, or debug, updating the issue status accordingly based on the execution outcome.