activitylisted

# br8n — Activity The cross-repo lens. While `/br8n:pickup` replays one repo+branch, **activity** answers "what have I been doing, everywhere" — backed by a knowledge graph that accumulates automatically on every `br8n_capture`. Nothing to build; just query. The graph's ontology: **repo, branch, file, session, task** nodes, related by `on_repo`, `on_branch`, `in_repo`, `edited`, `viewed`, `pursued`. ## Step 1 — Query the graph Call `mcp__plugin_br8n_br8n__br8n_activity`: - A natural-language `query` seeds a **semantic subgraph** ("what touches the store layer", "the KG work"). Omit it for the whole (capped) graph. - Optional `repo` narrows to one repository. It returns `{nodes, edges, summary}` — `summary` is a ready-to-show natural-language rollup; `nodes`/`edges` are the graph slice for anything more detailed. ## Step 2 — Answer Lead with the `summary` (repos, tasks, files in view). Then, if the user wants specifics, read the `nodes`/`edges`: - **Tasks** (`type: task`) — the intents pursued, distilled from hypotheses. - **Sessions** (`type: session`) — individual captures; `properties` carry `captured_at`, `repo`, `branch`, `hypothesis`. - **Files** (`type: file`) — what was edited vs. viewed (the edge `relation`). - Follow `edited`/`pursued`/`on_repo` edges to connect a file or task back to the repos and sessions that touched it. ## When to reach elsewhere - Single repo+branch "where was I" → `/br8n:pickup` (richer card for the here-and-now). - A question