aether-colony 3.1.17 → 5.0.0

package/.claude/commands/ant/continue.md

@@ -14,18 +14,11 @@ Parse `$ARGUMENTS`:
 ### Step 0: Initialize Visual Mode (if enabled)
 
 If `visual_mode` is true:
-```bash
-# Generate session ID
-continue_id="continue-$(date +%s)"
-
-# Initialize swarm display
-bash .aether/aether-utils.sh swarm-display-init "$continue_id"
-bash .aether/aether-utils.sh swarm-display-update "Queen" "prime" "excavating" "Phase continuation" "Colony" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "fungus_garden" 0
-```
+Run using the Bash tool with description "Initializing continue display...": `continue_id="continue-$(date +%s)" && bash .aether/aether-utils.sh swarm-display-init "$continue_id" && bash .aether/aether-utils.sh swarm-display-update "Queen" "prime" "excavating" "Phase continuation" "Colony" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "fungus_garden" 0`
 
 ### Step 0.5: Version Check (Non-blocking)
 
-Run using the Bash tool: `bash .aether/aether-utils.sh version-check 2>/dev/null || true`
+Run using the Bash tool with description "Checking colony version...": `bash .aether/aether-utils.sh version-check-cached 2>/dev/null || true`
 
 If the command succeeds and the JSON result contains a non-empty string, display it as a one-line notice. Proceed regardless of outcome.
 
@@ -48,7 +41,7 @@ Extract: `goal`, `state`, `current_phase`, `plan.phases`, `errors`, `memory`, `e
 
 ### Step 1.5: Load State and Show Resumption Context
 
-Run using Bash tool: `bash .aether/aether-utils.sh load-state`
+Run using the Bash tool with description "Loading colony state...": `bash .aether/aether-utils.sh load-state`
 
 If successful and goal is not null:
 1. Extract current_phase from state
@@ -63,7 +56,7 @@ If .aether/HANDOFF.md exists (detected in load-state output):
 - Read .aether/HANDOFF.md for additional context
 - Remove .aether/HANDOFF.md after display (cleanup)
 
-Run: `bash .aether/aether-utils.sh unload-state` to release lock.
+Run using the Bash tool with description "Releasing colony lock...": `bash .aether/aether-utils.sh unload-state` to release lock.
 
 **Error handling:**
 - If E_FILE_NOT_FOUND: "No colony initialized. Run /ant:init first." and stop
@@ -89,7 +82,7 @@ If `state != "EXECUTING"`:
 
 **The Iron Law:** No phase advancement without fresh verification evidence.
 
-Before ANY phase can advance, execute the 6-phase verification loop. See `.aether/verification-loop.md` for full reference.
+Before ANY phase can advance, execute the 6-phase verification loop. See `.aether/docs/disciplines/verification-loop.md` for full reference.
 
 #### 1. Command Resolution (Priority Chain)
 
@@ -119,54 +112,39 @@ If no build system detected, skip build/test/type/lint checks but still verify s
 Execute all applicable phases and capture output:
 
 ```
-Phase {id} Verification Loop
-============================
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+👁️🐜 V E R I F I C A T I O N   L O O P
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Phase {id} — Checking colony work...
 ```
 
 **Phase 1: Build Check** (if command exists):
-```bash
-{build_command} 2>&1 | tail -30
-```
+Run using the Bash tool with description "Running build check...": `{build_command} 2>&1 | tail -30`
 Record: exit code, any errors. **STOP if fails.**
 
 **Phase 2: Type Check** (if command exists):
-```bash
-{type_command} 2>&1 | head -30
-```
+Run using the Bash tool with description "Running type check...": `{type_command} 2>&1 | head -30`
 Record: error count. Report all type errors.
 
 **Phase 3: Lint Check** (if command exists):
-```bash
-{lint_command} 2>&1 | head -30
-```
+Run using the Bash tool with description "Running lint check...": `{lint_command} 2>&1 | head -30`
 Record: warning count, error count.
 
 **Phase 4: Test Check** (if command exists):
-```bash
-{test_command} 2>&1 | tail -50
-```
+Run using the Bash tool with description "Running test suite...": `{test_command} 2>&1 | tail -50`
 Record: pass count, fail count, exit code. **STOP if fails.**
 
 **Coverage Check** (if coverage command exists):
-```bash
-{coverage_command}  # e.g., npm run test:coverage
-```
+Run using the Bash tool with description "Checking test coverage...": `{coverage_command}  # e.g., npm run test:coverage`
 Record: coverage percentage (target: 80%+ for new code)
 
 **Phase 5: Security Scan**:
