Release 2.1.0.0: ciclo 2.1 da main, sem Comunidades e sem a nova janela de configurações

.claude/agents/winzapp-implementer.md

@@ -83,7 +83,7 @@ uv run pytest tests/test_<what you touched>.py
 ```
 
 Run the test files for what you changed. CI runs the whole suite on every PR;
-run `uv run pytest -n auto` locally only for a cross-cutting change. Never pass
+run `uv run pytest` serially, at most once, locally only for a cross-cutting change. Never pass
 `--run-wx-gui`.
 
 Hand the diff to `winzapp-reviewer` before opening a PR. Report what you did,

.claude/agents/winzapp-reviewer.md

@@ -131,7 +131,7 @@ for n, line in enumerate(open(sys.argv[1], encoding="utf-8", errors="replace"),
 EOF
 ```
 
-Non-Latin letters are normal inside `client/languages/*.json` string values
+Non-Latin letters are normal inside `translations/**/*.po` string values
 and the changelogs; they are a finding anywhere else, and a `Cf` character
 (bidi control, zero-width) is a finding everywhere.
 
@@ -197,12 +197,13 @@ release before.
   correlation ID and is matched to a pending virtual message **by message
   type**. Changing that matching swaps real WhatsApp IDs between unrelated
   messages — wrong status, wrong audio played.
-- **Every locale.** Any user-facing string exists in every file named by
+- **Every locale.** Any user-facing string exists in every catalog
+  (`translations/<locale>/LC_MESSAGES/winzapp.po`) named by
   `language_map.json`, with matching `{}` placeholders and `&&` for a
   literal ampersand.
 - **Established terminology.** A new or changed value uses the words its own
