# Refactor: Move Provider Tests to provider-inference
## Summary
Move azure-openai and openrouter-ai provider tests from `stage-ui` to
`provider-inference` package, placing them closer to their
implementations.
## Changes
- **Moved test files**:
-
`packages/stage-ui/src/libs/providers/providers/azure-openai/index.test.ts`
→
`packages/provider-inference/src/providers/cloud/azure-openai/index.test.ts`
-
`packages/stage-ui/src/libs/providers/providers/openrouter-ai/index.test.ts`
→
`packages/provider-inference/src/providers/cloud/openrouter-ai/index.test.ts`
- **Simplified test imports**: Updated tests to use direct provider
definitions instead of `getDefinedProvider()`, removing unnecessary
lookup logic
- **Added dependency**: `@proj-airi/core-agent` as devDependency for
test utilities
## Benefits
1. Tests are co-located with their implementations
2. Direct imports are simpler and more maintainable
3. Better package organization following module boundaries
## Verification
```bash
# Run tests for provider-inference
pnpm -F @proj-airi/provider-inference exec vitest run
# Typecheck
pnpm -F @proj-airi/provider-inference typecheck
```
## Test Results
All tests pass after the refactoring.
## Description
<!-- Please insert your description here and especially provide info
about the "what" this PR is solving -->
## Linked Issues
<!-- Optional, if you have any -->
## Additional Context
<!-- e.g. is there anything you'd like reviewers to focus on? -->
## 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`.
- Add `target?: string` field to `ButtonItem` interface
- Set `target: '_self'` on all locales' Try Live button configs (EN, ZH, JA)
- Bind `:target="item.target"` on the `<a>` element in HomeButton.vue
VitePress intercepts clicks on anchor tags without an explicit `target`
attribute and routes them through Vue Router, which causes a 404 for the
external https://airi.moeru.ai/ link. Setting `target="_self"` makes
the browser skip the router and perform a native navigation.
Co-authored-by-agent: GitHub Copilot <copilot@github.com>
- Move desktop-specific (amber) section before danger zone for better severity progression
- Add red border/background to danger zone card for visual prominence
- Remove redundant inner card backgrounds (white/red-950) since outer card now has red tinting
- Flatten one layer of nesting in danger zone item layout
Co-authored-by-agent: GitHub Copilot
Garfield Lee