-```bash
-# Check for exposed secrets
-grep -rn "sk-\|api_key\|password\s*=" --include="*.ts" --include="*.js" --include="*.py" src/ 2>/dev/null | head -10
-
-# Check for debug artifacts
-grep -rn "console\.log\|debugger" --include="*.ts" --include="*.tsx" --include="*.js" src/ 2>/dev/null | head -10
-```
+Run using the Bash tool with description "Scanning for exposed secrets...": `grep -rn "sk-\|api_key\|password\s*=" --include="*.ts" --include="*.js" --include="*.py" src/ 2>/dev/null | head -10`
+Run using the Bash tool with description "Scanning for debug artifacts...": `grep -rn "console\.log\|debugger" --include="*.ts" --include="*.tsx" --include="*.js" src/ 2>/dev/null | head -10`
 Record: potential secrets (critical), debug artifacts (warning).
 
 **Phase 6: Diff Review**:
-```bash
-git diff --stat
-```
+Run using the Bash tool with description "Reviewing file changes...": `git diff --stat`
 Review changed files for unintended modifications.
 
 **Success Criteria Check:**
@@ -178,23 +156,28 @@ For EACH criterion:
 
 Display:
 ```
-VERIFICATION LOOP REPORT
-========================
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+👁️🐜 V E R I F I C A T I O N   R E P O R T
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Phase 1: Build      [PASS/FAIL]
-Phase 2: Types      [PASS/FAIL] (X errors)
-Phase 3: Lint       [PASS/FAIL] (X warnings)
-Phase 4: Tests      [PASS/FAIL] (X/Y passed)
-         Coverage   {percent}% (target: 80%)
-Phase 5: Security   [PASS/FAIL] (X issues)
-Phase 6: Diff       [X files changed]
+🔨 Build        [PASS/FAIL/SKIP]
+🔍 Types        [PASS/FAIL/SKIP] (X errors)
+🧹 Lint         [PASS/FAIL/SKIP] (X warnings)
+🧪 Tests        [PASS/FAIL/SKIP] (X/Y passed)
+   Coverage     {percent}% (target: 80%)
+🔒 Security     [PASS/FAIL] (X issues)
+📋 Diff         [X files changed]
 
-Success Criteria:
+──────────────────────────────────────────────────
+🐜 Success Criteria
+──────────────────────────────────────────────────
   ✅ {criterion 1}: {specific evidence}
   ✅ {criterion 2}: {specific evidence}
   ❌ {criterion 3}: {what's missing}
 
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Overall: READY / NOT READY
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
 #### 3. Gate Decision
@@ -202,14 +185,16 @@ Overall: READY / NOT READY
 **If NOT READY (any of: build fails, tests fail, critical security issues, success criteria unmet):**
 
 ```
-⛔ VERIFICATION FAILED - PHASE BLOCKED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🐜 V E R I F I C A T I O N   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Phase {id} cannot advance until issues are resolved.
 
-Issues Found:
+🚨 Issues Found:
 {list each failure with specific evidence}
 
-Required Actions:
+🔧 Required Actions:
   1. Fix the issues listed above
   2. Run /ant:continue again to re-verify
 
@@ -226,12 +211,12 @@ Use AskUserQuestion to confirm they understand what needs to be fixed:
 **If READY (all checks pass with evidence):**
 
 ```
-✅ VERIFICATION PASSED
+✅🐜 VERIFICATION PASSED
 
 All checks completed with evidence:
 {list each check and its evidence}
 
-Proceeding to phase advancement.
+Proceeding to gate checks...
 ```
 
 Continue to Step 1.6.
@@ -242,29 +227,24 @@ Continue to Step 1.6.
 
 Read `.aether/data/spawn-tree.txt` to count spawns for this phase.
 
