@cryptiklemur/lattice 1.46.7 → 2.0.0

package/.serena/memories/project_overview.md

@@ -1,51 +0,0 @@
-# Lattice — Project Overview
-
-**Purpose**: Multi-machine agentic dashboard for Claude Code. Web UI for monitoring sessions, managing projects, tracking costs, and orchestrating across mesh-networked nodes.
-
-**Status**: Alpha (pre-1.0), work directly on main branch.
-
-## Tech Stack
-
-- **Runtime**: Bun (server), Node (CI), Vite (client bundler)
-- **Server**: Bun WebSocket server with typed message protocol
-- **Client**: React 19 + Vite 8 + Tailwind CSS + daisyUI
-- **Shared**: TypeScript types and constants (no build step, imported directly)
-- **State**: Tanstack Store (client), Tanstack Router (routing)
-- **Sessions**: Claude Agent SDK (`@anthropic-ai/claude-agent-sdk`)
-- **Charts**: Recharts
-- **Testing**: Playwright (chromium only)
-- **CI**: GitHub Actions (typecheck + build + Playwright)
-- **Release**: semantic-release on push to main
-
-## Monorepo Structure
-
-```
-lattice/
-├── shared/     — TypeScript types, message definitions, constants
-├── server/     — Bun WebSocket server, handlers, analytics, mesh networking
-├── client/     — React + Vite dashboard, UI components, 23 themes
-├── themes/     — Base16 theme JSON files (dark + light)
-├── tests/      — Playwright test files
-└── docs/       — Screenshots, audit docs
-```
-
-## Architecture
-
-- Server communicates with clients via WebSocket using typed messages defined in `shared/`
-- Sessions managed through Claude Agent SDK
-- 23 base16 themes with OKLCH color space
-- PWA with service worker caching (Workbox)
-- Mesh networking for multi-machine orchestration
-- Structured logging with `debug` package (lattice:* namespaces)
-
-## Key Features
-
-- Real-time chat with tool approval, context tracking, cost per message
-- Session tabs with split-pane support
-- Message bookmarks (per-session + global)
-- Analytics dashboard (15+ chart types)
-- Daily cost budget with configurable enforcement
-- Keyboard shortcuts overlay (press ?)
-- Session hover previews, auto-titling, date range search
-- MCP server management, skill marketplace
-- Memory management UI

package/.serena/memories/suggested_commands.md

@@ -1,32 +0,0 @@
-# Suggested Commands
-
-## Development
-- `bun run dev` — Start server (--watch) + Vite dev server, hot reloads both
-- `bun run build` — Build all workspaces (only client produces output)
-- `bun run typecheck` — Run tsc across all workspaces
-
-## Testing
-- `bunx playwright test` — Run all Playwright tests (server must be running on :7654)
-- `bunx playwright test tests/session-flow.spec.ts` — Run single test file
-
-## Type Checking (per-workspace, as CI does it)
-- `bunx tsc -p shared/tsconfig.json` — Build shared types (must run first)
-- `bunx tsc --noEmit -p server/tsconfig.json` — Typecheck server
-- `bunx tsc --noEmit -p client/tsconfig.json` — Typecheck client
-
-## Client Build
-- `cd client && npx vite build` — Build client for production
-
-## Server
-- `bun run server/src/index.ts daemon` — Run server daemon directly
-- `bun run server/src/index.ts daemon --port 8080` — Custom port
-- Default port: 7654, binds to 0.0.0.0
-
-## Environment
-- `ANTHROPIC_API_KEY` — Optional, uses `claude setup-token` if not set
-- `DEBUG=lattice:*` — Enable structured debug logging
-
-## Git
-- Commit messages: Angular Commit Convention (feat/fix/refactor/etc)
-- Releases: automated via semantic-release on push to main
-- Never add AI attribution to commits

package/.serena/memories/task_completion_checklist.md

@@ -1,15 +0,0 @@
-# Task Completion Checklist
-
-When a coding task is completed, verify the following:
-
-1. **Type check** — Run `bunx tsc --noEmit -p client/tsconfig.json` and `bunx tsc --noEmit -p server/tsconfig.json` (build shared first with `bunx tsc -p shared/tsconfig.json`)
-2. **Build** — Run `cd client && npx vite build` to verify client builds
-3. **Server build** — Run `bun build server/src/index.ts --target=bun --outdir=/tmp/check` to verify server bundles
-4. **No pre-existing errors** — Fix any errors you encounter, don't leave them
-5. **Code style** — const/let (not var), named functions (not arrows except callbacks), lucide-react icons only
-6. **Git** — Only commit when explicitly asked. Angular Commit Convention. No AI attribution.
-
-## Important Notes
-- The PWA service worker caches old bundles. After rebuilding client, users need to clear SW cache in browser to see changes.
-- Server serves from `client/dist/` (built output), NOT from Vite dev server. Client changes require `npx vite build` to appear on port 7654.
-- Vite dev server runs on :5173 separately but can't connect WebSocket without the Bun server on :7654.

