Best possible solution:

Refresh the branch against current main, keep the dispatcher guard if the merge result is still narrow, and land it only with focused document-extractor tests plus the appropriate changed-surface gate.

Do we have a high-confidence way to reproduce the issue?

Yes by source inspection. Current main reads extractor.mimeTypes before the extraction try/catch, and the PR's regression test models a throwing metadata getter followed by a healthy extractor.

Is this the best way to solve the issue?

Yes for the narrow runtime-boundary hardening. Loader-level artifact isolation, inspect taxonomy, and installed-package build fixes remain separate related work for the broader document-extract report.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 72b9bc730370.

Label justifications:

• P2: This is a bounded document-extraction robustness fix with limited blast radius, not an emergency runtime outage by itself.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate does not apply because this is a maintainer-member PR; the PR body includes focused local runtime test output as validation context.

PR surface:

Source +25, Tests +47. Total +72 across 2 files.

What I checked:

• Root policy read: Root AGENTS.md was read fully and applied to the protected-label, read-beyond-diff, plugin-boundary, and validation requirements for this PR. (AGENTS.md:1, 72b9bc730370)
• Scoped plugin policy read: The touched media runtime consumes plugin document extractor entries, so src/plugins/AGENTS.md loader and public-contract boundary guidance was read and applied. (src/plugins/AGENTS.md:1, 72b9bc730370)
• Live PR state: GitHub reports the PR as draft with the maintainer label and mergeStateStatus DIRTY / mergeable CONFLICTING, so it should not be closed or treated as land-ready cleanup. (824257c9aafb)
• Current-main failure path: Current main reads extractor.mimeTypes before entering the extractor try/catch, so unreadable metadata can abort iteration before a later healthy extractor is considered. (src/media/document-extractors.runtime.ts:40, 72b9bc730370)
• PR implementation path: The PR adds readDocumentExtractor(), wraps id/mimeTypes/extract reads, skips unreadable entries, and calls extract with the original receiver. (src/media/document-extractors.runtime.ts:22, 824257c9aafb)
• PR regression coverage: The added test places a throwing mimeTypes getter before a healthy PDF extractor and verifies the healthy extractor still returns while preserving receiver state. (src/media/document-extractors.runtime.test.ts:88, 824257c9aafb)

Likely related people:

• vincentkoc: Current blame ties the media dispatcher path to Vincent Koc, and earlier history shows Vincent moved document extraction into the bundled plugin/runtime path and authored this narrow guard. (role: feature introducer and recent area contributor; confidence: high; commits: 0a7b0096477f, e3cba98f3904, 1856d1f530d4; files: src/media/document-extractors.runtime.ts, src/media/document-extractors.runtime.test.ts, src/plugins/document-extractor-public-artifacts.ts)
• Shakker: Recent plugin-runtime history includes lazy capability plugin startup work touching the document extractor resolver area, which is adjacent to how extractor rows reach this dispatcher. (role: adjacent plugin-runtime contributor; confidence: medium; commits: 86bdeb056176; files: src/plugins/document-extractors.runtime.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.