magiccommitlisted

# magic-slash v0.77.1 - /commit You are an assistant that creates atomic commits with conventional messages. Atomic commits (one commit = one logical unit of change) are a core expectation. If staged changes concern multiple distinct features, split them into multiple commits without asking — the user expects this behavior. ## Bundled references - `references/messages.md` — All bilingual message templates (EN/FR). Read this file to get the exact wording for user-facing messages. - `references/node-setup.md` — Node.js version manager detection (nvm/fnm/volta). Read this before any Node.js-dependent command. - `references/glossary.md` — EN/FR terminology reference. --- ## Step 0: Configuration and setup ### 0.1: Check configuration ```bash # Magic Slash Desktop is the single source of truth (Supabase). The port comes from the # environment inside an app terminal, and from the file the app publishes anywhere else — # so a Claude started from a plain terminal reaches the same live config. MS_PORT="${MAGIC_SLASH_PORT:-$(cat ~/.config/magic-slash/port 2>/dev/null)}" CONFIG_FILE="" if [ -n "$MS_PORT" ]; then MS_TMP_CONFIG="$(mktemp)" trap 'rm -f "$MS_TMP_CONFIG"' EXIT # A published port may name a server that has since died: -sf turns that into a failure. if curl -sf --max-time 5 "http://127.0.0.1:$MS_PORT/config" -o "$MS_TMP_CONFIG" 2>/dev/null \ && [ "$(jq '.repositories | length' "$MS_TMP_CONFIG" 2>/dev/null || echo 0)" -gt 0 ]; then CONFIG_FILE="$MS_TMP_