package/.serena/project.yml

@@ -1,152 +0,0 @@
-# the name by which the project can be referenced within Serena
-project_name: "lattice"
-
-
-# list of languages for which language servers are started; choose from:
-#   al                  bash                clojure             cpp                 csharp
-#   csharp_omnisharp    dart                elixir              elm                 erlang
-#   fortran             fsharp              go                  groovy              haskell
-#   java                julia               kotlin              lua                 markdown
-#   matlab              nix                 pascal              perl                php
-#   php_phpactor        powershell          python              python_jedi         r
-#   rego                ruby                ruby_solargraph     rust                scala
-#   swift               terraform           toml                typescript          typescript_vts
-#   vue                 yaml                zig
-#   (This list may be outdated. For the current list, see values of Language enum here:
-#   https://github.com/oraios/serena/blob/main/src/solidlsp/ls_config.py
-#   For some languages, there are alternative language servers, e.g. csharp_omnisharp, ruby_solargraph.)
-# Note:
-#   - For C, use cpp
-#   - For JavaScript, use typescript
-#   - For Free Pascal/Lazarus, use pascal
-# Special requirements:
-#   Some languages require additional setup/installations.
-#   See here for details: https://oraios.github.io/serena/01-about/020_programming-languages.html#language-servers
-# When using multiple languages, the first language server that supports a given file will be used for that file.
-# The first language is the default language and the respective language server will be used as a fallback.
-# Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored.
-languages:
-- typescript
-
-# the encoding used by text files in the project
-# For a list of possible encodings, see https://docs.python.org/3.11/library/codecs.html#standard-encodings
-encoding: "utf-8"
-
-# line ending convention to use when writing source files.
-# Possible values: unset (use global setting), "lf", "crlf", or "native" (platform default)
-# This does not affect Serena's own files (e.g. memories and configuration files), which always use native line endings.
-line_ending:
-
-# The language backend to use for this project.
-# If not set, the global setting from serena_config.yml is used.
-# Valid values: LSP, JetBrains
-# Note: the backend is fixed at startup. If a project with a different backend
-# is activated post-init, an error will be returned.
-language_backend:
-
-# whether to use project's .gitignore files to ignore files
-ignore_all_files_in_gitignore: true
-
-# list of additional paths to ignore in this project.
-# Same syntax as gitignore, so you can use * and **.
-# Note: global ignored_paths from serena_config.yml are also applied additively.
-ignored_paths: []
-
-# whether the project is in read-only mode
-# If set to true, all editing tools will be disabled and attempts to use them will result in an error
-# Added on 2025-04-18
-read_only: false
-
-# list of tool names to exclude.
-# This extends the existing exclusions (e.g. from the global configuration)
-#
-# Below is the complete list of tools for convenience.
-# To make sure you have the latest list of tools, and to view their descriptions, 
-# execute `uv run scripts/print_tool_overview.py`.
-#
-#  * `activate_project`: Activates a project by name.
-#  * `check_onboarding_performed`: Checks whether project onboarding was already performed.
-#  * `create_text_file`: Creates/overwrites a file in the project directory.
-#  * `delete_lines`: Deletes a range of lines within a file.
-#  * `delete_memory`: Deletes a memory from Serena's project-specific memory store.
-#  * `execute_shell_command`: Executes a shell command.
-#  * `find_referencing_code_snippets`: Finds code snippets in which the symbol at the given location is referenced.
-#  * `find_referencing_symbols`: Finds symbols that reference the symbol at the given location (optionally filtered by type).
-#  * `find_symbol`: Performs a global (or local) search for symbols with/containing a given name/substring (optionally filtered by type).
-#  * `get_current_config`: Prints the current configuration of the agent, including the active and available projects, tools, contexts, and modes.
-#  * `get_symbols_overview`: Gets an overview of the top-level symbols defined in a given file.
-#  * `initial_instructions`: Gets the initial instructions for the current project.
-#     Should only be used in settings where the system prompt cannot be set,
-#     e.g. in clients you have no control over, like Claude Desktop.
-#  * `insert_after_symbol`: Inserts content after the end of the definition of a given symbol.
-#  * `insert_at_line`: Inserts content at a given line in a file.
-#  * `insert_before_symbol`: Inserts content before the beginning of the definition of a given symbol.
-#  * `list_dir`: Lists files and directories in the given directory (optionally with recursion).
-#  * `list_memories`: Lists memories in Serena's project-specific memory store.
-#  * `onboarding`: Performs onboarding (identifying the project structure and essential tasks, e.g. for testing or building).
-#  * `prepare_for_new_conversation`: Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
-#  * `read_file`: Reads a file within the project directory.
-#  * `read_memory`: Reads the memory with the given name from Serena's project-specific memory store.
-#  * `remove_project`: Removes a project from the Serena configuration.
-#  * `replace_lines`: Replaces a range of lines within a file with new content.
-#  * `replace_symbol_body`: Replaces the full definition of a symbol.
-#  * `restart_language_server`: Restarts the language server, may be necessary when edits not through Serena happen.
-#  * `search_for_pattern`: Performs a search for a pattern in the project.
-#  * `summarize_changes`: Provides instructions for summarizing the changes made to the codebase.
-#  * `switch_modes`: Activates modes by providing a list of their names
-#  * `think_about_collected_information`: Thinking tool for pondering the completeness of collected information.
-#  * `think_about_task_adherence`: Thinking tool for determining whether the agent is still on track with the current task.
-#  * `think_about_whether_you_are_done`: Thinking tool for determining whether the task is truly completed.
-#  * `write_memory`: Writes a named memory (for future reference) to Serena's project-specific memory store.
-excluded_tools: []
-
-# list of tools to include that would otherwise be disabled (particularly optional tools that are disabled by default).
-# This extends the existing inclusions (e.g. from the global configuration).
-included_optional_tools: []
-
-# fixed set of tools to use as the base tool set (if non-empty), replacing Serena's default set of tools.
-# This cannot be combined with non-empty excluded_tools or included_optional_tools.
-fixed_tools: []
-
-# list of mode names to that are always to be included in the set of active modes
-# The full set of modes to be activated is base_modes + default_modes.
-# If the setting is undefined, the base_modes from the global configuration (serena_config.yml) apply.
-# Otherwise, this setting overrides the global configuration.
-# Set this to [] to disable base modes for this project.
-# Set this to a list of mode names to always include the respective modes for this project.
-base_modes:
-
-# list of mode names that are to be activated by default.
-# The full set of modes to be activated is base_modes + default_modes.
-# If the setting is undefined, the default_modes from the global configuration (serena_config.yml) apply.
-# Otherwise, this overrides the setting from the global configuration (serena_config.yml).
-# This setting can, in turn, be overridden by CLI parameters (--mode).
-default_modes:
-
-# initial prompt for the project. It will always be given to the LLM upon activating the project
-# (contrary to the memories, which are loaded on demand).
-initial_prompt: ""
-
-# time budget (seconds) per tool call for the retrieval of additional symbol information
-# such as docstrings or parameter information.
-# This overrides the corresponding setting in the global configuration; see the documentation there.
-# If null or missing, use the setting from the global configuration.
-symbol_info_budget:
-
-# list of regex patterns which, when matched, mark a memory entry as read‑only.
-# Extends the list from the global configuration, merging the two lists.
-read_only_memory_patterns: []
-
-# list of regex patterns for memories to completely ignore.
-# Matching memories will not appear in list_memories or activate_project output
-# and cannot be accessed via read_memory or write_memory.
-# To access ignored memory files, use the read_file tool on the raw file path.
-# Extends the list from the global configuration, merging the two lists.
-# Example: ["_archive/.*", "_episodes/.*"]
-ignored_memory_patterns: []
-
-# advanced configuration option allowing to configure language server-specific options.
-# Maps the language key to the options.
-# Have a look at the docstring of the constructors of the LS implementations within solidlsp (e.g., for C# or PHP) to see which options are available.
-# No documentation on options means no options are available.
-ls_specific_settings: {}

