verhead. This feature adds SFTP as an alternative transfer protocol for Nextcloud accounts. SFTP writes directly to the filesystem and can achieve 80-100+ MB/s. After SFTP transfer, `occ files:scan` is executed on the Nextcloud server via SSH to index the new files.

Cap at 5000 files per side (HTTP 422 if exceeded).

-> "Alternativer"). The Toolbar keeps only a single Compare button that triggers deep compare directly.

`dest_only`. The `mismatch` status is retained but not produced by deep compare.

ss-account compare that finds duplicates anywhere in the tree.

ulated by a background indexer job. All browse, metadata, and compare endpoints are rewritten to read from the database first, with rclone as a fallback for un-indexed accounts. The result: folder browsing in <100ms, folder sizes in <10ms, and deep compare in <500ms.

ize, and deep compare operation. A single folder metadata request triggers a full recursive listing via the remote cloud API (Google Drive / Nextcloud), taking 5-60 seconds per folder. Deep compare requires two parallel recursive listings and regularly hits the 30-second timeout for large trees.

WebSockets for MVP

cess)

e` wrapping rclone's HTTP RC API. MariaDB stores cloud accounts, transfer tasks, and transfer history. No authentication required (single-user, internal tool).

e backend engine. The MVP delivers a beautiful two-panel file browser UI (inspired by MultCloud/CloudHQ) that lets users copy files from Google Drive to Nextcloud. Laravel provides the UI layer, task management, and progress tracking, while rclone (running as a daemon on localhost:5572) handles all cloud storage operations via its JSON RC API.

al (IndexedDB), @vueuse/core (utilities).

The two frameworks coexist on separate DOM trees. Existing `api.js` and `format.js` helpers are reused directly.

dedicated Blade template. The Vue app provides two panels (source/destination) with virtual-scrolled tree views, draggable split divider, sortable/resizable/hideable columns, folder metadata enrichment, multi-level sync checking, full file operations (mkdir, rename, move, copy, safe delete), IndexedDB caching with stale-while-revalidate, and persistent settings.

ual-panel file manager with virtual scrolling, tree view, column resizing, sync comparison, and file operations. An explore analysis (EX-0001) confirmed this conclusion and recommended Vue.js 3 with gradual migration (Perspective 4).

then auto-create one CloudAccount per user (My Drive) plus one per shared drive. rclone handles the rest via `service_account_file` + `impersonate` parameters.

This allows Skymirror to impersonate any user in a Google Workspace domain using a single JSON key file, without individual OAuth flows per user.

All gaps visible at: https://syncrovanis.magitek.no/gaps

Tell the user: > **GAP logged:** {GAP-NNN} [{priority}] {title} -> {workspace}

**syncrovanis types:** bug, feature, quality, docs, performance **mcp-servers types:** gap, error, perf, ux, bug, feature, quality, docs, performance **Priority:** critical, high, medium, low To see all current enums: `~/.claude/lib/gap-cli.sh enums`

Decide which workspace to post to based on WHERE the issue lives: | Issue relates to... | Workspace | Example components | |---------------------|-----------|-------------------| | Syncrovanis engine/pipeline/dashboard | syncrovanis | L0, L1, L2, L3, KB, dashboard, pipeline, logging, state, boilerplate, guardrail | | MCP server tools/functionality | mcp-servers | tools, translations, fields, deploy, graphql, cache, diagnostics, admin, relationships, extensions, build, docs, audit, manifest,...

**Step 1: Always search for duplicates FIRST:** ```bash ~/.claude/lib/gap-cli.sh search --workspace {ws} --query "short description" ``` **Step 2a: If duplicate found — add occurrence (bumps impact score):** ```bash ~/.claude/lib/gap-cli.sh occurrence --workspace {ws} --gap-id GAP-NNN --note "Seen again: {context}" ``` **Step 2b: If new — add gap:** ```bash ~/.claude/lib/gap-cli.sh add \ --workspace {ws} \ --title "Short descriptive title" \ --priority {critical|high|medium|low} \ ...

- You are fixing the issue right now (no need to track) - One-off operation that will never recur - Issues with third-party tools (Serena, Playwright, Context7) — use `_discovery-logging` instead - Trivially simple things the user can just do

Log BEFORE completing your task when you: - Find a bug you cannot fix in current scope - Encounter missing MCP tool functionality (fell back to SSH/bash) - Discover a quality issue or technical debt worth tracking - Notice a feature request surfaced during work - Find a pipeline/engine issue in Syncrovanis - Detect a missing or broken tool in an MCP server

When you discover a bug, quality issue, missing functionality, or performance problem during your work — and it is NOT something you can fix right now — log it as a GAP.

1. Resolve the project root (the current working directory) and run: ```bash .claude/switch-mcp.sh lighthouse ``` If `.claude/switch-mcp.sh` does not exist in the current project, check `/var/www/reportmaker/.claude/switch-mcp.sh` as fallback. 2. Inform the user that Lighthouse will be enabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

1. Note in response 2. Proceed with manual exploration 3. Consider creating handoff: `coordination/experts/handoffs/HANDOFF-{domain}-{date}-{agent}.md`

Each expert file contains: - Quick reference (key files, classes, methods) - Database schema - Known gotchas and bugs - Integration points - Data flow diagrams

All in: `coordination/experts/{domain}/` Current domains: - `security-audit-system` — security scanning, audit rules - `findings-templates` — template system, findings management - `findings-blocks-seo-migration` — block-based findings, SEO - `web-discovery-verification` — website discovery, verification - `page-crawler-system` — Puppeteer, web scraping - `analysis-execution-infrastructure` — analysis runners, queues - `backend-refactoring-patterns` — service patterns, DI -...

```bash # List all available expert domains ./coordination/scripts/discover-experts.sh --list # Match by agent type ./coordination/scripts/discover-experts.sh --agent {your-agent-type} ```

```bash ./coordination/scripts/discover-experts.sh --for-task "your task description" ``` Read ALL matched expert files BEFORE starting work. Token savings: 80-90% vs manual exploration.

```bash # Free-text search (ALL workspaces with Laravel): php artisan kb:query "TOPIC" --limit=5 # Structured lookup (specific file/domain/masterplan): php artisan kb:context domain:customer-management --limit=5 php artisan kb:context file:app/Services/Example.php --limit=5 # Non-Laravel workspaces (magitek-ops, dam): vendor/bin/kb query "TOPIC" --limit=5 --project-root=$(pwd) ``` KB returns relevant excerpts AND points to which expert files are most relevant. **If KB returns useful results...

- KB gives **direction**, not complete solutions - Always read the actual files for full context - If KB returns 0 results → proceed without it (do not block on this) - Max 5 results — more wastes tokens without benefit - Skip KB if task is purely administrative (git commits, file moves, etc.)

Extract 1-3 keywords from the task that represent the domain: - "Fix the analysis queue job" → topic: `analysis queue` - "Update Proxmox backup policy" → topic: `proxmox backup` - "Add CSV export for customers" → topic: `customers export` - "Debug NPM proxy issue" → topic: `npm proxy` **Keep topics short and specific** — 2-3 words max.