# Vigthoria CLI Local Machine Verification Checklist

Use this checklist on real user machines before and after rollout. The goal is to verify install, auth, routing, update, and core command reliability in the same environment users run.

## 1. Preflight

- [ ] Node.js `>=20.19` available
- [ ] `npm` available
- [ ] No stale shell aliases shadowing `vigthoria`
- [ ] Network access to:
  - `https://coder.vigthoria.io`
  - `https://api.vigthoria.io`
- [ ] If running browser runtime proofs: Chrome available for Puppeteer

Commands:

```bash
node -v
npm -v
which vigthoria || where.exe vigthoria
```

## 2. Install and Version Integrity

- [ ] Install succeeds
- [ ] Reported version matches release target
- [ ] Binary resolves to expected package

Commands:

```bash
npm install -g vigthoria-cli@latest
vigthoria --version
vigthoria doctor
```

Expected:
- `vigthoria --version` shows current release version
- `doctor` returns diagnostics without crash

## 3. Auth Reliability

- [ ] Login works
- [ ] Status shows account, plan, health lines
- [ ] Invalid token is rejected with gateway-auth message

Commands:

```bash
vigthoria login
vigthoria status
VIGTHORIA_AUTH_TOKEN=invalid-token-for-preflight vigthoria chat --no-agent --model balanced-4b --prompt "ok" --json
```

Expected:
- `status` includes `Account Status`, `Plan`, `Overall`, `Coder API`, `Models API`
- Invalid-token command returns JSON with `success: false` and gateway-auth failure message

## 4. Model and Routing Checks

- [ ] Balanced path resolves to balanced model
- [ ] Governance fallback maps blocked no-agent models to `vigthoria-v3-code-35b`
- [ ] Agent direct mode prints command/tool flow (non-JSON mode)

Commands:

```bash
vigthoria chat --no-agent --model balanced-4b --prompt "reply exactly: ok" --json
vigthoria chat --no-agent --model creative --prompt "say ok" --json
vigthoria agent --prompt "Read one file and summarize it" --auto-approve
```

Expected:
- balanced output model: `vigthoria-v3-balanced-4b`
- creative output model: `vigthoria-v3-code-35b`
- agent run shows direct prompt execution and tool activity

## 5. Command Surface Smoke Tests

- [ ] Aliases work
- [ ] Bridge status prints valid section and hidden internal endpoints
- [ ] Operator JSON command succeeds

Commands:

```bash
vigthoria hyper-loop status
vigthoria devtools connect
vigthoria bridge status
vigthoria operator --prompt "status check" --json
```

Expected:
- No crashes
- `bridge status` shows `DevTools Bridge` and either `Reachable` or `Not running`
- Operator JSON has `success: true`

## 6. Update Path

- [ ] Update check works
- [ ] Upgrade path works from npm/manifest

Commands:

```bash
vigthoria update --check
vigthoria update
```

Expected:
- No script errors
- Clear success/fallback guidance if update source fails

## 7. Release Gate (Local Build Validation)

Run this on release candidate machines when validating local package changes.

```bash
npm run build
npm run validate:no-go
```

Expected:
- `ALL NO-GO GATES PASSED`

## 8. Environment-Specific Prerequisites

These are external dependencies, not CLI code regressions:

- Workflow E2E requires reachable VigFlow backend
- Live repo/game/platform E2E requires:
  - `VIGTHORIA_COMMUNITY_EMAIL`
  - `VIGTHORIA_COMMUNITY_PASSWORD`
- Browser proof requires Chrome installed for Puppeteer runtime

## 9. Rollback Readiness

- [ ] Previous known-good CLI version pinned
- [ ] One-command rollback documented
- [ ] Support note prepared for users

Example rollback:

```bash
npm install -g vigthoria-cli@<known-good-version>
```

## 10. Signoff Template

- Machine/OS:
- Node/NPM versions:
- CLI version validated:
- Auth check: PASS/FAIL
- Model routing check: PASS/FAIL
- Command smoke check: PASS/FAIL
- Update check: PASS/FAIL
- No-go gate: PASS/FAIL
- Approved by:
- Timestamp:
