braid-text 0.2.116 → 0.2.117

package/index.js

@@ -1144,7 +1144,7 @@ function create_braid_text() {
             if (braid_text.db_folder) {
                 await db_folder_init()
                 var pages = new Set()
-                for (let x of await require('fs').promises.readdir(braid_text.db_folder)) pages.add(decode_filename(x.replace(/\.\w+$/, '')))
+                for (let x of await require('fs').promises.readdir(braid_text.db_folder)) if (/\.\d+$/.test(x)) pages.add(decode_filename(x.replace(/\.\d+$/, '')))
                 return [...pages.keys()]
             } else return Object.keys(braid_text.cache)
         } catch (e) { return [] }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "braid-text",
-  "version": "0.2.116",
+  "version": "0.2.117",
   "description": "Library for collaborative text over http using braid.",
   "author": "Braid Working Group",
   "repository": "braid-org/braid-text",
@@ -13,7 +13,6 @@
     "simpleton-client.js",
     "web-utils.js",
     "README.md",
-    "AI-README.md",
     "editor.html",
     "markdown-editor.html",
     "server-demo.js"

package/AI-README.md

@@ -1,82 +0,0 @@
-# AI-README for braid-text
-
-This document provides AI assistants with key information about the braid-text project, including development procedures and architecture notes.
-
-## Release Procedure
-
-Follow these steps to create a new release:
-
-1. **Version Bump**
-   - Update the version in `package.json` (use smallest version bump: patch level)
-   - Current version format: `0.2.x`
-
-2. **Run Tests**
-   - Run `node test/test.js` - should show all 74 tests passing
-   - Run `node test/fuzz-test.js` - runs 10,000 iterations (takes ~5-10 minutes), should complete with `best_n = Infinity @ NaN` indicating success
-   - Both tests must pass before proceeding
-
-3. **Commit Changes**
-   - Use commit message format: `VERSION - description`
-   - Example: `0.2.73 - adds automatic test cleanup`
-   - Keep description concise and descriptive
-
-4. **Push to Remote**
-   - Run `git push` to push to the remote repository
-
-5. **Publish to npm**
-   - Run `npm publish` to publish the new version
-
-## Test Suite
-
-### test/test.js
-- Main test suite with 74 tests
-- Tests Braid protocol, version control, syncing, and collaboration features
-- Automatically cleans up `test_db_folder` after completion
-- Run with: `node test/test.js`
-- Filter tests with: `node test/test.js --filter="sync"`
-
-### test/fuzz-test.js
-- Fuzz testing suite that generates random edits and verifies correctness
-- Tests diamond-types integration and merge operations
-- Runs 10,000 iterations by default (takes approximately 5-10 minutes)
-- Success indicated by `best_n = Infinity @ NaN` at completion (no failures found)
-- Run with: `node test/fuzz-test.js`
-- Let it run to completion - do not interrupt
-
-## Project Structure
-
-- **index.js** - Main library file implementing Braid protocol for collaborative text
-- **package.json** - Package configuration and dependencies
-- **test/** - Test suite directory
-  - **test.js** - Main test runner (supports both console and browser modes)
-  - **tests.js** - Test definitions (shared between console and browser)
-  - **fuzz-test.js** - Fuzz testing suite
-  - **test.html** - Browser test interface
-
-## Key Dependencies
-
-- **@braid.org/diamond-types-node** - CRDT implementation for conflict-free text editing
-- **braid-http** - Braid protocol HTTP implementation
-- **url-file-db** - File-based database for persistent storage
-
-## Architecture Notes
-
-- Implements the Braid protocol for synchronizing collaborative text over HTTP
-- Uses diamond-types CRDT for conflict-free merging
-- Supports both simpleton and dt (diamond-types) merge strategies
-- Provides version control with parents tracking and version history
-- File-based persistence with case-insensitive filesystem support
-
-## Common Operations
-
-### Running Tests Locally
-```bash
-node test/test.js              # Run all tests
-node test/test.js --filter="sync"  # Run tests matching "sync"
-node test/fuzz-test.js         # Run fuzz tests
-```
-
-### Test Cleanup
-The test suite automatically cleans up temporary files and databases. If manual cleanup is needed:
-- Test database is created at `test/test_db_folder` during tests
-- Automatically removed after test completion