Create a plugin with an LLM

my-plugin/
  plugin.toml
  ui/
    index.html

Create a local Wrengle view-only plugin for me.
 
Plugin idea:
[Describe what the plugin should do. Include what users type or paste, what
the plugin should show, and whether it should use selected text from a note.]
 
Wrengle plugin constraints:
- This is a local developer-preview plugin, not a marketplace or remote-install
  plugin.
- Prefer a view-only plugin.
- Produce a complete plugin folder with at minimum these required files:
  - plugin.toml
  - ui/index.html
- Do not include a [runtime] block.
- Do not include plugin.wasm.
- Do not require Rust, WASM, Node, npm, a bundler, or a build step.
- Do not claim the plugin can open terminal tabs, run shell commands, use
  process plugins, read arbitrary local files, install itself remotely, or use a
  marketplace.
- Do not use network requests by default. If I explicitly ask for network
  requests, list the exact destination hosts, explain what data is sent, and
  make each send action user-triggered.
- Do not claim `httpHosts` grants control direct `fetch` or `XMLHttpRequest`
  calls from view JavaScript. `httpHosts` applies only to Wrengle host-bridge
  HTTP made by WASM action plugins.
 
The plugin.toml file must include:
- top-level id, name, version, schema_version = 1, and description
- a top-level id that starts with plugin.
- one [[views]] block with id, label, and entry
- entry = "ui/index.html", relative to the plugin folder, pointing to an
  existing file
- a view id that starts with the plugin id plus a dot, such as
  plugin.my-tool.view
- lowercase ASCII ids using letters, digits, dots, and hyphens, with no ".."
- accepts_selection = true and a clear selection_label if the plugin should
  receive selected note text
 
The ui/index.html file must be one self-contained HTML file:
- inline all CSS and JavaScript
- do not reference external scripts or stylesheets
- do not reference companion JavaScript or CSS files
- keep the file under 5 MB
- use Wrengle CSS variables for all page surfaces, foreground text, borders,
  muted surfaces/text, and primary controls
- prefer variables such as var(--background), var(--foreground), var(--card),
  var(--card-foreground), var(--muted), var(--muted-foreground),
  var(--border), var(--input), var(--primary), and
  var(--primary-foreground)
- do not define an independent hard-coded light or dark color palette
- state that it does not make network requests unless I explicitly asked for them
- include this Wrengle postMessage bridge inside an HTML script element:
 
function applyWrengleTheme(message) {
  if (message.theme) {
    document.documentElement.dataset.theme = message.theme;
  }
 
  if (!message.themeTokens || typeof message.themeTokens !== "object") return;
 
  for (const [name, value] of Object.entries(message.themeTokens)) {
    if (/^--[A-Za-z0-9_-]+$/.test(name) && typeof value === "string" && value.length > 0) {
      document.documentElement.style.setProperty(name, value);
    }
  }
}
 
window.addEventListener("message", (event) => {
  if (event.source !== window.parent) return;
  const msg = event.data;
  if (!msg || typeof msg !== "object") return;
  if (msg.type === "wrengle:init" || msg.type === "wrengle:theme") {
    applyWrengleTheme(msg);
  } else if (msg.type === "wrengle:selection" && typeof msg.text === "string") {
    // Use msg.text as the selected note text.
  }
});
parent.postMessage({ type: "wrengle:ready" }, "*");
 
Return:
1. The folder tree.
2. The full contents of plugin.toml.
3. The full contents of ui/index.html.
4. Short steps to create the files, load the plugin in Settings -> Plugins,
   open it from the command palette, and test selected note text if supported.

Fix this Wrengle plugin using the diagnostic below. Keep it view-only unless the
diagnostic proves a different local plugin type is needed. Return the corrected
plugin.toml and ui/index.html files in full.
 
Diagnostic:
[Paste the diagnostic here.]