bug-fix-and-ship

Automate end-to-end bug fixes by reading structured bug reports, inspecting affected source code, applying minimal edits, adding regression tests, and validating changes in a Docker container. This workflow transforms issue reports into verified source changes and ships them with structured commit messages.

Run regression tests in a Docker slot by executing the full test suite inside a containerized environment after applying source changes. This automated verification validates bug fixes against the entire test suite before committing and pushing the updated code.

Bug reports should follow structured markdown templates like issues/NNN-*.md files. This declarative format allows the bug-fix workflow to parse issue details, inspect affected source code, apply minimal edits, add regression tests, and ship verified changes.

Docker is required to run the full test suite inside a containerized slot for automated verification. This deterministic step ensures regression tests validate the bug fixes before the workflow commits and pushes the source changes with a structured message.

Ship backend bug fixes with a standardized commit message by running an automated workflow that reads bug reports, applies source changes, adds regression tests, validates via Docker, and commits using structured messages. This enforces deterministic steps from report to push.

Handle structured bug reports for kernel-pipeline-backend by transforming issue files into verified source changes. The workflow reads issues/*.md templates, applies minimal code edits, adds regression tests, validates in Docker, and pushes fixes with standardized commit messages.