hzhang
a43ff2de62
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.
11 lines
580 B
SQL
11 lines
580 B
SQL
-- 002_topic_announce_target.sql — move announce-channel routing from
|
|
-- backend env to per-topic config. Topic creator picks which Fabric
|
|
-- guild + announce channel to broadcast lifecycle events to (a single
|
|
-- backend deployment can serve topics broadcasting to multiple guilds/
|
|
-- channels). Both fields are nullable; null means "do not broadcast
|
|
-- for this topic" (intentional opt-out).
|
|
|
|
ALTER TABLE topics
|
|
ADD COLUMN announce_guild_base_url VARCHAR(255) NULL AFTER cancelled_reason,
|
|
ADD COLUMN announce_channel_id VARCHAR(64) NULL AFTER announce_guild_base_url;
|