GitHub / repository rename checklist (deferred)

This tracker supports #113: a future repo or org rename (and optionally Go module path change) is intentionally not bundled into the Buck/policy migration. When you rename, sweep the surfaces below once in a coordinated pass—there is no Buck target that can prove cross-site consistency.

Source and config

Area	Examples
Go module	module line in src/searchbench-go/go.mod; github.com/... import paths everywhere (regenerate IDE/refs only after project-go-deps if go.sum churns).
Pkl @go.Package	configs/schema/**/*.pkl go.Package.name literals; rerun buck2 run //src/searchbench-go:pkl_go_types (+ release types if touching SearchBenchRelease).
Flake URLs	flake.nix, flake.lock only if flakes point at github: substitutes (normally they don't).

UX and CI

Area	Examples
Git remote / clone URLs	CONTRIBUTING snippets, onboarding docs, any hard-coded github.com/becker63/searchbench-go in markdown.
GitHub Actions	Workflow checkout repos, caches keyed by workspace, issue/annotation links.
Pages / docs base	VitePress base: in docs config and links like becker63.github.io/searchbench-go; update Development — Docs site.
AGENTS.md / Cursor rules	Any canonical clone URL or repo label.

Search hints

Replace the old slug in one pass:

# Example only — replace OLD/NEW before running outside this doc.
rg 'becker63/searchbench-go|github\.com/becker63/searchbench-go' AGENTS.md src/docs README.md .github flake.nix

After substantive URL or module edits: nix develop then buck2 test //:check_full as usual.