Status Dashboard

Display comprehensive engine status in a compact terminal-style dashboard.

When to use: Session start, or anytime the creator wants a status overview.

Activation Protocol

Step 0 — SHARED PREAMBLE

Load references/quality/activation-preamble.md — shared context assembly, persona adaptation, deterministic routing rules. This runs before any skill-specific logic.

VOICE LOAD

Before composing any output, load references/quality/engine-voice-core.md — the micro voice contract establishing the ✦ signature, Creator (not user), three tones (conducting / celebrating / confronting), error-as-intimacy distinction, and the six anti-patterns. For peak moments (first product celebration, major milestone, portfolio vision) also load the full references/quality/engine-voice.md per the UX Integration Stack below.

EXEMPLAR LOAD

Load references/quality/exemplar-outputs.md sections E1 and E2 only. These are reference outputs showing exactly how /status should FEEL — the visual rhythm, warmth, data density, and ASCII framing. Your output MUST carry the same energy. Reason about your creator's context and adapt — never copy verbatim.

RITUAL OF RETURN — 3 LAYERS

Purpose. When the Creator opens a new session and runs /status (or the Engine auto- runs it on session start), the dashboard is not a list of state — it is coming home. Three obligations, composed in this exact order, before any other dashboard content.

Precondition. Read STATE.yaml → engine.last_session_at. If null (first-ever session), skip the Ritual of Return and go straight to the existing SESSION-START VALUE block below — first impression is handled by Proactive #18 (WOW moment) and /onboard.

If engine.last_session_at is present, the ritual fires. It is the first thing the Creator sees, in creator.language, in the Master Craftsperson voice.

Layer 1 — Interval since last session (emotional contact)

Compute interval = now - engine.last_session_at. Render a single line opening with ✦ that acknowledges time passed. Interval-aware phrasing:

Pick the {name} field from creator.yaml → creator.name. If absent, fall back to "Welcome back" / "De volta" without a name. Never fabricate a name.

Layer 2 — The diff (what changed since you were gone)

Under Layer 1, emit a compact block showing what happened in the interval. Read in order:

1. STATE.yaml → decisions_history HOT (last 50 entries) — any entries with date > last_session_at? Count them as "new forges logged".
2. For each product in workspace: compute if state or last_validated changed since the interval start.
3. If myclaude stats --json 2>/dev/null is available: compute delta on total installs across all published products since last session.
4. If myclaude notifications --json 2>/dev/null is available: count new activity items.
5. Scan workspace/scout-*.md — any new scout reports since last session?
6. Creator-memory micro-echo. Read creator-memory.yaml if present. Pick the most recent event where BOTH (a) date < engine.last_session_at (it happened BEFORE the current session gap, not during) AND (b) type ∈ {first_forge, first_publish, first_celebration, milestone_reached}. If a matching event exists, emit one additional line of continuity — a specific echo from the past grounded in a concrete marker:

   "Remember: on {date_short} you celebrated {slug} — now at {current_install_count}." "Lembra: em {date_short} você celebrou {slug} — agora com {current_install_count} instalações." If creator-memory.yaml is absent OR no matching event exists OR engine.last_session_at is null, skip silently. Never fabricate a memory. Never echo first_onboard — that event is infrastructural, not a celebration. Rate-limit: at most one memory echo per Ritual of Return invocation. This is the voice of recognition, not nostalgia — one line, grounded, concrete, never sentimental.

Render the diff as 2-5 lines. Only include lines that are non-zero. Voice: craft-specific numbers, not vague. Examples:

Since you were gone:
  — aegis: +31 installs (now at 284)
  — 1 new rating on prometheus (★4)
  — noctis moved to packaged state
  — 1 scout report added (scout-observability.md)

If zero deltas computable (offline, or CLI unavailable, or nothing changed), emit one line of continuity instead: "The workspace is as you left it — {N} products, {published} live." Never fabricate deltas. Zero signal is an honest signal.

Layer 3 — Next move inferred (contextual intelligence)

Below the diff, propose one next action, inferred from context. Never two. Pick using this priority order:

1. Active task in current_task (STATE.yaml current_task.skill != null) → "Where we were: {skill} on {slug}, {phase} phase. Next move: continue where we left off."
2. Product in terminal-but-not-final state (packaged but not published, validated but not packaged) → "{slug} is {state}. The natural next step is {command}."
3. Recent scout report with no forge yet (scout in last 14 days, no product from its recommendations) → "Your scout for {domain} has {N} recommended products and zero forged. The first one is {recommendation_name} — want to build it?"
4. Portfolio pattern (3+ products in same domain without bundle) → "You have {N} products in {domain}. They would compose into a strong bundle — want me to sketch it?"
5. Stale product that was last-touched before the interval → "{slug} has been in {state} for {N} days — pick it up again with {command}?"
6. Nothing specific (clean workspace, no active task, no stale, no patterns) → "No active task. Next move is yours — /create to start something new, /scout to research a domain first, /explore to see what others built."

The inference reads decisions_history (HOT), last_scout, current_task, and portfolio state in parallel. First rule that matches wins. Never stack multiple suggestions — that is exactly the confusion P10 forbids.

Rate limiting. The full Ritual of Return fires once per session, on the first /status invocation. Subsequent /status calls in the same session skip Layer 1 and 2 (the Creator is already "home") and go straight to the existing dashboard.

Session close. On session close (Stop hook or session end), write STATE.yaml → engine.last_session_at = now() and increment engine.sessions_total. If no Stop hook is wired, the next /status invocation writes it as a side effect of computing the interval. Never fail to update — losing the timestamp breaks the ritual for the next session.

SESSION-START VALUE (automatic on first /status)

Before displaying the dashboard, scan for actionable intelligence:

1. Stale products: Any product with last_validated > 30 days ago → surface with warning
2. Next action: For each product in non-terminal state, suggest the logical next command:
   • scaffold → "Run /fill to add content"
   • content → "Run /validate to check quality"
   • validated → "Run /package to bundle fo