Review and publish a coherent change
A coherent change has one integration branch and draft PR, an exact reviewed candidate and evidence for its affected outcome. Toolora code reaches main through GitHub. In pre-launch, authorized completed application changes are published to the shared environment through the exact-commit release path; documentation-only changes produce their own static artifact.
Prerequisites
Section titled “Prerequisites”Read current status, open issue/PR state, worktrees and the deployment contract. Identify the affected component, schema dependencies, current published identities and required verification. Reuse the task branch while its PR remains open. A merged branch requires a new branch from current main.
Application and schema publication have different prerequisites. A schema candidate must meet the reviewed-main and upgrade-evidence contract in schema release. Do not assume a documentation delivery or PR publication authorizes shared database work.
Delivery procedure
Section titled “Delivery procedure”- Implement one coherent batch and run focused checks. Commit and push the first concrete change, then open its draft PR. Keep later fixes in that PR while it remains open.
- Review the complete diff, including generated files and operational boundaries. Run
make ci-plan BASE=origin/mainand the selected shared local checks. Record actual commands, outcomes, checked commit and platform prerequisites covered by CI. - Mark the PR ready only after local correction and review. Inspect the actual selected CI jobs and aggregate result. If implementation changes are required, return it to draft before pushing them.
- Use the current GitHub protection contract for merge. Strict required checks are active until merge-queue activation is explicitly recorded. Update from main when entering the final merge turn, not repeatedly while other work lands. A green PR that is behind can wait. Queue preparation or an Enterprise subscription alone does not activate a queue.
- For an authorized application publication, select the full candidate SHA and use the guarded release path. The read-only
scripts/ops/release.sh <full-sha> --checkinspects prerequisites; it does not publish. Follow the owning deployment guide for the mutating invocation and component order. - Observe component version, liveness/readiness and the affected authorized behaviour. Record what was actually published and verified. Close a linked issue only after its requested outcome has merged, been published where required and passed its scoped check.
Expected result
Section titled “Expected result”| Delivery fact | Required evidence | Insufficient substitute |
|---|---|---|
| Reviewable change | Pushed branch and open PR | Uncommitted local files |
| Selected checks pass | Actual candidate jobs and CI result |
Draft-only checks or an older run |
| Component published | Exact current source identity and service observations | A built directory |
| Behaviour verified | Named actor/target/input/result at the relevant version | A health endpoint alone |
| Handbook distributed | Clean-commit archive, hashes and extracted-browser check | An untested development server |
Failure and rollback
Section titled “Failure and rollback”Read failed steps before retrying CI. Retry failed jobs only for an unchanged transient infrastructure failure; do not dispatch a second full workflow beside an equivalent queued run. Preserve required scanning and policy baselines.
For a normal application release, use the previous compatible release through the deploy tool. After schema changes, forward-only handling may deliberately leave a failed candidate stopped rather than restart an incompatible writer. Inspect actual ledger/current-link/process state before deciding the next correction. Publication owns those mechanics; incidents owns containment and recovery reporting.
Verification scope
Section titled “Verification scope”For a synthetic portal correction, report the local denial/positive tests, candidate CI, observed API/frontend identities and the authorized portal outcome separately. Never infer provider acceptance from a local save. Vi Målar’s real Fortnox binding makes accounting and payroll sends unsuitable as routine shared tests.
Documentation delivery requires no application restart. Keep the clean source commit, local handbook checks and ZIP identity in the PR. Remove the delivered worktree while retaining an open-PR branch; delete the branch after merge. Status and evidence define the resulting delivery statement.