locus-consolidate

Locus Consolidate

Merges accumulated session logs into canonical room files, enforces size limits, and archives processed logs. Run per room — if multiple rooms need consolidation, run this skill once per room.

Arguments: $ARGUMENTS — room path relative to palace root (e.g. projects/my-project). If omitted, detect rooms needing consolidation automatically (Step 1b).

---

Step 1 — Identify the target room

1a — Argument provided: Navigate to <palace-root>/$ARGUMENTS. Verify the directory exists and contains a room main file and a sessions/ subdirectory.

1b — No argument (auto-detect): Read INDEX.md to get all room paths. For each room, check:

• Does sessions/ contain more than 5 files not in sessions/archived/?
• Does the room main file exceed 150 lines?

Process rooms that meet either condition, one at a time. Report which rooms were found and ask for confirmation before proceeding if running interactively.

---

Step 2 — Read the room state

Read in this order:

1. Room main file (<room>/<room-name>.md or README.md)
2. All unprocessed session logs: files in <room>/sessions/ that are not in <room>/sessions/archived/

Read session logs oldest-first (alphabetical by filename = chronological).

Do not read specialty files unless a Consolidation Note explicitly references them.

---

Step 3 — Extract consolidation candidates

For each session log, collect entries from the ### Consolidation Notes section. Discard sessions with empty or blank Consolidation Notes.

Build a working list:

[ { source: "sessions/2026-02-01.md", note: "promote X to Overview section" },
  { source: "sessions/2026-02-15.md", note: "update Y in technical-gotchas.md" },
  ... ]

Resolve conflicts: if two notes contradict each other, the newer one wins. Flag irreconcilable conflicts for user review rather than silently choosing.

---

Step 4 — Merge into canonical files

For each consolidation candidate:

1. Identify the target canonical file (room main file or a specialty file).
2. Read the target file if not already loaded.
3. Apply the change:
   • New fact → add to the appropriate section
   • Updated fact → edit the existing entry in place; remove the old version
   • Superseded entry → delete the outdated content entirely
4. Do not append alongside old content — canonical files must stay authoritative.