Fix desktop memory provider built-in option

[szafranski]

Summary

• Treat blank memory.provider as the built-in memory option in Desktop Settings.
• Remove the misleading builtin plugin option from the provider dropdown.
• Normalize legacy built-in aliases before rendering provider setup controls.
• Add regression coverage for the dropdown and legacy aliases.

Why

Built-in persistent memory is the default MEMORY.md / USER.md layer. The memory.provider setting selects an external provider plugin that runs alongside it.

Desktop Settings exposed builtin as if it were a provider plugin. Selecting it could also render plugin setup controls for a provider that does not exist. The backend already normalizes built-in, builtin, and none to the blank built-in value; this change applies the same contract in the desktop UI.

Closes #49513

Tests

• npm --prefix apps/desktop run test:ui -- src/app/settings/helpers.test.ts → 22 passed
• npm --prefix apps/desktop run typecheck → passed
• ESLint on all changed desktop files with --quiet → passed
• git diff --check upstream/main...HEAD → passed

[alt-glitch]

Related: #49513 (the issue this PR Closes), #12990 (adjacent memory-provider UX: CLI hermes memory setup picker defaulting wrong — different code path).

Note: the genuine scope of this PR is the desktop Memory Provider dropdown fix (apps/desktop/src/app/settings/*, i18n strings) plus the backend memory.provider config schema (hermes_cli/web_server.py). The diff also carries unrelated files from an unclean base — gateway/platforms/telegram.py + tests/gateway/test_telegram_voice_duration.py (a Telegram voice-duration change) and a scripts/release.py salvage-credit entry. Those appear to be sibling-branch contamination (PR is currently CONFLICTING); rebasing onto a clean main should drop them.

[szafranski]

Thanks, you were right. I rebased the branch onto a clean upstream/main and force-pushed with only the desktop memory-provider/settings schema fix.

The PR now contains one commit and no longer includes the Telegram voice-duration or release author-map files. While resolving the rebase I kept the newer external hindsight provider option from main and only removed the misleading builtin option.

Re-ran the focused checks:

• npm --prefix apps/desktop run test:ui -- src/app/settings/helpers.test.ts
• npm --prefix apps/desktop run typecheck
• .venv/bin/python -m pytest tests/hermes_cli/test_web_server_config_schema.py tests/hermes_cli/test_doctor.py::TestDoctorMemoryProviderSection -q
• git diff --check upstream/main..HEAD

[teknium1]

Thanks for the focused desktop fix. The premise is verified on current main: apps/desktop/src/app/settings/constants.ts:241 still exposes builtin, while apps/desktop/src/app/settings/config-settings.tsx:462-479 treats every non-empty value as a plugin provider and renders plugin-only controls. Current backend normalization already maps built-in, builtin, and none to the empty external-provider value (hermes_cli/web_server.py:4417-4421).

The PR's desktop-side normalization, blank-value label, removal of the misleading option, and alias regression coverage align with that existing backend contract. No additional correctness or design-fit issue was found in the nine-file diff.

Automated hermes-sweeper review.

[szafranski]

Superseded by merged PR #67206, which includes the built-in memory provider fix and closes #49513. Thanks.