obsidian-test-vault-smoke

name

obsidian-test-vault-smoke

description

Validate the personal-assistant Obsidian plugin in the repo-local test vault using both fast CLI runtime smoke and full app UI/UX interaction smoke. Use when end-to-end verification is needed after UI/runtime changes, Pagelet work, Chat, Memory/VSS, Preview/Stats, settings, release-gate smoke, or visible layout/copy/interaction changes. For real-device iOS validation, use `obsidian-ios-real-device-smoke`. For community compliance scan, use `obsidian-community-check`.

Obsidian Test Vault Smoke

Core Rules

• Do not claim Obsidian validation without deploying the current build to test/ and observing the affected behavior in the running app.
• Treat Jest, lint, type-check, build, and source scans as implementation validation, not app smoke.
• Require visible-window interaction for UI/UX PASS; CLI, DOM, and screenshots support the finding but do not replace real interaction.
• Use obsidian vault=test <command> for every Obsidian CLI call. vault=test must precede the command.
• Choose the lightest tier that covers the changed surface.

Validation Gate

For every code, DOM, or CSS change, run the complete Local Validation Gate from repo-root AGENTS.md before app smoke. Run all commands currently listed there, including the runtime <style> / innerHTML / outerHTML source scan.

Treat the source-scan rg exit code 1 with no output as PASS. Inspect every match manually. make deploy and the hosted community scan do not replace this local source scan.

Smoke Tiers

Tier	Use when	Required checks
quick	Narrow code-only or test-only change	Complete Local Validation Gate with focused suites; stop before app smoke only when no runtime/user path changed
app-runtime	Runtime, command, packaging, Pagelet shell, Chat/Preview/Stats mount, Memory readiness	Local Validation Gate, make deploy, plugin reload, affected CLI/DOM probes, fresh console/error capture
full-ui	Visible UI, CSS/layout/copy, Pagelet workflow, settings, keyboard/focus, mobile emulation	app-runtime plus real Obsidian interaction, screenshots, UX notes, and provider/write-path checks when applicable
release-gate	Release, broad refactor, shared infrastructure	Local Validation Gate, make deploy, broad runtime matrix, required UI surfaces, and release evidence reconciliation

make deploy already runs full Jest, lint, build, and asset deployment. Run standalone full Jest first only when serialized failure detail or a separate pre-deploy signal is useful.

Workflow

1. Inspect git status --short, relevant diffs, and affected surfaces.
2. Run the complete Local Validation Gate from AGENTS.md.
3. Select the smoke tier.
4. For app smoke, deploy and reload:

make deploy
obsidian vault=test vault info=path
obsidian vault=test plugin:reload id=personal-assistant
obsidian vault=test plugin id=personal-assistant

5. Read only the references required by the changed surface:
   • For any app-runtime, full-ui, or release-gate run, read CLI runtime smoke.
   • For visible UI/UX work, read UI/UX interaction smoke.
   • For Pagelet work, read both CLI runtime smoke and Pagelet smoke.
6. For historical fixtures, regression expectations, and prior evidence, consult the current Pagelet smoke checklist. Treat its verification log as provenance, not current-run evidence.
7. Record concrete PASS, FAIL, BLOCKED, or SKIP outcomes.
8. Always restore debug/mobile state, including after failure or interruption:

obsidian vault=test dev:debug off
obsidian vault=test dev:mobile off

Safety Boundaries

• Limit provider-backed checks to repo-local test-vault fixtures unless the user approves broader data. Report provider/model, note paths, and prompts sent.
• If a provider, browser, CLI, or GUI tool blocks the action, do not bypass the block; report BLOCKED and residual risk.
• Stop before deleting or rewriting test-vault data that may be user-authored.
• Stop before publishing, pushing, creating releases, or mutating non-test external systems unless the user authorized that action.
• Keep hosted Obsidian Community scans distinct from the local source scan. A hosted scan submits a ref to an external service and is never an automatic part of this skill.
• During release-gate, invoke obsidian-community-check only when the user explicitly requested the hosted scan or the active stable-release workflow explicitly authorized it. Otherwise report it as not run.

Output

Validation:
- PASS: `<check>` - `<observed result>`
- FAIL: `<path>` - `<regression or product gap>`
- BLOCKED: `<path>` - `<external blocker and residual risk>`
- SKIP: `<path>` - `<why it was outside this tier>`

CLI runtime smoke:
- Vault: `test/`
- Tier: `<quick/app-runtime/full-ui/release-gate>`
- Deployment/reload: `<result>`
- Obsidian: `<version>`
- Target: `<note/view/command>`
- Provider/model/prompt: `<if used>`
- Artifact: `<DOM output, console excerpt, runtime file>`

UI/UX smoke:
- Visible path: `<entry and interaction>`
- Observed UX: `<layout, copy, feedback, accessibility>`
- Screenshot: `<path if captured>`
- UX findings: `<UX-P0/UX-P1/UX-P2 or none>`

Cleanup:
- Debug off: PASS/FAIL
- Mobile emulation off: PASS/FAIL

Hosted community scan:
- Authorized and run / not authorized and not run / BLOCKED

Related Skills

• Use personal-assistant-review for code-level review.
• Use obsidian-ios-real-device-smoke after local app smoke for real-device iOS validation.
• Use obsidian-community-check only for an authorized hosted community scan.