김경종
31 lines
1.4 KiB
Markdown
31 lines
1.4 KiB
Markdown
---
|
|
description: Research current MinerU 3.1.0 facts for local integration planning
|
|
argument-hint: [research-question]
|
|
allowed-tools: [Read, Glob, Grep, Bash, WebFetch, Edit]
|
|
---
|
|
|
|
# /run-mineru-research
|
|
|
|
Research MinerU 3.1.0 facts that affect this project's documentation or future implementation.
|
|
|
|
## Arguments
|
|
|
|
The user invoked this command with: $ARGUMENTS
|
|
|
|
## Workflow
|
|
|
|
1. Read `PLAN.md`, `PROGRESS.md`, `ARCHITECTURE.md`, and `docs/KNOWLEDGEBASE.md`.
|
|
2. Read `docs/WORKARCHIVE.md` when prior MinerU setup, verification, or sample conversion evidence is needed.
|
|
3. Use official MinerU documentation, the MinerU GitHub repository, primary papers, and official dependency documentation.
|
|
4. Verify facts that can change: install commands, supported Python/CUDA versions, CLI flags, output formats, model download behavior, and licenses.
|
|
5. Record sources with URLs and access dates when updating docs.
|
|
6. Keep findings scoped to MinerU 3.1.0; do not add candidate-engine comparisons.
|
|
7. Update `PROGRESS.md` with what was verified and what remains uncertain.
|
|
|
|
## Guardrails
|
|
|
|
- Allow only direct `mineru` CLI execution and the CLI-internal temporary local `mineru-api` process.
|
|
- Do not add cloud OCR, hosted LLM, `--api-url`, remote API, router, HTTP client backend, or remote OpenAI-compatible backend paths.
|
|
- Do not turn research notes into implementation code.
|
|
- If official sources conflict, stop and ask for a decision instead of guessing.
|