Technical Reference
Validation and Release
Local checks, Salesforce deploy validation, governance gates, and QA release evidence
Local Setup
nvm use
npm ci
npm run doctor:localUse the repo Salesforce wrapper:
npm run sf -- org list --json
npm run sf -- project deploy start --helpCore Validation
| Command | Use |
|---|---|
npm run verify:governance | Fast permission and policy gate. |
npm run verify:governance:full | Full governance, dashboard, LWC, payment, and retirement checks. |
npm run architecture:payments:guard | Prevent unsafe payment runtime regression. |
npm run permissions:audit | Permission coverage summary. |
npm run permissions:policy | Permission-set group hierarchy policy. |
npm run architecture:retirement:audit | Stale references, deprecated assets, broken app/tab targets. |
npm run architecture:dashboards:audit | Report/dashboard metadata validation. |
npm run coverage:apex:snapshot -- --target-org vesper | Cache Apex coverage from QA. |
QA Deployment Evidence
For QA release readiness, keep evidence for:
- Source package or changed metadata scope.
- Deploy or validation IDs.
- Test classes or local checks run.
- Scheduler abort/restore steps when runtime classes are touched.
- Runtime setting state after deploy.
- One workflow-level validation for high-risk areas such as payments or 3PL fulfillment.
Dirty Worktree Rule
This repo often has unrelated local metadata edits. Do not revert files you did not change. Scope deploys, checks, and commits to the docs or feature slice you actually touched.
Last updated on