[scbrown]

Cloud setup still installed the legacy npm Beads tracker. Bootstrap Seeds from its checksummed release installer and report sd instead. Match Seeds help identity before skipping installation, so the unrelated find/replace tool named sd does not count as a tracker. Optional failures and timeouts keep the session available and report MISSING or UNRECOGNIZED accurately. Download and installer execution are bounded to 30s and 120s.

The existing CI bootstrap suite now runs the whole cloud setup with private copied tools, fixture downloads and no network or board writes. Controls cover both supported Seeds identities, command-name collision, failed help, download/install failure and timeout. Refresh only the two affected legacy-name inventory entries; compatibility names and reasons are retained.

Validation: 19 bootstrap tests, 2 product-name controls, shell syntax, compatibility inventory, and mdBook build passed. Meaningful tests and demo ran under the HOME/resource guard, clean. No live cloud install was performed.

Demo: recording and reproduction caption. Same empty-tool fixture on base 76f63a2e attempts npm Beads; candidate 7d357f9 requests the Seeds release. Both preinstalled Seeds identities skip download. Actual output/timing replay verified; requires downloading and terminal replay, and does not prove a published release or a deployed cloud environment.

Tracking: aegis-8rv. The design/checker update is separate PR #224.

Bead: aegis-8rv

Overlap preflight: 9c011877b5b4d863c2096746790e7c97130521ff8f7bd3f9346db4eac88207f5

• PR docs: align tracker vision with Seeds and guard it #224 @ c53baa9: independent — Both follow aegis-8rv, whose parent explicitly separates the cloud setup behavior into its own PR. PR224 changes only vision.md and the tracker-guidance checker/tests; this candidate changes setup-environment.sh, bootstrap tests, installing.md, the affected compatibility inventory and its demo. Fresh exact-head file inventory is disjoint; neither PR supersedes the other.