feat: add accountable identity and reciprocal artist sharing

[chubes4]

Problem

Community already has or tracks managed public voices, author-spoofing defenses, recurring prompts, taxonomy classification, and named agent experiments. The remaining gap is the product trust boundary around universal automation disclosure, reciprocal artist sharing, structured collaboration, and reporting/appeal.

Existing work to consume, not duplicate

• PR fix: prevent community author spoofing #236: bind create attribution to trusted actor.
• PR feat: add accountable managed public voices #239: accountable managed artist/venue public voices and bounded automation metadata, merged pending release.
• PR fix: bind community updates to execution actor #237: remaining update authorization/capability ceilings.
• Phase 5: rethink the room set — the forum needs a recurring-prompt ENGINE, not better category labels #80: recurring-prompt and artist-sharing ritual.
• Phase 5 follow-up [experiment]: Sarai Chinwag as a remote-invoked forum participant (agent bundle) #90: transparent named agent experiment and kill conditions.
• Replace local-only topic taxonomy pickers with network classification #241/fix: replace local topic taxonomy pickers with network classification #242: network taxonomy classification and human correction precedence.
• Phase 6 [DESIGN]: make the party fun — wire the chill-rank/upvote/badge play layer into the engine + the network #92: badge/play-layer integration.
• Phase 3 [DESIGN]: cross-network living-room feed — curated digest cards, NOT a firehose #73: human-first feed and machine-volume restraint.

Outcome

Community sharing occurs through accountable identities and tended reciprocal rituals, with clear disclosure and private moderation paths.

Acceptance criteria

Universal automated disclosure

• Disclose agent-authored topics/replies even when no artist/venue public voice is selected.
• Render disclosure consistently in topic lists, topic leads, replies, activity feeds, excerpts, notifications, abilities/REST, and moderation context.
• Reuse trusted execution-principal metadata.

Reciprocal artist sharing

• Compose releases with Phase 5: rethink the room set — the forum needs a recurring-prompt ENGINE, not better category labels #80's recurring ritual.
• Define duplicate-link, cooldown, and repetitive-promotion rules.
• Require managed artist authority only when posting as that artist; ordinary musicians may still discuss their own work under their account identity.

Structured collaboration

• Add bounded intents such as feedback request, collaborator search, and local connection.
• Compose with canonical topic entities and location taxonomy rather than a new relationship graph.

Reporting and appeal

• Add private reporting from topics, replies, and profiles.
• Include impersonation and deceptive-automation reasons.
• Record moderation disposition and provide an accountable correction/appeal route.

Badge semantics

• Never present a self-declared Artist/Professional role as verified authority.
• Distinguish broad role badges from managed artist/venue authority.
• Do not invent a generic verified human badge.

Measurement

• Measure unique non-staff humans, distinct artists, cross-artist replies, repeat contributors, promotion-to-reply ratio, and upheld reports/appeals.
• Exclude automated contributions from human participation metrics.

Non-goals

• No follower graph.
• No paid verification system.
• No AI-content detector.
• No second identity or prompt substrate.

Evidence

• https://www.reddit.com/r/musicians/comments/1s80y1n/is_there_a_chatroom_like_discord_for_musicians/
• https://www.reddit.com/r/musicians/comments/1uthggu/kinda_wanna_build_a_music_community_on_discord/