Snapshot import and module rename #34

Parent

Spec: #33 (Baseline release). Section numbers refer to its Implementation Decisions.

What to build

The wand repository gains its code: a byte-identical copy of the go-rod Snapshot minus the agreed exclusions, followed by the rename to github.com/headlesslab/wand. After this ticket a developer clones wand, builds it with Go 1.21 or newer, and runs the root suite locally against a browser of their choice through the -wand=bin= flag. Spec sections 1 and 2; ADR-0001, ADR-0002; ticket #16.

Acceptance criteria

• Commit 1, Import go-rod snapshot 393ac0d: the upstream tree at 393ac0d60b53f3c4a9b2a6504d250cbada55b546 minus .github/, the root README, fixtures/design.sketch, lib/utils/check-issue, lib/utils/rename, lib/launcher/revision/, lib/examples/anti-bot-detection and lib/examples/debug-deadlock. The only deviation is the removed check-issue use line in go.work. The commit message carries the upstream URL, the full hash, the exclusion list and the deviation.
• Verification recipe recorded in the PR: clone upstream at the hash, delete the excluded paths, diff -r against commit 1; the only difference is that one go.work line.
• Commit 2, Rename module to github.com/headlesslab/wand: module path and every import; root package wand; nested example module paths; go.work tracked and every go directive at 1.21; LICENSE is upstream's MIT text with Copyright 2019 Yad Smood and Copyright 2026 headlesslab; a root NOTICE with the attribution text decided in Choose the snapshot commit, the packages that come over, and how provenance is recorded #16; the -rod= CLI flag becomes -wand=; package READMEs say wand.
• A minimal English README and a Chinese README, each with the lineage paragraph (linking go-rod's repository and NOTICE) and a placeholder Roadmap section; the full READMEs come with the documentation ticket.
• go build ./... && go vet ./... pass in all three modules on Go 1.21.x and Go stable from the workspace root, and with GOWORK=off.
• The root suite runs locally against a system Chrome via -wand=bin=... with the same outcome as the Run upstream's test suite against current Chrome stable and record what breaks #14 report (only its known failures).
• No behaviour change beyond the rename; the pinned dependency graph is untouched.

Blocked by

• None (can start immediately).