Integrate BACKBEAT SDK and resolve KACHING license validation

Major integrations and fixes:
- Added BACKBEAT SDK integration for P2P operation timing
- Implemented beat-aware status tracking for distributed operations
- Added Docker secrets support for secure license management
- Resolved KACHING license validation via HTTPS/TLS
- Updated docker-compose configuration for clean stack deployment
- Disabled rollback policies to prevent deployment failures
- Added license credential storage (CHORUS-DEV-MULTI-001)

Technical improvements:
- BACKBEAT P2P operation tracking with phase management
- Enhanced configuration system with file-based secrets
- Improved error handling for license validation
- Clean separation of KACHING and CHORUS deployment stacks

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

pubsub/adapter_hmmm.go

@@ -5,25 +5,25 @@ import (
 	"fmt"
 )
 
-// GossipPublisher is a thin wrapper around the BZZZ PubSub system that
+// GossipPublisher is a thin wrapper around the CHORUS PubSub system that
 // satisfies the hmmm.PubSubAdapter interface. It ensures that HMMM messages
 // are published as raw JSON payloads to dynamic, per-issue topics.
 type GossipPublisher struct {
 	ps *PubSub
 }
 
-// NewGossipPublisher creates a new HMMM adapter for the BZZZ pubsub system.
+// NewGossipPublisher creates a new HMMM adapter for the CHORUS pubsub system.
 func NewGossipPublisher(ps *PubSub) *GossipPublisher {
 	return &GossipPublisher{ps: ps}
 }
 
 // Publish ensures the agent is subscribed to the per-issue topic and then
 // publishes the raw payload. This method is the primary bridge between HMMM's
-// routing logic and BZZZ's underlying gossipsub network.
+// routing logic and CHORUS's underlying gossipsub network.
 //
 // It performs two key actions:
-// 1. Joins the dynamic topic (e.g., "bzzz/meta/issue/42") to ensure message delivery.
-// 2. Publishes the byte payload directly, bypassing the standard BZZZ message envelope.
+// 1. Joins the dynamic topic (e.g., "CHORUS/meta/issue/42") to ensure message delivery.
+// 2. Publishes the byte payload directly, bypassing the standard CHORUS message envelope.
 func (g *GossipPublisher) Publish(ctx context.Context, topic string, payload []byte) error {
 	// 1. Ensure the node is subscribed to the dynamic topic.
 	//    This is idempotent and safe to call multiple times.