{"agent":"claude","input":"Migrate this Go repository's tests from Ginkgo v1 (github.com/onsi/ginkgo) to Ginkgo v2 (github.com/onsi/ginkgo/v2). First run the test suite as it is with go test -v, save the output, and note the number of specs and every line under any deprecation notice Ginkgo prints. Change every import of github.com/onsi/ginkgo and its subpackages (extensions/table, config, reporters, types) to the v2 path; DescribeTable and Entry now come from the main package. Then remove v1 features that v2 dropped, one kind at a time: specs or setup nodes that take a Done channel (if the body already blocks until the work finishes, drop the parameter and its close call; if it needs a deadline, take a SpecContext and add SpecTimeout or NodeTimeout; never leave a Done parameter in place), Measure blocks, custom reporters and RunSpecsWithDefaultAndCustomReporters (use ReportAfterSuite or the --junit-report flag), CurrentGinkgoTestDescription (use CurrentSpecReport), and GinkgoParallelNode (use GinkgoParallelProcess). For each kind, print the search you ran and the count before and after. Update the ginkgo CLI everywhere it is installed or called: Makefile, CI workflows, scripts and README. Use the v2 install path and replace removed or renamed flags; run each updated command line once to prove the CLI accepts it. Choose the Ginkgo v2 version deliberately: compare what go mod tidy picks on its own with what go get @latest picks, list every other line of go.mod each choice changes including the go directive and gomega, and take the smaller change unless a feature you used needs the newer release. Run go mod tidy and confirm github.com/onsi/ginkgo without /v2 is gone from go.mod. Run the suite again with -v and compare: the same number of specs must run and pass, and no deprecation notice may remain. Do not set ACK_GINKGO_DEPRECATIONS to hide one. Open a pull request with the before and after output.","resources":[{"url":"https://github.com/your-org/your-app"}]}