pdf-tooling 0.3.0__tar.gz → 0.3.1__tar.gz

{pdf_tooling-0.3.0 → pdf_tooling-0.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pdf-tooling
-Version: 0.3.0
+Version: 0.3.1
 Summary: One safe, permissively-licensed command-line tool for the common PDF chores.
 Project-URL: Homepage, https://github.com/ArmandoHerra/pdf-tooling
 Project-URL: Repository, https://github.com/ArmandoHerra/pdf-tooling
@@ -132,6 +132,8 @@ uv run pdftooling --version            # tool, Python and engine versions on one
 
 `uv run pdftooling --help` is the authoritative list of what is actually available at any moment — if a verb is not printed there, it does not exist yet.
 
+**Page selection across verbs.** `split` always operates on the whole document and takes no `--pages`; to act on a subset of pages, use `extract` (keep a subset), `delete` (remove pages) or `reorder` (permute), each of which accepts `--pages`.
+
 ## Output contract
 
 Rendered payloads go to **stdout**; diagnostics, warnings and progress go to **stderr**. `-o` selects the shape and defaults to `table` when stdout is a terminal and `json` when it is not, so piping into `jq` needs no flag.
@@ -200,7 +202,7 @@ Uniform across every verb.
 ## Safety contract
 
 - `--dry-run` plans and reports; it writes nothing, anywhere.
-- Outputs never clobber. An existing target needs `-f/--force`.
+- Outputs never clobber. An existing target needs `-f/--force`. On a non-interactive run, overwriting in a multi-input invocation (`merge`, `delete`, `convert`, etc.) additionally requires `-y`: bulk (more than a single input) plus destructive (in-place or clobbering) on a non-terminal stdin is refused with exit 5 rather than prompted.
 - Every write is write-to-temp-on-the-target-filesystem, `fsync`, then an atomic rename.
 - Inputs are never mutated unless you pass `--in-place`, which writes a `.bak` sidecar first. `--no-backup` suppresses the sidecar and requires `--in-place` — on its own it is a usage error.
 - A password is never accepted as a command-line value. `--password-file` takes a path or `-`, because `argv` is world-readable in `/proc` and lands in shell history.

{pdf_tooling-0.3.0 → pdf_tooling-0.3.1}/README.md

@@ -92,6 +92,8 @@ uv run pdftooling --version            # tool, Python and engine versions on one
 
 `uv run pdftooling --help` is the authoritative list of what is actually available at any moment — if a verb is not printed there, it does not exist yet.
 
+**Page selection across verbs.** `split` always operates on the whole document and takes no `--pages`; to act on a subset of pages, use `extract` (keep a subset), `delete` (remove pages) or `reorder` (permute), each of which accepts `--pages`.
+
 ## Output contract
 
 Rendered payloads go to **stdout**; diagnostics, warnings and progress go to **stderr**. `-o` selects the shape and defaults to `table` when stdout is a terminal and `json` when it is not, so piping into `jq` needs no flag.
@@ -160,7 +162,7 @@ Uniform across every verb.
 ## Safety contract
 
 - `--dry-run` plans and reports; it writes nothing, anywhere.
-- Outputs never clobber. An existing target needs `-f/--force`.
+- Outputs never clobber. An existing target needs `-f/--force`. On a non-interactive run, overwriting in a multi-input invocation (`merge`, `delete`, `convert`, etc.) additionally requires `-y`: bulk (more than a single input) plus destructive (in-place or clobbering) on a non-terminal stdin is refused with exit 5 rather than prompted.
 - Every write is write-to-temp-on-the-target-filesystem, `fsync`, then an atomic rename.
 - Inputs are never mutated unless you pass `--in-place`, which writes a `.bak` sidecar first. `--no-backup` suppresses the sidecar and requires `--in-place` — on its own it is a usage error.
 - A password is never accepted as a command-line value. `--password-file` takes a path or `-`, because `argv` is world-readable in `/proc` and lands in shell history.

{pdf_tooling-0.3.0 → pdf_tooling-0.3.1}/changelog.md

@@ -20,6 +20,14 @@ grep at `HEAD` — a grep at `HEAD` is exactly what hides a lost prepend.
 
 <!-- CHANGELOG-ANCHOR: insert new entries directly below this line, newest first -->
 
+## [PDF-49] Document two correct-but-surprising behaviours and cut the 0.3.1 patch — 2026-09-07
+
+- **Manual testing against the published `0.3.0` surfaced three shapes that read as bugs and are, in fact, documented, tested design/safety contracts — this entry records that finding rather than fixing anything.** `split --pages` (no such option — subsetting is `extract`/`delete`/`reorder`), `extract --dry-run` without a destination (already documented as required in `--help`), and `-f` overwrite on a multi-input non-TTY run without `-y` (the B-079 bulk-destructive gate in `src/pdf_tooling/safety/confirm.py`, refused with exit 5) all behaved exactly per contract.
+- **README's Safety-contract bullet on clobber-protection now also states the bulk-destructive `-y` rule**: on a non-interactive run, overwriting in a multi-input invocation (`merge`, `delete`, `convert`, etc.) additionally requires `-y`, because bulk plus destructive on a non-terminal stdin refuses with exit 5 rather than prompting.
+- **A new note near the verb table clarifies page selection across verbs**: `split` always operates on the whole document and has no `--pages`; page subsetting is `extract` (keep), `delete` (remove) or `reorder` (permute).
+- `website/` was verified against the same three components named in this spec's Evidence (`QuickStart.astro`, `Verbs.astro`, `ExitCodes.astro`) and no misrepresentation was found; `website/` is byte-unchanged.
+- Version `0.3.1`; `uv.lock` regenerated in the same commit via `uv lock`, never hand-edited (one-line diff). `src/` is byte-untouched — no verb, port, adapter, safety or error module edited; the B-079 gate is unchanged.
+
 ## [PDF-48] fix: the rename census was blind to its own untracked new files — 2026-09-06
 
 - **Two of this same spec's own new files were untracked throughout every local validation run, and `git grep` — which every census in `tests/test_rename_completeness.py` and `tests/test_brand_surfaces.py` uses — does not search untracked files by default.** `src/pdf_tooling/cli/deprecated.py` and `tests/test_rename_completeness.py` itself were staged only immediately before the prior commit, so `make test`/`make ci` reported clean locally while never actually exercising either file's content through the census instruments. CI's fresh checkout — where both files are tracked from the first commit — surfaced three real defects the local session could not: (1) `test_brand_surfaces.py`'s console-script-alias classifier (class `E`) did not include `deprecated.py`'s path, leaving its module docstring and its `pdf-toolkit`-alias notice call unclassified — class `E`'s count corrects `6 → 9` (the prior entry's `6 → 7` predates this fix and is not itself edited, per this file's own third rule); (2) `test_rename_completeness.py` spelled two of the frozen spellings literally in its own comments, the exact self-match hazard `test_brand_surfaces.py`'s needle-assembly trick exists to avoid, which this file had not applied to itself; (3) the remainder registries did not enumerate `deprecated.py`'s own occurrences. Re-verified with everything honestly tracked: `make test` 4093 passed / 0 failed; `make ci` 7/7 local checks, coverage unchanged at 94.69%; `make docs-gate` clean.

{pdf_tooling-0.3.0 → pdf_tooling-0.3.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pdf-tooling"
-version = "0.3.0"
+version = "0.3.1"
 description = "One safe, permissively-licensed command-line tool for the common PDF chores."
 readme = "README.md"
 requires-python = ">=3.11"