loadBundledPlugins was fire-and-forget (void), so the plugin registry
Map was still empty when React re-rendered PluginSlot. By awaiting
the loader before calling setPlugins, the registry is populated before
the re-render that causes PluginSlot to read from it.

Plugin exports now point to source .ts/.tsx files. Next.js compiles
them via transpilePackages, eliminating the need for a separate tsc
build that fails without @types/react in Docker. CI simplified too —
just clone the repo, no build needed.

The plugin frontend tsc build in Docker fails because @types/react
isn't installed in the workspace context (it's a devDependency of
the plugins monorepo, not the workspace). Since we only need the
JS output for bundling, --skipLibCheck skips type validation.

The web Dockerfile didn't copy the plugins workspace package, so
Turbopack couldn't resolve @barazo/plugin-signatures during next build.
Adds the plugin package.json to the deps stage and copies source +
builds frontend types in the builder stage.

* fix(plugins): restore static import for proper bundling + add plugins to CI

The variable import path from bca0280 bypassed webpack bundling,
preventing the plugin module from being included in the client bundle.
Restores the static import so Next.js can resolve and bundle the
plugin frontend at build time.

CI now clones and builds barazo-plugins (frontend only) alongside
barazo-lexicons so TypeScript can resolve the workspace dependency.

* fix(ci): remove plugins cache to ensure fresh clone with latest exports

The cache key was based on pnpm-lock.yaml which doesn't change when
plugins repo changes. Remove caching for now so CI always gets the
latest plugin-signatures with explicit exports entries.

* fix(ci): replace plugin symlink with copy for Turbopack compatibility

Turbopack cannot follow pnpm link: symlinks outside the project root.
After pnpm install creates the symlink, replace it with a real copy
so Turbopack can resolve and bundle the plugin frontend modules.

* fix(plugins): defensive null checks for settingsSchema and dependents

The API may not return settingsSchema or dependents fields. Use
optional chaining and nullish coalescing to prevent Object.keys()
and .length crashes on undefined values.

* feat(plugins): add toast notifications for plugin actions

Show toast confirmations when enabling, disabling, saving settings,
or uninstalling plugins. Uses existing useToast hook matching the
pattern from admin pages.

* feat(types): align frontend types with lexicon v0.3.0

- Rename Topic.createdAt → publishedAt (also in CreateTopicResponse,
SearchResult)
- Remove contentFormat from Topic and Reply types
- Add optional site field to Topic type
- Update all mock data, MSW handlers, components, and tests

* feat(plugins): wire up plugin frontend components and fix option labels

- Add plugin frontend loader that dynamically imports bundled plugin
register functions and wires them into the slot registry
- Call loader from PluginProvider after fetching enabled plugins
- Add @barazo/plugin-signatures as workspace dependency
- Add transpilePackages for plugin packages in next.config
- Format select option labels in SettingsField (replace underscores,
capitalize words) so "first_per_thread" displays as "First Per Thread"

* fix(plugins): use variable import path to avoid CI typecheck failure

The static import('@barazo/plugin-signatures/frontend/register') made
TypeScript resolve the module at compile time, which fails in CI where
the workspace plugin package isn't available. Using a variable path
bypasses static resolution while keeping the explicit return type.

* fix(plugins): defensive null checks for settingsSchema and dependents

The API may not return settingsSchema or dependents fields. Use
optional chaining and nullish coalescing to prevent Object.keys()
and .length crashes on undefined values.

* feat(plugins): add toast notifications for plugin actions

Show toast confirmations when enabling, disabling, saving settings,
or uninstalling plugins. Uses existing useToast hook matching the
pattern from admin pages.

The API may not return settingsSchema or dependents fields. Use
optional chaining and nullish coalescing to prevent Object.keys()
and .length crashes on undefined values.

Add optional chaining for plugin.dependencies to prevent crash
when API response omits the field.

Show a Bluesky butterfly icon with "Bluesky" label instead of the full
bsky.app/profile URL to reduce visual clutter in the AT Protocol stats
section.

apiFetch now safely handles empty response bodies by reading text first
before parsing JSON, preventing the JSON.parse error on DELETE 204/200
responses. LikeButton's error handler now treats "Not Found" during
unlike as a successful state transition instead of reverting, preventing
count inflation from repeated like/unlike cycles.

DELETE endpoints (like unlike/reaction delete) return 204 with empty body.
apiFetch was unconditionally calling response.json(), causing
"JSON.parse: unexpected end of data" errors.

* feat(reactions): disable reaction buttons on own content

Add isOwnContent prop to TopicView and ReplyCard, passed through to
ReactionBar (disabled) and LikeButton (new disabled prop). Prevents
clicking before the API 403 would reject it.

* style(reactions): fix Prettier formatting in reply-card