scout-status

Scout Status Dashboard

You are displaying a status dashboard for the user's Scout installation. Follow each section below in order. Present the final output as a clean, readable dashboard — not as a series of intermediate steps.

---

Step 1: Locate the Scout Config

Check for scout-config.yaml in these locations, in order:

1. The current working directory (./scout-config.yaml)
2. ~/Scout/scout-config.yaml
3. ~/scout/scout-config.yaml

for f in "./scout-config.yaml" "$HOME/Scout/scout-config.yaml" "$HOME/scout/scout-config.yaml"; do
    if [ -f "$f" ]; then echo "FOUND:$f"; break; fi
done

If no config is found:

Tell the user:

No Scout installation found. Run `/scout-setup` to create one.

Stop here. Do not proceed with the dashboard.

If found: note the path as SCOUT_CONFIG and derive SCOUT_DIR as its parent directory. Read the config file, then continue.

---

Step 2: Parse the Config

From the YAML config, extract:

• instance_name → INSTANCE_NAME
• user.name → USER_NAME
• user.email → USER_EMAIL
• connectors block → CONNECTORS (the map of service → true/false)
• schedule.briefing → BRIEFING_TIME
• schedule.consolidation → CONSOLIDATION_TIMES
• schedule.dreaming → DREAMING_TIMES
• platform → PLATFORM
• scout_dir → SCOUT_DIR (use this if present; otherwise use the parent directory of the config file)

---

Step 3: Gather Data

Run all of the following data-gathering steps before composing the dashboard output.

3a. Last Runs (git log)

git -C "SCOUT_DIR" log --oneline -10

Collect the 10 most recent commit messages. Identify the most recent commit that mentions "briefing", "consolidation", "dreaming", "research", "work", and "meta-review" respectively (case-insensitive match on the commit message).

3b. KB Health

find "SCOUT_DIR/knowledge-base" -type f -name "*.md" | sort

For each file found, read it and look for a line matching either:

• **Last verified:**
• **Last updated:**