docs(discovery): correct the Goose install row in the test plan

[pengyuzhang]

The test plan installs T-CLI-09 with npm i -g @block/goose-cli@<pin>. That package does not exist: the @block scope has no goose-cli on the npm registry, and a live install run against an Ubuntu guest surfaced it as a 404 rather than as a version mismatch.

The obvious substitution is the trap, and it is why this is worth its own change. The unscoped goose-cli package on npm is a wrapper around the database migration tool of the same name. Taking it would put an unrelated binary called goose on PATH, and the harness would record a successful install of the wrong product — a false positive manufactured by the test rig itself rather than found in the collector.

The row stays in the inventory with its channel marked unsettled, so the entry is visible as unresolved rather than quietly dropped.

Verification

$ curl -s https://registry.npmjs.org/@block%2fgoose-cli
{"error":"Not found"}

$ curl -s https://registry.npmjs.org/goose-cli | jq -r .description
A wrapper for the goose database migration tool.

Every other CLI row in that table installs cleanly at a pinned version; this is the only one that does not resolve.