bindery-cli 0.43.0__tar.gz → 0.44.1__tar.gz

bindery_cli-0.44.1/.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: VirInvictus
+liberapay: bdkl

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/.gitignore

@@ -29,3 +29,4 @@ test_facility/*.epub
 # which is the only reason they were invisible until now)
 venv/
 .venv_ci/
+testing_facility/top500candidates/*.txt

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/CLAUDE.md

@@ -37,7 +37,13 @@ Born from the 2026 library audit (see the user memory `calibre-library-epubcheck
     `--unwrap-block-in-inline`, `--strip-invalid-value`, `--unwrap-illegal-tags`,
     `--prune-missing-resources`, `--strip-broken-anchors`, `--encode-url-spaces`,
     `--fix-container`, `--fix-media-types`, `--fix-cover`; transforms.py, threaded
-    through epub.py):
+    through epub.py). Since v0.44.0 `--encode-url-spaces` also RENAMES the
+    archive entries whose names carry raw spaces to their underscore spellings
+    and rewrites every reference (OPF, NCX, content, CSS `url()`); underscore,
+    never percent-encoding (epubcheck decodes references before entry lookup,
+    verified against 5.3), ambiguous renames refused per entry (`space_rename_map`),
+    accepted under `no_worse` because PKG-010 sits on the warning axis the gate
+    does not measure:
     they alter markup structure or fabricate minimal content. v0.14–v0.16 ran these unconditionally, which broke this rule;
     v0.17.0 restored it. `--unwrap-illegal-tags` additionally protects any illegal-tag
     name that an EPUB stylesheet styles as an element selector (`css_protected_tags`,
@@ -86,7 +92,7 @@ Born from the 2026 library audit (see the user memory `calibre-library-epubcheck
 - `src/bindery/pagination.py`: the opt-in lossy page-number strip (runhead detection, page-layer decision, block-centric removal/merge, safety nets).
 - `src/bindery/watermark.py`: the opt-in lossy watermark strip (anchored and anchorless signature removal).
 - `src/bindery/reserialize.py`: structural repair via `html5lib`.
-- `src/bindery/audit.py`: read-only body-text audits (`content`, `pagenumbers`, `emptytext`, `ocr`, `monolithic` since v0.21.0 with `--max-doc-chars N`, and `completeness` since v0.36.0) behind the `audit` subcommand (v0.15.0). Since v0.18.0 library mode resolves EPUB paths through `cquarry.get_format_path()` and can apply a tag to flagged books via `cquarry.write.WritableCalibreDB` (only with explicit `--tag`; the only sanctioned write path). Since v0.19.0 `audit --id BOOK_ID` audits a single library book through cquarry's single-entity `get_book()` fetch (no library-wide cache; supports `--tag`; incompatible with the directory argument; comma lists since v0.23.0). Since v0.22.0 every archive entry is fully read (CRC + decompression) before analysis (a damaged entry reports its own CORRUPT verdict instead of feeding emptytext) and manifest/NCX references to absent files classify as `convention` (bloated ToC, consecutive span) or `fragment` (broken span). Hazard: the scan loop reuses `tag` as its per-book display column, so the `--tag` argument is captured as `audit_tag` at function entry; do not collapse them again. Since v0.29.0 `audit --json FILE` writes per-file analyzer verdicts in the `library --json` shape (directory, library, and single-book modes; with `--id`, exactly one id; emptytext omitted from a record when the archive verdict owns the body-text story). Since v0.36.0 the completeness analyzer (Phase 15) reports the phase-1 spot-check per book: spine/prose-doc counts (prose = >= 400 visible chars), first/middle/last prose-doc opening/closing excerpts, trailing-ToC classification (`_trailing_toc`: short link lines dominate, no paragraph-length blocks), and the unreadable fraction. It is ADVISORY by contract (problem always False; ADVISORY on a trailing ToC or unreadable fraction >= 10%), never moves the exit code, and is skipped like emptytext when the archive verdict owns the book. Since v0.38.0 the archive verdict distinguishes font obfuscation from DRM (`OBFUSCATION_ALGOS`: IDPF 2008/embedding + both Adobe URIs; readable obfuscated entries are the benign OBFUSCATED advisory, an unreadable one is CORRUPT, and only non-obfuscation algorithms give ENCRYPTED). Since v0.43.0 untrusted metadata XML is parsed through `_safe_xml_parse` (DOCTYPE/ENTITY declarations refused before xml.etree sees them; the stdlib shape of defusedxml's entity protection) and single entries above `_MAX_ENTRY_BYTES` (32 MB) are refused before decompression; a refused metadata file returns the shell book. Since v0.40.0 the vir-tui console renderer loads through the module-level `_LazyUI` proxy (a plain `import vir_tui as ui` at module level would make 3.12/3.13 installs unimportable now that the stack is marker-gated; LOAD_GLOBAL never consults module `__getattr__`, so a proxy object is the lazy shape that works).
+- `src/bindery/audit.py`: read-only body-text audits (`content`, `pagenumbers`, `emptytext`, `ocr`, `monolithic` since v0.21.0 with `--max-doc-chars N`, and `completeness` since v0.36.0) behind the `audit` subcommand (v0.15.0). Since v0.18.0 library mode resolves EPUB paths through `cquarry.get_format_path()` and can apply a tag to flagged books via `cquarry.write.WritableCalibreDB` (only with explicit `--tag`; the only sanctioned write path). Since v0.19.0 `audit --id BOOK_ID` audits a single library book through cquarry's single-entity `get_book()` fetch (no library-wide cache; supports `--tag`; incompatible with the directory argument; comma lists since v0.23.0). Since v0.22.0 every archive entry is fully read (CRC + decompression) before analysis (a damaged entry reports its own CORRUPT verdict instead of feeding emptytext) and manifest/NCX references to absent files classify as `convention` (bloated ToC, consecutive span) or `fragment` (broken span). Hazard: the scan loop reuses `tag` as its per-book display column, so the `--tag` argument is captured as `audit_tag` at function entry; do not collapse them again. Since v0.29.0 `audit --json FILE` writes per-file analyzer verdicts in the `library --json` shape (directory, library, and single-book modes; with `--id`, exactly one id; emptytext omitted from a record when the archive verdict owns the body-text story). Since v0.44.0 two more advisory analyzers ride the single pass: `cover` (the EPUB3 `properties~="cover-image"` slice of the ruled hybrid: dangling EPUB2 meta, EPUB3 declaration, cover-file presence) and `tocdrift` (the NCX navMap vs EPUB3 nav toc structural diff, fragments included; audit-only, ToC synthesis out of charter permanently); the loader now exposes the parsed OPF, the NCX text, and the nav HTML on `Book`. Since v0.36.0 the completeness analyzer (Phase 15) reports the phase-1 spot-check per book: spine/prose-doc counts (prose = >= 400 visible chars), first/middle/last prose-doc opening/closing excerpts, trailing-ToC classification (`_trailing_toc`: short link lines dominate, no paragraph-length blocks), and the unreadable fraction. It is ADVISORY by contract (problem always False; ADVISORY on a trailing ToC or unreadable fraction >= 10%), never moves the exit code, and is skipped like emptytext when the archive verdict owns the book. Since v0.38.0 the archive verdict distinguishes font obfuscation from DRM (`OBFUSCATION_ALGOS`: IDPF 2008/embedding + both Adobe URIs; readable obfuscated entries are the benign OBFUSCATED advisory, an unreadable one is CORRUPT, and only non-obfuscation algorithms give ENCRYPTED). Since v0.43.0 untrusted metadata XML is parsed through `_safe_xml_parse` (DOCTYPE/ENTITY declarations refused before xml.etree sees them; the stdlib shape of defusedxml's entity protection) and single entries above `_MAX_ENTRY_BYTES` (32 MB) are refused before decompression; a refused metadata file returns the shell book. Since v0.40.0 the vir-tui console renderer loads through the module-level `_LazyUI` proxy (a plain `import vir_tui as ui` at module level would make 3.12/3.13 installs unimportable now that the stack is marker-gated; LOAD_GLOBAL never consults module `__getattr__`, so a proxy object is the lazy shape that works).
 - `src/bindery/epub.py`: archive rewrite, NCX uid sync, RepairReport, mismatch detection, and the opt-in structural-repair plumbing (including the CSS precondition scan). Since v0.38.0/v0.39.0 (Phase 16): `generate_container` + the `--fix-container` gateway (insert after mimetype when missing, replace in-loop when stale; constant-epoch timestamp keeps bytes deterministic), `prune_dangling_edges` (prune_missing_manifest_items returns the pruned ids and the edges that pointed at them (spine@toc, media-overlay, fallback, EPUB2 cover meta) are rewritten so pruning cannot manufacture the regression the gate rejects), and `fix_manifest_media_types` (extension map + magic-byte confirmation via a `peek` callable over the open source zip; jpg/png/gif only), and `fix_cover_meta` (the ruling's deterministic half: dangling EPUB2 cover meta re-pointed from the guide's cover reference when exactly one manifest item carries that file, removed otherwise; accepted under no_worse like the lossy strips because cover wiring is invisible to epubcheck).
 - `src/bindery/validate.py`: epubcheck wrapper, the `gate` (improvement) and `no_worse` (no-regression, for the lossy strips) acceptance bars.
 - `src/bindery/library.py`: Calibre walk, atomic replace, backups, and native format installation. Since v0.19.0 `CalibreIdResolver` resolves the book id from `metadata.db` through cquarry (one lazy path→id map per run; since v0.20.0 the map comes from `CalibreDB.format_path_index()`, re-normalized with `resolve().lower()` for the resolver's symlinked-directory and case-insensitive matching); the `(id)` directory-name regex is only the no-catalog fallback. Since v0.24.0 `install_format()` places the repaired file atomically and updates the `data` row through `cquarry.write.WritableCalibreDB` (since v0.31.0 via `set_format`, cquarry 1.17's sanctioned remove+add in one transaction); the external `calibredb` CLI is gone. Since v0.32.0 a guessed id drives a row update only when metadata.db corroborates it (`_verify_guess`: books row exists, file in the book's own directory, catalogued `data.name` when a row exists); anything else saves in place and leaves the catalog untouched: never reintroduce directory-name guessing as the primary source: renamed/mismatched directories would replace the wrong book. Since 2026-09-15 `make_backup` takes the opt-in `--backup-keep N` ring: at most N backup files per book, the author original `.bak` never deleted, newest content at the highest name; default remains an unbounded rotation.

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: bindery-cli
-Version: 0.43.0
+Version: 0.44.1
 Summary: Audit EPUB body text and repair broken EPUBs with deterministic, epubcheck-gated fixes; atomic in-place replacement in a Calibre library.
 Project-URL: Homepage, https://github.com/VirInvictus/bindery-cli
 Project-URL: Repository, https://github.com/VirInvictus/bindery-cli

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/patchnotes.md

@@ -1,4 +1,21 @@
 # bindery-cli Patch Notes
+## v0.44.1 (2026-09-18)
+
+### Doctor names its interpreter
+
+* **`bindery doctor` prints `sys.executable` on its python line**, in the epubcheck line's `version  [path]` shape. The version-only line hid which environment was probed, so an html5lib "not installed" read as wrong when the module sat in the system interpreter: a uv tool venv (`include-system-site-packages = false`) genuinely cannot see system site-packages, and `find_spec` only ever consults the running interpreter. The path makes the install shape self-diagnosing.
+* Repo housekeeping with no runtime effect: `FUNDING.yml` (GitHub Sponsors + Liberapay).
+## v0.44.0 (2026-09-17)
+
+### The wave-2 batch: PKG-010 entry renames, the cover and ToC-drift audit slices, and the roman grammar unified
+
+* **`--encode-url-spaces` gained its rename half**, the biggest real-prevalence repair class left (PKG-010: 8,237 occurrences in 284 books at the 2026-09-17 refresh). Archive entries whose names carry raw spaces are renamed to their underscore spellings and every reference is rewritten (OPF, NCX, content `src`/`href`, stylesheet `url()`). The design was decided by experiment, not by the roadmap box's plan: epubcheck 5.3 DECODES references before entry lookup, so percent-encoded entries are unfindable by the encoded references pointing at them (all four raw/percent/underscore combinations built and checked); underscore on both sides resolves and clears PKG-010. Ambiguous renames are refused per entry (a target that already exists, two names converging, a duplicated archive name), a book with any non-UTF-8 document refuses all of its renames, a renamed OPF regenerates a stale container, and the acceptance rides `no_worse` because the gain sits on the warning axis the improvement gate does not measure (same bar as `--fix-cover`).
+* **The matcher fix that explains Theaetetus** (the 2026-09-16 hand-rescue): the encode pass's value class `[^"']` stopped at apostrophes inside double-quoted hrefs, so the 270 raw-space OPF hrefs never matched and the fatal survived. The matcher now takes the tempered-quote idiom (possessive, house style), and an apostrophe in a double-quoted filename is ordinary.
+* **`bindery audit cover`** (advisory, the EPUB3 half of the ruled hybrid): dangling EPUB2 `<meta name="cover">` (the `--fix-cover` class), the EPUB3 `properties~="cover-image"` declaration, and whether the named cover file exists. **`bindery audit tocdrift`**: the structural diff between the NCX navMap and the EPUB3 nav toc, keyed on the full target including fragments -- entries each side is missing plus label mismatches. Both never flag a book and never move the exit code; ToC synthesis stays out of the repair charter permanently. The loader exposes the parsed OPF, the NCX text, and the nav HTML on `Book`.
+* **The audit-refresh deep-dive ran** (read-only FastSweep extract over the full 5,228-book library; raw report in the facility): RSC-005 164,302 -> 13,782 occurrences, RSC-007 3,219 -> 14,162 in 604 books (the classics-wave imports), RSC-020 9,953 in 337 books, PKG-010 8,237 in 284 books (population flat: the rename class was still live, hence this ship).
+* **The roman grammar is one copy again**: pagination.py is the canonical home (it vendors into the plugin; audit does not), audit.py imports `ROMAN_RE`/`ROMAN_MAX`/`roman_value`, and the two byte-identical copies cannot drift. The RepairFlags dataclass refactor stays boxed with its reason (pure churn on the signatures this release touched).
+* Suite: 497 -> 521 tests (tests/test_space_renames.py, tests/test_cover_tocdrift.py, and the updated `--encode-url-spaces` end-to-end pins).
+
 ## v0.43.0 (2026-09-16)
 
 ### The stdlib XML hardening: untrusted metadata is bounded and entity-refused, no dependency

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "bindery-cli"
-version = "0.43.0"
+version = "0.44.1"
 description = "Audit EPUB body text and repair broken EPUBs with deterministic, epubcheck-gated fixes; atomic in-place replacement in a Calibre library."
 readme = "README.md"
 classifiers = [

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/roadmap.md

@@ -1812,25 +1812,72 @@ four interpreter families.
 
 ### Reopened / boxed by the final blitz (2026-09-15)
 
-- [ ] **--encode-url-spaces entry renames** (PKG-010, top-6 warning
+- [x] **--encode-url-spaces entry renames** (PKG-010, top-6 warning
       class, 280 books): rename archive entries whose filenames carry
       raw spaces, rewriting every reference; the reference half
       shipped v0.28.0. Biggest real-prevalence repair class left; the
-      gate must re-measure the whole book.
-- [ ] **Cover advisory analyzer**: the EPUB3 `properties="cover-image"`
+      gate must re-measure the whole book. *(SHIPPED 2026-09-17,
+      v0.44.0 -- with the plan CHANGED by experiment. epubcheck 5.3
+      DECODES references before entry lookup, so percent-encoded entry
+      names are unfindable by the encoded refs pointing at them
+      (variants built and checked: raw/raw = PKG-010 only,
+      pct/pct = broken lookups, pct-raw = broken, underscore/underscore
+      = clean); renames therefore use the underscore spelling, and
+      references are rewritten to the identical form. Ambiguous renames
+      are refused per entry (target exists, two names converging, a
+      duplicated archive name); a book with any non-UTF-8 document
+      refuses all renames. The rename rides the existing
+      --encode-url-spaces flag and is accepted under no_worse (its gain
+      sits on the warning axis the gate does not measure; same bar as
+      fix-cover). The refresh also found the real reason Theaetetus's
+      OPF fatal survived the 0.28 reference half: the value class
+      [^"'] stopped at apostrophes inside double-quoted hrefs; the
+      matcher now takes the tempered-quote idiom. Refresh counts:
+      PKG-010 at 8,237 occurrences in 284 books (was 4,112 in ~280;
+      the class persisted). Pinned by tests/test_space_renames.py
+      plus the updated test_epub pins.)*
+- [x] **Cover advisory analyzer**: the EPUB3 `properties="cover-image"`
       audit slice completing the ruled hybrid (21 dangling EPUB2 metas
-      and 3 absent cover files measured behind it).
-- [ ] **Audit-refresh deep-dive**: per-class deltas vs the 2026-09-12
-      baselines; sizes the two boxes above for free.
-- [ ] **NCX<->nav drift detector** (audit-only): the remaining
-      unticked Phase 16 C box; size it after the deep-dive.
+      and 3 absent cover files measured behind it). *(SHIPPED 2026-09-17,
+      v0.44.0: `bindery audit cover` reads the package's own wiring --
+      dangling EPUB2 meta, EPUB3 property declaration, cover-file
+      presence -- advisory by contract like completeness; the loader
+      now exposes the parsed OPF.)*
+- [x] **Audit-refresh deep-dive**: per-class deltas vs the 2026-09-12
+      baselines; sizes the two boxes above for free. *(DONE 2026-09-17:
+      read-only FastSweep extract over the full 5,228-book library;
+      raw report at testing_facility/top500candidates/
+      extract-2026-09-17.txt. RSC-005 164,302 -> 13,782 occurrences
+      (the repair waves did land); RSC-007 3,219 -> 14,162 in 604
+      books (up: the classics-wave imports); RSC-020 8,431 -> 9,953
+      in 337 books; PKG-010 4,112 -> 8,237 in 284 books (population
+      flat -- the rename class stayed live, hence the ship). 2,910
+      books carry findings.)*
+- [x] **NCX<->nav drift detector** (audit-only): the remaining
+      unticked Phase 16 C box; size it after the deep-dive. *(SHIPPED
+      2026-09-17, v0.44.0: `bindery audit tocdrift` diffs the NCX
+      navMap against the EPUB3 nav toc -- entries each side is missing
+      plus label mismatches, keyed on the full target including the
+      fragment. Advisory by contract; the loader exposes the NCX text
+      and the nav document's HTML. ToC synthesis stays out of charter
+      permanently.)*
 - [ ] **Internal refactors (polish, no behavior change)**: a
       RepairFlags dataclass for the triplicated ~25-kwarg
       process_book/repair_epub signature; shared roman/arabic number
       helpers for pagination.py and audit.py (their year-range
       grammars differ by design: document or unify, never a third
       copy). Deliberately not refactored mid-blitz: pure churn risk
-      around five releases of work.
+      around five releases of work. *(Roman/arabic half DONE
+      2026-09-17, v0.44.0: the two copies were byte-identical, so the
+      box resolves to UNIFY -- pagination.py is the canonical home
+      (it vendors into the plugin; audit does not), audit.py imports
+      ROMAN_RE/ROMAN_MAX/roman_value from it, and the comment records
+      that any future divergence is a decision at pagination, not a
+      fork. RepairFlags dataclass DEFERRED with reason: pure churn on
+      a ~25-kwarg surface immediately after the v0.44 batch touched
+      exactly those signatures; do it as a standalone lane with the
+      full suite and the plugin byte-compat job green at every step,
+      not as a rider.)*
 - [ ] **MobileRead listing for the Bindery Repair plugin** (Brandon's
       manual step): post the listing with name/identity, the
       release-attached zip, minimum Calibre 7.0, Linux platform note.
@@ -1902,3 +1949,37 @@ four interpreter families.
       15 tests (spin shapes alarm-guarded per greedy site, unterminated-
       quote skips, well-formed byte-identity, prune spin over the
       truncated-OPF shape). Never a third grammar copy.)*
+
+- [x] **`--encode-url-spaces` left an OPF-manifest RSC-020 FATAL standing
+      on the Theaetetus fixture** (observed 2026-09-16, classics wave
+      phase 1): the Hackett Aristotle *Theaetetus* EPUB (McDowell) arrived
+      with 270 raw-space zip entry names AND 270 raw-space hrefs in
+      content.opf — epubcheck fatal RSC-020 at content.opf(33,110). The
+      `--all` sweep's encode pass recorded `url_spaces_encoded:351` and
+      dropped errors 356→6, but the fatal survived it (1f before → 1f
+      after). A hand rebuild (percent-encode every reference in
+      .opf/.ncx/.xhtml while KEEPING the raw-space entry names — epubcheck
+      decodes hrefs to find entries, so renaming entries to encoded form
+      breaks lookups the other way) cleared the fatal entirely: 0f.
+      Suspect the encode pass covers content docs and NCX but not the OPF
+      manifest's own href attributes, or a reserialize round-trip writes
+      them back decoded. Fixture: the imported book (id 9135, the file was
+      hand-fixed in place) — the defects and the fix script's operations
+      are documented in the library's phase-1 record for 2026-09-16.
+      *(RESOLVED 2026-09-17, v0.44.0: neither suspicion was right. The
+      real cause was the value class [^"'] in the encode matcher, which
+      stopped at the apostrophes in the OPF's filenames -- the OPF
+      branch DID run but matched nothing. The tempered-quote idiom
+      fixes the matcher, and the entry-rename half clears the class
+      outright.)*
+
+- [ ] **Candidate transform: `--` inside XML comments (RSC-016 fatal)**.
+      Same book: `OEBPS/...split_269.html` carried a `--` inside an XML
+      comment (illegal XML, fatal RSC-016), costing the file its only
+      fatal after the OPF fix. Hand fix applied: replace `--` with an
+      en-dash inside comment nodes (2 sites, prose preserved). A small
+      `fix_comment_double_hyphen` transform (comment nodes only, `--` ->
+      en-dash, byte-counted) would make the always-on core able to parse
+      such books at all — until then the book parses in lenient readers
+      but never passes epubcheck. Low frequency (one book in the wave),
+      noted with the fixture reference above.

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/spec.md

@@ -184,11 +184,20 @@ every EPUB3 book in an `--all` sweep taking exactly that damage).
   reader resolves (`kindle:embed:`, `file:`, ...) are stripped under the same flag; the
   resolvable set is fixed (`http`, `https`, `mailto`) and extends only with a named
   finding.
-- **`--encode-url-spaces`**: percent-encode raw spaces in `src`/`href` attribute values
-  across the package (OPF manifest, NCX `content src`, content documents). A URL with a
-  literal space is not a valid URL (RSC-020 "not a valid URL") and unresolvable on
-  strict readers; the encoded form denotes the same file and renders identically. Scope
-  is fixed to the space character: extend only with a named epubcheck finding.
+- **`--encode-url-spaces`**: repairs raw-space URLs two ways. The reference half
+  percent-encodes raw spaces in `src`/`href` attribute values across the package
+  (OPF manifest, NCX `content src`, content documents): a URL with a literal space is
+  not a valid URL (RSC-020 "not a valid URL") and unresolvable on strict readers; the
+  encoded form denotes the same file and renders identically. The rename half (v0.44.0)
+  renames archive entries whose names carry raw spaces to their underscore spellings
+  and rewrites every reference to them (OPF, NCX, content `src`/`href`, stylesheet
+  `url()`), clearing PKG-010: underscore, never percent-encoding, because epubcheck
+  decodes references before entry lookup (both-sides-%20 breaks lookups; verified
+  against epubcheck 5.3). Ambiguous renames (a target that already exists, two names
+  converging, a duplicated entry name) are refused per entry, and a book with any
+  non-UTF-8 document refuses all of its renames (those entries pass through
+  byte-for-byte with no chance to rewrite their references). Scope stays fixed to the
+  space character: extend only with a named epubcheck finding.
 
 - **`--fix-container`**: generate `META-INF/container.xml` at the located OPF when the
 container is missing, unparseable, or names a file the archive does not contain. This is the
@@ -400,8 +409,8 @@ crashing the sweep.
 
 ## Audit subcommand (read-only)
 
-`bindery audit {content,pagenumbers,emptytext,ocr,monolithic,completeness,all} [PATH] [--max-doc-chars N]
-[--tag TAG] [--id IDs]` (v0.15.0, `audit.py`; `--tag` since v0.18.0; `monolithic` since v0.21.0, `--max-doc-chars N`; `--id` since v0.19.0, comma-lists in v0.23.0; `completeness` since v0.36.0) inspects
+`bindery audit {content,pagenumbers,emptytext,ocr,monolithic,completeness,cover,tocdrift,all} [PATH] [--max-doc-chars N]
+[--tag TAG] [--id IDs]` (v0.15.0, `audit.py`; `--tag` since v0.18.0; `monolithic` since v0.21.0, `--max-doc-chars N`; `--id` since v0.19.0, comma-lists in v0.23.0; `completeness` since v0.36.0; `cover` and `tocdrift` since v0.44.0) inspects
 EPUB body text for flaws epubcheck cannot see: non-English script blocks, baked-in page-number
 layers (sliding-window density heuristics), empty or thin books, systemic OCR damage, and
 single oversized content documents (one spine doc at or above 300k characters: readers refuse
@@ -417,6 +426,15 @@ read fine are the OBFUSCATED advisory (publisher embedding, benign, never a fail
 unreadable obfuscation entry is CORRUPT (a broken font, not a business model), and only
 non-obfuscation algorithms give the ENCRYPTED verdict with its DRM skip advice.
 
+Two more advisory analyzers ship in v0.44.0. `cover` reads the package's own cover
+wiring (the EPUB3 half of the ruled hybrid): a dangling EPUB2 `<meta name="cover">`
+(the `--fix-cover` repair class), an EPUB3 `properties~="cover-image"` declaration,
+and whether the named cover file exists. `tocdrift` diffs the two tables of contents
+an EPUB 3 book may carry -- the NCX navMap against the nav document -- reporting
+entries each side is missing and labels that disagree; it feeds decisions, never a
+rewrite (ToC synthesis is out of the repair charter permanently). Both never flag a
+book and never move the exit code.
+
 The completeness analyzer is the phase-1 spot-check and is advisory by contract: it never
 flags a book and never moves the exit code. Per book it reports the spine doc count, the
 prose-doc count (spine docs carrying at least 400 visible characters), the opening and closing

{bindery_cli-0.43.0 → bindery_cli-0.44.1}/src/bindery/__init__.py

@@ -11,7 +11,7 @@ Calibre plugin built from this core.
 Single source of truth for the version. pyproject.toml must match VERSION below.
 """
 
-VERSION = "0.43.0"
+VERSION = "0.44.1"
 __version__ = VERSION
 
 from .epub import RepairReport, repair_epub  # noqa: E402