package/CLAUDE.md

@@ -1,71 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code when working with code in this repository.
-
-## Project Structure
-Bun monorepo with three workspaces:
-- `shared/` — TypeScript types and constants (no build, imported directly)
-- `server/` — Bun daemon serving WebSocket API + static client assets on port 7654
-- `client/` — React 19 + Vite + Tailwind + daisyUI web app
-
-## Commands
-- `bun run dev` — starts server (--watch) + Vite dev server, hot reloads both
-- `bun run build` — builds all workspaces (only client produces output)
-- `bun run typecheck` — runs tsc across all workspaces
-- `bunx playwright test` — runs Playwright tests (server must be running on :7654)
-- Single test: `bunx playwright test tests/session-flow.spec.ts`
-
-## Coding Standards
-- Use `const`/`let` (not `var`). Use named function declarations, not arrow functions — except for anonymous callbacks where arrows are fine.
-- No emojis for icons or in UI. Use `lucide-react` for all icons.
-- No section separator comments or organizational comments.
-- Follow .editorconfig (2-space indent, LF, UTF-8).
-- Server: ESM with Bun. Client: ESM with Vite + React.
-
-## Git
-- Never add "Co-Authored-By" lines mentioning Claude/AI.
-- Commit messages follow Angular Commit Convention (feat/fix/refactor/etc).
-- Only commit when explicitly asked.
-- Releases are automated via semantic-release on push to main.
-
-## Design
-See `.impeccable.md` for comprehensive design guidelines. Key constraints:
-- Dark-first with 23 base16 themes via OKLCH CSS variables
-- Tailwind + daisyUI component framework
-- Typography: JetBrains Mono (headings/code), IBM Plex Sans (body)
-- Three surface tiers: Chrome (base-200), Stage (base-100 + dot-grid), Elevated (base-300 + shadow)
-- Never hardcode colors — always use CSS variables/theme tokens
-- WCAG AA contrast, prefers-reduced-motion, keyboard-first
-
-## Pre-existing Errors
-DO NOT EVER LEAVE PRE-EXISTING ERRORS. FIX THEM.
-
-## Environment
-- ANTHROPIC_API_KEY is optional — server uses the token from `claude setup-token` if not set.
-- Server binds to 0.0.0.0:7654 in production, 0.0.0.0:17654 in dev (WSL2 compatible).
-- Client dev server runs on :5173 and proxies to :17654. Production serves from server via client/dist/.
-- `LATTICE_HOME` — override data directory (default: `~/.lattice`).
-- `LATTICE_PORT` — override server port (default: 7654). Also: `--port=N`.
-
-## Testing
-- Playwright tests live in `tests/` at the project root.
-- Tests require the server running on localhost:7654.
-- Screenshots on failure go to `test-results/`.
-- Use Playwright MCP for visual verification. Save screenshots to `.playwright-mcp/`.
-
-### Testing Mesh/Node Functionality
-Run a second Lattice instance with a separate data directory and port:
-```bash
-LATTICE_HOME=/tmp/lattice-test-node LATTICE_PORT=7655 bun server/src/index.ts daemon
-```
-Then pair the two instances via the UI or WebSocket:
-```bash
-# Generate invite on :7654, then pair from :7655:
-bun -e "
-var ws = new WebSocket('ws://localhost:7655/ws');
-ws.onopen = function() { ws.send(JSON.stringify({ type: 'mesh:pair', code: 'LTCE-XXXX-...' })); };
-ws.onmessage = function(e) { console.log(JSON.parse(e.data).type); };
-"
-```
-The test instance serves from `client/dist/` (run `bun run build` first for UI access on :7655).
-Clean up: `rm -rf /tmp/lattice-test-node`

