df1: massively-parallel parity-checklist campaign (tracking)

[danshapiro]

Campaign: drive every unchecked, non-host-limited item of docs/plans/2026-07-14-rust-tauri-parity-completion-checklist.md to merged + verified closure using up to 32 concurrent fire-and-forget item agents.

Layout

• Control plane: branch df1/control-plane (dir df1-control/ — README is the campaign manual; scripts/, prompts/, queue/items.json)
• Integration branch: df1/integration (starts at origin/main = 4c2297667)
• Durable runtime state: ~/.freshell/df1/ (status files, event ledger, leases) — outside git, survives worktree teardown
• Queue: 235 items → 7 already done / 66 host-limited / 162 queued for the swarm

Pre-flight

• Coordinated npm test at base 4c2297667: GREEN (unit 437 files/4904 tests, server 314/4889, electron 34/350)
• cargo test --workspace baseline: running at kickoff (green required before item worktrees spawn)
• Smoke workers to validate the pipeline: CFG-04, SESSION-05
• Wave 0 (harness enablers): HARNESS-03/04/05/06/11/12/14

Host-limited 66 — verdict

~52 are the Tauri/Windows/installer/updater desktop epic (packaging, wizard, tray, native startup) + 13 MIGRATE upgrade-path items. Recommendation: not worth hands now — park as a future dedicated Windows-desktop campaign; the Linux swarm can't execute them either way. (Plans-only pass remains a user option.)

Frozen rules (full text in df1-control/README.md)

One item = one worktree .worktrees/df1-<id>-<slug> = one agent. Workers commit at phase boundaries, never push/PR, never edit the checklist (evidence files in docs/plans/df1-evidence/<ID>.md instead). Verifier re-runs workers' claimed green commands at the claimed SHA before any merge. Only the gatekeeper merges into df1/integration (batches ~10; per-branch spec ordering proofs; canary e2e set). Items merged in the main phase are merged-unverified-e2e, NEVER done — a close-out Playwright campaign converts them. Resource leases (agent/provision/cargo/pw/sandbox/gate) with TTL heartbeats; nice/ionice all builds; never touch the live server or ports 3001/3002/17871/17872/17874.

PR policy

No PR without explicit user approval (repo rule). Intended shape once approved: themed PRs cut per wave from df1/integration → main (~15–25 total), self-merged on green checks per repo norm.

Progress: orchestrator will post per-wave status comments below. Per-item durable state lives in the ledger; this issue is the human-readable receipt spine.

[danshapiro]

KICKOFF 2026-08-09: base greenness fully established (npm suite 4,904+4,889+350 green; cargo 2,817 green / 0 fail). Smoke workers dispatched: CFG-04 → df1/cfg-04-browser-seed, SESSION-05 → df1/session-05-project-colors (branches from df1/integration). Pipeline validation precedes wave-0.