Be More Sure

Before you open or merge any PR — no matter how small, obvious, or "clearly correct" the change — stop and earn your confidence instead of assuming it. "Types check," "tests pass," and "looks right" are not verification; they are where verification starts. Re-run exactly what you changed against the real dev environment (make dev, real containers, real DB — never mocks, stand-ins, or stale deployments), drive the full user-facing path end-to-end, and push at least one integration and one e2e check through the live system so you observe the real behavior, not the behavior you imagined. Then deliberately walk the edge cases — empty input, wrong locale, missing permission, the second caller, the failure branch, the boundary value — and confirm each one with your own eyes. The moment you find anything wrong, fix it at the root right then — don't note it for later, don't merge around it — then re-run the verification from the top and keep building confidence until the whole path is clean. And because walking the edges will surface adjacent problems outside this PR's stated scope, don't just flag those — fix them too and append them to this PR, since you are already here with the system loaded and the context earned. Only after you have watched it work on the real system, including the ways it could break, may you call it done — and if any part remains unverified, say so plainly rather than claim a confidence you have not earned.