[bd-kzw] Centralize SQLite storage to ~/.agent-relay + add session/summary tracking

[khaliqgant]

• Move SQLite storage from /tmp to ~/.agent-relay (fixes data loss on reboot)
• Support XDG_DATA_HOME and AGENT_RELAY_DATA_DIR env overrides
• Add sessions table to track agent connection history
• Add agent_summaries table for running agent context
• Record session start/end in daemon on connect/disconnect
• Add [[SUMMARY]] block parsing in wrapper for agent summaries
• Update dashboard API to include sessions and summaries data
• Dashboard now shows recent sessions and agent summaries

Closes: agent-relay-kzw (SQLite in /tmp cleared on reboot)

[Copilot]

Pull request overview

This PR centralizes SQLite storage from /tmp to ~/.agent-relay to prevent data loss on system reboots, while adding session and summary tracking capabilities for agent connections.

Key Changes:

• Relocated SQLite storage with XDG_DATA_HOME and AGENT_RELAY_DATA_DIR environment variable support
• Introduced sessions and agent_summaries tables for tracking agent connection history and context
• Added [[SUMMARY]] and [[SESSION_END]] block parsing for agents to maintain running context

Reviewed changes

Copilot reviewed 11 out of 12 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/utils/project-namespace.ts	Implements getBaseDir() to support environment-based storage directory configuration
src/storage/adapter.ts	Defines StoredSession, SessionQuery, and AgentSummary interfaces for new tracking features
src/storage/sqlite-adapter.ts	Adds sessions and agent_summaries tables with CRUD operations
src/storage/sqlite-adapter.test.ts	Provides comprehensive test coverage for session management and agent summary features
src/wrapper/parser.ts	Implements parseSummaryFromOutput() and parseSessionEndFromOutput() functions
src/wrapper/parser.test.ts	Tests for the new summary and session-end parsing functions
src/wrapper/client.ts	Exposes currentSessionId getter for session tracking
src/wrapper/tmux-wrapper.ts	Integrates storage adapter, parses output blocks, and saves summaries/sessions
src/daemon/server.ts	Records session start/end events on agent connect/disconnect
src/dashboard/server.ts	Extends API to include sessions and summaries data with duration formatting
src/cli/index.ts	Removes unused DEFAULT_SOCKET_PATH import

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Storage initialization is asynchronous but not awaited. Methods like parseSummaryAndSave() (line 632) may attempt to use this.storage before initialization completes, leading to race conditions. Consider using a promise/flag pattern to ensure storage is ready before use, or await initialization in an async setup method.

[Copilot]

The sessionEndProcessed flag is never reset. If the wrapper instance is reused or lives across multiple sessions, this flag would prevent processing [[SESSION_END]] blocks in subsequent sessions. Consider resetting this flag when starting a new session or tying it to the session ID.

Suggested change

	/**
	/**
	* Reset per-session state, allowing this wrapper instance to process
	* [[SESSION_END]] blocks for a new logical session.
	*
	* Call this when starting a new session on a reused TmuxWrapper instance.
	*/
	public resetSessionState(): void {
	this.sessionEndProcessed = false;
	}
	/**

[Copilot]

The code logs "Cannot close session: no session ID" but doesn't set sessionEndProcessed = false to allow retry. If currentSessionId becomes available later, the session end will never be processed. Consider handling this case differently or resetting the flag.

[Copilot]

The COALESCE(?, summary) pattern means if a summary was set during startSession(), a null summary in endSession() won't clear it. This may be intentional, but could cause confusion if an explicit null is meant to clear the summary. Consider documenting this behavior or using a different pattern if clearing should be supported.

Suggested change

	// Note: The COALESCE(?, summary) pattern intentionally preserves any existing
	// session summary that was set earlier (for example, in startSession()) when
	// endSession() is called without a new summary. Because options?.summary is
	// coerced to null when undefined, passing no summary (or null) here will not
	// clear an existing summary; it will simply leave the current value unchanged.

[Copilot]

The comment "Active if no end time" describes the implementation but doesn't explain that this doesn't account for closedBy values. A session could have endedAt set but still be considered inactive if it hasn't been explicitly closed. Consider clarifying the semantics of "active" in relation to both fields.

Suggested change

	isActive: !s.endedAt, // Active if no end time
	isActive: !s.endedAt, // Considered "active" solely when there is no end time; closedBy is not taken into account here