fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime by stainlu · Pull Request #62846 · openclaw/openclaw

stainlu · 2026-04-08T02:20:46Z

Summary

Problem 1 (registration): Microsoft TTS and ElevenLabs providers are not available at runtime — /tts provider only shows OpenAI, and /tts status reports microsoft (not configured) with skipped(no_provider_registered). Users configuring Microsoft voices (e.g. zh-CN-XiaoxiaoNeural) or ElevenLabs get no TTS output despite correct config; the gateway silently falls back to OpenAI.
Problem 2 (parser regression): Once Microsoft and ElevenLabs participate in directive parsing, parseTtsDirectives walks providers in autoSelectOrder with first-match-wins and does not honor an explicit provider=X token when routing generic tokens. Inputs like [[tts:provider=minimax speed=1.2]] would silently route speed to whichever provider comes first in order, not to the declared MiniMax.
What changed:
- Added "enabledByDefault": true to extensions/microsoft/openclaw.plugin.json and extensions/elevenlabs/openclaw.plugin.json, matching the pattern of other working bundled speech provider plugins (openai, minimax, vydra).
- parseTtsDirectives now pre-scans for provider=X and routes generic tokens to the declared provider first, falling back to autoSelectOrder only when the declared provider doesn't handle the key. Token order inside the directive no longer matters.
- Added src/tts/directives.test.ts covering the ElevenLabs/MiniMax speed collision and fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives previously had no test coverage.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

greptile-apps · 2026-04-08T02:21:42Z

Greptile Summary

Adds "enabledByDefault": true to the openclaw.plugin.json manifests for the microsoft and elevenlabs speech provider plugins, bringing them in line with the three other bundled speech providers (openai, minimax, vydra) that already carry this flag. Without it, resolveEffectivePluginActivationState treats these plugins as disabled at gateway startup, so their providers are never registered and TTS silently falls through to OpenAI.

Confidence Score: 5/5

Safe to merge — purely declarative fix with no logic changes, matching the established pattern for all other bundled speech providers.

The change is exactly two added lines across two JSON manifests. It corrects an omission (missing enabledByDefault: true) that is clearly verified against the three working speech provider manifests and the activation gate in src/plugins/config-policy.ts. No code was modified, no new logic introduced, and the PR author confirmed pnpm build, pnpm lint, and both extension test suites pass.

No files require special attention.

Vulnerabilities

No security concerns identified. The change is limited to declarative JSON manifests, adds no new network calls, secrets handling, or permission grants, and matches the existing activation pattern for all other bundled speech providers.

_{Reviews (1): Last reviewed commit: "fix(microsoft,elevenlabs): add enabledBy..." | Re-trigger Greptile}

stainlu · 2026-04-08T03:48:03Z

CI failures are pre-existing and unrelated to this manifest change:

check-additional: TypeScript lint errors in discord/imessage/openshell extensions (same failures seen on other PRs)
checks-node-test: Missing env vars (VOLCANO_ENGINE_API_KEY, NVIDIA_API_KEY), Gemini model ID normalization drift, auth test drift
checks-windows-node-test: Timed out (1h+)

Extension-specific tests for both microsoft and elevenlabs pass cleanly.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 661cc9dd36

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9a042170ee

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…egister at runtime

…rovider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f7bffe3656

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…stainlu

…stainlu)

obviyus

Verified the Microsoft and ElevenLabs bundled speech providers now register by default, and confirmed TTS directive routing prefers the explicit or active provider so speed overrides stop landing on the wrong provider.

Maintainer follow-up: fixed the Discord voice runtime import to use an exported Plugin SDK seam and resolved the package-exports review thread on the latest head.

Local gate: pnpm test src/tts/directives.test.ts; pnpm test extensions/speech-core/src/tts.test.ts; pnpm build; pnpm check.

obviyus · 2026-04-16T09:57:07Z

Landed on main.

Landed source commit: 1200a2e
Merge commit: 6ea3cdd

Thanks @stainlu.

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

@stainlu