-```bash
-grep -c "spawned" .aether/data/spawn-tree.txt 2>/dev/null || echo "0"
-```
-
-Also check for Watcher spawns specifically:
-```bash
-grep -c "watcher" .aether/data/spawn-tree.txt 2>/dev/null || echo "0"
-```
+Run using the Bash tool with description "Verifying spawn requirements...": `spawn_count=$(grep -c "spawned" .aether/data/spawn-tree.txt 2>/dev/null || echo "0") && watcher_count=$(grep -c "watcher" .aether/data/spawn-tree.txt 2>/dev/null || echo "0") && echo "{\"spawn_count\": $spawn_count, \"watcher_count\": $watcher_count}"`
 
 **HARD REJECTION - If spawn_count == 0 and phase had 3+ tasks:**
 
 ```
-⛔ SPAWN GATE FAILED - PHASE BLOCKED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🐜 S P A W N   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 This phase had {task_count} tasks but spawn_count: 0
 The Prime Worker violated the spawn protocol.
 
-The colony metaphor requires actual parallelism:
+🐜 The colony requires actual parallelism:
   - Prime Worker MUST spawn specialists for non-trivial work
   - A single agent doing everything is NOT a colony
   - "Justifications" for not spawning are not accepted
 
-Required Actions:
+🔧 Required Actions:
   1. Run /ant:build {phase} again
   2. Prime Worker MUST spawn at least 1 specialist
   3. Re-run /ant:continue after spawns complete
@@ -282,17 +262,19 @@ bash .aether/aether-utils.sh error-flag-pattern "no-spawn-violation" "Prime Work
 **HARD REJECTION - If watcher_count == 0 (no testing separation):**
 
 ```
-⛔ WATCHER GATE FAILED - PHASE BLOCKED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔👁️🐜 W A T C H E R   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 No Watcher ant was spawned for testing/verification.
 Testing MUST be performed by a separate agent, not the builder.
 
-Why this matters:
+🐜 Why this matters:
   - Builders verify their own work = confirmation bias
   - Independent Watchers catch bugs builders miss
   - "Build passing" ≠ "App working"
 
-Required Actions:
+🔧 Required Actions:
   1. Run /ant:build {phase} again
   2. Prime Worker MUST spawn at least 1 Watcher
   3. Watcher must independently verify the work
@@ -305,12 +287,7 @@ The phase will NOT advance until a Watcher validates.
 **If spawn_count >= 1 AND watcher_count >= 1:**
 
 ```
-✅ SPAWN GATE PASSED
-
-Spawns: {spawn_count} workers
-Watchers: {watcher_count} (independent verification)
-
-Proceeding to runtime verification.
+✅🐜 SPAWN GATE PASSED — {spawn_count} workers | {watcher_count} watchers
 ```
 
 Continue to Step 1.7.
@@ -319,29 +296,25 @@ Continue to Step 1.7.
 
 Scan all modified/created files for known anti-patterns. This catches recurring bugs before they reach production.
 
-```bash
-bash .aether/aether-utils.sh check-antipattern "{file_path}"
-```
+For each file, run using the Bash tool with description "Scanning for anti-patterns...": `bash .aether/aether-utils.sh check-antipattern "{file_path}"`
 
 Run for each file in `files_created` and `files_modified` from Prime Worker output.
 
 **Anti-Pattern Report:**
 
 ```
-Anti-Pattern Scan
-=================
-Files scanned: {count}
+🔍🐜 Anti-Pattern Scan — {count} files scanned
 
 {if critical issues:}
-🛑 CRITICAL ISSUES (must fix):
+🛑 CRITICAL (must fix):
 {list each with file:line and description}
 
 {if warnings:}
-⚠️ WARNINGS (review recommended):
+⚠️ WARNINGS:
 {list each with file:line and description}
 
 {if clean:}
-✅ No anti-patterns detected
+✅🐜 No anti-patterns detected
 ```
 
 **CRITICAL issues block phase advancement:**
@@ -358,9 +331,9 @@ Files scanned: {count}
 If CRITICAL issues found, display:
 
 ```
-⛔ ANTI-PATTERN GATE FAILED
+⛔🐜 ANTI-PATTERN GATE FAILED
 
-Critical anti-patterns detected that must be fixed:
+Critical anti-patterns detected:
 {list issues with file paths}
 
 Run /ant:build {phase} again after fixing.
@@ -376,29 +349,25 @@ If no CRITICAL issues, continue to Step 1.8.
 
 If Prime Worker reported TDD metrics (tests_added, tests_total, coverage_percent), verify test files exist:
 
-```bash
-# Check for test files based on project type
-find . -name "*.test.*" -o -name "*_test.*" -o -name "*Tests.swift" -o -name "test_*.py" 2>/dev/null | head -10
-```
+Run using the Bash tool with description "Locating test files...": `find . -name "*.test.*" -o -name "*_test.*" -o -name "*Tests.swift" -o -name "test_*.py" 2>/dev/null | head -10`
 
 **If Prime Worker claimed tests_added > 0 but no test files found:**
 
 ```
