@rubytech/taskmaster 1.0.38 → 1.0.40

package/dist/memory/manager.js

@@ -1,4 +1,5 @@
 import { randomUUID } from "node:crypto";
+import fsSync from "node:fs";
 import fs from "node:fs/promises";
 import path from "node:path";
 import chokidar from "chokidar";
@@ -323,7 +324,25 @@ export class MemoryIndexManager {
             maxEntries: params.settings.cache.maxEntries,
         };
         this.fts = { enabled: params.settings.query.hybrid.enabled, available: false };
-        this.ensureSchema();
+        try {
+            this.ensureSchema();
+        }
+        catch (err) {
+            // Database is corrupted (e.g. orphaned FTS5 metadata blocking writes).
+            // Delete and rebuild from scratch.
+            const msg = err instanceof Error ? err.message : String(err);
+            log.warn(`schema init failed, rebuilding database: ${msg}`);
+            try {
+                this.db.close();
+            }
+            catch {
+                /* ignore */
+            }
+            const dbPath = resolveUserPath(this.settings.store.path);
+            this.removeIndexFilesSync(dbPath);
+            this.db = this.openDatabase();
+            this.ensureSchema();
+        }
         this.vector = {
             enabled: params.settings.store.vector.enabled,
             available: null,
@@ -848,6 +867,17 @@ export class MemoryIndexManager {
         const suffixes = ["", "-wal", "-shm"];
         await Promise.all(suffixes.map((suffix) => fs.rm(`${basePath}${suffix}`, { force: true })));
     }
+    removeIndexFilesSync(basePath) {
+        const suffixes = ["", "-wal", "-shm"];
+        for (const suffix of suffixes) {
+            try {
+                fsSync.rmSync(`${basePath}${suffix}`, { force: true });
+            }
+            catch {
+                /* ignore */
+            }
+        }
+    }
     ensureSchema() {
         const result = ensureMemoryIndexSchema({
             db: this.db,
@@ -1337,8 +1367,12 @@ export class MemoryIndexManager {
             const shouldSyncMemory = this.sources.has("memory") && (params?.force || needsFullReindex || this.dirty);
             const shouldSyncSessions = this.shouldSyncSessions(params, needsFullReindex);
             if (shouldSyncMemory) {
-                await this.syncMemoryFiles({ needsFullReindex, progress: progress ?? undefined });
-                this.dirty = false;
+                try {
+                    await this.syncMemoryFiles({ needsFullReindex, progress: progress ?? undefined });
+                }
+                finally {
+                    this.dirty = false;
+                }
             }
             if (shouldSyncSessions) {
                 await this.syncSessionFiles({ needsFullReindex, progress: progress ?? undefined });

package/dist/memory/memory-schema.js

@@ -64,6 +64,9 @@ export function ensureMemoryIndexSchema(params) {
             // Leaving them in the DB can cause "no such module: fts5" errors on
             // unrelated operations if SQLite touches the virtual table machinery.
             dropOrphanedFtsTables(params.db, params.ftsTable);
+            // Verify the database is still writable after cleanup. FTS5 virtual table
+            // metadata left in sqlite_master can corrupt the database for all writes.
+            verifyWritable(params.db);
         }
     }
     ensureColumn(params.db, "files", "source", "TEXT NOT NULL DEFAULT 'memory'");
@@ -72,6 +75,21 @@ export function ensureMemoryIndexSchema(params) {
     params.db.exec(`CREATE INDEX IF NOT EXISTS idx_chunks_source ON chunks(source);`);
     return { ftsAvailable, ...(ftsError ? { ftsError } : {}) };
 }
+/**
+ * Verify the database is writable by performing a test write.
+ * If FTS5 cleanup left orphaned virtual table metadata in sqlite_master,
+ * SQLite may refuse all writes. Throws so the caller can delete and rebuild.
+ */
+function verifyWritable(db) {
+    try {
+        db.prepare(`INSERT INTO meta (key, value) VALUES ('_write_check', '1') ON CONFLICT(key) DO UPDATE SET value = '1'`).run();
+        db.prepare(`DELETE FROM meta WHERE key = '_write_check'`).run();
+    }
+    catch (err) {
+        const msg = err instanceof Error ? err.message : String(err);
+        throw new Error(`database not writable after FTS cleanup (needs rebuild): ${msg}`);
+    }
+}
 /**
  * When fts5 module is unavailable but the virtual table and its shadow tables
  * exist from a previous run, drop them to prevent "no such module" errors.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/taskmaster",
-  "version": "1.0.38",
+  "version": "1.0.40",
   "description": "AI-powered business assistant for small businesses",
   "publishConfig": {
     "access": "public"

package/taskmaster-docs/USER-GUIDE.md

@@ -495,6 +495,18 @@ When you add or change a file, your assistant picks it up automatically — no r
 
 When your assistant writes to **public/** or **shared/**, a shield icon appears in the navigation bar so you can review what was written (see [Data Safety Alert](#data-safety-alert) above).
 
+### Searching Memory
+
+The Files page includes a **memory search bar** that lets you test what your assistant finds when it searches its knowledge base.
+
+1. Type a query in the **Search memory** box and press Enter (or click **Search**)
+2. Results show the file path, relevance score (as a percentage), matching line numbers, and a snippet of the matched text
+3. Click any result to open the file preview
+4. Use the **agent selector** dropdown next to the search bar to switch between agents (e.g., public vs admin) — this lets you verify what each assistant can see
+5. Click **Clear** to return to the normal file tree view
+
+This is useful for diagnosing search issues — if your assistant can't find something in conversation, test the same query here to see what comes back. All results are shown regardless of score threshold, so you can see everything the search engine found.
+
 ---
 
 ## Status Dashboard
@@ -952,19 +964,50 @@ Only the business owner can change the activation mode.
 
 ## Updating Taskmaster
 
-When a new version of Taskmaster is available, the **Software** row on the Status Dashboard turns yellow and shows the new version number (e.g., "v1.2.3 → v1.3.0").
+### Checking for Updates
+
+Taskmaster checks for updates automatically when you open the Setup page. The **Software** row in the Status Dashboard shows your current version and whether an update is available:
 
-To update:
+- **Green** — You're running the latest version
+- **Yellow** — An update is available (shows the new version number, e.g., "v1.0.38 → v1.0.39")
+- **Grey** — Not yet checked
+
+If the row shows "Unknown", tap the **refresh** button (circular arrow) to check manually. Tap the **(i)** button to see version details (current version, latest version, and status).
+
+### Installing an Update
 
 1. Open the **Setup** page
-2. Look for the **Software** row in the dashboard
-3. If an update is available, tap the **download** button (down-arrow icon)
-4. Wait for the update to complete — the page will reload automatically
-5. After reload, the Software row should show "Up to date" in green
+2. Look for the **Software** row — if it's yellow, an update is available
+3. Tap the **download** button (down-arrow icon)
+4. A progress overlay appears showing each step of the update (fetching, building, running checks, etc.)
+5. When the update completes, the gateway restarts automatically
+6. The page reconnects on its own — you'll see a result banner showing the version change (e.g., "Updated: v1.0.38 → v1.0.39")
+7. The Software row should now show green
+
+You don't need to refresh the page — the overlay stays visible during the update and the page reconnects automatically after the gateway restarts.
+
+### Alternative: Re-run the Installer
+
+You can also update by re-running the install command in Terminal:
+
+```bash
+curl -fsSL https://taskmaster.bot/install.sh | bash
+```
+
+This detects your existing installation and upgrades it in place.
+
+### If an Update Fails
+
+If something goes wrong during the update:
+
+- The progress overlay shows which step failed (marked with an X)
+- A result banner appears with the failure reason
+- Your previous version remains running — a failed update does not leave your system broken
+- Tap **Dismiss** to close the result banner
 
-If the Software row shows "Unknown", tap the **refresh** button (circular arrow) to check for updates. Tap the **(i)** button to see version details.
+If the page loses connection during the update and doesn't reconnect within two minutes, refresh the page manually. If the gateway doesn't come back, try power-cycling your device (unplug and replug).
 
-> **Note:** Updates require an internet connection. The update process takes about 30 seconds. Your assistant will be briefly unavailable during the restart.
+> **Note:** Updates require an internet connection. The update process typically takes 30–60 seconds. Your assistant will be briefly unavailable during the restart.
 
 ---