Added end-to-end tests

automatic-pdf-renamer/API.md

@@ -64,7 +64,6 @@ This convention applies to HTTP error responses from every endpoint. Successful
 | GET | `/files` | Browse, filter, sort, and search documents |
 | GET | `/files/{sha256}` | Document detail and metadata |
 | GET | `/files/{sha256}/pdf` | Stream the current PDF for the embedded viewer |
-| GET | `/files/{sha256}/text` | Retrieve complete extracted text |
 | POST | `/files/{sha256}/preview` | Validate proposed fields and calculate the target key without mutation |
 | POST | `/files/{sha256}/validate` | Validate metadata and apply the final move/rename if required |
 | GET | `/consistency` | List known storage/index anomalies |
@@ -226,7 +225,7 @@ The response must not claim ML confidence for a rules-only decision. `confidence
 
 ### GET `/files/{sha256}`
 
-Returns the latest sidecar-backed record, including fields needed by the detail page. SQLite may be used to locate the record, but authoritative metadata must be reconciled from the sidecar where needed.
+Returns the complete document detail in a single request, including metadata and the full extracted text from the PDF.
 
 Example response:
 
@@ -242,6 +241,7 @@ Example response:
   "emitting_company": "EDF",
   "document_type": "invoice",
   "optional_fields": {"invoice_number": null, "amount": 125.5},
+  "extracted_text": "Complete text from page 1...\\n\\nComplete text from page 2...",
   "target_key_preview": null,
   "confidence": null,
   "events": [
@@ -268,17 +268,6 @@ Requirements:
 - Return `404` if the object is genuinely missing and create/retain a consistency anomaly for diagnosis.
 - Never return the extracted text in place of the PDF bytes.
 
-### GET `/files/{sha256}/text`
-
-Returns the complete extracted text stored in the sidecar/replica, including all pages. Useful for a separate text panel or troubleshooting; the UI may instead use the detail response if the payload size is acceptable.
-
-```json
-{
-  "sha256": "0123456789abcdef...",
-  "text": "Complete text from page 1...\n\nComplete text from page 2..."
-}
-```
-
 ## 8. Preview and validation
 
 All mutation endpoints must validate the requested state, recompute the period from `emission_date` and the applicable template period rules, calculate the destination key from the template's key pattern, and prevent an invalid document from being renamed. Filename parsing must never be used as a source for the period.