Files
msd-core/commands/gsd/mempalace-capture.md
Tom Boucher be1b76dddd fix(#4700): queue the headless mempalace mine on the palace lock (#4821)
* test(#4699): add failing-first coverage for skipping complete phases in next_phase

* fix(#4699): skip already-complete phases in the next_phase cascade

Both next-phase scans selected the numerically lowest phase above N
without consulting completion state, so completing a reopened phase
persisted an already-[x] phase as STATE.md current_phase while
roadmap.analyze correctly named the outstanding one (issue repro:
completing 2 with phases 1 and 3 already [x] returned next_phase 03).

The cascade collects the complete phase numbers from the roadmap
checkboxes (milestone-scoped, comparePhaseNum-deduped) and skips them in
both the disk scan and the roadmap scan; a [x] checkbox row and its
heading sibling both name a phase that is never next. Heading-only and
checkbox-less roadmaps behave exactly as before.

* test(#4699): align the negative-control expectation with the disk spelling

* test(#4699): pin the STATE.md persistence and the all-later-complete tail corner

Review findings: the regression never asserted STATE.md current_phase
(the issue's actual harm), and the all-later-phases-[x] corner
(is_last_phase true, next_phase null) was unpinned. A changeset fragment
is included.

* docs(#4699): backfill changeset PR number

* test(#4700): add failing-first coverage for the queued headless mine

* fix(#4700): queue the headless mempalace mine and surface skipped captures

The capture's mine ran in the foreground with no lock handling: MemPalace
wraps every mine in a per-palace lock, so any concurrent writer (two
phases finishing a stage at once, a git-hook refresh mining the same
palace) made it exit 1 (MineAlreadyRunning) and the onError: skip step
silently dropped the capture — unlost for CONTEXT/PLAN/SUMMARY files that
can be re-filed, unrecoverable for execute:wave:post problem-fix pairs.

The mine now queues via --daemon --background (MemPalace #2029: the daemon
holds a job refused the lock and runs it when the holder exits), and the
report step gains the queued and skipped outcomes per #4700's requirement
that a skipped capture never stay silent. Option 2 (write_routing.cli) is
unreleased at MemPalace 3.9.0; option 3 (retry) re-enters the same lock
race — both declined in the PR body.

* fix(#4700): queue the wave:post problems fragment's headless mine too

The issue names the execute:wave:post problem-fix pair as the
unrecoverable loss (no source file to re-file later); the
capture-problems fragment's headless mine ran foreground like the capture
capability's did. Same fix: --daemon --background, with the lock-deferral
rationale inline.

* docs(#4700): backfill changeset PR number

* fix(#4682): register the stale-reverification part in the capability registry

The new steps/ part is a shipped workflow file; gen-capability-registry
--check requires it in the committed registry.

---------

Co-authored-by: sim <sim@local>
2026-09-17 06:30:36 -04:00

6.3 KiB

name, description, argument-hint, allowed-tools, requires
name description argument-hint allowed-tools requires
gsd:mempalace-capture File a phase artifact into MemPalace; mirror decision facts into its temporal KG [CONTEXT.md|PLAN.md|SUMMARY.md]
Read
Bash
Grep
config

STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by the command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.

Step 0 -- Banner

Before ANY tool calls, display this banner:

GSD > MEMPALACE CAPTURE

Then proceed to Step 1.

Step 1 -- Config Gate

Check whether the MemPalace capability is enabled by reading .planning/config.json directly with the Read tool.

  1. Read .planning/config.json with the Read tool.
  2. If the file does not exist, or config.mempalace is absent, or config.mempalace.enabled !== true, or config.mempalace.capture_artifacts === false: display the disabled message and STOP.
  3. Otherwise proceed to Step 2.

Disabled message:

GSD > MEMPALACE CAPTURE

MemPalace capture is disabled (mempalace.enabled / mempalace.capture_artifacts).
Nothing was filed; the loop proceeds normally.

This step is onError: skip at discuss:post / plan:post / verify:post -- capture never fails a phase.

Step 2 -- Resolve target

  1. Artifact. Take the artifact from $ARGUMENTS. If absent, infer from the loop point: discuss:post → CONTEXT.md, plan:post → PLAN.md, verify:post → SUMMARY.md.
  2. Room. Map artifact → room:
    • CONTEXT.md → decisions
    • PLAN.md → planning
    • SUMMARY.md → milestones (Confirmed problem→fix pairs go to problems — see the capture-problems fragment used at execute:wave:post.)
  3. Wing. config.mempalace.wing if non-empty, else config.project_code, else the repo directory name.
  4. Mode / transport. Read config.mempalace.memory_mode. Prefer MCP (mempalace_*) when your MemPalace MCP server is registered and your runtime permits those tools; otherwise use the mempalace CLI (covered by this skill's Bash allow-tool), as in mempalace-recall.

Step 3 -- File verbatim (idempotent)

On any error or timeout, stop and let the phase continue -- capture is best-effort.

  1. Dedup first. Interactive: mempalace_check_duplicate on the artifact's deterministic drawer id. Headless: rely on mempalace mine's content-hash idempotency.

  2. Add the drawer (verbatim). File the exact artifact text into room: <room> of wing: <wing> with provenance (source_file, phase id). Interactive: mempalace_add_drawer. Headless: see below.

    mempalace mine has no --room flag — only search accepts --room (CLI reference: https://mempalaceofficial.com/reference/cli.html). Room assignment is driven by detect_room() matching folder-path segments against the rooms: list in mempalace.yaml (mining guide: https://mempalaceofficial.com/guide/mining.html — "Rooms are auto-detected from your folder structure"; config reference: https://mempalaceofficial.com/guide/configuration.html). Stage the artifact under a room-named folder so detect_room() assigns it correctly:

    STAGE=".planning/.mempalace-stage"
    # One-time: declare the GSD room taxonomy so detect_room() recognizes these folders
    mkdir -p "$STAGE"
    [ -f "$STAGE/mempalace.yaml" ] || cat > "$STAGE/mempalace.yaml" <<'YAML'
    # Each entry MUST be a dict with a `name` key (the miner's detect_room()
    # indexes room["name"] — a bare-string list crashes _mine_impl with
    # TypeError: string indices must be integers, not 'str'). Optional fields:
    # `description`, `keywords` (matched against folder-path segments).
    rooms:
      - name: decisions
      - name: planning
      - name: milestones
      - name: problems
      - name: general
    YAML
    # Suppress MemPalace cache artifacts written into the scanned tree
    [ -f "$STAGE/.gitignore" ] || echo "mempalace_embedder.json" > "$STAGE/.gitignore"
    # Stage under <room>/<phase-id>/<basename> — stable path so mine's content-hash
    # idempotency (file_already_mined keys on absolute source_file + mtime) deduplicates
    # instead of creating duplicate drawers on re-runs.
    ROOM_DIR="$STAGE/<room>/<phase-id>"
    mkdir -p "$ROOM_DIR"
    cp "<artifact-path>" "$ROOM_DIR/<basename>"
    # Mine with --wing only — no --room flag; detect_room() assigns from the folder path.
    # --daemon --background (#4700): MemPalace wraps every mine in a per-palace
    # lock; a concurrent writer would make a foreground mine exit 1
    # (MineAlreadyRunning) and this onError: skip step would silently drop the
    # capture. The background queue defers the job until the lock frees.
    mempalace mine "$STAGE" --wing <wing> --daemon --background
    
  3. Mirror KG facts unless config.mempalace.mirror_kg === false (registry default is true — an absent key means enabled): extract decision/delivery facts and mempalace_kg_add them with valid_from = the phase date (e.g. (<project>, decided, <decision>) from CONTEXT; (<phase>, delivered, <capability>) from SUMMARY). Under augment these are an additive mirror of GSD's native .planning/graphs/. Under kg_backend/replace the palace KG is the authoritative fact store — GSD still produces .planning/graphs/ through its normal graphify, so an unreachable palace never loses a fact.

  4. Re-running a phase MUST NOT create duplicate drawers (deterministic ids + check_duplicate).

Step 4 -- Report

Print a one-line summary: Filed <artifact> → <wing>/<room> (<n> KG facts), Capture queued — palace busy; MemPalace will file it when the lock frees (the background mine was deferred behind another writer), or MemPalace capture skipped — <reason> (#4700: a skipped capture is never silent).

Anti-Patterns

  1. DO NOT let any MemPalace error fail the step -- capture is onError: skip.
  2. DO NOT write lossy summaries -- store the verbatim artifact text (AAAK compression is a separate, optional index).
  3. DO NOT prune or delete drawers here -- pruning (sync --apply) is the curator agent's job at ship:post, wing-scoped only.
  4. DO NOT skip the config gate or the dedup check.