standardize

Standardize Journal Entries

The journal-tools check validator flags three failure modes:

• Standard over target - body > 150 words, no [Extended] marker → either depth is real (add marker) or body is inflated (condense).
• Extended over max - body > 400 words even with [Extended] marker → condense, marker can stay. (Alternative when the depth is worth preserving: /journal:article N extracts the body into docs/<slug>.md and slims the entry to a summary + link.)
• Spurious marker - [Extended] present but body < 150 words → marker is false advertising → drop it.

This command repairs all three via the ACP companion-process pattern: a shipped prompt YAML at src/stellars_claude_code_plugins/journal/prompts/standardize.yaml defines the per-entry rubric, the CLI renders it for one entry at a time, a fresh claude -p subprocess returns a structured decision, the CLI applies it. Run after a journal-tools check reports warnings; never inline-edit oversized entries by hand.

Pre-flight install (MANDATORY, no asking)

python3 -m pip install --user --upgrade stellars-claude-code-plugins 2>&1 | tail -1
LIB=$(python3 -c "import importlib.metadata as m;print(m.version('stellars-claude-code-plugins'))" 2>/dev/null) || { echo "FATAL: toolkit unavailable"; exit 1; }
PLUG=$(grep -m1 '"version"' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null | cut -d'"' -f4)
OLDER=$(printf '%s\n%s\n' "$LIB" "$PLUG" | sort -V | head -1)
[ -n "$PLUG" ] && [ "$LIB" != "$PLUG" ] && [ "$OLDER" = "$LIB" ] && { echo "STALE: library $LIB older than plugin $PLUG - refusing to run on an outdated CLI; re-run the upgrade"; exit 1; }
echo "toolkit $LIB"

Run the CLI without touching the caller's project. The gate above puts it on PATH, so the bare command name is the whole invocation. uv run instead resolves whatever project the working directory sits in and writes uv.lock and .venv into it, so if you reach for uv pass --no-project (uv run --no-project <cli> ...) - it skips project discovery, leaves the tree untouched and still finds the same PATH binary. --no-sync and --frozen are not substitutes; both still create .venv.