mosaicstack/stack
1
0
Fork 1
Code Issues 200 Pull Requests 10 Actions Packages Projects Releases 15 Wiki Activity

promote: /mosaic-promote slash command shipped in runtime/claude/commands/ but not seeded into the seat's CLAUDE_CONFIG_DIR/commands/ → 'Unknown command', UserPromptSubmit hook never fires (fomo-lin E2E, #1124 fix re-run) #1125

New Issue
Open
opened 2026-08-08 22:00:42 +00:00 by scooby · 0 comments
scooby commented 2026-08-08 22:00:42 +00:00
Collaborator
Copy Link
Copy Source

With #1124 fix (b) in place, mosaic promote now RESOLVES the seat correctly (BFS walk finds the claude child's MOSAIC_LEASE_SESSION_ID — confirmed working). The next link then failed: the injected /mosaic-promote returned ● Unknown command: /mosaic-promote in the seat, so the UserPromptSubmit ^/mosaic-promote$ hook (promote-begin) never fired → PROMOTION_TIMEOUT.

Root cause: the slash command IS shipped at ~/.config/mosaic/runtime/claude/commands/mosaic-promote.md, but the seat's home (CLAUDE_CONFIG_DIR=~/.config/mosaic/.claude) had no commands/ dir — the framework's settings-seeding step wires settings.json into the seat home but NOT the companion commands/ dir. Claude Code loads slash commands from $CLAUDE_CONFIG_DIR/commands/, so an unseeded seat rejects the trigger. Same asset-seeding gap class as F7/#1116 (MCP block dropped).

Worked around on fomo-lin by copying the command file into the seat's commands/ and relaunching — after which /mosaic-promote is recognized and the hook fires (see #1126 for what happens next).

Fix: seat-home composition (W-F1 / the gated-seat seeding path) must install commands/mosaic-promote.md alongside the gated settings.json. Ties into HARNESS-HOMES gap 7 (base must own all companion assets, not just settings). Filed by scooby (fomo-lin).

With #1124 fix (b) in place, `mosaic promote` now RESOLVES the seat correctly (BFS walk finds the claude child's MOSAIC_LEASE_SESSION_ID — confirmed working). The next link then failed: the injected `/mosaic-promote` returned `● Unknown command: /mosaic-promote` in the seat, so the `UserPromptSubmit ^/mosaic-promote$` hook (promote-begin) never fired → PROMOTION_TIMEOUT. **Root cause:** the slash command IS shipped at `~/.config/mosaic/runtime/claude/commands/mosaic-promote.md`, but the seat's home (`CLAUDE_CONFIG_DIR=~/.config/mosaic/.claude`) had no `commands/` dir — the framework's settings-seeding step wires settings.json into the seat home but NOT the companion `commands/` dir. Claude Code loads slash commands from `$CLAUDE_CONFIG_DIR/commands/`, so an unseeded seat rejects the trigger. Same asset-seeding gap class as F7/#1116 (MCP block dropped). **Worked around** on fomo-lin by copying the command file into the seat's `commands/` and relaunching — after which `/mosaic-promote` is recognized and the hook fires (see #1126 for what happens next). **Fix:** seat-home composition (W-F1 / the gated-seat seeding path) must install `commands/mosaic-promote.md` alongside the gated settings.json. Ties into HARNESS-HOMES gap 7 (base must own all companion assets, not just settings). Filed by scooby (fomo-lin).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
be-coder-05 be-coder-06 be-coder-07 be-coder-08 coder-mos1 coder-mos2 f10-coder jason.woltje (Jason Woltje) merge-gate mos-dt-0 pepper rev-974 (Rev-974 (Mosaic reviewer seat, web1)) rev-security-02 scooby (Scooby)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1125