Files

T

Zhou fanqi 39b68ddf12 fix(stage-ui): robust spark:command result + TTS session isolation (#1949 )

## Summary

Two small, generic robustness fixes, split out of the Minecraft desktop
integration (#1916) so they can land independently of that rework — as
suggested in @shinohara-rin's review:

> The generic fixes in this PR, like the TTS session cleanup and
`spark:command` result handling, seem separable and worth keeping in a
smaller PR.

Both are in shared `stage-ui` runtime code and contain **no
Minecraft-specific logic**.

## What's included

- **`spark:command` result handling**
(`tools/character/orchestrator/spark-command.ts`):
`command.destinations` may be `undefined` — the channel sender
(`stores/llm.ts` `sendSparkCommand`) deletes it to broadcast to all
authenticated peers. The success message's `.join()` therefore surfaced
`Cannot read properties of undefined (reading 'join')` back to the LLM
even though the send had already succeeded. Guard it and report a
broadcast instead.
- **TTS session isolation** (`components/scenes/Stage.vue`
`openTtsSession`): a completing/erroring session now only clears the
module-level `currentSession` if it **is** that session. The previous
code cleared it whenever any `stream-` session completed, which becomes
unsafe once sessions exist that are not assigned to `currentSession`
(e.g. one-off read-aloud sessions) — one of those finishing would null a
still-active chat session and drop the rest of the reply.

## How tested

```bash
pnpm -F @proj-airi/stage-ui exec vitest run src/tools/character/orchestrator/spark-command.test.ts # 9 passed (+1 new)
pnpm -F @proj-airi/stage-ui typecheck # 0 errors
pnpm exec eslint <changed files> # 0 problems
```

- Regression test for the broadcast-destinations result message.

## Context

This is the first, low-risk slice of reworking the Minecraft↔desktop
integration around the neutral Context Flow architecture (per the #1916
review). The Minecraft relay/read-aloud behavior will be reintroduced
through a Minecraft-owned adapter in a follow-up.

---------

2026-06-10 14:47:25 +08:00

public

docs(stage-ui): updated logo

2026-03-12 05:09:32 +08:00

src

fix(stage-ui): robust spark:command result + TTS session isolation (#1949 )

2026-06-10 14:47:25 +08:00

stories

fix(stage-ui,ui): histoire wasn't configured correctly

2026-04-22 16:57:35 +08:00

.env

feat(stage-*): experimental realtime transcription powered by Aliyun NLS

2025-11-02 04:20:27 +08:00

env.d.ts

feat(stage-ui): integrate histoire storyboard (#70 )

2025-03-12 10:32:05 +08:00

histoire.config.ts

fix(stage-ui): configure Histoire to exclude node_modules from vendor chunking

2026-04-25 16:46:08 +08:00

package.json

chore: update package dependencies and remove specific catalog references

2026-06-07 19:45:28 +08:00

README.md

chore: lint & lock

2026-03-06 16:49:31 +08:00

tsconfig.json

chore(ci): fix typecheck on navigator.gpu (#1700 )

2026-04-21 20:27:17 +08:00

uno.config.ts

feat: Refactor Font Configuration for Consistency and Correctness (#409 )

2025-08-25 11:44:10 +08:00

vite.config.ts

refactor(stage-web,stage-ui): replace warpdrive plugin with unplugin-basemove (#1818 )

2026-05-13 12:03:30 +08:00

vitest.config.ts

test: migrate more test into browser mode, fix all existing tests

2026-05-07 18:48:39 +08:00

README.md

Stage UI

Shared core for stage

Histoire (UI storyboard)

https://histoire.dev/

pnpm -F @proj-airi/stage-ui run story:dev

Project structure

If a story is bound to a specific component, it can be placed beside the component in the src folder. e.g., MyComponent.story.vue
If a story is not bound to a specific component, then it should be placed in the stories folder. e.g., MyStory.story.vue