docs(guide): describe both library save modes in database.md and architecture.md (#580)

Closes #578. Rewrites the user file library save-mode description in the English database.md and architecture.md guides (independent-new by default, parent-linked on overwrite) and updates all 20 translated copies of each, with i18n_source_hash re-stamped so the parity gate stays green.
This commit is contained in:
SnapOtter
2026-07-19 22:59:34 +08:00
committed by GitHub
parent 1113c761ea
commit 5558cf18b8
42 changed files with 82 additions and 82 deletions
+1 -1
View File
@@ -51,7 +51,7 @@ Shared TypeScript types, constants (like `APP_VERSION` and tool definitions), an
A Fastify v5 server exposing 242 tool routes across five modalities (image, video, audio, PDF, file) that handles:
- File uploads, temporary workspace management, and persistent file storage
- User file library with version chains (`user_files` table) - each processed result links back to its source file and records which tool was applied, with auto-generated thumbnails for the Files page
- User file library (`user_files` table): a saved edit is stored as an independent new file by default, or as a parent-linked version when you overwrite the original. It records which tools were applied (`toolChain`) and gets an auto-generated thumbnail for the Files page
- Tool execution (routes each tool request to the image engine or AI bridge)
- Pipeline orchestration (chaining multiple tools sequentially)
- Batch processing with concurrency control via BullMQ job queues (pools: image, media, ai, docs, system)