{"owner":"infiniflow","repo":"ragflow","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# RAGFlow Instructions\n\nUse this file as the local operating guide for the current codebase. Prefer the code and the current CLAUDE.md over any older convention or remembered project shape.\n\n## Core Stance\n- Treat legacy code as liability, not as a compatibility target.\n- Prefer deletion over shims, deprecated branches, wrapper APIs, and dual-track migration notes.\n- If old and new implementations coexist, converge to one path unless an external contract forces compatibility.\n- Remove dead tests, commented-out code, stale docs, and \"move later\" notes instead of preserving them.\n- Reduce public surface area when a helper can be made private or internal.\n- Keep refactors centered on the owning abstraction, not on adjacent compatibility layers.\n\n## Current stack\n- Backend: Python 3.13+, Quart-based API server, Peewee ORM, async workers.\n- Frontend: React + TypeScript + Vite in `web/`.\n- Go: the repository also has a substantial Go module for servers, ingestion, parser/runtime, CLI, and supporting services.\n- Runtime services commonly include MySQL/PostgreSQL, Redis, MinIO, and Elasticsearch/Infinity/OpenSearch depending on configuration.\n\n## Code Layout to Expect\n- `api/`: Python API server entrypoints, blueprints, services, and database code.\n- `rag/`: ingestion, retrieval, LLM integration, and graph RAG logic.\n- `deepdoc/`: parsing and OCR.\n- `agent/`: workflow canvas, components, tools, and templates.\n- `cmd/`: Go entrypoints. `ragflow_main` is the main server/admin/ingestor binary surface; `ragflow-cli` is the CLI entrypoint.\n- `internal/`: main Go application code. Important subtrees:\n- `internal/agent/`: Go agent runtime, canvas execution, components, tool bindings, workflow helpers.\n- `internal/cli/`: CLI parsing, HTTP transport, command execution, response formatting.\n- `internal/dao/`: Go data-access layer and persistence-facing helpers.\n- `internal/deepdoc/`: Go DeepDOC integrations, especially native-backed PDF/DOCX parsing.\n- `internal/engine/`: search/index backends such as Elasticsearch and Infinity.\n- `internal/entity/`: shared Go entities and model definitions.\n- `internal/handler/`: HTTP handlers and route-facing request logic.\n- `internal/ingestion/`: Go ingestion pipeline, canvas adapter, components, wiring, service orchestration.\n- `internal/ingestion/component/`: stage implementations such as file/parser/chunker/tokenizer/extractor.\n- `internal/ingestion/pipeline/`: DSL translation, canvas-driven execution, checkpoints, resume/run logic.\n- `internal/parser/`: parser and chunk libraries used by ingestion and other Go paths.\n- `internal/parser/parser/`: typed parse-result parsers for markdown/html/pdf/docx/xlsx/text and related families.\n- `internal/parser/chunk/`: chunk operator library and DSL/typed execution helpers.\n- `internal/service/`: higher-level business services used by handlers and server flows.\n- `internal/storage/`: storage backends and in-memory test doubles.\n- `internal/router/`: HTTP route registration.\n- `internal/server/`: server bootstrap/config wiring.\n- `internal/cpp/`: C++ sources used by native-backed Go features.\n- `web/`: frontend application.\n- `docker/`: local and production compose files.\n- `sdk/` and `test/`: SDK and automated tests.\n\n## Go-Specific Rules\n- Treat `internal/ingestion`, `internal/parser`, and `internal/deepdoc` as actively refactored code. Prefer collapsing duplicate paths over preserving transitional wrappers.\n- Do not add or preserve deprecated Go APIs just to ease migration inside the repo.\n- Remove commented-out Go code instead of leaving recovery notes in place.\n- Keep package comments and doc comments aligned with the current runtime path, not with migration history.\n\n## Go Test Tiers\nGo tests are classified by build tag so the default `go test ./...` run stays self-contained. Tag a test file with `//go:build <tier>` placed before the `package` clause.\n\n| Tier | Build tag | Runs by default? | Needs |\n|---|---|---|---|\n| Unit | (none) | Yes (`go test ./...`) | Native CGO static libs (wired by `build.sh --test`); no external services — uses in-memory SQLite, miniredis, or `httptest` stubs. |\n| Integration | `integration` | No (`-tags integration`) | A real service: MySQL/MinIO/Elasticsearch/Infinity/LLM. Single component, reasonably fast. |\n| E2E | `e2e` | No (`-tags e2e`) | Full cross-component pipeline (ingest → index → retrieve) against real services; heavy/slow. |\n| Manual | `manual` | No (`-tags manual`) | Very slow/expensive (deepdoc render/parity/snapshot/bench). **Local opt-in ONLY — never run in CI.** |\n| Native (orthogonal) | `cgo` / `!cgo` | `cgo` auto-satisfies under CGO_ENABLED=1 | Native static libs (`office_oxide`/`pdfium`/`pdf_oxide`). Combine with tiers, e.g. `//go:build cgo && integration`. |\n\nRun tiers locally via `build.sh`:\n```bash\nbash build.sh --test                      # unit tier (no tags)\nbash build.sh --test-integration ./...    # integration tier\nbash build.sh --test-e2e                  # e2e tier\nbash build.sh --test-manual               # manual tier (very slow)\nbash build.sh --test-all                  # integration + e2e (never includes manual)\n```\nRules:\n- New tests that touch a real external service MUST carry `integration`/`e2e`/`manual` — do not rely on `t.Skip` + env vars to soft-isolate them in the default unit run. Keep an env guard as a harmless secondary safety net if desired.\n- `manual` is never wired into CI or any automated pipeline.\n- `unit` (no tag) must stay free of external-service dependencies so `go test ./...` passes without MySQL/MinIO/ES/Infinity/LLM. The native CGO static libraries (`office_oxide`/`pdfium`/`pdf_oxide`) are still required at build time and are wired automatically by `build.sh --test`; that is expected, not an external service.\n\n## Working Rules\n- When reviewing documentation or code, inspect the full affected path and report all verifiable findings in one review; do not return after only a few findings and expose further issues in later rounds.\n- When handling review comments, independently verify each substantive claim against the current code or tests before accepting, rejecting, or acting on it.\n- Before editing, inspect the nearest code path that actually owns the behavior.\n- Keep changes small and local unless the task is explicitly a broader refactor.\n- Prefer one implementation path instead of preserving old and new versions side by side.\n- Preserve behavior with focused tests when the behavior is still valid; do not keep tests that protect obsolete behavior.\n- If a surface is only there for compatibility, remove it unless the user asks to keep it.\n- Do not add new compatibility wording in comments or docs.\n- When a maintainer takes over a community PR, a new commit generated by rewriting history (e.g. `merge`, `rebase -i`) must preserve the original author and add the maintainer as co-author (via a `Co-authored-by:` trailer) instead of overwriting the author with the maintainer alone.\n\n## Commands\n### Backend\n```bash\nuv sync --python 3.13 --all-extras\nuv run python3 ragflow_deps/download_deps.py\ndocker compose -f docker/docker-compose-base.yml up -d\nsource .venv/bin/activate\nexport PYTHONPATH=$(pwd)\nbash docker/launch_backend_service.sh\nuv run pytest\nruff check\nruff format\n```\n\n### Frontend\n```bash\ncd web\nnpm install\nnpm run dev\nnpm run build\nnpm run lint\nnpm run test\nnpm run type-check\n```\n\n### Go\n```bash\nuv run ragflow_deps/download_deps.py\nbash build.sh --test ./path/to/package/...\nbash build.sh --go\n# or build specific binaries:\nbash build.sh --all\n```\n\n## Validation Preference\n- Run the narrowest relevant test, lint, or build command after a change.\n- For backend changes, prefer targeted pytest or ruff checks over full-suite runs.\n- For frontend changes, prefer the touched-package lint, type-check, or test command.\n- For Go changes, prefer package-scoped `bash build.sh --test ...` first.\n- Do not default to raw `go test`, `go build`, or IDE Run/Debug for Go in this repo. They often miss the required CGO flags and native static libraries (`office_oxide`, `pdfium-static`, `pdf_oxide`) that `build.sh` wires correctly.\n- If Go native builds fail, inspect `build.sh` and `internal/development.md` before changing code. Common environment issues are missing downloaded native deps and missing `lld` on Linux.\n\n## Default review checklist\n- Remove instead of retaining `deprecated`, `legacy`, or compatibility-only code.\n- Collapse duplicate implementations to one path.\n- Drop stale comments and documentation that describe a superseded design.\n- Keep exported APIs only when the current code actually needs them.\n"},"files":{"AGENTS.md":"# RAGFlow Instructions\n\nUse this file as the local operating guide for the current codebase. Prefer the code and the current CLAUDE.md over any older convention or remembered project shape.\n\n## Core Stance\n- Treat legacy code as liability, not as a compatibility target.\n- Prefer deletion over shims, deprecated branches, wrapper APIs, and dual-track migration notes.\n- If old and new implementations coexist, converge to one path unless an external contract forces compatibility.\n- Remove dead tests, commented-out code, stale docs, and \"move later\" notes instead of preserving them.\n- Reduce public surface area when a helper can be made private or internal.\n- Keep refactors centered on the owning abstraction, not on adjacent compatibility layers.\n\n## Current stack\n- Backend: Python 3.13+, Quart-based API server, Peewee ORM, async workers.\n- Frontend: React + TypeScript + Vite in `web/`.\n- Go: the repository also has a substantial Go module for servers, ingestion, parser/runtime, CLI, and supporting services.\n- Runtime services commonly include MySQL/PostgreSQL, Redis, MinIO, and Elasticsearch/Infinity/OpenSearch depending on configuration.\n\n## Code Layout to Expect\n- `api/`: Python API server entrypoints, blueprints, services, and database code.\n- `rag/`: ingestion, retrieval, LLM integration, and graph RAG logic.\n- `deepdoc/`: parsing and OCR.\n- `agent/`: workflow canvas, components, tools, and templates.\n- `cmd/`: Go entrypoints. `ragflow_main` is the main server/admin/ingestor binary surface; `ragflow-cli` is the CLI entrypoint.\n- `internal/`: main Go application code. Important subtrees:\n- `internal/agent/`: Go agent runtime, canvas execution, components, tool bindings, workflow helpers.\n- `internal/cli/`: CLI parsing, HTTP transport, command execution, response formatting.\n- `internal/dao/`: Go data-access layer and persistence-facing helpers.\n- `internal/deepdoc/`: Go DeepDOC integrations, especially native-backed PDF/DOCX parsing.\n- `internal/engine/`: search/index backends such as Elasticsearch and Infinity.\n- `internal/entity/`: shared Go entities and model definitions.\n- `internal/handler/`: HTTP handlers and route-facing request logic.\n- `internal/ingestion/`: Go ingestion pipeline, canvas adapter, components, wiring, service orchestration.\n- `internal/ingestion/component/`: stage implementations such as file/parser/chunker/tokenizer/extractor.\n- `internal/ingestion/pipeline/`: DSL translation, canvas-driven execution, checkpoints, resume/run logic.\n- `internal/parser/`: parser and chunk libraries used by ingestion and other Go paths.\n- `internal/parser/parser/`: typed parse-result parsers for markdown/html/pdf/docx/xlsx/text and related families.\n- `internal/parser/chunk/`: chunk operator library and DSL/typed execution helpers.\n- `internal/service/`: higher-level business services used by handlers and server flows.\n- `internal/storage/`: storage backends and in-memory test doubles.\n- `internal/router/`: HTTP route registration.\n- `internal/server/`: server bootstrap/config wiring.\n- `internal/cpp/`: C++ sources used by native-backed Go features.\n- `web/`: frontend application.\n- `docker/`: local and production compose files.\n- `sdk/` and `test/`: SDK and automated tests.\n\n## Go-Specific Rules\n- Treat `internal/ingestion`, `internal/parser`, and `internal/deepdoc` as actively refactored code. Prefer collapsing duplicate paths over preserving transitional wrappers.\n- Do not add or preserve deprecated Go APIs just to ease migration inside the repo.\n- Remove commented-out Go code instead of leaving recovery notes in place.\n- Keep package comments and doc comments aligned with the current runtime path, not with migration history.\n\n## Go Test Tiers\nGo tests are classified by build tag so the default `go test ./...` run stays self-contained. Tag a test file with `//go:build <tier>` placed before the `package` clause.\n\n| Tier | Build tag | Runs by default? | Needs |\n|---|---|---|---|\n| Unit | (none) | Yes (`go test ./...`) | Native CGO static libs (wired by `build.sh --test`); no external services — uses in-memory SQLite, miniredis, or `httptest` stubs. |\n| Integration | `integration` | No (`-tags integration`) | A real service: MySQL/MinIO/Elasticsearch/Infinity/LLM. Single component, reasonably fast. |\n| E2E | `e2e` | No (`-tags e2e`) | Full cross-component pipeline (ingest → index → retrieve) against real services; heavy/slow. |\n| Manual | `manual` | No (`-tags manual`) | Very slow/expensive (deepdoc render/parity/snapshot/bench). **Local opt-in ONLY — never run in CI.** |\n| Native (orthogonal) | `cgo` / `!cgo` | `cgo` auto-satisfies under CGO_ENABLED=1 | Native static libs (`office_oxide`/`pdfium`/`pdf_oxide`). Combine with tiers, e.g. `//go:build cgo && integration`. |\n\nRun tiers locally via `build.sh`:\n```bash\nbash build.sh --test                      # unit tier (no tags)\nbash build.sh --test-integration ./...    # integration tier\nbash build.sh --test-e2e                  # e2e tier\nbash build.sh --test-manual               # manual tier (very slow)\nbash build.sh --test-all                  # integration + e2e (never includes manual)\n```\nRules:\n- New tests that touch a real external service MUST carry `integration`/`e2e`/`manual` — do not rely on `t.Skip` + env vars to soft-isolate them in the default unit run. Keep an env guard as a harmless secondary safety net if desired.\n- `manual` is never wired into CI or any automated pipeline.\n- `unit` (no tag) must stay free of external-service dependencies so `go test ./...` passes without MySQL/MinIO/ES/Infinity/LLM. The native CGO static libraries (`office_oxide`/`pdfium`/`pdf_oxide`) are still required at build time and are wired automatically by `build.sh --test`; that is expected, not an external service.\n\n## Working Rules\n- When reviewing documentation or code, inspect the full affected path and report all verifiable findings in one review; do not return after only a few findings and expose further issues in later rounds.\n- When handling review comments, independently verify each substantive claim against the current code or tests before accepting, rejecting, or acting on it.\n- Before editing, inspect the nearest code path that actually owns the behavior.\n- Keep changes small and local unless the task is explicitly a broader refactor.\n- Prefer one implementation path instead of preserving old and new versions side by side.\n- Preserve behavior with focused tests when the behavior is still valid; do not keep tests that protect obsolete behavior.\n- If a surface is only there for compatibility, remove it unless the user asks to keep it.\n- Do not add new compatibility wording in comments or docs.\n- When a maintainer takes over a community PR, a new commit generated by rewriting history (e.g. `merge`, `rebase -i`) must preserve the original author and add the maintainer as co-author (via a `Co-authored-by:` trailer) instead of overwriting the author with the maintainer alone.\n\n## Commands\n### Backend\n```bash\nuv sync --python 3.13 --all-extras\nuv run python3 ragflow_deps/download_deps.py\ndocker compose -f docker/docker-compose-base.yml up -d\nsource .venv/bin/activate\nexport PYTHONPATH=$(pwd)\nbash docker/launch_backend_service.sh\nuv run pytest\nruff check\nruff format\n```\n\n### Frontend\n```bash\ncd web\nnpm install\nnpm run dev\nnpm run build\nnpm run lint\nnpm run test\nnpm run type-check\n```\n\n### Go\n```bash\nuv run ragflow_deps/download_deps.py\nbash build.sh --test ./path/to/package/...\nbash build.sh --go\n# or build specific binaries:\nbash build.sh --all\n```\n\n## Validation Preference\n- Run the narrowest relevant test, lint, or build command after a change.\n- For backend changes, prefer targeted pytest or ruff checks over full-suite runs.\n- For frontend changes, prefer the touched-package lint, type-check, or test command.\n- For Go changes, prefer package-scoped `bash build.sh --test ...` first.\n- Do not default to raw `go test`, `go build`, or IDE Run/Debug for Go in this repo. They often miss the required CGO flags and native static libraries (`office_oxide`, `pdfium-static`, `pdf_oxide`) that `build.sh` wires correctly.\n- If Go native builds fail, inspect `build.sh` and `internal/development.md` before changing code. Common environment issues are missing downloaded native deps and missing `lld` on Linux.\n\n## Default review checklist\n- Remove instead of retaining `deprecated`, `legacy`, or compatibility-only code.\n- Collapse duplicate implementations to one path.\n- Drop stale comments and documentation that describe a superseded design.\n- Keep exported APIs only when the current code actually needs them.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# RAGFlow Instructions\n\nUse this file as the local operating guide for the current codebase. Prefer the code and the current CLAUDE.md over any older convention or remembered project shape.\n\n## Core Stance\n- Treat legacy code as liability, not as a compatibility target.\n- Prefer deletion over shims, deprecated branches, wrapper APIs, and dual-track migration notes.\n- If old and new implementations coexist, converge to one path unless an external contract forces compatibility.\n- Remove dead tests, commented-out code, stale docs, and \"move later\" notes instead of preserving them.\n- Reduce public surface area when a helper can be made private or internal.\n- Keep refactors centered on the owning abstraction, not on adjacent compatibility layers.\n\n## Current stack\n- Backend: Python 3.13+, Quart-based API server, Peewee ORM, async workers.\n- Frontend: React + TypeScript + Vite in `web/`.\n- Go: the repository also has a substantial Go module for servers, ingestion, parser/runtime, CLI, and supporting services.\n- Runtime services commonly include MySQL/PostgreSQL, Redis, MinIO, and Elasticsearch/Infinity/OpenSearch depending on configuration.\n\n## Code Layout to Expect\n- `api/`: Python API server entrypoints, blueprints, services, and database code.\n- `rag/`: ingestion, retrieval, LLM integration, and graph RAG logic.\n- `deepdoc/`: parsing and OCR.\n- `agent/`: workflow canvas, components, tools, and templates.\n- `cmd/`: Go entrypoints. `ragflow_main` is the main server/admin/ingestor binary surface; `ragflow-cli` is the CLI entrypoint.\n- `internal/`: main Go application code. Important subtrees:\n- `internal/agent/`: Go agent runtime, canvas execution, components, tool bindings, workflow helpers.\n- `internal/cli/`: CLI parsing, HTTP transport, command execution, response formatting.\n- `internal/dao/`: Go data-access layer and persistence-facing helpers.\n- `internal/deepdoc/`: Go DeepDOC integrations, especially native-backed PDF/DOCX parsing.\n- `internal/engine/`: search/index backends such as Elasticsearch and Infinity.\n- `internal/entity/`: shared Go entities and model definitions.\n- `internal/handler/`: HTTP handlers and route-facing request logic.\n- `internal/ingestion/`: Go ingestion pipeline, canvas adapter, components, wiring, service orchestration.\n- `internal/ingestion/component/`: stage implementations such as file/parser/chunker/tokenizer/extractor.\n- `internal/ingestion/pipeline/`: DSL translation, canvas-driven execution, checkpoints, resume/run logic.\n- `internal/parser/`: parser and chunk libraries used by ingestion and other Go paths.\n- `internal/parser/parser/`: typed parse-result parsers for markdown/html/pdf/docx/xlsx/text and related families.\n- `internal/parser/chunk/`: chunk operator library and DSL/typed execution helpers.\n- `internal/service/`: higher-level business services used by handlers and server flows.\n- `internal/storage/`: storage backends and in-memory test doubles.\n- `internal/router/`: HTTP route registration.\n- `internal/server/`: server bootstrap/config wiring.\n- `internal/cpp/`: C++ sources used by native-backed Go features.\n- `web/`: frontend application.\n- `docker/`: local and production compose files.\n- `sdk/` and `test/`: SDK and automated tests.\n\n## Go-Specific Rules\n- Treat `internal/ingestion`, `internal/parser`, and `internal/deepdoc` as actively refactored code. Prefer collapsing duplicate paths over preserving transitional wrappers.\n- Do not add or preserve deprecated Go APIs just to ease migration inside the repo.\n- Remove commented-out Go code instead of leaving recovery notes in place.\n- Keep package comments and doc comments aligned with the current runtime path, not with migration history.\n\n## Go Test Tiers\nGo tests are classified by build tag so the default `go test ./...` run stays self-contained. Tag a test file with `//go:build <tier>` placed before the `package` clause.\n\n| Tier | Build tag | Runs by default? | Needs |\n|---|---|---|---|\n| Unit | (none) | Yes (`go test ./...`) | Native CGO static libs (wired by `build.sh --test`); no external services — uses in-memory SQLite, miniredis, or `httptest` stubs. |\n| Integration | `integration` | No (`-tags integration`) | A real service: MySQL/MinIO/Elasticsearch/Infinity/LLM. Single component, reasonably fast. |\n| E2E | `e2e` | No (`-tags e2e`) | Full cross-component pipeline (ingest → index → retrieve) against real services; heavy/slow. |\n| Manual | `manual` | No (`-tags manual`) | Very slow/expensive (deepdoc render/parity/snapshot/bench). **Local opt-in ONLY — never run in CI.** |\n| Native (orthogonal) | `cgo` / `!cgo` | `cgo` auto-satisfies under CGO_ENABLED=1 | Native static libs (`office_oxide`/`pdfium`/`pdf_oxide`). Combine with tiers, e.g. `//go:build cgo && integration`. |\n\nRun tiers locally via `build.sh`:\n```bash\nbash build.sh --test                      # unit tier (no tags)\nbash build.sh --test-integration ./...    # integration tier\nbash build.sh --test-e2e                  # e2e tier\nbash build.sh --test-manual               # manual tier (very slow)\nbash build.sh --test-all                  # integration + e2e (never includes manual)\n```\nRules:\n- New tests that touch a real external service MUST carry `integration`/`e2e`/`manual` — do not rely on `t.Skip` + env vars to soft-isolate them in the default unit run. Keep an env guard as a harmless secondary safety net if desired.\n- `manual` is never wired into CI or any automated pipeline.\n- `unit` (no tag) must stay free of external-service dependencies so `go test ./...` passes without MySQL/MinIO/ES/Infinity/LLM. The native CGO static libraries (`office_oxide`/`pdfium`/`pdf_oxide`) are still required at build time and are wired automatically by `build.sh --test`; that is expected, not an external service.\n\n## Working Rules\n- When reviewing documentation or code, inspect the full affected path and report all verifiable findings in one review; do not return after only a few findings and expose further issues in later rounds.\n- When handling review comments, independently verify each substantive claim against the current code or tests before accepting, rejecting, or acting on it.\n- Before editing, inspect the nearest code path that actually owns the behavior.\n- Keep changes small and local unless the task is explicitly a broader refactor.\n- Prefer one implementation path instead of preserving old and new versions side by side.\n- Preserve behavior with focused tests when the behavior is still valid; do not keep tests that protect obsolete behavior.\n- If a surface is only there for compatibility, remove it unless the user asks to keep it.\n- Do not add new compatibility wording in comments or docs.\n- When a maintainer takes over a community PR, a new commit generated by rewriting history (e.g. `merge`, `rebase -i`) must preserve the original author and add the maintainer as co-author (via a `Co-authored-by:` trailer) instead of overwriting the author with the maintainer alone.\n\n## Commands\n### Backend\n```bash\nuv sync --python 3.13 --all-extras\nuv run python3 ragflow_deps/download_deps.py\ndocker compose -f docker/docker-compose-base.yml up -d\nsource .venv/bin/activate\nexport PYTHONPATH=$(pwd)\nbash docker/launch_backend_service.sh\nuv run pytest\nruff check\nruff format\n```\n\n### Frontend\n```bash\ncd web\nnpm install\nnpm run dev\nnpm run build\nnpm run lint\nnpm run test\nnpm run type-check\n```\n\n### Go\n```bash\nuv run ragflow_deps/download_deps.py\nbash build.sh --test ./path/to/package/...\nbash build.sh --go\n# or build specific binaries:\nbash build.sh --all\n```\n\n## Validation Preference\n- Run the narrowest relevant test, lint, or build command after a change.\n- For backend changes, prefer targeted pytest or ruff checks over full-suite runs.\n- For frontend changes, prefer the touched-package lint, type-check, or test command.\n- For Go changes, prefer package-scoped `bash build.sh --test ...` first.\n- Do not default to raw `go test`, `go build`, or IDE Run/Debug for Go in this repo. They often miss the required CGO flags and native static libraries (`office_oxide`, `pdfium-static`, `pdf_oxide`) that `build.sh` wires correctly.\n- If Go native builds fail, inspect `build.sh` and `internal/development.md` before changing code. Common environment issues are missing downloaded native deps and missing `lld` on Linux.\n\n## Default review checklist\n- Remove instead of retaining `deprecated`, `legacy`, or compatibility-only code.\n- Collapse duplicate implementations to one path.\n- Drop stale comments and documentation that describe a superseded design.\n- Keep exported APIs only when the current code actually needs them.\n","category":"root","tokens":2153}]}