pdf-tooling 0.1.1__tar.gz

pdf_tooling-0.1.1/.gitignore

@@ -0,0 +1,54 @@
+# Dependencies
+node_modules/
+venv/
+.venv/
+__pycache__/
+
+# Build
+dist/
+build/
+target/
+
+# Environment
+.env
+.env.local
+.env.*.local
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Python tooling caches and coverage artefacts produced by this repo's own targets
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+*.egg-info/
+
+# make cover's mkdir-based concurrency guard (B-090). Removed on every exit
+# path by its own trap; this entry only matters if that trap is bypassed
+# (e.g. SIGKILL) and the lock dir is left stranded in a checkout.
+.make-cover.lock/
+
+# Dedicated license-measurement environments built by scripts/licenses.py
+# (PDF-02 Design §4.2). The inventory is generated from a pinned --no-dev
+# closure, never from the ambient venv, so these are build scratch, not sources.
+.venv-licenses/
+.venv-licenses-dev/
+
+# Per-interpreter environments built by `make ci PYTHON=<x.y>` (PDF-28 B-029,
+# AC15). `.venv/` above is the exact-name entry for the ambient venv; this is
+# deliberately a separate glob rather than widening it to `.venv*/`.
+.venv-py*/
+
+# Scratch space for manual probing against real documents. Never committed.
+.scratch/

pdf_tooling-0.1.1/CONTRIBUTING.md

@@ -0,0 +1,65 @@
+# Contributing
+
+Thanks for considering a contribution. This document is short on purpose: everything it asks for is mechanically checked, so you can verify you have satisfied it before you push.
+
+## Developer Certificate of Origin
+
+Every commit must be signed off:
+
+```bash
+git commit -s -m "feat: add the thing"
+```
+
+That adds a `Signed-off-by:` trailer, which is your statement that you have the right to submit the work under this project's licence. There is no CLA. Commits without the trailer are rejected.
+
+## Commit conventions
+
+Conventional commit subjects: `feat|fix|docs|refactor|test|chore`, imperative mood, no trailing period.
+
+Work that implements a planned specification carries that specification's tag as a subject prefix, so the change and its rationale can be found from either direction:
+
+```
+[PDF-NN] feat: <what the specification delivers>
+```
+
+Write the subject about the *why*, not the *what* — the diff already says what changed.
+
+Each implemented specification appends **its own** entry to `changelog.md`, in the same commit as the code. Entries go directly below the anchor comment, newest first. Never batch entries, never back-fill one later, and never edit an entry that has landed — a correction is a new entry with a new date.
+
+## The local gate
+
+```bash
+uv sync
+make ci
+```
+
+`make ci` is a **subset** of CI, run with the same commands. It does not predict CI — `.github/gate-parity.toml` declares exactly what runs locally and what does not, why, and where a local counterpart exists; `make ci`'s own epilogue prints that gap on every run, and `make help` lists every target it does not run.
+
+Three things about the gate are deliberate and should not be "fixed":
+
+- **No target degrades.** No recipe ends in `|| true`, is prefixed with `-`, or swallows a missing tool. A gate that cannot fail is not a gate; a check that quietly did not run is worse than one that failed loudly.
+- **`make secret-scan` needs the `gitleaks` binary** and fails loudly when it is absent, rather than passing. It is not part of `make ci` locally: the local binary, when present, is a different scanner version than the one CI pins (`GITLEAKS_VERSION` in `ci.yml`), so running it inside `make ci` would trade a known gap for an unnoticed one — same command, different check.
+- **Some CI checks are not part of `make ci` at all, on purpose.** A few (`make engines-gate`, `make licenses-check`, `make artifacts-check`) are runnable on demand but cost real wall-clock; others need CI's own host, matrix, or a pinned binary and have no local form. `.github/gate-parity.toml` is the record of which is which.
+
+Individual targets, when you want a faster loop:
+
+```bash
+make fmt          # format the tree
+make lint         # lint
+make typecheck    # strict type checking of src/
+make test         # the test suite
+make test-e2e     # only the subprocess-level CLI tests
+```
+
+`make help` lists every target.
+
+## What a change must not do
+
+- **Add anything under AGPL, GPL or LGPL to the call graph** — not as an import, not as an optional extra, not as a `subprocess` fallback. This is a licence-compatibility rule, not a preference, and it is checked in CI.
+- **Add a runtime dependency.** The runtime stack is declared up front and deliberately frozen: the licence manifest is generated from the lockfile and diffed in CI, so a mid-stream addition turns that check red on an unrelated commit and the failure looks like something else entirely. If you believe you need one, raise it before writing the code.
+- **Change an exit code or a structured output field.** Both are public API. Adding is fine; renumbering and renaming are major-version changes.
+- **Import the CLI framework below the CLI layer**, or write to a user-visible path outside the safety layer. Both are enforced by tests, not by review alone.
+
+## Tests
+
+See `TESTING.md` for how each suite is run and what a legitimate skip looks like. The short version: a test that cannot run because an engine or a corpus is missing must **skip visibly, with a reason** — never pass silently, and never be deleted so the suite turns green.

pdf_tooling-0.1.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Armando Herra
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.