Completes the Phase 0 scaffold. The app builds, links and renders; no
screens yet.
Frontend (ARCHITECTURE section 9, UI-SPEC section 2):
- React 19 + Vite 8 + Tailwind 4 with the UI-SPEC dark terminal-tech
tokens, plus a contrast test asserting WCAG AA over every
text/surface pair, which UI-SPEC section 8 requires be verified.
- EN and VI catalogs with a test that vi has every en key and no
orphans, standing in for the CI parity script I18N section 1 asks for.
- A local eslint rule enforcing the no-hardcoded-JSX-strings policy.
eslint-plugin-react was the obvious choice but caps at ESLint 9, which
drags in six high-severity advisories that would fail npm audit in CI;
a local rule also implements the documented allowlist (product name,
package names, versions, catalog codes, glyphs) precisely, which
react/jsx-no-literals cannot express. Verified it fires on real copy
and stays quiet on all five allowed shapes.
- no-restricted-imports keeps invoke() out of components, so the
"no component calls invoke directly" rule is enforced, not just stated.
Tauri (ARCHITECTURE section 7): commands and events only, identifier
com.skullmute.pipdock, NSIS and MSI targets, minimal capability set,
placeholder icon pending the Phase 3 branding pass.
CI (docs/RELEASE-CI.md section 1 as corrected):
- ci-rust.yml and release.yml are project-local, on Windows runners,
because no reusable Rust or Tauri workflow exists in the ops repo.
Windows matters here: env discovery reads the PEP 514 registry and the
py launcher, so a Linux run would skip the code most likely to break.
- ci-node.yml calls the ops web-react reusable and adds the npm audit
job that reusable lacks.
- codeql.yml is JS/TS only; CodeQL has no Rust analyzer.
- Discord notifiers replace the six-platform notify.yml that never
existed. Every caller carries an explicit permissions block.
- Action versions checked against the registry rather than assumed:
checkout v7, cache v6, gh-release v3, setup-node v6.
Two toolchain holds, both forced and both recorded:
- TypeScript 6.0.3, not 7: typescript-eslint peers on <6.1.0.
- ESLint 10 with eslint-plugin-react dropped, as above.
Verified: cargo fmt/clippy -D warnings/28 tests green, tsc clean,
18 vitest tests green, eslint clean, npm audit reports 0
vulnerabilities, vite build and both binaries link.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>