fix(12.1): align cloud browser contract — kind, provider_item_id, server freshness
Normalized cloud frontend for DocuVault v0.2.5: - Cloud UI classifies items by kind=folder/file (is_dir removed from all active paths) - Folder navigation uses provider_item_id (opaque provider ref) — DocuVault id kept for row identity - Server freshness (refresh_state, last_refreshed_at) mapped verbatim — no browser-clock evidence - Breadcrumb lineage built from explicit visited nodes — never split(provider_item_id) - CloudFolderTreeItem: expandable/icon/navigate/loadChildren all use kind and provider_item_id - Version bump 0.2.4 → 0.2.5 - SECURITY.md: T-12.1-11 through T-12.1-15 closed - 369 tests pass, npm audit clean, production build clean
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
|
||||
DocuVault is a multi-user SaaS document management platform built on FastAPI (Python) + Vue 3. It handles document upload, text extraction (PDF/DOCX/image/text), AI-based topic classification, per-user isolated storage, folder organization, document sharing, and pluggable cloud storage backends (OneDrive, Google Drive, Nextcloud, WebDAV).
|
||||
|
||||
**Current state:** v0.2.1 — Phase 12 gap-closure complete (2026-06-20). Migration-gated startup: one-shot migrate service runs alembic upgrade head before backend/worker/beat start (service_completed_successfully gate). 0005→0006 upgrade regression in test_migration_0006.py. RUNBOOK migration ops section. Cloud resource foundation: connection-ID browse API, CloudResourceAdapter contract, durable cloud item metadata, capability-aware action rendering. Not cleared for public internet deployment.
|
||||
**Current state:** v0.2.5 — Phase 12.1 Plan 03 complete (2026-06-22). Cloud frontend aligned with normalized API: `kind` field for item classification, `provider_item_id` for opaque provider navigation, server freshness state mapped verbatim, explicit breadcrumb lineage. Phase 12.1 in progress. Not cleared for public internet deployment.
|
||||
|
||||
## Stack
|
||||
|
||||
|
||||
Reference in New Issue
Block a user