-  locale file already uses for that concept — grep the file to check. Flag a
-  synonym that diverges (e.g. Polish `rozmowa` where `pl.json` settled on
+  locale catalog already uses for that concept — grep the PO to check. Flag a
+  synonym that diverges (e.g. Polish `rozmowa` where the Polish catalog settled on
   `czat` in f292049f): existing terms were chosen by native speakers, and no
   test catches the drift.
 - **Screen reader.** Plain wx controls; all speech through

.claude/rules/screen-reader-speech.md

@@ -16,6 +16,6 @@ paths:
 
 **Read `docs/traps/screen-reader-speech.md` before changing these files.** Short form:
 
-Suppressing a focus announcement is done by the focus cloak (MSAA state without FOCUSED, disarmed after ~500 ms), never by cancelling speech. A list row must not be rewritten while focus is moving off it — hold repaints and release them when the sequence ends.
+Suppressing a focus announcement is done by the focus cloak (MSAA state without FOCUSED, disarmed after ~500 ms), never by cancelling speech. A list row must not be rewritten while focus is moving off it — during a voice-note sequence hold the repaints of the focused row and of the row the chain just left (only those: `core/chain_repaint_guard.py`) and release them when the sequence ends or is paused.
 
 Switching to a chat panel (Alt+1, Alt+4, locked, navigation list) goes through `show_chat_panel()` only: a real switch from another panel hides the open conversation's pane (the conversation stays open, never reshown by a switch: that was a perceptible delay), but pressing Alt+1/Alt+4 inside the panel the conversation is already visible in switches nothing and keeps it (`keep`), focuses the panel's chat list (never a message list), and never rebuilds, loads or requests anything. The conversation returns only on an explicit ask (Alt+M, Alt+2, Alt+3: `reveal_open_conversation()`, in the panel it belongs to) or by opening a chat.

.claude/rules/transcription.md

@@ -0,0 +1,22 @@
+---
+paths:
+  - "client/core/transcription/**"
+  - "client/ui/transcription_flow.py"
+  - "client/ui/dialogs/transcription_*.py"
+  - "client/main_window/transcription_store.py"
+  - "client/main_window/transcription_background.py"
+  - "client/main_window/auto_transcription.py"
+  - "client/ui/conversation_panel/bulk_transcription.py"
+  - "client/ui/conversation_panel/accelerators.py"
+  - "client/ui/conversation_panel/message_accels.py"
+  - "client/ui/conversation_panel/message_menu.py"
+  - "client/core/tls_trust.py"
+  - "client/core/database.py"
+  - "tests/test_transcription_*.py"
+---
+
+# Local transcription
+
+**Read `docs/traps/transcription.md` before changing these files.** Short form:
+
+No top-level import of the backend or wx in `client/core/transcription/`: a copy without it must still open (whisper.cpp, or `BACKEND_MISSING`). No int8 on a card unless chosen, and never from sm_120 up or on an unknown capability. whisper.cpp's CUDA build only for [5.0, 12.0), and whisper-cli always gets `-l`. Catalogues pin revision, sizes and sha256. A single-language model forces its language, and the automatic choice never downloads a third-party model or a 32-bit GGML file. Resolve an unsupported precision before the load, because CTranslate2 refuses it. Probe free memory right before the run, off the wx thread. The models folder is install-wide: `coord_locks.models_lock()`, `canonical_dir()`, `_app_settings` with the underscore. A user's own model is never copied or deleted. Downloads go through `tls_trust`. `vad_used is False` is always spoken. The stored text lives in the encrypted record and needs both defences. Never log the text, the contact or the message id; a file path is logged as its basename. New temp prefixes go into `temp_sweep.PREFIXES`. A status's text lives in the status's own record (`core/transcription/statuses.py`) and is carried over whenever the tab's list is rebuilt.

.claude/rules/updater.md

@@ -2,9 +2,16 @@
 paths:
   - "client/updater.py"
   - "client/update_coord.py"
+  - "client/update_channel_choice.py"
   - "client/update_background.py"
   - "client/update_package.py"
+  - "client/update_progress.py"
+  - "client/core/update_handoff.py"
+  - "client/update_relaunch.py"
+  - "client/update_node_kill.py"
+  - "client/core/npm_environment.py"
   - "client/core/api_staging.py"
+  - "client/core/update_keeps_server.py"
   - "client/main_window/wpp_background_update.py"
   - "client/version.py"
   - ".github/workflows/*.yml"

.claude/settings.json

@@ -11,7 +11,10 @@
       "Bash(git diff:*)",
       "Bash(git log:*)",
       "Bash(git show:*)",
-      "Bash(git branch:*)"
+      "Bash(git branch:*)",
+      "mcp__github__merge_pull_request",
+      "mcp__github__update_pull_request",
+      "Bash(git push https://github.com/gabrielhhaber/WinZapp_Python*:*)"
     ]
   },
   "enabledPlugins": {

.claude/skills/README.md

@@ -11,8 +11,8 @@ primeiro vem junto com o `git clone`.
 ### Skills: ninguém invoca, elas aparecem
 
 Uma skill **carrega sozinha** quando a tarefa bate com a descrição dela. Mexeu
-em `client/languages/`, a `i18n-ui-string` entra em cena e o agente já sabe dos
-arquivos de todos os idiomas registrados, do `&&` e dos placeholders — você não precisa lembrar de nada.
+em `translations/` ou `client/languages/`, a `i18n-ui-string` entra em cena e o agente já sabe dos
+catálogos de todos os idiomas registrados, do `&&` e dos placeholders — você não precisa lembrar de nada.
 Para forçar, digite `/nome-da-skill`.
 
 ### Agentes: você chama pelo nome
@@ -95,8 +95,9 @@ próprio agente quando a tarefa se encaixa na descrição — não é preciso in
 | `write-test` | Teste novo ou estendido. `MainWindow` é `wx.Frame` e `ConversationsPanel` é `wx.Panel`: nenhum dos dois instanciável sem `wx.App`, então ou a lógica sai para nível de módulo, ou o método real é ligado a um stub. Também as fixtures do `conftest.py` e o `asyncio_mode=auto` (teste async é só `async def`, sem decorator). |
 | `wppconnect-patch` | Conserto do lado Node. São três mecanismos de patch diferentes, cada um com suas listas; escolher o errado é silencioso, e a mudança some no próximo `setup_api.py`. Nunca editar `client/api/` direto. |
 | `accessible-ui` | Qualquer mexida em `client/ui/`, `status_panel.py` ou no wx do `main.py`. Controles padrão do wx, toda fala por `speak_output`, `Freeze`/`Thaw` com `try/finally` em volta de mutação de lista, e o limite de 511 caracteres do SysListView32. |
+| `extract-from-god-file` | Extrair lógica testável ou dividir um módulo de mixin que excedeu o orçamento, sem mudar comportamento. Os índices dos pacotes mostram a responsabilidade de cada módulo. |
 
-As quatro estão escritas em inglês, para casar com o `CLAUDE.md` e o `AGENTS.md`
+As skills do projeto estão escritas em inglês, para casar com o `CLAUDE.md` e o `AGENTS.md`
 — são documentos do mesmo tipo, dirigidos ao agente.
 
 ### Escrevendo uma skill nova
@@ -229,5 +230,5 @@ Vale saber antes de alguém pedir "roda o code-review" e receber outra coisa:
 
 O `ci.yml` roda a suíte completa em todo PR para a `main`. Localmente rode só
 os arquivos de teste do que você mudou (`uv run pytest tests/test_x.py`); a
-suíte inteira (`uv run pytest -n auto`, ~1 min) fica para mudanças transversais. Os testes
+suíte inteira (`uv run pytest`, serial, no máximo uma execução local) fica para mudanças transversais. Os testes
 `load` só rodam no CI ou com `--run-load`. Nunca `--run-wx-gui`.

.claude/skills/accessible-ui/SKILL.md

@@ -56,13 +56,16 @@ Row-by-row mutation fires one accessibility event per row.
 focused = self.messages_list.GetFocusedItem()
 self.messages_list.Freeze()
 try:
-    ...  # inserts, deletes, DeleteAllItems + rebuild
+    ...  # apply changed rows through _sync_message_rows()
 finally:
     self.messages_list.Thaw()
 # restore focus, adjusting the index if rows before it moved
 ```
 
 `try/finally` is mandatory, and so is restoring the focused row.
+The messages list must never be cleared and rebuilt. Use
+`MessageRowsMixin._sync_message_rows()` and preserve its row identities;
+`DeleteAllItems()` re-announces the focused message even inside Freeze/Thaw.
 
 ## The 511-character limit
 

.claude/skills/i18n-ui-string/SKILL.md

@@ -1,24 +1,32 @@
 ---
 name: i18n-ui-string
-description: Add, change or remove a user-facing string in WinZapp. Use whenever a change introduces text a person can read or a screen reader can speak — dialog titles, buttons, menu items, list labels, error boxes, notifications, tooltips — or whenever a file under client/languages/ needs editing. Covers every registered locale (language_map.json), the mnemonic and placeholder rules, and the tests that enforce them.
+description: Add, change or remove a user-facing string in WinZapp. Use for readable/spoken UI text or editing translations/*.po and language_map.json. Covers every registered locale, gettext updates, mnemonics, placeholders and validation.
 ---
 
 # Adding a user-facing string
 
 `I18n.t()` is `translations.get(key, key)` (`client/core/i18n.py`): no
 fallback to another locale. A missing key is not an error — the screen reader
 speaks the raw key name. So **a key added anywhere is owed by every locale
-file listed in `client/languages/language_map.json`, in the same change.**
+catalog listed in `client/languages/language_map.json`, in the same change: CI and release
+builds reject a missing or fuzzy entry.**
 
 ## Procedure
 
 1. Name the key in English `snake_case`, after its role
    (`status_reply_send`, not `send_button_2`).
-2. Add it to every locale file in `client/languages/` with a real
-   translation; a blank value fails the suite.
+2. Add `msgctxt` (stable key) and `msgid` (English source) to
+   `translations/en-US/LC_MESSAGES/winzapp.po`.
 3. Call it as a literal: `i18n.t("my_key")`. A key built at runtime escapes
    the static check.
-4. Run the tests below.
+4. Update POT and merge every locale with `uv run translations-update`.
+   Translate the new blank entries and review changed `fuzzy` entries in
+   `translations/<locale>/LC_MESSAGES/winzapp.po`. Preserve translator comments.
+   Use `uv run translations-check-draft` while work is pending. When every PO
+   is complete, run `uv run translations-compile` and then
+   `uv run translations-check`. Never edit generated MO/key-map resources or POT.
+   Details: `docs/reference/gettext-migration.md`.
+5. Run the tests below.
 
 ## Rules
 
@@ -40,6 +48,7 @@ file listed in `client/languages/language_map.json`, in the same change.**
 
 ```
 uv run pytest tests/test_language_files_in_sync.py tests/test_i18n_keys_exist.py
+uv run pytest tests/test_gettext_catalogs.py
 ```
 
 The first compares the locale files with each other (keys, blanks,
@@ -48,7 +57,9 @@ mnemonics, placeholders); the second checks every literal `i18n.t("...")` in
 
 ## Adding a locale
 
-Drop `<code>.json` into `client/languages/` and add
-`"<code>": "<Display Name>"` to `language_map.json` (dict order is the
-Settings combobox order). Tests derive the locale list from the map — never
-write the list out in a test.
+Add `"<code>": "<Display Name>"` to `client/languages/language_map.json`
+(dict order is the Settings combobox order), run `uv run translations-update`,
+translate its new `translations/<code>/LC_MESSAGES/winzapp.po`, then run
+`uv run translations-compile` and `uv run translations-check`.
+Update the installer/uninstaller tables too (`docs/reference/build-and-setup.md`).
+Tests derive the locale list from the map — never repeat it in a test.

.claude/skills/wppconnect-patch/SKILL.md

@@ -36,7 +36,7 @@ carry that list; a test holds them equal.
   homologated pair, pinned exact.** Mechanism 3 rewrites their compiled code
   by literal search-and-replace, so a moved version silently disables a
   patch. To move the pair: bump both keys and
-  `client/wpp_minimum_version.txt` in one commit, after running all five
+  `client/wpp_minimum_version.txt` in one commit, after running all six
   `node_modules` patches against the candidate.
 - When a new runtime restructures patched code, add a **second patch set
   selected by matching the file** (as `host.layer.js` has for ≤ 2.3.1 and
@@ -48,22 +48,26 @@ carry that list; a test holds them equal.
 
 ## 3 — compiled code inside `node_modules`
 
-For bugs in `@wppconnect-team/wppconnect`'s compiled output. Four modules in
+For bugs in `@wppconnect-team/wppconnect`'s compiled output. Five modules in
 `client/core/`:
 
 ```
 wppconnect_host_layer_patch.py      host.layer.js    pairing-code lifecycle
 wppconnect_sender_layer_patch.py    sender.layer.js  attachment sending
 wppconnect_status_layer_patch.py    status.layer.js  status post success/failure
 wppconnect_welcome_layer_patch.py   welcome.js
+wppconnect_browser_layer_patch.py   browser.js       injectApi readiness timeout
 ```
 
-Each holds `ORIGINAL_*` / `PATCHED_*` constants and an `ALL_PATCHES` tuple,
+The first four hold `ORIGINAL_*` / `PATCHED_*` constants and an `ALL_PATCHES` tuple,
 applied by idempotent search-and-replace (re-running must be a no-op). A
 shipped `_V<n>` constant is never edited — add a version and a migration
 (`docs/traps/large-media.md`).
 
-A fifth module patches the other half of the pair, `@wppconnect/wa-js`'s
+`wppconnect_browser_layer_patch.py` is shaped like the wa-js one below instead
+(matched by structure, owns its file handling).
+
+A sixth module patches the other half of the pair, `@wppconnect/wa-js`'s
 bundle — the script injected into the WhatsApp Web page, so a bug in
 `WPP.*` itself is fixed there:
 

.claude/skills/write-test/SKILL.md

@@ -87,5 +87,5 @@ uv run pytest tests/test_<subject>.py
 ```
 
 Run the files for what you touched. CI runs the whole suite on every PR; run
-`uv run pytest -n auto` locally only for a cross-cutting change (`tests/conftest.py`,
+`uv run pytest` serially, at most once, locally only for a cross-cutting change (`tests/conftest.py`,
 a shared helper, a module split). Never pass `--run-wx-gui`.

.github/scripts/audit_wpp_upgrade.py

@@ -252,8 +252,9 @@ def built_source_changes(changed_paths) -> list:
     build configuration and scripts at the repository root.
 
     They reach an install through a server update, but every WinZapp update
-    brings the release's own api/ (dist/ built at the pin) back over it, so
-    they would come and go with each WinZapp release. A release approved without a WinZapp release must have
+    copies the release's dist/, built at the pin, back over it
+    (core/update_keeps_server.py), so they would come and go with each
+    WinZapp release. A release approved without a WinZapp release must have
     none.
     """
     return sorted(p for p in set(changed_paths) if _is_built(p))

.github/scripts/release_signing.py

@@ -338,7 +338,7 @@ def cmd_sign_stable(args) -> int:
         return 0
     _gh(["--method", "PATCH", f"repos/{repo}/releases/{release['id']}",
          "-F", "draft=false", "-F", "prerelease=false", "-f", "make_latest=true"])
-    print(f"Published {tag}. release-published.yml now bumps client/version.py on main.")
+    print(f"Published {tag}. client/version.py on main is not touched; change it yourself when main's version should move.")
     return 0
 
 

.github/workflows/alpha-release.yml

@@ -23,16 +23,17 @@
 #     Settings > General. It is also a real, parseable WinZapp version
 #     (parse_version() in updater.py accepts a dev/alpha/beta suffix), so an
 #     alpha still compares correctly against stable versions.
-#   - No bump-version job: client/version.py in main must keep tracking the
-#     stable release line. Committing an alpha version back to main would
-#     also push to main, which is what triggers this workflow.
+#   - No bump-version job: client/version.py in main is changed by hand, only
+#     when the maintainers want main's version to move. Committing an alpha
+#     version back to main would also push to main, which is what triggers
+#     this workflow. Publishing a stable release never touches main.
 name: Alpha Build
 
 on:
   push:
     branches: [main]
-    # version.py-only commits come from release-published.yml's bump-version job (which
-    # already marks them [skip ci]); nothing in a docs/CI-only change alters
+    # A version.py-only commit changes nothing that gets compiled, and nothing
+    # in a docs/CI-only change alters
     # what gets compiled, so don't burn a ~15 minute build and a release on it.
     paths-ignore:
       - "client/version.py"
@@ -100,8 +101,8 @@ jobs:
   # two channels stop ordering against each other. updater.py compares
   # ((major, minor, patch, build), pre_order) with alpha < beta < final, so:
   #
-  #   base 0.25.0.0beta (client/version.py, kept current by
-  #   release-published.yml's bump-version job) + commit count N  ->  0.25.0.<N>alpha
+  #   base 0.25.0.0beta (client/version.py, changed by hand
+  #   when main's line moves) + commit count N  ->  0.25.0.<N>alpha
   #
   # The suffix on the base is irrelevant to all of this — only major.minor.
   # patch are read off it — so the scheme keeps working unchanged when the
@@ -264,8 +265,8 @@ jobs:
       # Uses the default GITHUB_TOKEN deliberately: GitHub does not re-trigger
       # workflows for events raised by GITHUB_TOKEN, so publishing this release
       # (and the tag GitHub creates for it) does NOT fire release.yml's tag
-      # push trigger or release-published.yml (both also skip alpha tags
-      # outright, as a second line of defence).
+      # push trigger (which also skips alpha tags outright, as a second
+      # line of defence).
       # A run cancelled partway through the upload below leaves its draft
       # behind, and cancellation is routine here (a newer commit supersedes an
       # in-flight build). Nothing ever collects those, so they'd pile up on the