-⛔ TDD GATE FAILED - FABRICATED METRICS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🧪🐜 T D D   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Prime Worker claimed:
   tests_added: {claimed_count}
   tests_total: {claimed_total}
-  coverage_percent: {claimed_coverage}%
+  coverage: {claimed_coverage}%
 
 But no test files were found in the codebase.
 
-This is a CRITICAL violation:
-  - TDD metrics were fabricated
-  - No actual tests were written
-  - "All passing: true" was a lie
+🚨 CRITICAL violation — fabricated TDD metrics.
 
-Required Actions:
+🔧 Required Actions:
   1. Run /ant:build {phase} again
   2. Actually write test files (not just claim them)
   3. Tests must exist and be runnable
@@ -424,10 +393,11 @@ Before advancing, the user must confirm the application actually runs.
 Use AskUserQuestion:
 
 ```
-Runtime Verification Required
-=============================
+──────────────────────────────────────────────────
+🐜 Runtime Verification Required
+──────────────────────────────────────────────────
 
-Build and compile checks passed, but we need to verify the app actually works.
+Build checks passed — but does the app actually work?
 
 Have you tested the application at runtime?
 ```
@@ -440,18 +410,13 @@ Options:
 
 **If "Yes, tested and working":**
 ```
-✅ RUNTIME VERIFICATION PASSED
-
-User confirmed application runs correctly.
-Proceeding to phase advancement.
+✅🐜 RUNTIME VERIFIED — User confirmed app works.
 ```
 Continue to Step 2.
 
 **If "Yes, tested but has issues":**
 ```
-⛔ RUNTIME GATE FAILED
-
-User reported runtime issues. The phase cannot advance with a broken app.
+⛔🐜 RUNTIME GATE FAILED — User reported issues.
 
 Please describe the issues so they can be addressed:
 ```
@@ -465,17 +430,12 @@ Do NOT proceed to Step 2.
 
 **If "No, haven't tested yet":**
 ```
-⏸️ RUNTIME VERIFICATION PENDING
+⏸️🐜 RUNTIME PENDING — Test the app, then run /ant:continue again.
 
-Please test the application and run /ant:continue again.
-
-Testing checklist:
   - [ ] App launches without crashing
   - [ ] Core features work as expected
   - [ ] UI responds to user interaction
   - [ ] No freezes or hangs
-
-Come back when you've tested.
 ```
 
 Do NOT proceed to Step 2.
@@ -498,33 +458,29 @@ Continue to Step 1.10.
 **The Iron Law:** No phase advancement with unresolved blockers.
 
 First, auto-resolve any flags eligible for resolution now that verification has passed:
-```bash
-bash .aether/aether-utils.sh flag-auto-resolve "build_pass"
-```
+Run using the Bash tool with description "Auto-resolving flags...": `bash .aether/aether-utils.sh flag-auto-resolve "build_pass"`
 
 Then check for remaining blocking flags:
-```bash
-bash .aether/aether-utils.sh flag-check-blockers {current_phase}
-```
+Run using the Bash tool with description "Checking for blockers...": `bash .aether/aether-utils.sh flag-check-blockers {current_phase}`
 
 Parse result for `blockers`, `issues`, and `notes` counts.
 
 **If blockers > 0:**
 
 ```
-⛔ FLAGS GATE FAILED - BLOCKERS ACTIVE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🚩🐜 F L A G S   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-{blockers} blocking flag(s) must be resolved before phase advancement.
+{blockers} blocker(s) must be resolved first.
 
-Active Blockers:
+🚩 Active Blockers:
 {list each blocker flag with ID, title, and description}
 
-Required Actions:
+🔧 Required Actions:
   1. Fix the issues described in each blocker
   2. Resolve flags: /ant:flags --resolve {flag_id} "resolution message"
   3. Run /ant:continue again after resolving all blockers
-
-The phase will NOT advance with active blockers.
 ```
 
 **CRITICAL:** Do NOT proceed to Step 2. Do NOT advance the phase.
@@ -532,15 +488,11 @@ The phase will NOT advance with active blockers.
 **If blockers == 0 but issues > 0:**
 
 ```
-⚠️ FLAGS GATE: ISSUES NOTED
+⚠️🐜 FLAGS: {issues} issue(s) noted (non-blocking)
 
-No blockers, but {issues} issue(s) are active.
-These don't block advancement but should be addressed.
-
-Active Issues:
 {list each issue flag}
 
-Use /ant:flags to review and acknowledge or resolve.
+Use /ant:flags to review.
 ```
 
 Continue to Step 2.
