Mark
323dd695ee
D-08-29 closes the planning miss where D-08-28 locked "Android-parity automated test pyramid because operator does not possess a Windows machine" yet Plan 8-3 Task 5 still required ~2-4 h of manual VM clicks. Verdict: dockur/windows v5.15 (2026-05-17, ACTIVE, 51.4k stars) invoked from scripts/build-windows.sh Step 0 as a one-shot bootstrap container. ~30 min one-shot unattended (cached afterward). ~150 LOC integration. ZERO new host deps (docker 29.1.3 + parf in kvm+docker groups verified). Dismissed candidates: - Packer + qemu builder (~300 LOC, no built-in 24H2 helper) - Vagrant + community Win 11 box (vagrant-libvirt stale 3 yr; 24H2 archeology) - virt-install + libvirt + autounattend.xml (~250 LOC hand-rolling) - custom bash + qemu + autounattend (same hand-rolling burden) - Self-hosted Gitea Actions (Gitea 1.25.4 verified, but Linux act_runner cannot run Windows jobs — downstream of VM-creation problem, not solution) Confidence HIGH — 3+ corroborating sources including primary production reference (Jesse Vincent blog 2026-03), version verified via gh release view API, dockur src/define.sh confirmed to bake Win 11 24H2 build 26100.1742 natively. Full research at 08-RESEARCH-vm-autoprov.md. AP-4 byte-freeze invariant trivially preserved (no source-code edits, only new tooling files: tools/windows/dockur-bootstrap.sh + tools/windows/oem/install.bat + Step 0 hook). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Prowler
Anti-censorship proxy infrastructure for private use. Multi-layer connectivity through EU exit nodes with a domestic relay chain surviving TSPU IP blocking.
Monorepo Structure
prowler/
├── prowler-server/ # v1 — Server infrastructure (shipped)
│ ├── ansible/ # Provisioning & deployment
│ ├── docs/ # Server PRD, SDD, brief
│ └── AGENTS.md # Server architecture & conventions
│
├── prowler-client/ # v2 — Client application (upcoming)
│ └── docs/ # Client PRD, SDD, design system
│
└── .planning/ # GSD project management
prowler-server
Two VPS nodes (EU exit + Russian relay) providing Layer 1 (direct proxy) and Layer 3 (domestic relay chain) connectivity. Serves third-party clients (V2Box, sing-box) via manually distributed configs.
See prowler-server/AGENTS.md for full architecture, conventions, and gotchas.
prowler-client
Cross-platform client (Android + Windows) wrapping three escalation layers in a single app. Flutter UI + Go proxy core (libXray) + ByeDPI for client-side DPI bypass.
See prowler-client/docs/ for PRD, SDD, and design system.