Add chorus-entrypoint label to standardized label set

**Problem**: The standardized label set was missing the `chorus-entrypoint`
label, which is present in CHORUS repository and required for triggering
council formation for project kickoffs.

**Changes**:
- Added `chorus-entrypoint` label (#ff6b6b) to `EnsureRequiredLabels()`
  in `internal/gitea/client.go`
- Now creates 9 standard labels (was 8):
  1. bug
  2. bzzz-task
  3. chorus-entrypoint (NEW)
  4. duplicate
  5. enhancement
  6. help wanted
  7. invalid
  8. question
  9. wontfix

**Testing**:
- Rebuilt and deployed WHOOSH with updated label configuration
- Synced labels to all 5 monitored repositories (whoosh-ui,
  SequentialThinkingForCHORUS, TEST, WHOOSH, CHORUS)
- Verified all repositories now have complete 9-label set

**Impact**: All CHORUS ecosystem repositories now have consistent labeling
matching the CHORUS repository standard, enabling proper council formation
triggers.

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

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

internal/server/server.go

@@ -341,6 +341,9 @@ func (s *Server) setupRoutes() {
 			r.Put("/{agentID}/status", s.updateAgentStatusHandler)
 		})
 
+		// Bootstrap peer discovery for P2P mesh formation
+		r.Get("/bootstrap-peers", s.HandleBootstrapPeers)
+
 		// SLURP proxy endpoints
 		r.Route("/slurp", func(r chi.Router) {
 			r.Post("/submit", s.slurpSubmitHandler)