keyhunter/.planning/phases/04-input-sources/04-01-PLAN.md

phase, plan, type, wave, depends_on, files_modified, autonomous, requirements, must_haves

phase	plan	type	wave	depends_on	files_modified	autonomous	requirements	must_haves
04-input-sources	01	execute	0		go.mod go.sum	true		truths artifacts key_links go-git/v5, atotto/clipboard, x/exp/mmap are available as imports go build ./... succeeds with new dependencies path provides contains go.mod Module declarations for go-git, clipboard, and x/exp github.com/go-git/go-git/v5 path provides go.sum Checksums for added dependencies from to via pattern go.mod module cache go mod tidy go-git/go-git/v5

Add the three external Go dependencies that Phase 4 input sources require: - `github.com/go-git/go-git/v5` — git history traversal (INPUT-02) - `github.com/atotto/clipboard` — cross-platform clipboard access (INPUT-05) - `golang.org/x/exp/mmap` — memory-mapped large file reads (CORE-07)

Purpose: Wave 0 dependency bootstrap so the parallel source implementation plans (04-02, 04-03, 04-04) compile cleanly on first attempt with no dependency resolution thrash. Output: Updated go.mod and go.sum with all three modules resolved.

<execution_context> @$HOME/.claude/get-shit-done/workflows/execute-plan.md @$HOME/.claude/get-shit-done/templates/summary.md </execution_context>

@.planning/PROJECT.md @.planning/ROADMAP.md @.planning/STATE.md @.planning/phases/04-input-sources/04-CONTEXT.md @go.mod Task 1: Add go-git, clipboard, and x/exp/mmap dependencies - go.mod - .planning/phases/04-input-sources/04-CONTEXT.md go.mod, go.sum Run the following commands from the repo root in order:

go get github.com/go-git/go-git/v5@latest
go get github.com/atotto/clipboard@latest
go get golang.org/x/exp/mmap@latest
go mod tidy
go build ./...

Verify the require block in go.mod now contains direct entries (non-indirect) for:

github.com/go-git/go-git/v5 vX.Y.Z
github.com/atotto/clipboard vX.Y.Z
golang.org/x/exp vYYYYMMDD-hash

If go build ./... fails, do NOT try to fix anything beyond the dependency graph — unrelated build failures must be surfaced. If go mod tidy moves a module to indirect, that is acceptable only if no source file yet imports it; the follow-on plans in Wave 1 will promote them to direct.

Do NOT modify any source files in this plan. This is dependency bootstrap only. go build ./... && grep -E "go-git/go-git/v5|atotto/clipboard|golang.org/x/exp" go.mod <acceptance_criteria> - grep "github.com/go-git/go-git/v5" go.mod returns a match - grep "github.com/atotto/clipboard" go.mod returns a match - grep "golang.org/x/exp" go.mod returns a match - go build ./... exits 0 - go.sum contains entries for all three modules </acceptance_criteria> All three new modules are present in go.mod, go.sum has their checksums, and go build ./... succeeds.

- `go build ./...` succeeds - `go vet ./...` succeeds - `grep -c "go-git/go-git/v5\|atotto/clipboard\|golang.org/x/exp" go.mod` returns 3 or more

<success_criteria> Dependencies resolved and build is green. Wave 1 plans can import from these modules without needing their own go get calls. </success_criteria>

After completion, create `.planning/phases/04-input-sources/04-01-SUMMARY.md` with: - Resolved version numbers for the three modules - Any warnings from `go mod tidy` - Confirmation that `go build ./...` passed