Branching and reviews

Fetch the current remote before work and branch from origin/test. Keep each branch limited to one coherent outcome. Commit imperative subjects, never commit credentials or generated dependency/build directories, and push without force.

Open a pull request into test. Acceptance requires review of the exact candidate head, Gitea Actions whose head_sha equals that head, and all required checks passing. Merge only an eligible exact-head-green change under the active project authority. After integration, verify the default-head SHA, its Actions runs, and the deployed artifact when the change publishes documentation or application behavior.