856 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Ilia Denisov	12e616ceae	feat(payments): send no fiscal receipt; keep the code switchable ... The merchant accepts payments as a sole proprietor on НПД, which is outside 54-ФЗ: there is no online cash register, YooKassa does not serve receipts for that regime at all (checked with their support), and each operation is reported by the merchant to «Мой налог», which issues the чек. So no `receipt` is sent with a payment or a refund. This also removes a failure class rather than just code: a malformed receipt was an API error at payment creation, which broke the purchase outright. The fiscal code is kept dormant rather than deleted. All of it now sits behind one switch, `BACKEND_YOOKASSA_VAT_CODE`: unset — the default — builds and sends nothing; a 54-ФЗ rate code turns «Чеки от ЮKassa» back on unchanged. The return is foreseeable, which is why the switch exists: НПД carries an annual income ceiling, and losing the regime puts 54-ФЗ back in force, at which point this is a deploy-variable edit instead of writing the integration again. The D36 email anchor still gates a direct purchase. It had two justifications — a recovery anchor and the receipt address — and only the second is gone; without an email a paying customer who loses the account loses the chips with it. What was missing is that the rule was enforced but never communicated: the wallet showed the packs to a player signed in through VK or Telegram in a browser, and tapping Buy produced a bare "something went wrong". It now says "add an email in your profile" in the buy tab instead, linking to the profile; spending already-earned chips is untouched. The predicate is a pure function so it is covered by the node-env unit tests rather than needing a browser. Tests: the receipt-off default is pinned by an integration test asserting a purchase carries no receipt, and the dormant path by one that switches a VAT code on and checks the receipt reappears with the right fiscal attributes; plus unit coverage for the enable predicate and the wallet's email rule. A note for whoever runs the numbers next: the shared (svelte + i18n) chunk is now 40 bytes under its 31 KB gzip budget. Decision D51 revised.	2026-07-28 11:40:59 +02:00
Ilia Denisov	395a307eca	feat(payments): reverse refunds issued outside the console ... Two holes on the refund path, both found by asking what happens when a refund does not come from our own `/_gm` button. The merchant cabinet is a second entry point. An operator can refund there, and such a refund never passes through our API — so the money went back while the chips stayed credited, silently. Handle `refund.succeeded`: the refund is re-read from the API (the notification body is no more evidence here than it is for a payment), bound back to its order through the payment id recorded when the payment was minted, and reversed through the same engine. It is idempotent on (provider, refund id), so the event for a refund the console already recorded reverses nothing twice. The reversal engine is full-refund-only by design — it revokes exactly what the pack funded and rejects any other amount — so a partial refund is recorded as nothing at all and logged loudly for an operator. There is no non-arbitrary way to decide how many chips a part-refund costs, and guessing would be worse than asking a human. Second hole: a refund can still be canceled while pending, and the ledger is append-only. Recording on any non-empty refund id therefore risked revoking a customer's chips for money that stayed with us, with no way to take the row back. The console now records only a `succeeded` refund and tells the operator to press again otherwise — the idempotency key returns the same refund rather than paying twice. Tests: unit (GetRefund, the refund notification envelope, a non-final status surfaced to the caller); integration (a cabinet refund is reversed once and a redelivery is a no-op, the event after a console refund changes nothing, a partial refund records nothing, an unconfirmed refund reverses nothing, a pending refund records nothing until it settles and then does). The suite shares one database and the ledger dedupes refunds globally, so the fake provider now mints a refund id per payment — a constant id made one test's refund look like another's duplicate. Decisions D50 (amended) and D52; the notification subscription list in the deploy docs gains refund.succeeded.	2026-07-28 09:18:19 +02:00
Ilia Denisov	92ba527575	feat(payments): settle the direct rail through YooKassa ... Replace Robokassa with YooKassa as the RUB direct-rail provider. The wallet model is untouched: one `direct` segment, the same spend wall, the same per-channel merchant shops (D42) and `shop` on the order (D44). The two providers are not shaped alike, and that drives the change: - Opening a purchase is now an outbound API call (`POST /v3/payments`, single-stage capture, redirect confirmation). The order id is both the `Idempotence-Key` and `metadata.order_id`, so a retried create cannot mint a second payment and a notification always resolves to its order. - YooKassa does NOT sign notifications, so the body is never evidence: it only names a payment, which is re-read with `GET /v3/payments/{id}`, and only that answer is acted on. Two guards ride on it — the payment's metadata must name the order, and its `test` flag must match the shop's, so a test-shop payment can never credit real chips. The sender address is checked against YooKassa's published ranges first, which stops a forger turning each fabricated notification into an outbound call of ours. - A notification lost for good would leave the money taken and the chips unowed, silently. The existing pending-order reaper now asks the provider about each order that reached its expiry age carrying a payment id, and credits the ones really paid — one request per order over its whole life, not polling. - `payment.canceled` records a `failed` event, so a declined payment is finally surfaced to the customer as PAYMENTS.md §9 already specified. - The admin refund moves the money through `POST /v3/refunds` before recording anything; a failed call records nothing, so the ledger cannot claim a refund that did not happen, and the recorded id is the provider's own. - YooKassa has no cabinet-side generic receipt: «Чеки от ЮKassa» registers one only if the request carries it, so every payment and refund now sends an itemized `receipt` to the D36 confirmed email. The VAT rate code is a deploy variable; the settlement subject and method are constants. Robokassa is retired, not deleted: the direct rail falls back to it when no YooKassa shop is configured and no deployment sets its credentials, so reviving it is a credentials change rather than a code change. Its variables are removed from compose, .env.example, write-prod-env.sh and the three workflows, and recorded in backend/internal/robokassa/README.md together with the cabinet configuration and the revival steps. Ledger rows keep `provider = 'robokassa'`; that literal is load-bearing for the idempotency index. No migration and no wire change: `orders.provider_payment_id` already existed, and the client is rail-agnostic. Decisions D47-D51 (revising D41) and stage E12 are baked into the docs.	2026-07-28 08:51:31 +02:00
developer	985ed40639	Merge pull request 'fix(ui): highlight the word the engine played, not the run it abuts' (#291) from fix/offline-highlight-direction into development	2026-07-27 21:46:32 +00:00
Ilia Denisov	27e19e82bd	fix(ui): highlight the word the engine played, not the run it abuts ... The board's green highlight re-derived the play's orientation itself ("the longer run wins"), while the engine settles a lone staged tile under the single-word rule through the validator, because its two orientations can differ in legality. A vertical play that merely abuts a longer horizontal word therefore greened that horizontal run — a word the play does not form — and anchored the score badge on it, while the caption, the score and the committed move all stayed correct. formedGeometry now takes the orientation from the preview, which every preview source already carries (EvalResult.dir: the on-device evaluator, the network evaluate and a reused hint), and no longer infers it. The rule, not the transport, is the trigger, so this fixes online one-word games as well as offline ones. A differential test now walks random positions, asks the engine port for every legal play it can find, and asserts the highlighted cells are exactly the cells of the words the engine says that play forms.	2026-07-27 23:32:59 +02:00
developer	621a1ac99f	Merge pull request 'feat(ui): open the move history at the newest move; scale the landscape rack glyphs' (#289) from feature/history-autoscroll-landscape-rack into development	2026-07-27 19:18:44 +00:00
Ilia Denisov	92700d0646	feat(ui): open the move history at the newest move; scale the landscape rack glyphs ... The move table fills top to bottom, oldest first, so it used to open on the opening moves — the least interesting end of a long game. Pin it to its last row when it is shown (the portrait drawer and the landscape dock alike), once per showing rather than on every arriving move, so a player reading back through the journal is not yanked to the bottom by an opponent's move. The landscape tray shares the narrow left panel, so its tiles — and with them the cqw-sized glyphs — come out markedly smaller than the full-width portrait tray. Scale the letter and Erudit's blank star up a quarter there; the point value keeps its size (it reads fine small, and growing it would crowd the letter on a tile that size).	2026-07-27 21:11:34 +02:00
developer	f383442430	Merge pull request 'feat(variants): default a registered account to Erudit + Russian Scrabble' (#288) from feature/default-variants-scrabble-ru into development	2026-07-27 18:52:13 +00:00
Ilia Denisov	c3d36dda2d	fix(ui): use the guest stubs' "sign in" wording, and link it in Stats ... The New Game hint said "Register" where the Stats and Profile guest stubs say "Sign in". Move the shared word into common.signInLink so the two screens cannot drift, and turn the Stats stub's opening word into the same link to the profile screen.	2026-07-27 20:45:10 +02:00
Ilia Denisov	b6d88da78c	feat(variants): default a registered account to Erudit + Russian Scrabble ... New Game opened on a single variant for everyone, which reads poorly on VK where Russian Scrabble is the familiar game. A registered account now starts with both Russian-alphabet games, so the picker offers a real choice with no pre-selection. A guest stays on Erudit alone and is invited to register for the rest: the device-local guest has no profile at all, so the client-side fallback has to keep matching the server. Registering promotes the set, but only while the guest still carries the untouched guest default. Existing accounts are not backfilled — the set they carry may be a deliberate choice. The Telegram promo start-param becomes additive rather than a replacement, with English Scrabble withheld from a Russian-speaking arrival; otherwise the English campaign link would have taken Russian Scrabble away from every account it onboarded.	2026-07-27 20:38:09 +02:00
developer	69b1a50644	Merge pull request 'fix(offline): keep the local composition; feat(rules): no repeated words in Erudit' (#287) from feature/no-repeat-words into development	2026-07-27 17:46:35 +00:00
Ilia Denisov	f3c08e031e	fix(rules): case-fold the played words, so the rule fires online too ... The no-repeat-words rule never fired in an online game. The move preview builds its set of already-used words from the history the client holds, and the codec upper-cases those words for display, while the evaluator decodes the candidate word to lower — so "БРА" was never found to equal "бра" and every repeat scored as an ordinary play, right up to the server refusing it. Offline was unaffected: that engine compares alphabet-index keys taken from its own journal, which carry no case at all. The tests missed it because they hand-built the played set in the form the server sends rather than deriving it the way the game screen does. They now go through playedWordsFromHistory with history records shaped as the codec produces them — upper-cased words and all — which is the path that was broken; three of the five fail without this fix.	2026-07-27 19:37:34 +02:00
Ilia Denisov	5be8116607	docs(agent): note the UI job's bundle-size gate as a local pre-push step	2026-07-27 19:21:20 +02:00
Ilia Denisov	e011b2ebe5	build(ui): move the rule's played-word set into the lazy dict chunk ... Building the set of words a game has already used belonged with the rest of the rule, behind the same lazy import as the evaluator that consumes it, rather than in the always-loaded game screen. What is left in the app entry — the per-game flag on the decoded GameView and the caption that names a rejected word — costs more than the budget had free, so raise it by the usual kilobyte with the reason recorded alongside the earlier raises.	2026-07-27 19:19:26 +02:00
Ilia Denisov	4f4768b092	fix(rules): name a repeated word in the move preview instead of scoring it ... Composing an already-played word read as a perfectly legal move: the tiles drew as legal, the caption showed "БРА = 6" and the ✅ was enabled, and only the server refused the play with the bare "illegal move" toast. The on-device evaluator already applied the rule, but it reported the refusal as a plain illegal play, so nothing distinguished a repeated word from a misspelling and the caption fell back to the turn label. It now names the word it rejected, and the game screen reads "БРА: уже использовано" above the scores while the tiles stay marked invalid — the composition is wrong, but for a reason the player cannot read off the board, since the word itself is in the dictionary. The verdict is reached on the device before the play is ever offered to the server, in an online game exactly as in an offline one; the offline source reports the same reason through the same field. Only the main word is ever refused: a cross-word the game has already used still stands (it is incidental to laying the main word) and merely scores nothing, so the rule cannot falsely block a play in a game with several words per turn. The scoring of such a play is now pinned to the point on both sides: the engine test and the client test evaluate the same position — РОТ laid across a standing КО, completing an already-played КОТ — and assert the same totals (10 unrestricted, 5 with the rule), so a divergence between the two engines breaks one of them. The client test also replays the exact test-contour position this was reported from.	2026-07-27 19:12:37 +02:00
Ilia Denisov	d7337d24ea	feat(rules): forbid repeating a word already on the board in Erudit ... Russian "Эрудит" treats a word laid on the board as belonging to the game: it cannot be laid again. Neither the solver, the backend nor the offline JS port knew the rule, so a player (and the robot) could replay a word freely. Official Scrabble places no such restriction, so both Scrabble variants keep playing unrestricted. The rule applies in two ways. A play whose main word is already on the board is illegal, and is neither accepted nor generated. A play whose perpendicular cross-word is already there stands — that word is incidental to laying the main word — but scores nothing. The set of played words is the game's own move journal, main words and cross-words alike, compared decoded, so a word spelled with a blank is the same word. It lives in the game layer, not the solver: only a game knows its history, and the solver stays stateless and standard-rules. The backend applies it at submit, at the move preview and over generated moves (filtering and re-ranking them, so neither the robot nor the hint can offer a play the engine would then refuse); the client port does the same for the offline engine and for the on-device preview of an online game. The rule is pinned per game (games.no_repeat_words, set from the variant at creation) rather than keyed on the variant, because a game is replayed from its journal on every open. Applied retroactively it would make an already-played repeat illegal — closing that game as a draw — and would rescore a play whose cross-word repeats an earlier word, shifting a live game's totals. Games created before the rule keep playing without it. The flag rides the wire as a trailing field because the client's preview must score the way the server does, and offline games pin the same answer in their own record.	2026-07-27 18:33:56 +02:00
Ilia Denisov	ebd1f05da8	fix(offline): keep the local game's composition across a state reload ... A local (offline) game persisted no draft: draftGet returned an empty string and draftSave was a no-op, on the assumption that the arrangement is only ever rebuilt from the rack when the game is reopened. The game screen, however, refetches the state on several triggers, and every one of them applied that empty draft over the live composition — dropping the player's pending tiles back into the rack and resetting the rack order. Offline the most visible trigger fires on its own: with no network the live-stream watchdog declares the stream dead after 25 s, the reconnect 4 s later flips app.streamAlive back to true, and the game screen's reconnect effect refetches. Composing a move offline was therefore reset roughly every half minute. Store the draft in the game's own record instead, so a reload restores it and it survives leaving and reopening the app, and clear it wherever the turn advances (a committed move, a resignation, a host skip) so a hotseat seat never inherits the previous player's arrangement. Gate the two stream-driven refetches on the game being a network one: a local game takes its events from the source, so reacting to the stream only cost it a pointless reload.	2026-07-27 18:12:09 +02:00
developer	6ec557d33f	Merge pull request 'feat(social): hide social controls on a deleted opponent's seat' (#286) from feature/deleted-seat-social into development	2026-07-27 15:15:00 +00:00
Ilia Denisov	9471341a0e	feat(social): hide social controls on a deleted opponent's seat ... A deleted account keeps its seats in every shared game, so its opponents still saw the add-friend and block controls on the scoreboard (deletion drops the friendship, so the 🤝 even reappeared for a former friend) and a chat composer nobody was behind. A friend request sent that way was accepted by the server and stayed pending forever. The per-viewer game views now mark such a seat (SeatView.deleted, resolved beside the seat display names by a batch accounts.deleted_at lookup) and the client hides every control aimed at it: add-friend, block, and the chat composer (message + nudge) once no reachable opponent is left. Live events carry the game domain's seat standings and so leave the mark unset, so the delta reducers preserve the cached one. SendFriendRequest and Block against a tombstone are refused with social.ErrAccountDeleted (410 account_deleted) — the source of truth for an older client.	2026-07-27 17:06:10 +02:00
developer	9506f89d9e	Merge pull request 'feat(vk): VK community cover' (#285) from feature/vk-group-cover into development	2026-07-27 14:03:31 +00:00
Ilia Denisov	b53e23fe4d	chore(vk): keep the two chosen covers, drop the rest ... The dark and light covers move up beside the generator as the shipped assets; the six exploratory variants and the contact sheet go. Trims the generator to match: VARIANTS is now only the two covers, and with the retired variants gone so are the knobs nothing reaches any more — the wordmark caption, the branded palette, the whole-board height fit and the non-brand tile face. Left behind, they would read as supported options that no output exercises. `node build-cover.mjs` now reproduces exactly the two committed PNGs.	2026-07-27 15:59:40 +02:00
Ilia Denisov	70b88c567f	feat(vk): move the tile letter to the corner, add the light cover ... Sets the letter in the tile's top-left corner with the value staying bottom right — the in-game tile layout — instead of centring it. The glyph is placed by its ink box rather than the text origin, so every letter lands on the same corner whatever its side bearings and ascent. Adds day-spot: the same crop and camera as night-spot on a light ground, so the chosen composition exists as a light/dark pair.	2026-07-27 15:46:58 +02:00
Ilia Denisov	92a97c6c93	feat(vk): draft the VK community cover ... Adds VK's own cover template (1920x768) and a self-contained generator that renders an Эрудит board in perspective with ГРАМОТНОСТЬ / СОПЕРНИК / ЭРУДИЦИЯ / УМ already played, in six art-direction variants for review. The position is checked, not asserted: assertLegal re-reads the finished grid and fails the build unless the centre is covered, every declared word is on the board, and no maximal run of two or more letters is a word nobody played. All four words are in the Эрудит dictionary and tile values come from scrabble-solver rules.Erudit(). The camera has pitch only, so the perspective warp reduces to an exact per-scanline remap of a flat texture; tile thickness is filled as 3D quads between the board plane and the tile plane. skia-canvas is borrowed from the render sidecar rather than installed a second time for a one-off asset build. Composition respects the two VK keep-outs measured off the template: the top 130 px some clients crop, and the mobile avatar circle over the bottom-left — which is why the default word arrangement keeps that corner empty.	2026-07-27 15:21:46 +02:00
owner	9cdd7138e3	Merge pull request 'chore(docs): update legal info' (#283) from chore/legal-info into development ... Reviewed-on: https://gitea.lan/developer/scrabble-game/pulls/283	2026-07-20 11:03:19 +00:00
Ilia Denisov	30a1baca12	chore(docs): update legal info	2026-07-20 12:53:23 +02:00
developer	9eacb9b115	Merge pull request 'fix(vk): route the Wallet public-offer link out of the Mini App WebView' (#281) from feature/vk-offer-link-escape into development	2026-07-17 18:27:06 +00:00
Ilia Denisov	584384487c	fix(vk): route the Wallet public-offer link out of the Mini App WebView ... The "Public offer" link in the Wallet pointed at the same-origin static /offer/ page with a plain target=_blank anchor and no click handler. The Android VK client ignores target=_blank and navigates its own WebView to the page, stranding the player with no way back to the game (iOS opens a child browser, so it was unaffected). The existing onExternalLinkClick router could not help: it escapes only cross-origin links, and /offer/ is same-origin (a static legal page, not an SPA route). Add onInAppPageLinkClick, which routes a same-origin, non-SPA page out through the host escape hatch (Telegram openLink, VK away.php) while bypassing the cross-origin gate, and attach it to the offer link. Outside a Mini App host it is a no-op and the anchor's own target=_blank stands. The "Rules" (About) and ad-banner links already route correctly (cross-origin + a handler) and are left unchanged.	2026-07-17 20:20:22 +02:00
developer	0ba8fb6514	Merge pull request 'fix(payments): reject HTML-special chars in product titles (VK payment guard)' (#279) from feature/vk-title-guard into development	2026-07-16 19:17:45 +00:00
Ilia Denisov	f60327c1ce	fix(payments): reject HTML-special chars in product titles (VK payment guard) ... A product title containing & < > " ' silently breaks VK purchases: VK HTML-escapes the character in its order_status_change payment-callback echo (e.g. " -> &quot;) but signs the notification over a different form, so the gateway's signature check no longer matches ("vk callback: bad signature") and the purchase never confirms — while get_item (whose request carries no title) still passes. validateProduct now rejects those characters at the admin catalog editor — the single write path for CreateProduct/UpdateProduct/SetProductActive — so a title can't reintroduce the break. Reject, not transform: the operator retypes a clean title (« » guillemets, not straight quotes), so the stored value stays identical everywhere (storefront, wallet, VK box). Docs: docs/PAYMENTS.md §7 + agent field notes; Go Doc on validateProduct. Test: validateProduct HTML-special-char cases. No wire/schema change.	2026-07-16 20:57:04 +02:00
developer	69246eb0c0	Merge pull request 'fix(vk): persist settings via VK Bridge storage; hide competing sign-in in Mini App hosts' (#278) from feature/vk-moderation-fixes into development	2026-07-16 17:12:46 +00:00
Ilia Denisov	6c0daeb177	fix(vk): persist settings via VK Bridge storage; hide competing sign-in in Mini App hosts ... VK moderation follow-ups. 1. Settings (theme, language, board style, reduce-motion, zoom, first-run coachmark flags) were lost between reloads in VK's desktop iframe: Firefox partitions/blocks IndexedDB and localStorage in a cross-origin iframe, so the browser-local store is empty on every reload (a plain tab / PWA keeps them — first-party storage — and Telegram has its own CloudStorage sync). Mirror the prefs (plus the locale, which has no other durable client home on VK) and the coachmark flags to VK Bridge storage (VKWebAppStorageSet/Get), which travels over postMessage to vk.com and survives; reconcile them on the VK launch before the first paint. The VK identity re-derives from the signed launch params each load, so the values reload onto the same account. 2. Inside a proprietary Mini App host (VK or Telegram) the profile now surfaces only email linking — both the Telegram and VK link/unlink entries are hidden (signInProvidersVisible), so a competing sign-in is never advertised (a platform ToS requirement; VK forbids showing a Telegram login, mirrored in Telegram for VK). A provider linked earlier on the web stays attached and is managed from the web; web/native builds show both. Tests: vkprefs codec + signInProvidersVisible unit tests. Docs: ARCHITECTURE, FUNCTIONAL (+_ru). No schema/wire change.	2026-07-15 22:53:58 +02:00
developer	b285e27d55	Merge pull request 'docs(apple): native iOS/iPadOS app plan' (#277) from feature/apple-ios-plan into development	2026-07-15 17:27:30 +00:00
Ilia Denisov	3dfc0932ef	docs(apple): drop remaining [FIXED ...] header tags (sections 8, 12)	2026-07-15 19:26:36 +02:00
Ilia Denisov	e04e97fb66	docs(apple): drop [FIXED] tags from the plan ... Decisions stay recorded; the tag implied false permanence. Open items keep their [OPEN / TRACKED] / [GATE] markers.	2026-07-15 19:24:45 +02:00
Ilia Denisov	ebc413f5e5	docs(apple): add native iOS/iPadOS app plan (apple/PLAN.md) ... Design/continuity doc for the from-scratch SwiftUI iPhone+iPad app: Mac build model, engineering decisions (min iOS 18, apple/ dir, XcodeGen+SPM, @Observable, Swift 6 strict concurrency, SF Symbols, runtime-vector tiles), the five determining optimizations, storage/audio/testing/crash choices, region-aware payment seam with tracked App Store risks, and the full A-L + game-screen UX inventory. Delivery staged; several items tracked for follow-up sessions.	2026-07-15 19:19:31 +02:00
developer	d48797e297	Merge pull request 'native polish 2: two-robots fix, guest offline-host UX, Guest###### name, silent+fast native boot, minSdk 29' (#275) from feature/native-polish-2 into development	2026-07-15 00:26:27 +00:00
Ilia Denisov	fe29c6fe58	chore(android): raise minSdk to 29 (Android 10) ... The bundled WebView build is only compatible from Android 10 (API 29); on Android 9 it lands on the in-app unsupported-engine screen. Declaring minSdk 29 lets RuStore/Google Play block older devices at install rather than shipping a known-incompatible build.	2026-07-15 02:17:13 +02:00
Ilia Denisov	3429dbec5f	fix(boot): native offline-first launch is silent and fast (Android 10) ... Two native offline-first boot glitches (seen on Android 10): - bootOffline forced offlineNoNetwork, so its first successful reconcile healed to online with a spurious "back online" toast on a first launch that actually had connectivity. The boot-assumed offline is now PROVISIONAL: the first probe confirms it — a success heals silently (nothing to come back from), a failure turns it into a real offline whose later recovery does toast. - A native launch with a cached guest session (no email) skipped the offline short-circuit and hung ~25 s on adoptSession's retrying profile fetch in airplane mode. The native channel is offline-first, so it now takes the same reachability-gated fallback (~3 s bound) as an installed email PWA.	2026-07-15 02:17:13 +02:00
Ilia Denisov	74026223ee	feat(account): give a fresh guest a distinct "Guest######" display name ... Every guest showed a bare "Guest" to opponents (e.g. in a random match). Mint the display name as "Guest" + a random six-digit suffix at provisioning, so guests are distinguishable. Not an identifier and not unique — a label only, so collisions are harmless.	2026-07-15 02:17:13 +02:00
Ilia Denisov	896b7f57a7	feat(newgame): skip the take-a-seat prompt for a guest offline host ... A guest host has no meaningful display name to seat, so the offline 'with friends' flow's "do you take a seat?" prompt only produced a nameless seat. For a guest the prompt is skipped: after the master PIN, the two empty player seats show directly. A durable host is still asked.	2026-07-15 02:17:13 +02:00
Ilia Denisov	aa803260a1	fix(game): recognise the device-local guest as "me" in the game header ... The game header identified the viewer's seat only by app.session.userId, but a device-local game (vs_ai / hotseat) created offline is seated under the local guest id (the lobby already matches both). After a merge switched the active account to a durable id, the human seat matched neither, so a vs_ai game showed BOTH seats as robots (the turn still worked — it is seat-index based). seatName now matches app.session.userId OR localGuestId, like the lobby. Completes the v1.22.0 repointLocalGameSeats fix, which only covered games seated under the retired session id.	2026-07-15 02:17:13 +02:00
developer	8758cbd35d	Merge pull request 'native polish: guest-locale banner, seamless guest sign-in (+local-game fix), 'Opponent's turn' label, deploy-authoritative dictionary' (#273) from feature/native-polish-and-dict-deploy into development	2026-07-14 23:07:05 +00:00
Ilia Denisov	1d306ec0fc	chore(ui): change hints symbol for backward unicode compatibility	2026-07-15 00:56:47 +02:00
Ilia Denisov	513b772cd4	feat(game): show 'Opponent's turn' instead of the opponent's name in the turn strip ... When it is not the viewer's turn in an online PvP or vs_ai game, the under-board status now reads the generic 'Opponent's turn' (game.opponentsTurn) rather than the opponent's display name or the robot mark, so whose turn it is reads uniformly. The hotseat branch still names the seat to move (whose device-turn it is matters there), and the seat row below continues to name each player.	2026-07-15 00:34:58 +02:00
Ilia Denisov	da25eac070	feat(link): auto-merge a guest initiator into its durable account (seamless sign-in) ... When a guest links an identity (email/TG/VK) that already belongs to a durable account, the guest-primary rule already made the durable account the survivor and switched the session — but the client still showed an irreversible 'merge two accounts?' confirmation, which is nonsense from the user's side (they are simply signing into their account). The confirm step now merges inline for a GUEST initiator and returns the completed merge (the switched token); a durable initiator still gets the explicit confirmation (consolidating two real accounts is consequential). The active-game guard still refuses, surfaced as the clear error.merge_active_game_conflict message rather than swallowed. Also fixes the merged-away device-local games: their human/host seat was recorded under the retired account id, so after the switch the lobby and game header could not identify 'me' and showed every seat as an opponent (the game still played — turn logic is seat-index based). applyLinkResult now re-points local game seats from the retired id to the survivor (repointLocalGameSeats). Docs: FUNCTIONAL.md (+_ru).	2026-07-15 00:34:58 +02:00
Ilia Denisov	48614e622d	feat(dict): make the build's dictionary version deploy-authoritative ... The dictionary lives on a persistent volume seeded from the image once and never re-seeded, so a redeploy that bumped BACKEND_DICT_VERSION left the new DAWGs unreachable (the volume mount shadows the image copy) and the active version stuck at whatever the admin console last installed — a native offline-first client then fetched the server's older pinned version over the network instead of using its bundled dict. On boot the backend now DELIVERS the build version onto the volume add-only, from a second unshadowed image copy at BACKEND_DICT_SEED_DIR, into DICT_DIR/<version>/ when absent (the flat seed and prior uploads untouched, so in-flight games keep theirs), and InitActiveVersion makes the build version active — except a console-installed version NEWER than the build (compared numerically) is not downgraded by a restart. The .seed_version guard still protects the flat seed's label (a bump is a new subdirectory, never a relabel). The console stays for out-of-band updates. Docs: ARCHITECTURE.md §5, deploy/README.md, seedmarker.go. Tests: engine.DeliverVersion (add-only, idempotent, flat-seed skip), compareDictVersions, and the dictionary-update integration test's deploy-delivers path.	2026-07-15 00:21:20 +02:00
Ilia Denisov	f8aeec8008	fix(account): seed a fresh guest's interface language from the client locale ... A guest was provisioned with only its detected time zone; its PreferredLanguage fell to the 'en' column default. The client already sends its locale in the guest login (GuestLoginRequest.locale), but the gateway dropped it and ProvisionGuest took no language — so a Russian user's brand-new native guest got English language-dependent server content (the ad banner, bot messages) until the client's later language reconcile. Read the locale in the gateway guest handler, thread it through GuestAuth -> ProvisionGuest, and seed PreferredLanguage from it (validated; an unsupported/absent value keeps the 'en' default). Wire field already present — no schema change.	2026-07-15 00:06:23 +02:00
developer	b5fe61279b	Merge pull request 'android: shrink adaptive icon mark 25% + full-bleed legacy square + Erudit-only default for the profileless client' (#271) from feature/native-icons-variant-defaults into development	2026-07-14 20:23:04 +00:00
Ilia Denisov	e07886ecb1	test(ui): update the native offline-first e2e for the Erudit-only guest default ... The offline native guest is now offered only Erudit (the profileless default from the variants fix), so the specs that picked the English "Scrabble" variant timed out. Play Erudit instead: the single `.variant` click both selects it and asserts nothing else is offered; the vs_ai test plays НОЖ from the pinned Erudit rack (ОЖЬЯНАО), and the bundled ru_erudit dawg drives the robot reply.	2026-07-14 22:13:42 +02:00
Ilia Denisov	4a3e12c85a	feat(icons): shrink the Android adaptive mark 25%, give old square launchers the full-bleed master ... The adaptive foreground's asterisk grazed the round mask's safe zone. Scale the foreground mark 0.75 about the icon centre (25% smaller, the letter-to-star arrangement unchanged) so it sits well inside the 61% safe zone. Independently, the legacy square ic_launcher.png now renders the full-bleed master instead of the safe-zone composite, so old Android (< API 26) shows a large mark rather than a shrunk one; the legacy round icon keeps the safe-zone composite (a round mask would clip the master's corner star). Regenerate the layer set, Android res and the brandbook foreground previews; update ICON_BRANDBOOK.md / ICONS.md.	2026-07-14 21:57:32 +02:00