feat: per-topic announce target (move guild+channel from env to topic row)

Operator decision: backend env hard-coding a single guild/channel was
wrong because (a) one Center can host many guilds and (b) one guild
can have many announce channels for different purposes. The
proposing agent now chooses where this topic's lifecycle events go,
passed as create-topic params and stored on the topic row.

Schema migration 002:
- ALTER topics ADD announce_guild_base_url VARCHAR(255) NULL,
                  announce_channel_id     VARCHAR(64)  NULL.
- Both nullable; one-of-two is rejected at POST time; both null =
  topic creator opted out of broadcasts (announcer skips with log).

handlers/topics.go: createTopicBody adds announce_guild_base_url +
announce_channel_id; validates both-or-neither.

fabric/announce.go: rewritten signature. NewAnnouncer takes only
the system api key. PostTopicAnnouncement + PostLifecycleEvent take
a Target {GuildBaseURL, ChannelID} per call. Zero-value Target -> skip.

orchestrator/ticker.go: new helper topicTarget(topic) extracts the
target from the topic row; all broadcasts route through it.

verdict.go: same per-topic target extraction at completion.

config: removed FabricGuildBaseURL, FabricAnnounceChannelID,
FabricBotBearerToken from the Config struct + env reads.
FabricSystemAPIKey env renamed to DIALECTIC_FABRIC_SYSTEM_API_KEY
to disambiguate from the Fabric backend's own
FABRIC_BACKEND_GUILD_SYSTEM_API_KEY (operator: paste the same value
into both - one says "I am the system caller", the other says "I
accept this caller as system").

FABRIC_BOT_BEARER_TOKEN is gone entirely. The upgraded Guild
ApiKeyGuard accepts x-fabric-system-key alone for announce posts;
no per-user Bearer needed. Pairs with the matching change on
nav/Fabric.Backend.Guild commit 985b06a.

internal/httpapi/handlers/verdict.go

@@ -119,14 +119,20 @@ func (h *VerdictHandler) Submit(w http.ResponseWriter, r *http.Request) {
 
 	// Lifecycle broadcast — completed event. Best-effort; runs async
 	// outside the request context so a slow Fabric doesn't slow the
-	// judge's response.
+	// judge's response. Target is per-topic (nil announcer or nil
+	// target on topic → silently skipped by announcer).
 	if h.announcer != nil {
-		go func(t *fabric.Announcer, tID, title string, judge string) {
-			summary := fmt.Sprintf("verdict published by judge=%s. Use dialectic_view_verdict to see the structured result.", judge)
-			if err := t.PostLifecycleEvent(context.Background(), tID, title, "completed", summary); err != nil {
-				// silent failure; the announcer logs internally
+		var tgt fabric.Target
+		if topic.AnnounceGuildBaseURL != nil && topic.AnnounceChannelID != nil {
+			tgt = fabric.Target{
+				GuildBaseURL: *topic.AnnounceGuildBaseURL,
+				ChannelID:    *topic.AnnounceChannelID,
 			}
-		}(h.announcer, verdict.TopicID, topic.Title, caller.ID)
+		}
+		go func(t *fabric.Announcer, tID, title, judge string, target fabric.Target) {
+			summary := fmt.Sprintf("verdict published by judge=%s. Use dialectic_view_verdict to see the structured result.", judge)
+			_ = t.PostLifecycleEvent(context.Background(), target, tID, title, "completed", summary)
+		}(h.announcer, verdict.TopicID, topic.Title, caller.ID, tgt)
 	}
 
 	writeJSON(w, http.StatusCreated, map[string]any{