laminark 0.1.0 → 2.21.7

package/plugin/ui/timeline.js

@@ -98,7 +98,7 @@ async function loadTimelineData(range) {
   sessionsContainer.innerHTML = '';
 
   if (!data.sessions.length && !data.observations.length) {
-    showTimelineEmptyState(sessionsContainer);
+    showEmptyState(sessionsContainer);
     return;
   }
 
@@ -403,7 +403,7 @@ function createTopicShiftMarker(shift) {
  * Show the empty state message.
  * @param {HTMLElement} container
  */
-function showTimelineEmptyState(container) {
+function showEmptyState(container) {
   var msg = document.createElement('p');
   msg.className = 'empty-state';
   msg.textContent = 'No sessions recorded yet. Timeline will populate as you use Claude.';

package/plugin/CLAUDE.md

@@ -1,10 +0,0 @@
-# Memory & Context
-
-When you need to recall prior work, decisions, or context:
-- **First** query Laminark's memory tools (`recall`, `query_graph`, `query_branches`) before resorting to grep/glob searches
-- Use `recall` with keyword searches to find past observations, decisions, and findings
-- Use `query_graph` to find relationships between files, decisions, and problems
-- Use `query_branches` to see work history - what was investigated, fixed, built, and where it left off
-- Use `show_branch` to trace the full arc of a specific work unit (investigation -> diagnosis -> planning -> execution -> verification)
-- Use `save_memory` to persist important decisions, findings, and reference material
-- Only fall back to raw file searches (Grep, Glob) when Laminark has no relevant results

package/plugin/commands/recall.md

@@ -1,55 +0,0 @@
-# /laminark:recall
-
-Search Laminark memories by description or topic.
-
-## Usage
-
-/laminark:recall {description of what you're looking for}
-
-## Instructions
-
-When the user invokes this command:
-
-1. Take the text provided after the command as the search query
-2. Call the `search` MCP tool with:
-   - `query`: The user's search description
-   - `limit`: 10 (show top 10 results)
-3. Present the results to the user in a readable format:
-   - Show each result with its relevance score, a content snippet, the source, and when it was created
-   - Group results by relevance tier if helpful (highly relevant, somewhat relevant)
-   - If results include memories from different sessions, note which session they came from
-
-## Response Format
-
-Present results like this:
-
-**Memory Search: "{query}"**
-
-Found {N} relevant memories:
-
-1. **[{score}% match]** {content snippet, first 200 chars}
-   _{source} | {relative time}_
-
-2. **[{score}% match]** {content snippet}
-   _{source} | {relative time}_
-
-...
-
-_Use the search tool for more specific queries, or get_observations for full details on any memory._
-
-## Examples
-
-User: /laminark:recall authentication decisions
-Action: Call search with query="authentication decisions"
-Response: Show top results about auth-related memories with scores and snippets
-
-User: /laminark:recall what database did we choose
-Action: Call search with query="what database did we choose"
-Response: Show results mentioning database selection decisions
-
-## Notes
-
-- Results use hybrid search (keyword + semantic) for best matching
-- If no results are found, suggest the user try different search terms or check if they have saved any memories yet
-- If no query is provided after the command, ask the user what they'd like to search for
-- For detailed view of any result, Claude can use the get_observations MCP tool with the observation ID

package/plugin/commands/remember.md

@@ -1,34 +0,0 @@
-# /laminark:remember
-
-Save a memory to Laminark for future retrieval.
-
-## Usage
-
-/laminark:remember {text to remember}
-
-## Instructions
-
-When the user invokes this command:
-
-1. Take the text provided after the command as the memory content
-2. Call the `save_memory` MCP tool with:
-   - `content`: The user's text exactly as provided
-   - `source`: "slash:remember" (identifies this as an explicit user save)
-3. Confirm to the user that the memory has been saved
-4. Show a brief snippet of what was saved (first 100 characters)
-
-## Examples
-
-User: /laminark:remember The auth system uses JWT with 15-minute expiry and refresh tokens stored in httpOnly cookies
-Action: Call save_memory with content="The auth system uses JWT with 15-minute expiry and refresh tokens stored in httpOnly cookies" and source="slash:remember"
-Response: "Saved to memory: 'The auth system uses JWT with 15-minute expiry and refresh tokens stored in httpOnly cookies'"
-
-User: /laminark:remember We decided to use Postgres instead of MySQL for the new service because of JSONB support
-Action: Call save_memory with the full text
-Response: "Saved to memory: 'We decided to use Postgres instead of MySQL for the new serv...'"
-
-## Notes
-
-- Memories saved via /laminark:remember are high-priority in search results (source: "slash:remember")
-- These memories persist across sessions and are included in session context injection
-- If no text is provided after the command, ask the user what they'd like to remember

package/plugin/commands/resume.md

@@ -1,45 +0,0 @@
-# /laminark:resume
-
-Resume a previously stashed context thread, or list all available stashed threads.
-
-## Usage
-
-/laminark:resume
-/laminark:resume {stash-id}
-
-## Instructions
-
-When the user invokes this command:
-
-### List mode (no ID provided)
-
-1. Call the `topic_context` MCP tool with no arguments (or limit: 5)
-2. Present the stashed threads as a numbered list showing:
-   - Topic label
-   - How long ago it was stashed
-   - Brief summary (first 80 characters)
-3. Tell the user they can resume a specific thread by providing its ID
-
-### Resume mode (ID provided)
-
-1. Call the `topic_context` MCP tool to look up the stash
-2. Restore the context from the stash observations into the conversation
-3. Confirm to the user which thread was resumed and how many observations were restored
-4. Summarize the key context from the restored thread so the user can pick up where they left off
-
-## Examples
-
-User: /laminark:resume
-Action: Call topic_context to list stashed threads
-Response: Show numbered list of available threads with topic labels and timestamps
-
-User: /laminark:resume abc123def456
-Action: Resume the specific stash, inject its context
-Response: "Resumed: 'JWT authentication' -- Context restored with 5 observations. Here's where you left off: ..."
-
-## Notes
-
-- Only threads with status "stashed" are shown (already resumed threads are excluded)
-- Resuming a thread marks it as "resumed" so it no longer appears in the list
-- The restored context includes observation snapshots from the time of stashing
-- If no stashed threads exist, inform the user they are working in a single thread

package/plugin/commands/stash.md

@@ -1,34 +0,0 @@
-# /laminark:stash
-
-Manually stash the current session's context for later retrieval.
-
-## Usage
-
-/laminark:stash [optional label]
-
-## Instructions
-
-When the user invokes this command:
-
-1. Call the `save_memory` MCP tool to persist current observations, then call the stash handler to snapshot the current session
-2. If a label is provided after the command, use it as the stash topic label
-3. If no label is provided, one is generated automatically from the earliest observation
-4. Confirm to the user that their context was stashed
-5. Show the topic label and remind them about /laminark:resume
-
-## Examples
-
-User: /laminark:stash authentication implementation
-Action: Stash current session context with label "authentication implementation"
-Response: "Context stashed: 'authentication implementation'. Use /laminark:resume to return to it."
-
-User: /laminark:stash
-Action: Stash current session context with auto-generated label
-Response: "Context stashed: 'Initial project setup and configur...'. Use /laminark:resume to return to it."
-
-## Notes
-
-- Stashing preserves a snapshot of the current session's observations
-- The stash remains available across sessions until resumed or deleted
-- Use /laminark:resume to list available stashes or restore a specific one
-- Automatic stashing also occurs when topic shifts are detected during normal work

package/plugin/commands/status.md

@@ -1,33 +0,0 @@
-# /laminark:status
-
-Show Laminark system status: connection info, memory count, token estimates, and capabilities.
-
-## Usage
-
-/laminark:status
-
-## Instructions
-
-When the user invokes this command:
-
-1. Call the `status` MCP tool with no arguments
-2. Present the returned dashboard directly to the user
-
-The tool returns a formatted status report including:
-- **Connection**: project path, project hash, database path, uptime
-- **Capabilities**: vector search availability, embedding worker status
-- **Memories**: observation count, embedded count, session count, stashed threads
-- **Tokens**: estimated total tokens across all stored memories
-- **Knowledge Graph**: node and edge counts
-
-## Examples
-
-User: /laminark:status
-Action: Call the status MCP tool
-Response: Display the formatted status dashboard
-
-## Notes
-
-- This is a read-only diagnostic command with no side effects
-- Token estimates use the ~4 chars/token heuristic
-- Uptime reflects time since the MCP server process started

package/plugin/dist/observations-CorAAc1A.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"observations-CorAAc1A.d.mts","names":[],"sources":["../../src/shared/types.ts","../../src/storage/observations.ts"],"mappings":";;;;;;;;;;KA0DY,yBAAA;AAAA,KAEA,eAAA;AAAA,UAEK,WAAA;EACf,KAAA;EACA,EAAA;EACA,WAAA;EACA,OAAA;EACA,KAAA;EACA,MAAA;EACA,SAAA;EACA,IAAA,EAAM,eAAA;EACN,SAAA,EAAW,YAAA;EACX,cAAA;EACA,gBAAA;EACA,cAAA,EAAgB,yBAAA;EAChB,YAAA;EACA,SAAA;EACA,SAAA;EACA,SAAA;AAAA;;;;;cAWW,uBAAA,EAAuB,CAAA,CAAA,SAAA;;;;;;;;;;KAWxB,iBAAA,GAAoB,CAAA,CAAE,KAAA,QAAa,uBAAA;AAAA,UAM9B,OAAA;EACf,EAAA;EACA,WAAA;EACA,SAAA;EACA,OAAA;EACA,OAAA;AAAA;AAAA,UAOe,YAAA;EACf,WAAA,EAAa,WAAA;EACb,KAAA;EACA,SAAA;EACA,OAAA;AAAA;AAAA,UAOe,cAAA;EACf,MAAA;EACA,WAAA;AAAA;;;;;;AAzEF;;;;;AAEA;;cCrCa,qBAAA;EAAA,iBACM,EAAA;EAAA,iBACA,WAAA;EAAA,iBAGA,UAAA;EAAA,iBACA,WAAA;EAAA,iBACA,2BAAA;EAAA,iBACA,cAAA;EAAA,iBACA,WAAA;EAAA,iBACA,SAAA;cAEL,EAAA,EAAI,QAAA,CAAc,QAAA,EAAU,WAAA;EDuCC;;;;ECIzC,MAAA,CAAO,KAAA,EAAO,iBAAA,GAAoB,WAAA;EDXlC;;;;;;;EAAA,QC2DQ,SAAA;EDrDR;;;;;;EC+EA,OAAA,CAAQ,EAAA,WAAa,WAAA;ED1EZ;;AAWX;;EC4EE,IAAA,CAAK,OAAA;IACH,KAAA;IACA,MAAA;IACA,SAAA;IACA,KAAA;IACA,IAAA;IACA,mBAAA;EAAA,IACE,WAAA;;;;;;EA6CJ,MAAA,CACE,EAAA,UACA,OAAA,EAAS,OAAA,CACP,IAAA,CACE,WAAA,sEAIH,WAAA;;;;;;;EAuDH,UAAA,CAAW,EAAA;;;;;;;EAcX,OAAA,CAAQ,EAAA;ED7M0B;;;;ECuNlC,oBAAA,CACE,EAAA,UACA,cAAA,EAAgB,yBAAA;;;;;EAgBlB,gBAAA,CAAiB,KAAA,EAAO,iBAAA,EAAmB,cAAA,EAAgB,yBAAA,GAA4B,WAAA;;;;;EAWvF,gBAAA,CAAiB,KAAA,YAAqB,WAAA;;;;;SAe/B,mBAAA,CAAoB,EAAA,EAfsB,eAAA,CAeO,QAAA,EAAU,KAAA,YAAqB,WAAA;;;;;EAevF,WAAA,CAAY,UAAA,UAAoB,UAAA,YAAyB,WAAA;;;;EAsCzD,KAAA,CAAA;;;;;;;EAWA,uBAAA,CAAwB,EAAA,WAAa,WAAA;;;;;EA8BrC,oBAAA,CAAqB,OAAA;IACnB,KAAA;IACA,MAAA;EAAA,IACE,WAAA;;;;;EAuBJ,UAAA,CACE,KAAA,UACA,OAAA;IAAY,KAAA;IAAgB,aAAA;EAAA,IAC3B,WAAA;AAAA"}