Claude Opus 5
6e07da7a36
Everything the plugin is, moved out of officerdev/platform on 2026-08-15 — 41 files, unchanged from the tree they left. manifest.ts identity, one permission, ffmpeg/ffprobe declared api/ the sidecar proxy; the prefix comes from mountPrefix() sidecar/ the whole /api/music contract — indexing, streaming, per-user state db/ music_favorites, _playlists, _playlist_items, _now_playing web/ panels, layout, and the player: engine, bar, lyrics, favourites cliamp/ the second playback path, parked — not working, kept deliberately widgets/ the dashboard widget, parked — plugins cannot contribute widgets assets/ icon.png, the dock tile scripts/ the reindex CLI PLUGIN.md is the design record: what moved, what stayed, what broke, and why. MUSIC_API.md is the contract the phone and tablet apps speak, and the reason the sidecar's HTTP shape is not free to change. ── It does not build here, and that is the point ── The platform resolves `hooks/useClient`, `officerdev`, `officerdb/db` and `@@/*` through the workspace links in its own node_modules. Measured from this directory, outside the platform checkout, every one of them fails to resolve — 7 imports in the backend, ~29 in the frontend. So this repository is the source of truth, not yet a buildable unit. Making it one means the host API becoming something a plugin can depend on rather than something it reaches into. That is the next problem, and having the code here is what makes it unavoidable rather than theoretical. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
19 lines
1.0 KiB
TypeScript
19 lines
1.0 KiB
TypeScript
import type { AppRegistryMeta } from 'officerdev';
|
|
import { Music, ListMusic } from 'lucide-react';
|
|
import { MusicBrowser } from './MusicBrowser';
|
|
import { MusicDetail } from './MusicDetail';
|
|
|
|
// The panels this plugin contributes. The shell renders `WorkspaceView` around them, arranged by
|
|
// `layout.ts` — a plugin never renders the screen.
|
|
//
|
|
// The two do not coordinate with each other: both read `?path=` off the URL, which is why there is no
|
|
// channel between them and why a library location is linkable and cmd-clickable. `MusicDetail` opens a
|
|
// NESTED workspace of its own for the lyrics split, which is a layout inside a panel rather than a second
|
|
// screen.
|
|
//
|
|
// `availableOnPanel: false` keeps them off the generic panel picker: they belong to this plugin's screen.
|
|
export const appRegistryMetas: AppRegistryMeta[] = [
|
|
{ key: 'music-browser', name: 'Library', icon: ListMusic, component: MusicBrowser, availableOnPanel: false },
|
|
{ key: 'music-detail', name: 'Music', icon: Music, component: MusicDetail, availableOnPanel: false },
|
|
];
|