KNELBMS/.gitea/pull_request_template.md

Release PR (dev -> release)

Merging this deploys to production (pfv-bms restarts if packages/** or configuration.yaml changed).

Gate checklist (branch protection enforces the mechanical parts)

• CI green on the head commit (yamllint + secret scan + SDLC suite)
• Adversarial pass done: what breaks if this is wrong? what watches for it?
• post-deploy validation (#778) will run on restart — expected entity changes noted below

Reviewer (founder)

• Diff reviewed
• Approve to release

Expected entity/automation changes: <list or "none"> Rollback: git revert on dev, re-PR, or push previous release sha directly.