package/CONTRIBUTING.md

@@ -1,93 +0,0 @@
-# Contributing to Lattice
-
-Thanks for your interest in contributing to Lattice! This document covers the basics you need to get started.
-
-## Development Setup
-
-### Prerequisites
-
-- [Bun](https://bun.sh/) v1.1+
-- Node.js 20+ (for some tooling)
-- Git
-
-### Getting Started
-
-```bash
-git clone https://github.com/cryptiklemur/lattice.git
-cd lattice
-bun install
-bun run dev
-```
-
-The dev server starts on `http://localhost:7654` with hot reload for both server and client.
-
-### Project Structure
-
-```
-lattice/
-  shared/    # Shared TypeScript types and message definitions
-  server/    # Bun server — WebSocket handlers, session management, mesh networking
-  client/    # React + Vite client — dashboard, settings, chat UI
-```
-
-## Development Workflow
-
-### Coding Standards
-
-- Use `var` instead of `const`/`let`
-- No arrow functions — use `function` keyword
-- Use `lucide-react` for all icons
-- Follow `.editorconfig` (2-space indent, LF line endings, UTF-8)
-- One class per file
-
-### Commit Messages
-
-We follow [Angular Commit Message Conventions](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format):
-
-```
-<type>(<scope>): <short summary>
-```
-
-**Types:** `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `chore`, `ci`
-
-**Scopes:** `client`, `server`, `shared`, or omit for cross-cutting changes
-
-**Examples:**
-```
-feat(client): add skill marketplace search
-fix(server): use correct node identity for project list
-refactor(shared): extract MCP form components
-```
-
-### Building
-
-```bash
-bun run build        # Build all packages
-bun run typecheck    # Type-check without emitting
-```
-
-### Testing Changes
-
-1. Run the dev server: `bun run dev`
-2. Open `http://localhost:7654` in your browser
-3. Verify your changes work visually
-
-## Pull Requests
-
-1. Fork the repo and create a branch from `main`
-2. Make your changes following the coding standards above
-3. Ensure the project builds without errors: `bun run build`
-4. Write a clear PR description explaining what changed and why
-5. Submit your PR
-
-## Reporting Issues
-
-Use [GitHub Issues](https://github.com/cryptiklemur/lattice/issues) to report bugs or suggest features. Include:
-
-- Steps to reproduce (for bugs)
-- Expected vs actual behavior
-- Your environment (OS, Bun version, browser)
-
-## License
-
-By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).