Point the Transifex CLI at the integration's resource

[koral--]

The Transifex GitHub integration did not link the existing enpo resource. It synced master into a new resource, res..po/stf.pot (master) (ec7e411575b0c3a867983b0a7e0113d9). This points .tx/config and doc/TRANSLATING.md at that resource, so node build.mts translate and other manual tx commands use the same one as the app.

On Transifex (already done):

• The new resource has all translations from enpo. The 12 shipped languages were imported from the repo. The partial languages that exist only on Transifex (nl 181, cs 46, zh-Hans 10, da 5) were uploaded from enpo.
• A re-pull shows every language identical to enpo, string for string, fuzzy flags included.
• enpo is untouched. Once this is merged, it can be archived or deleted without losing translations. Only its per-string history and translator credits would go.

Tested: tx pull --translations --force with the new config leaves every .po file in the repo byte for byte unchanged.

🤖 Generated with Claude Code

[github-actions]

❌ STF CI report

1 failing  ·  6 test tiers (6 pass / 0 fail / 0 skip)  ·  20 Android versions (19 with a usable device in STF)

Test tiers

	Tier	Result
✅	Build (npm + webpack)	deps cache hit
✅	Lint (eslint + jsonlint + translations + workflow shell)	lib/, res/ and root JS + JSON, translation catalogs, and every workflow run: block
✅	Unit tests (mocha)	lib/util, lib/wire and lib/db specs
✅	Component tests (vitest + React)	64 specs, 0 failed, 0 errored
✅	Integration + device-less E2E (stf local + RethinkDB + Playwright + SeaweedFS)	stf local success, fake devices success, web UI suite success, storage success
✅	Docker Compose + AVD + Playwright (Android 16, API 36)	21 Playwright tests, image success, Compose/AVD success, teardown success

Android device matrix

	Android	API	Image	Boot	In STF	Usable	SIM IDs	Screen	Touch	Shell	UI E2E	Teardown
✅	5.0	21	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	5.1	22	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	6.0	23	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	7	24	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	7.1	25	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	8	26	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	8.1	27	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	9	28	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	10	29	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	11	30	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	12	31	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	12L	32	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	13	33	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	14	34	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
❌	15	35	➖	➖	➖	➖	➖	➖	➖	➖	➖	➖
✅	16	36	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	16.1	36.1	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	17	37.0	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	17	37.1	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅	17	37.2	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅

_{Image = a system image is published for that API and arch. Boot = emulator reached sys.boot_completed and answers adb. In STF = the device registered with the STF provider. Usable = STF offered it as Use and handed over control. SIM IDs = imei, imsi, iccid and phoneNumber landed on the device document, which from API 23 up needs an STFService build whose agent answers --telephony (a leg whose emulator reports no usable SIM records a pass, because there is nothing to read). Screen = minicap frames reached the browser canvas and kept changing. Touch = a browser tap and swipe showed up in getevent on the device, at the coordinates they were aimed at: the tap within 5% of the centre of the touch axes, the swipe descending monotonically from 0.75 to 0.25 (the emulator runs with adb root, which minitouch needs to open /dev/input). Shell = the dashboard shell widget ran a command on it. UI E2E = the rest of the Playwright web UI suite. Teardown = the emulator action shut the AVD down and exited on its own.}

Failures

• Android 15 (API 35): the emulator never finished booting, so nothing ran against it (emulator step: failure) (attempt 2)

🔁 Retried once after failing: Android 15 (API 35, now fail).

_{Logs, screenshots, logcat and Playwright traces are attached to the run as artifacts · full run · commit 7e2536d}