@@ -548,9 +500,7 @@ Continue to Step 2.
 **If all clear (no blockers or issues):**
 
 ```
-✅ FLAGS GATE PASSED
-
-No blocking flags. Proceeding to phase advancement.
+✅🐜 FLAGS GATE PASSED — No blockers.
 ```
 
 Continue to Step 2.
@@ -665,6 +615,66 @@ Update COLONY_STATE.json:
 
 Write COLONY_STATE.json.
 
+Validate the state file:
+Run using the Bash tool with description "Validating colony state...": `bash .aether/aether-utils.sh validate-state colony`
+
+### Step 2.1: Auto-Emit Phase Pheromones (SILENT)
+
+**This entire step produces NO user-visible output.** All pheromone operations run silently — learnings are deposited in the background. If any pheromone call fails, log the error and continue. Phase advancement must never fail due to pheromone errors.
+
+#### 2.1a: Auto-emit FEEDBACK pheromone for phase outcome
+
+After learning extraction completes in Step 2, auto-emit a FEEDBACK signal summarizing the phase:
+
+```bash
+# phase_id and phase_name come from Step 2 state update
+# Take the top 1-3 learnings by evidence strength from memory.phase_learnings
+# Compress into a single summary sentence
+
+# If learnings were extracted, build a brief summary from them (first 1-3 claims)
+# Otherwise use the minimal fallback
+phase_feedback="Phase $phase_id ($phase_name) completed. Key patterns: {brief summary of 1-3 learnings from Step 2}"
+# Fallback if no learnings: "Phase $phase_id ($phase_name) completed without notable patterns."
+
+bash .aether/aether-utils.sh pheromone-write FEEDBACK "$phase_feedback" \
+  --strength 0.6 \
+  --source "worker:continue" \
+  --reason "Auto-emitted on phase advance: captures what worked and what was learned" \
+  --ttl "phase_end" 2>/dev/null || true
+```
+
+The strength is 0.6 (auto-emitted = lower than user-emitted 0.7). Source is "worker:continue" to distinguish from user-emitted feedback. TTL is "phase_end" so the signal survives through the NEXT phase and expires when THAT phase advances.
+
+#### 2.1b: Auto-emit REDIRECT for recurring error patterns
+
+Check `errors.flagged_patterns[]` in COLONY_STATE.json for patterns that have appeared in 2+ phases:
+
+```bash
+flagged_patterns=$(jq -r '.errors.flagged_patterns[]? | select(.count >= 2) | .pattern' .aether/data/COLONY_STATE.json 2>/dev/null || true)
+```
+
+For each pattern returned by the above query, emit a REDIRECT signal:
+
+```bash
+bash .aether/aether-utils.sh pheromone-write REDIRECT "$pattern_text" \
+  --strength 0.7 \
+  --source "system" \
+  --reason "Auto-emitted: error pattern recurred across 2+ phases" \
+  --ttl "30d" 2>/dev/null || true
+```
+
+REDIRECT strength is 0.7 (higher than auto FEEDBACK 0.6 — anti-patterns produce stronger signals than successes). TTL is 30d (not phase_end) because recurring errors should persist across multiple phases.
+
+If `errors.flagged_patterns` doesn't exist or is empty, skip silently.
+
+#### 2.1c: Expire phase_end signals and archive to midden
+
+After auto-emission, expire all signals with `expires_at == "phase_end"`. The newly-emitted FEEDBACK from 2.1a will survive this call (it was just written and is active) — it will expire when the NEXT phase advances.
+
+Run using the Bash tool with description "Maintaining pheromone memory...": `bash .aether/aether-utils.sh pheromone-expire --phase-end-only 2>/dev/null && bash .aether/aether-utils.sh eternal-init 2>/dev/null`
+
+This is idempotent — runs every time continue fires but only creates the directory/file once.
+
 ### Step 2.2: Promote Validated Learnings to QUEEN.md
 
 After extracting learnings in Step 2, promote high-confidence validated learnings to QUEEN.md wisdom.
