unic-spec-review S2: self-contained auth + preflight — /setup-confluence wizard and /spec-doctor

[orioltf]

Parent

Epic: #200 — unic-spec-review plugin.

What to build

Make the plugin self-contained for setup and preflight. Ship its own /setup-confluence credential wizard (vendored from unic-pr-review) that writes ~/.unic-confluence.json, and a /spec-doctor preflight command that verifies all prerequisites before a review: Confluence credentials are present and valid, and the Figma Dev Mode MCP and Playwright MCP are connected.

A user who installed only this plugin can configure Confluence through this plugin alone (no dependency on unic-pr-review or unic-confluence). A user who already has the shared ~/.unic-confluence.json reuses it — the file is a shared credential store keyed by convention, not a plugin coupling.

/spec-doctor reports each prerequisite's status clearly. Missing MCPs are reported as loud, explicit failures (never silent), consistent with the fail-loud-per-source rule the review path will enforce later.

Acceptance criteria

• /setup-confluence interactively collects Confluence credentials and writes ~/.unic-confluence.json (or guides CONFLUENCE_* env usage), vendored by copying the wizard from unic-pr-review — no cross-import.
• /spec-doctor checks: Confluence credentials present + a basic auth/connectivity check; Figma Dev Mode MCP connected; Playwright MCP connected.
• Absent Figma or Playwright MCP is reported as an explicit failure with remediation guidance, not a silent skip.
• The plugin has no runtime or setup dependency on any other plugin; installing it alone is sufficient to set up and preflight.
• node:test unit tests cover the vendored setup-confluence wizard and any pure preflight/credential-check logic with injected homedir/env/fetch; no live services. Command orchestrators are not unit-tested.
• PR adds CHANGELOG.md bullets under [Unreleased] and bumps the patch version; verify:changelog passes. No em dash in authored text (except the mandated CHANGELOG version header).

Blocked by

• unic-spec-review S1: skeleton tracer bullet — classify one URL, fetch page, one Gaps agent, write report #202 (S1 — skeleton: vendored credentials + test harness).

[orioltf]

✅ Issue Resolution Report

PR: #211 (#211)
Status: COMPLETE

---

Summary

Delivered a self-contained credential wizard (/setup-confluence) and preflight command (/spec-doctor) for unic-spec-review, vendored from unic-pr-review with zero cross-plugin runtime dependencies. Implementation adds two new Node.js scripts, vendored tests, full command orchestrators, and bumps the plugin to 0.1.2. A post-implementation review found 6 findings (1 MEDIUM, 5 LOW), all fixed in a follow-up commit — growing the test suite from 93 to 101.

---

Changes Made

File	Change
scripts/lib/args.mjs	Added parseArgs utility
scripts/setup-confluence.mjs	Created — vendored wizard (no cross-plugin import)
scripts/spec-doctor.mjs	Created — Confluence-only preflight with injectable deps
commands/setup-confluence.md	Replaced stub with full interactive wizard
commands/spec-doctor.md	Replaced stub; MCP absence = loud ✗ + remediation
tests/setup-confluence.test.mjs	Created — 8 wizard cases
tests/spec-doctor.test.mjs	Created — preflight unit tests
tests/args.test.mjs	Extended — parseArgs describe block (7 cases, post-review)
CHANGELOG.md + version files	Bumped 0.1.1 → 0.1.2

---

Validation

✅ Type check | ✅ Lint (Biome + Prettier) | ✅ Tests — 1190 passed workspace-wide (101 in unic-spec-review, up from 93) | ✅ verify:changelog

---

Review & Self-Fix

• 6 review findings across 5 agents (1 MEDIUM, 5 LOW)
• 6 / 6 fixed (100%) — no findings skipped or blocked
• Tests grew: 93 → 101 (+8 new cases)

Notable fixes from review pass:

• Added parseArgs unit tests covering all four branches
• Fixed process.env.HOME → require('os').homedir() for Windows portability
• Improved stack trace output in top-level catch
• Removed dead skipped branch from formatLine / CheckResult typedef
• Added 401 HTTP-error path test for runSpecDoctorCredentials

---

Unaddressed Items

All review findings were addressed in the PR.

---

Suggested Follow-up Issues

No follow-up issues needed.

---

Resolved by Archon workflow f8fe1b4a1a348ed0d6cda23050c03da2