- Enable PP-StructureV3's use_doc_orientation_classify feature - Detect rotation angle from doc_preprocessor_res.angle - Swap page dimensions (width <-> height) for 90°/270° rotations - Output PDF now correctly displays landscape-scanned content Also includes: - Archive completed openspec proposals - Add simplify-frontend-ocr-config proposal (pending) - Code cleanup and frontend simplification 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3.0 KiB
REMOVED Requirements
Requirement: Legacy OCR Service Implementation
Reason: ocr_service_original.py was the original OCR service implementation that has been completely superseded by the current ocr_service.py. The legacy file is no longer referenced by any part of the codebase.
Migration: No migration needed. The current ocr_service.py provides all required functionality with improved architecture.
Scenario: Legacy service file removal
- WHEN the legacy
ocr_service_original.pyfile is removed - THEN the system continues to function normally using
ocr_service.py - AND no import errors occur in any service or router
Requirement: Unused Preprocessor Service
Reason: preprocessor.py was a document preprocessor that is no longer used. Its functionality has been absorbed by layout_preprocessing_service.py.
Migration: No migration needed. The preprocessing functionality is available through layout_preprocessing_service.py.
Scenario: Preprocessor file removal
- WHEN the unused
preprocessor.pyfile is removed - THEN the system continues to function normally
- AND layout preprocessing works correctly via
layout_preprocessing_service.py
Requirement: Unused PDF Font Manager
Reason: pdf_font_manager.py was intended for font management but is not referenced by pdf_generator_service.py or any other service.
Migration: No migration needed. Font handling is managed within pdf_generator_service.py directly.
Scenario: Font manager file removal
- WHEN the unused
pdf_font_manager.pyfile is removed - THEN PDF generation continues to work correctly
- AND fonts are rendered properly in generated PDFs
Requirement: Legacy Frontend Components
Reason: MarkdownPreview.tsx and ResultsTable.tsx are frontend components that are not referenced by any page or component in the application.
Migration: No migration needed. MarkdownPreview functionality is not currently used. ResultsTable functionality has been replaced by TaskHistoryPage.
Scenario: Unused frontend component removal
- WHEN the unused
MarkdownPreview.tsxandResultsTable.tsxfiles are removed - THEN the frontend application compiles successfully
- AND all pages render and function correctly
Requirement: Legacy API Client Migration
Reason: services/api.ts and types/api.ts are legacy API client files with only 2 remaining references. These should be migrated to apiV2 for consistency.
Migration:
- Move
ExportRuletype totypes/apiV2.ts - Add export rules API functions to
services/apiV2.ts - Update
SettingsPage.tsxandLayout.tsxto use apiV2 - Remove legacy api.ts files
Scenario: Legacy API client removal after migration
- WHEN the legacy
api.tsfiles are removed after migration - THEN all API calls use the unified
apiV2client - AND
SettingsPageexport rules functionality works correctly - AND
Layoutlogout functionality works correctly