Bump suno-band-manager registry entry to v1.7.2

[zarlor]

Summary

Updates the registry/community/suno-band-manager.yaml registry manifest to point at the v1.7.2 release of the Suno Band Manager module.

Field	Old	New
version	1.7.0	1.7.2
approved_tag	v1.7.0	v1.7.2
approved_sha	da591c9	cacb332
approved_date	2026-04-26	2026-04-29

Release notes: https://github.com/zarlor/suno-band-manager/releases/tag/v1.7.2

Supersedes #11 (v1.7.1 bump). v1.7.2 is a strict superset — the v1.7.1 changes (JSON archives + auto-refreshing companion docs for audio analysis) plus the v1.7.2 multi-band architecture fixes are all included in this release.

What's new in v1.7.2

Multi-Band Architecture — Per-Band Playlist YAML as Single Source of Truth

Closes a multi-band drift class discovered while reviewing a project's second band's playlist:

• The first band had a docs/{band-slug}-playlist.yaml as a single source of truth, but a second band did not.
• The second band's track sequence was duplicated across the band profile YAML's playlist: block, voice-context narratives, and ordering doc — drifting independently as new tracks published.
• The module convention had not picked a winner; per-band YAML was the right answer but wasn't documented or scaffolded.

A second symptom: playlist-sequencing-data.py --companion (introduced in v1.7.1) wrote to a single global path docs/playlist-sequencing-data.md, so two bands' runs overwrote each other.

A third symptom: project-specific band names were hardcoded in two scripts' band-display lookups.

Fixed

• Per-album companion paths — playlist-sequencing-data.py --companion now writes to docs/{band-slug}-playlist-sequencing.md. Multiple bands no longer overwrite each other.
• Apostrophe-aware slugify in _shared/json_archiver.py.
• Hardcoded band-name lookups removed from validate-sidecar.py and regenerate-index-sections.py — band-name → slug maps now derived dynamically from docs/band-profiles/*.yaml files.

Added

• scaffold-playlist.py new utility in suno-band-profile-manager/scripts/ — bootstraps docs/{band-slug}-playlist.yaml for any band. Default mode writes empty template; --from-songbook pre-populates from existing songbook entries.
• validate-profile.py v2.1.0 — checks per-band playlist YAML exists for any band with songbook entries; flags deprecated in-profile playlist: block.
• New "Per-Band Playlist YAML" section in profile-schema.md documenting the convention.
• New Multi-Band Discipline principle in creed.md, activation-loaded for Mac.
• Band creation flow in suno-band-profile-manager/SKILL.md now scaffolds the playlist YAML in the same write batch as the profile YAML.
• Cross-references updated in playlist-sequencing-methodology.md, capabilities.md, reconcile.md, save-memory.md.

Bundled v1.7.1 changes (still in this release)

• _shared/companion_writer.py + _shared/json_archiver.py — marker-based MD-companion-file refresh + JSON archive layer
• --archive and --companion flags on playlist-sequencing-data.py, batch-full-analysis.py, analyze-audio.py, audio-deep-analysis.py (default ON; opt out with --no-archive / --no-companion)
• 5 Suno-knowledge findings folded upstream into reference docs (brass-out limitation, brass-band gravity, Camelot framework limits, Replace Section seam quality, Mid-Word Vowel Anchoring)

Test plan

• Per-album companion paths verified working — both solitary-fire-playlist-sequencing.md and lennys-voice-playlist-sequencing.md populate independently from the same script
• scaffold-playlist.py tested empty template + --from-songbook flows (smoke-tested in /tmp scaffold-test-area)
• validate-profile.py v2.1.0 correctly flags deprecated in-profile playlist block on a real profile
• validate-sidecar.py runs cleanly with dynamically-derived band-display map (51 published songs, 0 errors)
• regenerate-index-sections.py runs cleanly with the same dynamic derivation
• All 4 audio analysis scripts still emit valid JSON to stdout (pipe-friendly)
• Module manifest version bumped to 1.7.2 in both module.yaml and marketplace.json
• CHANGELOG.md updated with full v1.7.2 release notes
• Tag v1.7.2 pushed; GitHub Release created

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated Suno band manager to version 1.7.2 with latest approval metadata.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 13853756-972a-472c-bb5d-122dcef08980

📥 Commits

Reviewing files that changed from the base of the PR and between 2952bed and 92084a9.

📒 Files selected for processing (1)

• registry/community/suno-band-manager.yaml

---

Walkthrough

The Suno band manager package in the registry is bumped from version 1.7.0 to 1.7.2, with corresponding updates to the approval tag, commit SHA, and approval date.

Changes

Cohort / File(s)	Summary
Package Version Update registry/community/suno-band-manager.yaml	Version bumped from 1.7.0 to 1.7.2 with corresponding updates to approved_tag (v1.7.0 → v1.7.2), approved_sha, and approved_date.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Bump suno-band-manager registry entry to v1.7.0 #10: Sequential version bump of the same suno-band-manager package with identical manifest field updates
• Add Suno Band Manager community module #7: Earlier registry metadata update for the same manifest file with the same release fields

Poem

🐰 A tiny hop, a version leap,
From 1.7.0, a promise to keep,
To 1.7.2, approved with care,
New hash, new date, fresh registry air! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically summarizes the main change: bumping the suno-band-manager registry entry from v1.7.0 to v1.7.2.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the Suno Band Manager community registry manifest to reference the upstream v1.7.2 release.

Changes:

• Bumped version from 1.7.0 to 1.7.2
• Updated approved_tag, approved_sha, and approved_date to match the new release

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.