Fix table, simpler properties, add devdrive

Author: joepio

.claude/settings.local.json

@@ -16,7 +16,13 @@
       "Bash(adb devices)",
       "Bash(echo $PATH)",
       "Bash(cargo build:*)",
-      "Bash(cargo test:*)"
+      "Bash(cargo test:*)",
+      "Bash(for f:*)",
+      "Bash(do echo:*)",
+      "Read(//Users/joep/dev/github/atomicdata-dev/atomic-server/**)",
+      "Bash(done)",
+      "Bash(npx tsc:*)",
+      "mcp__charlotte__charlotte_screenshot"
     ]
   }
 }

AGENTS.md

@@ -2,89 +2,32 @@
 
 Guidance for coding agents working in this repo.
 
-## Read First
+## Local Setup
 
-Before assuming the browser or local dev setup is broken, check:
+- `http://localhost:5173` — Vite dev server (frontend).
+- `http://localhost:9883` — local Atomic Server.
 
-- [`README.md`](/Users/joep/dev/github/atomicdata-dev/atomic-server/README.md)
-- [`CONTRIBUTING.md`](/Users/joep/dev/github/atomicdata-dev/atomic-server/CONTRIBUTING.md)
-- [`browser/CONTRIBUTING.md`](/Users/joep/dev/github/atomicdata-dev/atomic-server/browser/CONTRIBUTING.md)
-- [`browser/e2e/tests/e2e.spec.ts`](/Users/joep/dev/github/atomicdata-dev/atomic-server/browser/e2e/tests/e2e.spec.ts)
-- [`browser/e2e/tests/test-utils.ts`](/Users/joep/dev/github/atomicdata-dev/atomic-server/browser/e2e/tests/test-utils.ts)
+The frontend auto-updates via HMR. If changes don't appear, reload the page. If you edit `@tomic/lib` or `@tomic/react`, those packages may need a rebuild first.
 
-The Playwright E2E helpers are the best source of truth for expected local browser flows.
+## Quick Dev Setup
 
-## Local Browser Mental Model
+Navigate to `http://localhost:5173/app/dev-drive` to instantly create a fresh agent + drive on `localhost:9883` and switch to it. Only works in dev mode.
 
-- `http://localhost:5173` is the frontend app origin.
-- `http://localhost:9883` is the local Atomic Server origin.
-- The frontend on `5173` should auto-update during normal local development.
-- If you patch browser code and do not see the change, reload the page first.
-- If the UI still looks stale, check whether the changed package needs a rebuild.
+In E2E tests, use `devDrive(page)` from `test-utils.ts`:
 
-From [`browser/CONTRIBUTING.md`](/Users/joep/dev/github/atomicdata-dev/atomic-server/browser/CONTRIBUTING.md):
-
-- Vite provides HMR for the data browser.
-- If you edit `@tomic/lib` or `@tomic/react`, the browser may still depend on built `.js` output, so those packages may need rebuilding or watch mode.
+```ts
+await devDrive(page); // goes to /app/dev-drive and waits for the drive to be ready
+```
 
 ## Charlotte / Browser Automation
 
-When using Charlotte or any browser automation:
-
-- Keep the main automation anchored in the frontend app at `5173`.
-- Do not treat direct navigation to `9883` as equivalent to the app state on `5173`.
-- Use the top-left `Open Drive Settings` control as the main entry point for drive/server changes.
-
-If the app is pointed at `5173` as its active drive/server, the UI can look broken:
-
-- opening `http://localhost:5173/` as a resource returns `404`
-- websocket attempts go to `ws://localhost:5173/ws` and fail
-- you may see `Unauthorized`, `Resource not found`, or `Something went wrong`
-
-This usually means the drive/server configuration is wrong, not that the app is dead.
-
-## Known Good UI Flow
-
-### Sign in or create a local identity
-
-1. Open `Login / New User`.
-2. Click `Create new identity`.
-3. Copy the generated secret.
-4. Click `Yes, I've stored it safely`.
-
-After that, the sidebar entry becomes `User Settings`.
-
-Known oddity:
-
-- During identity creation you may see an error like `Could not fetch url 'did:ad:agent:...', must start with http.`
-- Treat that as noise unless it blocks the flow.
-
-### Switch to the local server
-
-1. Click `Open Drive Settings`.
-2. Go to the drive configuration UI.
-3. Set the custom drive URL to `http://localhost:9883`.
-4. Save it.
-
-See the `changeDrive()` helper in [`browser/e2e/tests/test-utils.ts`](/Users/joep/dev/github/atomicdata-dev/atomic-server/browser/e2e/tests/test-utils.ts).
-
-### Create a fresh drive
-
-Once an agent exists:
-
-1. Click `Open Drive Settings`.
-2. Click `New Drive`.
-3. Fill `Name` and `Subdomain`.
-4. Click `Create`.
-5. Wait for the app to navigate to a `did:ad:` subject.
-6. Confirm the sidebar drive title updates.
-
-See the `newDrive()` helper in [`browser/e2e/tests/test-utils.ts`](/Users/joep/dev/github/atomicdata-dev/atomic-server/browser/e2e/tests/test-utils.ts).
+- Always operate the app at `localhost:5173`, not `9883` directly.
+- Start every session by navigating to `http://localhost:5173/app/dev-drive` to get a clean, authenticated state.
+- If the app shows `Unauthorized` or `Something went wrong`, navigate to `/app/dev-drive` to fix it.
 
-## Practical Debugging Checklist
+## Debugging Checklist
 
 - Is the frontend open on `5173`?
-- Is the active drive/server actually `9883`?
+- Is the active drive/server `9883`?
 - Is there a signed-in agent?
-- If browser flows need isolation, create a fresh drive first.
-- For browser behavior, compare against the E2E helpers before inventing a new interaction path.
+- Run `devDrive(page)` to reset to a clean state.

browser/data-browser/src/bootstrap.ts

@@ -1,6 +1,10 @@
 import { JSONADParser, type Store } from '@tomic/react';
 import baseModels from '../../../lib/defaults/default_base_models.json';
 import defaultStore from '../../../lib/defaults/default_store.json';
+import tableDefaults from '../../../lib/defaults/table.json';
+import chatroomDefaults from '../../../lib/defaults/chatroom.json';
+import ontologiesDefaults from '../../../lib/defaults/ontologies.json';
+import aiDefaults from '../../../lib/defaults/ai.json';
 
 /**
  * Injects base models and default store resources into the store.
@@ -25,6 +29,10 @@ export function bootstrap(store: Store): void {
   try {
     const baseCount = addBootstrapped(baseModels);
     const storeCount = addBootstrapped(defaultStore);
+    addBootstrapped(tableDefaults);
+    addBootstrapped(chatroomDefaults);
+    addBootstrapped(ontologiesDefaults);
+    addBootstrapped(aiDefaults);
 
   } catch (e) {
     console.error('Failed to bootstrap store:', e);