fix-compilelisted

# Fix compile The user's paper failed to compile. They clicked **Fix with AI** and asked you to repair it. Read the compile-error bundle, parse the compiler's stderr, locate each reported error in source, and **edit the source files in place** to clear every error. You are applying the fix, not proposing one; the user has already authorised the edit by clicking the button. The desktop re-runs the compiler as soon as you finish. If the compile still fails, the user is shown the new error and can click **Fix with AI** again. If it succeeds, the session is marked done. You do **not** need to verify the fix yourself. ## Inputs - `<bundle-path>`: absolute path to a `compile-error-*.json` file matching the `CompileErrorBundle` schema at `${CLAUDE_PLUGIN_ROOT}/schemas/compile-error.schema.json`. The path lives under `$OBELUS_WORKSPACE_DIR` (the Obelus desktop sets that env var when spawning Claude Code); standalone CLI users must export the env var to a writable directory outside the paper repo and place the bundle there themselves. There is no `.obelus/` fallback — the plugin must never write into the user's paper repo. - `paperId`: the paper's UUID in the Obelus registry (for traceability; do not look it up). Fields you will use from the bundle: - `project.main.relPath`, `project.main.format`: the paper's root source and its format token (`typ` / `tex` / `md`). Use the format to pick parsing rules for `stderr`, not to decide what to edit. - `compiler`: `typst` / `latexmk` /