fix(distribution): manage dotfiles' cloud bootstrap — its adoption already landed

[kyle-sexton]

Summary

Corrects a wrong exclusion recorded in #397: dotfiles was left out of the cloud-bootstrap component's targets on the claim it had no adoption yet, but melodic-software/dotfiles main already carries .claude/cloud-bootstrap.sh.

Fix

Drop the stale exclusion comment and add cloud-bootstrap to dotfiles' managed list. Verified live via the GitHub contents API: dotfiles main has the bootstrap (an older generic generation, 70 lines, no repo-specific content — safe to converge), the SessionStart hook registration, and the full baseline plugin declaration. The clone that informed the original comment was on a stale feature branch. dotfiles is already a sync target, so the App installation's selected-repo set is untouched.

Verification

• distribution/sync-manifest.sh validate: Manifest valid: 38 components, 8 targets.
• plan --targets melodic-software/dotfiles renders 100755 components/cloud-bootstrap/cloud-bootstrap.sh -> .claude/cloud-bootstrap.sh.

No linked issue

Related

• feat(cloud-bootstrap): add canonical synced repo cloud bootstrap #397 (component introduction; recorded the exclusion this PR reverses)
• docs: reconcile cloud-fleet setup, freeze the renames map, add a retirement policy claude-code-plugins#2885 (fleet audit that surfaced the discrepancy)

🤖 Generated with Claude Code

https://claude.ai/code/session_012tKxg98B3QySqEPf8UqwX3

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[claude]

Claude finished @kyle-sexton's task in 1m 41s —— View job

---

Claude finished the review

• Gather context (PR body, diff, custom instructions)
• Read CLAUDE.md and repo conventions
• Read changed file and surrounding manifest
• Verify claims (manifest structure, cross-references)
• Post findings

Summary

This is a clean, minimal, self-contained fix: it removes the stale dotfiles: no cloud-bootstrap adoption yet exclusion comment and adds cloud-bootstrap to melodic-software/dotfiles's managed list in distribution/sync-manifest.yml.

Verified statically:

• The new cloud-bootstrap entry is inserted in the correct alphabetical position within the melodic-software/dotfiles target's managed list (between claude-review-caller and editorconfig-checker), consistent with every other target block in the file.
• No other file in the repo (distribution/README.md, distribution/REVIEW-CREDENTIAL.md, distribution/sync-manifest.test.sh, components/cloud-bootstrap/README.md, components/cloud-bootstrap/cloud-bootstrap.test.sh) references the removed exclusion comment or asserts a cloud-bootstrap-specific target list, so nothing else needs a matching update.
• The removed comment's sibling exclusions (standards, claude-code-plugins, medley) are untouched and still accurate — this PR only reverts the dotfiles line, as intended.

One limitation: this review lane's Bash tool required interactive approval to execute distribution/sync-manifest.sh validate/plan, which isn't available in this non-interactive context, so I could not independently re-run the validator or plan --targets melodic-software/dotfiles myself. I relied on static inspection of the manifest and its schema/tests instead; the PR description already reports passing output for both (38 components, 8 targets; correct cloud-bootstrap.sh -> .claude/cloud-bootstrap.sh render). Likewise, the live claim that melodic-software/dotfiles's main branch already carries .claude/cloud-bootstrap.sh is an external fact I have no network access to re-verify here — the PR author states it was checked via the GitHub contents API.

No bugs, inconsistencies, or style issues found in the diff. No inline comments needed.

[github-actions]

Claude has reviewed this PR 1 time. The lane skips further automatic reviews after 5; deleting this comment resets the count.