feat(file-library): add AI file and folder management

[zhangjiadi225]

What this PR does

Before this PR, agents could read and write library files but had no tools to move, rename, delete, or restore them, even though the app already supported those operations.

After this PR, agents can find folders, move and rename files or folders, move items to trash, list recently deleted items, and restore them. File-library tools now follow the Agent's approval mode like every other built-in tool: reads (search, read, list folders, list trash) are auto, and move, rename, trash, and restore are ask, all eligible for automatic approval. File search results include the containing folder id to distinguish matching names.

Screenshots or videos

Not captured: the new actions reuse the existing tool card. Device acceptance has not been run.

Why we need it and why it was done in this way

• The tools reuse FileLibraryService for moves and renames, preserving directory-cycle checks, collision handling, file versions, and cache notifications.
• TrashRuntime is now the single owner of trashing and restoration for both the library screen and the Agent tools. FileModule.moveToTrash and folder DELETE delegate to its new trashFile/trashFolder, replacing the file-storage trash helper and the folder handler's separate notification path; the screen's contracts and routes are unchanged. Permanent deletion and emptying the trash are not exposed to the Agent.
• The six management tools are deferred and found through tool_search, the same mechanism perf(agent-context): load plugin guides on demand #1260 introduced for Skill installation. That keeps about 5k characters (roughly 1.2k–1.4k tokens) out of every first request. Deferral is now a RuntimeTool.deferred flag, persisted in tool blueprints and the configuration key, replacing the Pi adapter's hard-coded Skill tool names.
• Cancellation is checked inside write transactions, so unfinished changes roll back together.

Breaking changes

Library search and read no longer require confirmation on every call. With the default automatic approval mode, library mutations also run without asking; trashed items remain recoverable for 30 days. No database migration or dependency changes.

Special notes for your reviewer

• This reverses the earlier rule that library reads always ask and are never auto-approval eligible. That rule guarded against prompt injection exfiltrating library content through web_fetch.
• Library screen behavior is unchanged; only its backend trash path moved. Folder deletion now also fires the file-change emitter, which invalidates the same queries the previous per-entry Data API paths did.
• Individual version trashing is removed: DELETE /files/versions/:id, the version trash kind, and the restore, purge, and draft-discard branches that only served it. No screen called the route since version history was hidden, and none of it reached a release tag, so no stored data needs compatibility.
• Regression coverage: tool availability, approval, and deferral; folder discovery and pagination; moves and renames; trash and restoration with notifications; cancellation rollback; blueprint persistence of deferred.
• Local gates on the final head: pnpm lint (0 errors), pnpm format:check, pnpm typecheck, pnpm i18n:check, and the 78 Jest suites related to the branch (1154 tests) pass.

Checklist

• Branch: This PR targets main
• PR: The description explains the final behavior
• Preview: Screenshots or a video are attached
• Code: Existing library and trash services are reused
• Upgrade: No migration or dependency changes are required
• Documentation: Agent tool and file model documentation is updated
• Self-review: Reviewed the local changes against origin/main

Release note

AI agents can now find library folders, move and rename files or folders, move items to the recycle bin, and restore deleted items. File-library actions follow the Agent's approval setting.