multi-project-context-bridgelisted

# Multi-Project Context Bridge The operator runs 7 projects in parallel. Each session is loaded in one project's context window only — that is the discipline from `workflows/parallel-projects.md` Habit 3 (no two projects deploy in the same session). The unintended cost is a "where was I on project A?" tax when the operator references a decision from another project mid-session. graphify closes the gap by treating the entire `~/Brain/` corpus as a single knowledge graph: project notes, decisions, daily logs, and code all become nodes, and the bridge is a graph traversal — but only if the bridge is honest. Found references cross over, real names and URLs do not. This skill is the bridge. ## When to Use - The operator is in project A's directory and references a concept from project B ("what did we decide about Stripe Connect on the marketplace?", "the equivalent for the legal tool was…"). - The operator says "bridge context from <project>" or "pull decisions from <project>" while working in a different project's session. - The operator is at the start of a session after switching focus between the 2-of-N picks from the Monday review and wants the prior project's last decisions surfaced as background. - The operator is writing a case study or post-mortem and wants the cross-project decisions made over the last quarter, anonymised, as raw material. - ECC has `context-budget` (token budgeting) and `strategic-compact` (compaction). Both operate **inside** one session; this skill