Clarify release preparation, publishing, tests, and documentation

[samuel-williams-shopify]

The release implementation was difficult to scan: preparation and publishing mixed several responsibilities, task files loaded libraries through relative source paths, and one guide covered the entire release lifecycle. This cleanup makes the operation order explicit, documents the API contracts, and gives preparation, verification, and recovery their own guides while preserving the release checks and artifact handling.

The commits cover:

1. Improve layout and use explicit returns for multi-step methods.
2. Load Bake task dependencies by feature name and load the publisher only when needed.
3. Document parameters, results, failure conditions, and working-directory requirements.
4. Extract named preparation operations while retaining core Bake tasks.
5. Separate publishing, recovery, and registry verification, preserving the existing exception alias.
6. Exercise initialized interfaces with Sus fixtures and mock external boundaries.
7. Reorganize the guides and regenerate distributed agent context.
8. Follow the bake-modernize README template, retaining the GitHub release command and linking to the project documentation.
9. Call utopia:project:update during release preparation, with a documentation URL and dedicated README Releases section for generated content.

Validation: 105 tests and 439 assertions pass, with 474/474 lines covered using the standard Covered integration; RuboCop passes; Decode reports 30/30 public definitions documented; consumer task loading passes. Static documentation renders and crawls successfully, with 184 local links and anchors checked across 17 pages. The local Pagefind search-index step remains unverified: its macOS binary is killed even with --version.

The release hook was also exercised in a disposable checkout: it updates the versioned notes, README, and agent context, preserves the Making Releases command, and produces no further changes when documentation generation is repeated.