@@ -954,9 +964,9 @@ Runs ONLY when all phases complete.
 2. Display tech debt report:
 
 ```
-🐜 ═══════════════════════════════════════════════════
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    🎉 P R O J E C T   C O M P L E T E 🎉
-═══════════════════════════════════════════════════ 🐜
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 👑 Goal Achieved: {goal}
 📍 Phases Completed: {total}
@@ -981,17 +991,14 @@ Runs ONLY when all phases complete.
 ### Step 3: Display Result
 
 **If visual_mode is true, render final swarm display:**
-```bash
-bash .aether/aether-utils.sh swarm-display-update "Queen" "prime" "completed" "Phase advanced" "Colony" '{"read":5,"grep":2,"edit":3,"bash":2}' 100 "fungus_garden" 100
-bash .aether/aether-utils.sh swarm-display-inline "$continue_id"
-```
+Run using the Bash tool with description "Rendering advancement summary...": `bash .aether/aether-utils.sh swarm-display-update "Queen" "prime" "completed" "Phase advanced" "Colony" '{"read":5,"grep":2,"edit":3,"bash":2}' 100 "fungus_garden" 100 && bash .aether/aether-utils.sh swarm-display-text "$continue_id"`
 
 Output:
 
 ```
-🐜 ═══════════════════════════════════════════════════
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    P H A S E   A D V A N C E M E N T
-═══════════════════════════════════════════════════ 🐜
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ✅ Phase {prev_id}: {prev_name} -- COMPLETED
 
@@ -1015,10 +1022,11 @@ Output:
    📋 Tasks: {task_count}
    📊 State: READY
 
-🐜 Next Steps:
-   /ant:build {next_id}   🔨 Start building Phase {next_id}: {next_name}
-   /ant:phase {next_id}   📋 Review phase details first
-   /ant:focus "<area>"    🎯 Guide colony attention
+──────────────────────────────────────────────────
+🐜 Next Up
+──────────────────────────────────────────────────
+   /ant:build {next_id}     🔨 Build next phase
+   /ant:status              📊 Check progress
 
 💾 State persisted — context clear suggested above
 
@@ -1034,3 +1042,5 @@ Update the session tracking file to enable `/ant:resume` after context clear:
 ```bash
 bash .aether/aether-utils.sh session-update "/ant:continue" "/ant:build {next_id}" "Phase {prev_id} completed, advanced to Phase {next_id}"
 ```
+
+Run using the Bash tool with description "Saving session state...": `bash .aether/aether-utils.sh session-update "/ant:continue" "/ant:build {next_id}" "Phase {prev_id} completed, advanced to Phase {next_id}"`

package/.claude/commands/ant/council.md

@@ -13,7 +13,7 @@ Parse `$ARGUMENTS`:
 
 ### Step 0: Initialize Visual Mode (if enabled)
 
-If `visual_mode` is true:
+If `visual_mode` is true, run using the Bash tool with description "Initializing council display...":
 ```bash
 # Generate session ID
 council_id="council-$(date +%s)"
@@ -43,9 +43,9 @@ Capture the current state for context:
 ### Step 2: Display Council Header
 
 ```
-📜🐜🏛️🐜📜 ═══════════════════════════════════════════════
+📜🐜🏛️🐜📜 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
               A N T   C O U N C I L
-═══════════════════════════════════════════════ 📜🐜🏛️🐜📜
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📜🐜🏛️🐜📜
 
 👑 Queen convenes the council for guidance
 
@@ -239,10 +239,10 @@ Keep max 100 events.
 
 ### Step 8: Display Summary
 
-**If visual_mode is true, render final swarm display:**
+**If visual_mode is true, render final swarm display** by running using the Bash tool with description "Updating council display...":
 ```bash
 bash .aether/aether-utils.sh swarm-display-update "Queen" "prime" "completed" "Council adjourned" "Colony" '{"read":3,"grep":0,"edit":2,"bash":1}' 100 "fungus_garden" 100
-bash .aether/aether-utils.sh swarm-display-inline "$council_id"
+bash .aether/aether-utils.sh swarm-display-text "$council_id"
 ```
 
 ```
@@ -297,3 +297,13 @@ If `prior_state` was PLANNING:
 ```
    Planning will continue with new guidance.
 ```
+
+### Step 9: Next Up
+
+Generate the state-based Next Up block by running using the Bash tool with description "Generating Next Up suggestions...":
+```bash
+state=$(jq -r '.state // "IDLE"' .aether/data/COLONY_STATE.json)
+current_phase=$(jq -r '.current_phase // 0' .aether/data/COLONY_STATE.json)
+total_phases=$(jq -r '.plan.phases | length' .aether/data/COLONY_STATE.json)
+bash .aether/aether-utils.sh print-next-up "$state" "$current_phase" "$total_phases"
+```