feat: Projects — organize sessions and issues into logical groups

[OneStepAt4time]

Projects — Organize Work into Logical Groups

Why

Teams think in projects. Currently Aegis has a flat list of sessions. Projects let users group work logically, track progress per project, and organize agents by project scope.

Concept

• A Project groups sessions, issues, and agents under a named scope
• Projects have their own context, templates, and settings
• Sessions can be tagged with a project
• Dashboard shows per-project views

DB Schema

CREATE TABLE project (
  id TEXT PRIMARY KEY,
  workspace_id TEXT NOT NULL,
  name TEXT NOT NULL,
  description TEXT NOT NULL DEFAULT '',
  slug TEXT NOT NULL,
  status TEXT NOT NULL DEFAULT 'active' CHECK(status IN ('active', 'archived')),
  created_by TEXT NOT NULL,
  created_at TEXT NOT NULL DEFAULT (datetime('now')),
  updated_at TEXT NOT NULL DEFAULT (datetime('now')),
  UNIQUE(workspace_id, slug)
);

-- Link sessions to projects
ALTER TABLE sessions ADD COLUMN project_id TEXT REFERENCES project(id);

API Endpoints

• GET /v1/projects — list projects
• POST /v1/projects — create project
• GET /v1/projects/:id — get project with stats
• PUT /v1/projects/:id — update project
• DELETE /v1/projects/:id — archive project
• GET /v1/projects/:id/sessions — list sessions in project

Frontend

• Projects page: list with name, session count, agent count, last activity
• Project detail: sessions, agents, activity timeline
• Project picker in session creation

Acceptance Criteria

• CRUD API for projects
• Session-project linking
• Dashboard projects page
• Project filter in session list
• Tests
• npm run gate passes

Reference

Competitive analysis: references/multica-competitive-analysis.md §2.7

[OneStepAt4time]

Triage (Athena, May 24): Labeled phase-4. Platform feature — valid for enterprise teams but not our current target (solo dev, 1-100 CC agents). Remains deferred per May 16 strategic refocus until concrete demand surfaces.