Improve coding flow

The current coding workflow needs a clearer, repeatable path from task definition to implementation, review, deployment preview, and QA. Work should not start directly from an informal prompt or land directly in development without a visible issue, branch, pull request, and review step.

This task belongs to the tasks repository and documents the desired workflow for coding work across project repositories. The workflow should connect the Regular Task Board with the correct GitHub repository, make each implementation traceable through a matching GitHub Issue, and ensure that agents work on dedicated branches instead of shared long-lived branches.

Create or document a standard coding flow with the following sequence:

1. Create or select the related task in the Regular Task Board.
2. Create the corresponding GitHub Issue in the correct project repository.
3. Create a branch from the issue using a predictable naming pattern, such as fix/123-arena-refresh-after-cancel.
4. Run the coding agent only on that branch.
5. Require the agent to make separate, focused commits and push the branch.
6. Open a Pull Request targeting development.
7. Review the PR, diff, status checks, and tests before merging.
8. Merge into development only after review.
9. Let the preview deployment run from the merged branch or configured preview workflow.
10. Run manual QA and/or E2E checks after the preview deploy is available.

• Keep the flow repository-agnostic enough to work across Regular Punks repositories, but preserve the requirement that each GitHub Issue must be created in the correct repo.
• Do not let agents commit directly to development or main for normal implementation work.
• Prefer short-lived branches named from the issue number and task summary.
• Prefer small commits that map to reviewable implementation steps.
• The PR should be the checkpoint for human review, diff inspection, status checks, and test review.
• Manual QA and E2E should happen after the preview deploy, not before the review process is complete.
• This task is about improving and standardizing the workflow; implementation may be documentation, automation scripts, taskboard conventions, or GitHub templates, depending on the repo state.