使迁移安全
先测量问题。添加版本列并在更新时检查，使并发编辑被检测且最后写者获得 409 而非静默覆盖。 最常见的错误是未确认门禁能捕获你关心的问题就先加上。在接入 CI 之前，先对当前代码库运行 UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; 并检查输出。
UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3;验证与回滚
门禁就位后，让失败可操作。UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; 失败时应指向具体文件和行号，而非泛泛的错误。在锁文件中固定工具版本，防止上游发布悄悄改变行为。每次拉取请求都应像审查测试结果一样审查门禁输出。
验证
在本地运行 UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; 确认通过后推送。CI 中门禁应阻断不合规的拉取请求。若人为绕过门禁直接推送，应在下次定期扫描中被发现。
注意事项
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.