robel-auth

To prevent Convex auth wiring drift, you must enforce upstream validation by consulting official documentation and release READMEs before implementing or updating authentication code. This ensures reproducible setups and safe deployments aligned with official sources.

The best way to validate Convex auth changes is by running an upstream check script, such as check-upstream.sh. This process inspects official docs and performs environment checks to verify dependencies and wiring against the latest upstream guidance.

Yes, you can use upstream validation when debugging existing authentication wiring in Convex apps. The process requires inspecting official docs and running environment checks to identify and resolve drift from official patterns safely.

You need to check upstream documentation for Convex auth integration whenever you are adding, updating, or debugging authentication wiring. Consulting main and release READMEs plus self-hosting docs prevents pattern drift before code changes are applied.

Yes, updating Convex authentication requires checking self-hosting docs when relevant to your deployment. Documentation-driven decisions are mandatory, meaning you must consult main and release READMEs alongside upstream validation to ensure safe, reproducible setups.