modify pdftomd

2026-05-14 10:16:59 +09:00
parent 2232b51fc9
commit dc11880140
69 changed files with 7784 additions and 1150 deletions
@@ -13,11 +13,11 @@ Use this skill when Markdown output quality matters more than raw text extractio

 1. Read `PLAN.md` and `PROGRESS.md` first.
 2. Read `docs/WORKARCHIVE.md` when prior Markdown output, MathJax, or sample conversion evidence is needed.
-3. Read `PRD.md` and `ARCHITECTURE.md` when output behavior, metadata, or reporting is affected.
+3. Read `PRD.md` and `ARCHITECTURE.md` when output behavior, internal provenance, or reporting is affected.
 4. Preserve project delimiter policy: inline math uses `$...$`; display math uses `$$...$$`.
 5. Check asset links, table fallback behavior, heading/list interactions, and page boundary markers against Obsidian rendering assumptions.
 6. Define warnings for low-confidence math, non-renderable LaTeX, broken asset links, table degradation, and reading-order uncertainty.
-7. Ensure `.report.md` content is derived from metadata, not separate manual state.
+7. Ensure `_report.md` content is derived from internal provenance, not separate manual state.

 ## Checks

@@ -25,7 +25,7 @@ Use this skill when Markdown output quality matters more than raw text extractio
 - Display math should be separated from surrounding paragraphs by blank lines.
 - Asset paths should be stable, relative to the Markdown file, and safe for Obsidian vaults.
 - Tables with formulas should prefer readable Markdown when reliable and warn when downgraded.
- Every renderability failure should be countable in metadata and visible in `.report.md`.
+- Every renderability failure should be countable in internal provenance and visible in `_report.md`.

 ## Reference