Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/desktop/src/renderer/styles/preview.css`:
- Around line 554-559: Replace the hard-coded red values in this preview.css
block (background, border-left, color) with semantic theme tokens so error
styling follows the app theme; update the background, border-left and color
declarations to use centralized CSS variables (e.g. --error-background,
--error-border, --error-foreground or the existing theme token names used
elsewhere) and ensure padding, margin, and font-size remain unchanged; modify
only the property values in this rule so other styles continue to apply and
later set those token values in the global theme variables file.
- Around line 553-562: The .plugin-error-block can be broken by very long
unbroken error.message text injected by safePluginWrapper.ts; update the
.plugin-error-block CSS to allow long words to wrap and prevent horizontal
overflow by adding rules such as overflow-wrap: anywhere (or overflow-wrap:
break-word), word-break: break-word (or break-word/normal combos for
cross-browser), and ensure white-space is not preventing wrapping (e.g.,
white-space: normal); apply these changes to the .plugin-error-block rule so
arbitrary error.message content from safePluginWrapper.ts wraps instead of
expanding the preview width.

In `@docs/plans/2026-03-11-remark-rehype-hooks-enhancement.md`:
- Around line 52-54: The document uses two different CSS class names for the
injected error node—plugin-error-boundary and plugin-error-block—causing
inconsistency; pick one canonical class name (e.g., plugin-error-block) and
update all references across the plan (mentions in Task 2, the node example, and
the CSS) to use that single name consistently, replacing every occurrence of the
alternate symbol (plugin-error-boundary) with the chosen symbol so the
implementation steps, examples, and styles match.
- Around line 108-109: Update the docs to use the correct bulk-removal method
name: replace references to unregister(pluginId) with unregisterAll(pluginId)
and keep the existing single-remove API as unregister(id); also ensure the
backward-compatible note about register(plugin) remains (defaults: priority=100,
name='unknown', version='0.0.0') and update any other occurrences that mention
unregister(pluginId) to unregisterAll(pluginId).
- Line 13: The top-level task headings are H3 but should be H2 to maintain
proper outline and avoid MD001; update the heading "### Task 1: Define
PluginHookOptions type" (and all other "### Task N" headings) to "## Task 1:
Define PluginHookOptions type" so the document goes H1 -> H2 for tasks and
retains consistent lower-level headings under each task.
- Around line 203-220: The togglePlugin flow updates plugin state but never
triggers a preview refresh; modify togglePlugin (the function used by
PluginsSection after replacing setEnabled with
pluginRuntimeStore.getState().togglePlugin) to call requestReload() after making
changes—specifically, after pluginRegistry.deactivate/pluginStore.unregister
calls when disabling and after await get().reloadPlugins() when enabling—so the
active preview is explicitly refreshed whenever a plugin is toggled.

In `@packages/plugin-api/src/preview/rehypePluginStore.ts`:
- Around line 39-41: Replace the disallowed console.debug call with an allowed
console method (use console.warn to match ESLint constraints) in the
registration logging statement inside rehypePluginStore.ts — update the
console.debug invocation that logs `[RehypePlugins] Registered:
${registration.metadata.name}@${registration.metadata.version} (priority:
${registration.metadata.priority})` to use console.warn (keeping the same
message and interpolation) so the log uses an allowed method; ensure no other
console.debug occurrences remain in the rehype plugin registration code path.

In `@packages/plugin-api/src/preview/remarkPluginStore.ts`:
- Around line 39-41: Replace the disallowed console.debug call with an allowed
console method (e.g., console.warn) or remove it; specifically update the
statement that logs `[RemarkPlugins] Registered:
${registration.metadata.name}@${registration.metadata.version} (priority:
${registration.metadata.priority})` so it uses console.warn (or the project's
logger) instead of console.debug, keeping the same message and references to
registration.metadata.name/version/priority.

In `@packages/plugin-api/src/preview/safePluginWrapper.ts`:
- Line 25: The code uses the overly-permissive Function type when invoking
plugins (e.g., the assignment transformer = (plugin as Function)(...args); and
the similar occurrence at the other site), causing the ESLint
no-unsafe-function-type error; replace the cast with a concrete function
signature such as (plugin as (...args: unknown[]) => unknown)(...args) (or a
more specific parameter/return signature if you know the plugin shape), and
update any downstream typing to treat the result as unknown/appropriate typed
value instead of any so the call is both safe and satisfies
`@typescript-eslint/no-unsafe-function-type`.
- Around line 57-60: The HTML injected into children in safePluginWrapper.ts
uses metadata.name and message without full escaping; create/use an escapeHtml
helper and replace all special chars (& < > " ' /` ) in metadata.name and
message (instead of only replacing `"` and `<`) before embedding them in the
value string so the error marker cannot introduce executable HTML; update the
children.push call to use escapedMetadataName and escapedMessage variables
(referencing metadata.name and message) and ensure the data-plugin and
data-error attributes and the element text all use the escaped values.

In `@packages/plugin-api/tests/rehypePluginStore.test.ts`:
- Around line 4-5: Add a test that registers a plugin without passing metadata
to ensure backward compatibility: create a registration call using the existing
register function (the same one used by other tests) with no metadata argument,
then assert that the stored plugin metadata equals the defaultMeta object
(name:'test' or appropriate default fields) and that the plugin ordering
respects the default priority/order; reference the existing defaultMeta constant
in the test to compare expected values and place the test alongside the other
registration tests in rehypePluginStore.test.ts.

In `@packages/plugin-api/tests/remarkPluginStore.test.ts`:
- Around line 4-5: Add a test that covers the metadata-free registration path:
register a plugin without passing the metadata argument and assert that the
store fills in the defaults (name 'test'/'1.0.0'/priority 100 as represented by
defaultMeta). Locate the registration call used in this file (the function that
currently takes a metadata parameter) and add one case that omits that
parameter, then assert the stored plugin's name, version and priority match the
defaults (use the defaultMeta constant to compare). Ensure the test name clearly
indicates "metadata-free registration" so this backward-compatible path remains
exercised.