[Draft] Bootstrap repository verification tooling and developer guardrails

[BASIC-BIT]

Problem

#51 defines the verification model at the policy/design level, but VRDex still needs the first practical implementation pass that makes verification easy to run and hard to forget.

We want local development, pre-commit, pull-request checks, and post-merge/pre-deploy validation to feel like one coherent system instead of a pile of disconnected commands.

Scope

• define the first repo-standard verification commands contributors should run locally
• add or normalize package/repo scripts for baseline checks like lint, format, typecheck, and test
• make the baseline verification path easy to run locally with minimal setup friction
• wire a pre-commit hook for the fast checks that should happen before code leaves a workstation
• add PR automation for the baseline verification suite
• define and wire a post-merge / pre-deploy verification pass for slower or broader checks where appropriate
• keep the setup flexible enough for later e2e, visual, policy, and infrastructure checks without pretending they all need to land in this first slice

Non-goals

• implementing the full long-term verification vision from #51
• requiring heavyweight checks on every tiny change
• finishing every e2e, visual, policy, or infrastructure validation layer immediately
• locking the repo into an overcomplicated CI/CD design before the core app exists

Acceptance criteria

• the repo has a clear baseline verification command set for local use
• contributors can discover the expected local verification flow quickly from repo docs
• a pre-commit hook exists for the agreed fast checks
• PR checks run the baseline automated verification suite
• a post-merge / pre-deploy validation path is documented and wired at an initial practical level
• the implementation is explicitly framed as the first execution slice under #51, not the final verification end state

Likely docs to update

• README.md
• docs/agentic/contributor-workflow.md
• docs/agentic/definition-of-ready.md
• docs/agentic/definition-of-done.md
• docs/planning/engineering-strategy.md
• any future app/bootstrap setup doc created alongside the initial app

Soft dependencies

• #51 Define layered verification loops and human validation package expectations
• #53 Scaffold initial Next.js web app
• #54 Bootstrap initial Convex backend

Soft dependents

• most implementation issues after the initial app/backend bootstrap
• future e2e, visual regression, policy-check, and deployment-hardening work