…enclaw#62846) (thanks @stainlu) * fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime * fix(tts): route generic directive tokens to the explicitly declared provider Addresses the P2 Codex review on openclaw#62846 that flagged auto-enabling ElevenLabs as a product regression for MiniMax users. Both providers claim the generic `speed` token, and parseTtsDirectives walked providers in autoSelectOrder with first-match-wins, so inputs like `[[tts:provider=minimax speed=1.2]]` silently routed speed to providerOverrides.elevenlabs once elevenlabs participated in every parse pass. The parser now pre-scans for `provider=` (honoring legacy last-wins semantics) and routes generic tokens with the declared provider tried first, falling back to autoSelectOrder when it doesn't handle the key. Token order inside the directive no longer matters: `speed=1.2` before or after `provider=minimax` both resolve to MiniMax. Adds a regression test suite covering the exact ElevenLabs/MiniMax speed collision plus fallback, mixed-token, last-wins, and allowProvider-disabled cases. parseTtsDirectives had no prior test coverage. * fix(tts): prefer active provider for generic directives * fix: register bundled TTS providers safely (openclaw#62846) (thanks @stainlu) * fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu) --------- Co-authored-by: Ayaan Zaidi <[email protected]>

openclaw-barnacle Bot added the size: XS label Apr 8, 2026

stainlu force-pushed the fix/issue-62574-microsoft-tts-enabledByDefault branch 2 times, most recently from de84361 to 661cc9d Compare April 14, 2026 13:41

chatgpt-codex-connector Bot reviewed Apr 14, 2026

View reviewed changes

Comment thread extensions/elevenlabs/openclaw.plugin.json

openclaw-barnacle Bot added size: M and removed size: XS labels Apr 14, 2026

chatgpt-codex-connector Bot reviewed Apr 14, 2026

View reviewed changes

Comment thread extensions/elevenlabs/openclaw.plugin.json

stainlu force-pushed the fix/issue-62574-microsoft-tts-enabledByDefault branch 2 times, most recently from cc2d801 to ed6f581 Compare April 16, 2026 05:18

openclaw-barnacle Bot added the channel: discord Channel integration: discord label Apr 16, 2026

obviyus self-assigned this Apr 16, 2026

stainlu and others added 3 commits April 16, 2026 15:05

fix(microsoft,elevenlabs): add enabledByDefault so speech providers r…

ffbf203

…egister at runtime

fix(tts): prefer active provider for generic directives

d5fe470

chatgpt-codex-connector Bot reviewed Apr 16, 2026

View reviewed changes

Comment thread extensions/discord/src/voice/manager.ts Outdated

fix: register bundled TTS providers safely (openclaw#62846) (thanks @…

80061e0

…stainlu)

obviyus force-pushed the fix/issue-62574-microsoft-tts-enabledByDefault branch from f7bffe3 to 80061e0 Compare April 16, 2026 09:42

fix: use exported TTS SDK seam (openclaw#62846) (thanks @stainlu)

1200a2e

obviyus approved these changes Apr 16, 2026

View reviewed changes

obviyus merged commit 6ea3cdd into openclaw:main Apr 16, 2026
46 checks passed

clawsweeper Bot mentioned this pull request Apr 29, 2026

Feature Request: Add speed parameter support for OpenAI TTS #12163

Closed

stainlu mentioned this pull request Apr 29, 2026

fix(openai/tts): handle [[tts:speed]] directive in OpenAI speech provider (#12163) #74089

Merged

21 tasks

This was referenced May 1, 2026

[Bug]: TTS elevenlabs provider generates audio but OpenClaw plays OpenAI voice instead #52186

Open

[Feature]: Language-aware TTS routing for inbound voice replies #74722

Open

This was referenced May 2, 2026

[Bug]: messages.tts ElevenLabs provider silently falls back to Edge TTS in Discord; no per-agent voice support #46015

Closed

[Bug]: Microsoft TTS on Telegram uses the wrong voice despite correct voice configuration #76855

Closed

clawsweeper Bot mentioned this pull request May 11, 2026

TTS: enforce standalone directive lines parsing #56706

Closed

19 tasks

clawsweeper Bot mentioned this pull request Jun 15, 2026

Bug: [[tts:text]] tag content not passed to TTS engine — surrounding text sent instead #89509

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime#62846

fix(microsoft,elevenlabs): add enabledByDefault so speech providers register at runtime#62846
obviyus merged 5 commits into
openclaw:mainfrom
stainlu:fix/issue-62574-microsoft-tts-enabledByDefault

stainlu commented Apr 8, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented Apr 8, 2026

Vulnerabilities

Uh oh!

stainlu commented Apr 8, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

obviyus left a comment

Uh oh!

Uh oh!

obviyus commented Apr 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

stainlu commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Uh oh!

greptile-apps Bot commented Apr 8, 2026

Greptile Summary

Confidence Score: 5/5

Vulnerabilities

Uh oh!

stainlu commented Apr 8, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

obviyus left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

obviyus commented Apr 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

stainlu commented Apr 8, 2026 •

edited

Loading