Ilia Denisov
57c778f9b2
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 13s
CI / ui (pull_request) Successful in 54s
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 57s
Collapse the two per-language Telegram bots into one unified bot and
replace language-based variant gating with explicit per-user variant
preferences.
- Telegram: one bot; drop service_language and the supported_languages
set everywhere (DB, account, auth, FlatBuffers Session wire, gateway,
connector proto). The single bot renders chat and out-of-app push in
the recipient's preferred_language; remove the game-language push
routing override (notify Intent.Language / push Event.language).
- Preferences: new accounts.variant_preferences (text[], DB default
{erudit_ru}, CHECK non-empty + subset of the three variants). Gates
the New Game picker, vs-AI and the friend invitation the player
creates, enforced server-side (HTTP 400 otherwise); an invited friend
may still accept any variant. Edited on the Settings screen; variants
are Erudit-first everywhere.
- Admin: drop the per-bot language selectors (broadcast / send-to-user)
and the feedback channel_lang column/field.
- Env/CI: collapse TELEGRAM_BOT_TOKEN_{EN,RU}, TELEGRAM_GAME_CHANNEL_ID_{EN,RU},
VITE_TELEGRAM_LINK{,_EN,_RU} and VITE_TELEGRAM_GAME_CHANNEL_NAME_{EN,RU}
to single unsuffixed names; drop GATEWAY_DEFAULT_SUPPORTED_LANGUAGES.
- Docs updated (ARCHITECTURE, FUNCTIONAL + _ru, platform/telegram, gateway,
backend, ui, UI_DESIGN, PRERELEASE).
The migration squash is deferred to a follow-up PR.
37 lines
1.5 KiB
Protocol Buffer
37 lines
1.5 KiB
Protocol Buffer
syntax = "proto3";
|
|
|
|
// Package scrabble.push.v1 is the backend -> gateway live-event control channel.
|
|
// The gateway opens Subscribe once at startup and keeps the stream open; the
|
|
// backend pushes one Event per notification intent. The payload is an opaque
|
|
// FlatBuffers message (the scrabblefb.* tables) that the gateway forwards to the
|
|
// client without re-interpreting it. The transport is plain gRPC server-stream
|
|
// (ARCHITECTURE.md §2); the client edge is Connect-RPC (gateway/proto/edge).
|
|
package scrabble.push.v1;
|
|
|
|
option go_package = "scrabble/pkg/proto/push/v1;pushv1";
|
|
|
|
// Push is the unidirectional live-event channel from backend to gateway.
|
|
service Push {
|
|
// Subscribe opens the single backend -> gateway event stream. The backend
|
|
// sends every event for every user; the gateway fans them out to the active
|
|
// client subscriptions by user_id.
|
|
rpc Subscribe(SubscribeRequest) returns (stream Event);
|
|
}
|
|
|
|
// SubscribeRequest opens a push subscription. gateway_id identifies the gateway
|
|
// instance for logging; the MVP backend keeps no per-gateway state.
|
|
message SubscribeRequest {
|
|
string gateway_id = 1;
|
|
}
|
|
|
|
// Event is one live-event frame. kind is the notification catalog kind
|
|
// (your_turn, opponent_moved, chat_message, nudge, match_found). payload is the
|
|
// FlatBuffers-encoded body for that kind. event_id is a correlation id the
|
|
// gateway carries through to the client envelope.
|
|
message Event {
|
|
string user_id = 1;
|
|
string kind = 2;
|
|
bytes payload = 3;
|
|
string event_id = 4;
|
|
}
|