Adobe Acrobat Pro

Build me a local PDF page organizer as a narrow substitute for Adobe Acrobat Pro. Requirements:

- Use Python, FastAPI, PyMuPDF, and a local folder chosen at startup. Bind the web UI to localhost and store each imported original unchanged under a generated ID.
- Accept PDFs only. Show page thumbnails and metadata; let me select and reorder pages, rotate pages by quarter turns, split at chosen page numbers, and merge selected documents.
- Preview the output page sequence before writing a new PDF. Save it under a new filename and record source IDs, page order, rotation, output path, and a hash of each original in a JSON manifest.
- Reject password-protected or malformed PDFs with a visible reason rather than modifying or bypassing protection. Warn if forms, signatures, annotations, or fonts may change during page operations.
- Export a ZIP containing the output PDF and manifest. Allow deleting derived files separately from originals, with confirmation.
- No accounts, telemetry, hosted sharing, OCR, Office conversion, electronic signatures, compression claims, or redaction. Do not draw black boxes and call that redaction.
- README: supported operations, local storage, backup, PDF fidelity limits, and when to use a mature PDF tool for sensitive documents.

# AGENTS.md — Build guide for Adobe Acrobat Pro

## Project scope
Perform a focused set of PDF edits and conversions, preserve originals, generate auditable outputs, and keep files in a user-owned store.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Adobe Acrobat Pro, perform a focused set of PDF edits and conversions while preserving originals. The hard boundary is decades of pdf engine work, format fidelity, integrations, signatures, and enterprise trust, plus document fidelity, identity, and compliance.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Docker
- PostgreSQL
- LibreOffice headless
- local or S3-compatible storage
- public HTTPS for signature links

## Stack and architecture
- Python and FastAPI
- PyMuPDF page selection, copy, and rotation
- Local original and derived PDF folders
- JSON operation manifest

## Security and data integrity
- Preserve each original and verify its hash after processing
- Reject encrypted or malformed inputs with an explicit error
- Do not claim secure redaction or signature preservation

## Agent implementation rules
- Preserve source page provenance in every output manifest
- Inspect outputs for page count and order before showing success

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Show the supported page operations precisely, with no Acrobat feature-parity claim

## Engineering roadmap
1. Implement immutable PDF import and page thumbnails.
2. Build reorder, rotate, split, and merge previews and derived-file export.
3. Write a manifest and document unsupported redaction, signatures, and conversion.

## Paid-product capabilities outside this build
- decades of PDF engine work, format fidelity, integrations, signatures, and enterprise trust
- pixel-perfect proprietary PDF engine
- identity verification
- qualified trust services
- large template and integration ecosystem

## Implementation prompt
Build me a local PDF page organizer as a narrow substitute for Adobe Acrobat Pro. Requirements:

- Use Python, FastAPI, PyMuPDF, and a local folder chosen at startup. Bind the web UI to localhost and store each imported original unchanged under a generated ID.
- Accept PDFs only. Show page thumbnails and metadata; let me select and reorder pages, rotate pages by quarter turns, split at chosen page numbers, and merge selected documents.
- Preview the output page sequence before writing a new PDF. Save it under a new filename and record source IDs, page order, rotation, output path, and a hash of each original in a JSON manifest.
- Reject password-protected or malformed PDFs with a visible reason rather than modifying or bypassing protection. Warn if forms, signatures, annotations, or fonts may change during page operations.
- Export a ZIP containing the output PDF and manifest. Allow deleting derived files separately from originals, with confirmation.
- No accounts, telemetry, hosted sharing, OCR, Office conversion, electronic signatures, compression claims, or redaction. Do not draw black boxes and call that redaction.
- README: supported operations, local storage, backup, PDF fidelity limits, and when to use a mature PDF tool for sensitive documents.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.