Files

T

Garfield Lee 59a064ea80 refactor(stage-ui): extract provider-inference package for runtime-neutral definitions (#2444 )

## Summary

Extract runtime-neutral provider definitions from `@proj-airi/stage-ui`
into a new `@proj-airi/provider-inference` package that runs in both
Node.js and browser without Vue/Pinia dependencies.

## What changed

- **New package** `packages/provider-inference/` — owns
`ProviderDefinition`, `ProviderRegistry`, validators, and all provider
modules (cloud + local)
- **Provider modules relocated** — ~45 providers moved from
`stage-ui/src/libs/providers/providers/` to
`provider-inference/src/providers/cloud/` and
`provider-inference/src/providers/local/`
- **Type decoupling** — `ProviderContext.t` changed from
`ComposerTranslation` (Vue) to generic `ProviderTranslator`, removing
the Vue dependency from core types
- **stage-ui types slimmed** — `types.ts` now re-exports from
`provider-inference` and only adds the Vue-specific `ProviderViews`
extension
- **validators/run.ts** — becomes a pass-through re-export
- **Registry** — portable `createProviderRegistry()` with deterministic
ordering and duplicate-id detection

## Verification

```bash
pnpm -F @proj-airi/provider-inference typecheck
pnpm -F @proj-airi/provider-inference test:node
pnpm -F @proj-airi/provider-inference test:browser
pnpm -F @proj-airi/provider-inference build
pnpm -F @proj-airi/stage-ui typecheck
pnpm -F @proj-airi/stage-web typecheck
pnpm -F @proj-airi/stage-tamagotchi typecheck
pnpm lint
```

## Why

Provider definitions were tightly coupled to Vue (`ComposerTranslation`,
`Component`), preventing reuse in non-Vue runtimes (Node.js services,
tests, future Electron backend). This extraction creates a clean
boundary: runtime-neutral definitions live in `provider-inference`,
while Vue/Pinia-specific concerns stay in `stage-ui`.

2026-09-02 19:35:25 +08:00

public

docs(stage-ui): updated logo

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

src

refactor(stage-ui): extract provider-inference package for runtime-neutral definitions (#2444 )

2026-09-02 19:35:25 +08:00

stories

Revert "style: lint"

2026-08-26 20:13:10 +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

Revert "style: lint"

2026-08-26 20:13:10 +08:00

package.json

refactor(stage-ui): extract provider-inference package for runtime-neutral definitions (#2444 )

2026-09-02 19:35:25 +08:00

README.md

feat(stage): add global button analytics directive (#2146 )

2026-07-29 15:59:53 +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

Revert "style: lint"

2026-08-26 20:13:10 +08:00

vitest.config.ts

feat(stage-tamagotchi,stage-ui-live2d): procedural motion generation (#2376 )

2026-08-29 18:15:28 +08:00

README.md

Stage UI

Shared core for stage

Button analytics

import { trackButtonPlugin } from '@proj-airi/stage-ui/directives/track-button'

createApp(App)
  .use(trackButtonPlugin)
  .mount('#app')

Buttons that represent a product-analysis click intent can then declare a typed event without wrapping their business handler:

<Button
  v-track-button="{ name: 'update_check_clicked', channel: selectedChannel }"
  @click="checkForUpdates()"
/>

Keep async outcomes, confirmed state changes, impressions, and lifecycle events in their owning business flows instead of attaching them to the initial click.

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