---
name: mineru-research
description: Research MinerU 3.1.0 setup, CLI behavior, output formats, model/runtime requirements, licensing, and local-only integration constraints for this PDF-to-Markdown project. Use when Codex needs to update project knowledge, verify MinerU facts, plan the MinerU adapter, or resolve uncertainty about installation, execution, or output behavior without adding alternate engines.
---

# MinerU Research

## Overview

Use this skill to verify MinerU 3.1.0 facts before changing project docs or plans. Keep the scope narrow: MinerU 3.1.0 is the only conversion engine and direct local CLI execution is the only v1 execution mode.

## Workflow

1. Read `PLAN.md` and `PROGRESS.md` first.
2. Read `docs/WORKARCHIVE.md` when prior MinerU setup, verification, or sample conversion evidence is needed.
3. Read `PRD.md`, `ARCHITECTURE.md`, and `docs/KNOWLEDGEBASE.md` when the change affects product or architecture decisions.
4. Prefer official MinerU documentation, the MinerU GitHub repository, release notes, primary papers, and official dependency docs.
5. Verify time-sensitive facts with web research before updating docs.
6. Record source URLs and access dates in durable docs when the finding affects future implementation.
7. Update `PROGRESS.md` with the verified fact, unresolved uncertainty, and next action.

## Constraints

- Do not reintroduce candidate engine comparisons.
- Allow only direct `mineru` CLI execution and the CLI-internal temporary local `mineru-api` process.
- Do not add cloud OCR, remote LLM, `--api-url`, remote API, router, HTTP client backend, or remote OpenAI-compatible backend paths.
- Do not imply perfect LaTeX reconstruction.
- Do not implement converter code unless the user explicitly requests implementation.
- Treat GTX 1070 Ti 8GB, Python 3.12, uv, and Windows PowerShell as active project constraints.

## Reference

Read `references/source-checklist.md` when planning a research pass or updating source-backed documentation.