aether-colony 3.1.2 → 3.1.4

package/.claude/commands/ant/build.md

@@ -209,6 +209,7 @@ CONSTRAINTS: (none)
    ```bash
    bash .aether/aether-utils.sh generate-ant-name "archaeologist"
    bash .aether/aether-utils.sh spawn-log "Queen" "scout" "{archaeologist_name}" "Pre-build archaeology scan"
+   bash .aether/aether-utils.sh swarm-display-update "{archaeologist_name}" "scout" "excavating" "Pre-build archaeology scan" "Queen" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "fungus_garden" 15
    ```
 
    Display:
@@ -257,9 +258,10 @@ CONSTRAINTS: (none)
 
    **Wait for results** (blocking — use TaskOutput with `block: true`).
 
-   Log completion:
+   Log completion and update swarm display:
    ```bash
    bash .aether/aether-utils.sh spawn-complete "{archaeologist_name}" "completed" "Pre-build archaeology scan"
+   bash .aether/aether-utils.sh swarm-display-update "{archaeologist_name}" "scout" "completed" "Pre-build archaeology scan" "Queen" '{"read":8,"grep":5,"edit":0,"bash":2}' 100 "fungus_garden" 100
    ```
 
 3. **Store and display findings:**
@@ -425,9 +427,12 @@ DO NOT spawn for work you can complete in < 10 tool calls.
 Before spawning:
   1. Check: bash .aether/aether-utils.sh spawn-can-spawn {depth}
   2. Generate name: bash .aether/aether-utils.sh generate-ant-name "{caste}"
-  3. Log: bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
-  4. Use Task tool with subagent_type="general"
-  5. After completion: bash .aether/aether-utils.sh spawn-complete "{child_name}" "{status}" "{summary}"
+  3. Log spawn: bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
+  4. Update swarm display: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "excavating" "{task}" "{your_name}" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "fungus_garden" 10
+  5. Use Task tool with subagent_type="general"
+  6. After completion:
+     - Log completion: bash .aether/aether-utils.sh spawn-complete "{child_name}" "{status}" "{summary}"
+     - Update swarm display: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "completed" "{task}" "{your_name}" '{"read":5,"grep":3,"edit":2,"bash":1}' 100 "fungus_garden" 100
 
 Full spawn format: .aether/workers.md section "Spawning Sub-Workers"
 
@@ -549,7 +554,9 @@ You are at depth {depth}. You MAY spawn sub-workers for:
 Spawn limits: Depth 1→4, Depth 2→2, Depth 3→0
 
 Before spawning:
-  bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
+  1. Log spawn: bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
+  2. Update swarm display: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "observing" "{task}" "{your_name}" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "nursery" 50
+  3. After completion: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "completed" "{task}" "{your_name}" '{"read":3,"grep":2,"edit":0,"bash":0}' 100 "nursery" 100
 
 --- CRITICAL ---
 - You did NOT build this code — verify it objectively

package/.opencode/commands/ant/build.md

@@ -218,6 +218,7 @@ CONSTRAINTS: (none)
    ```bash
    bash .aether/aether-utils.sh generate-ant-name "archaeologist"
    bash .aether/aether-utils.sh spawn-log "Queen" "scout" "{archaeologist_name}" "Pre-build archaeology scan"
+   bash .aether/aether-utils.sh swarm-display-update "{archaeologist_name}" "scout" "excavating" "Pre-build archaeology scan" "Queen" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "fungus_garden" 15
    ```
 
    Display:
@@ -259,9 +260,10 @@ CONSTRAINTS: (none)
 
    **Wait for results** (blocking — use TaskOutput with `block: true`).
 
-   Log completion:
+   Log completion and update swarm display:
    ```bash
    bash .aether/aether-utils.sh spawn-complete "{archaeologist_name}" "completed" "Pre-build archaeology scan"
+   bash .aether/aether-utils.sh swarm-display-update "{archaeologist_name}" "scout" "completed" "Pre-build archaeology scan" "Queen" '{"read":8,"grep":5,"edit":0,"bash":2}' 100 "fungus_garden" 100
    ```
 
 3. **Store and display findings:**
@@ -425,9 +427,12 @@ DO NOT spawn for work you can complete in < 10 tool calls.
 Before spawning:
   1. Check: bash .aether/aether-utils.sh spawn-can-spawn {depth}
   2. Generate name: bash .aether/aether-utils.sh generate-ant-name "{caste}"
-  3. Log: bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
-  4. Use Task tool with subagent_type="general"
-  5. After completion: bash .aether/aether-utils.sh spawn-complete "{child_name}" "{status}" "{summary}"
+  3. Log spawn: bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
+  4. Update swarm display: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "excavating" "{task}" "{your_name}" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "fungus_garden" 10
+  5. Use Task tool with subagent_type="general"
+  6. After completion:
+     - Log completion: bash .aether/aether-utils.sh spawn-complete "{child_name}" "{status}" "{summary}"
+     - Update swarm display: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "completed" "{task}" "{your_name}" '{"read":5,"grep":3,"edit":2,"bash":1}' 100 "fungus_garden" 100
 
 Full spawn format: .aether/workers.md section "Spawning Sub-Workers"
 
@@ -538,7 +543,9 @@ You are at depth {depth}. You MAY spawn sub-workers for:
 Spawn limits: Depth 1→4, Depth 2→2, Depth 3→0
 
 Before spawning:
-  bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
+  1. Log spawn: bash .aether/aether-utils.sh spawn-log "{your_name}" "{caste}" "{child_name}" "{task}"
+  2. Update swarm display: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "observing" "{task}" "{your_name}" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "nursery" 50
+  3. After completion: bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{caste}" "completed" "{task}" "{your_name}" '{"read":3,"grep":2,"edit":0,"bash":0}' 100 "nursery" 100
 
 --- CRITICAL ---
 - You did NOT build this code — verify it objectively

package/CHANGELOG.md

@@ -5,6 +5,16 @@ All notable changes to the Aether Colony project will be documented in this file
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.1.4] - 2026-02-15
+
+### Fixed
+- **Archaeologist Visualization** — Added swarm display integration for the Archaeologist scout (Step 4.5). The archaeologist now appears in the visual display with proper emoji (🏺), progress tracking (15% → 100%), and tool usage stats when spawned during pre-build scans. (`.claude/commands/ant/build.md`, `.opencode/commands/ant/build.md`)
+
+## [3.1.3] - 2026-02-15
+
+### Fixed
+- **Nested Spawn Visualization** — When builders or watchers spawn sub-workers, the swarm display now updates to show those nested spawns with colors and emojis. Added `swarm-display-update` calls to workers.md spawn protocol (Step 3 and Step 5), builder prompts, and watcher prompts. (`.aether/workers.md`, `.claude/commands/ant/build.md`, `.opencode/commands/ant/build.md`)
+
 ## [3.1.2] - 2026-02-15
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aether-colony",
-  "version": "3.1.2",
+  "version": "3.1.4",
   "description": "Multi-agent system using ant colony intelligence for Claude Code and OpenCode — workers self-organize via pheromone signals",
   "bin": {
     "aether": "bin/cli.js"

package/runtime/workers.md

@@ -50,103 +50,42 @@ bash .aether/aether-utils.sh spawn-complete "Hammer-42" "completed" "auth module
 
 ---
 
-## Model-Aware Spawning
+## Model Selection (Session-Level)
 
-Aether colony workers are spawned with model-specific configurations based on their caste. This enables optimal task routing through the LiteLLM proxy.
+Aether can work with different AI models through a LiteLLM proxy, but **model selection happens at the session level**, not per-worker.
 
 ### How It Works
 
-1. **Model Assignment**: Each caste is mapped to an optimal model in `.aether/model-profiles.yaml`
-2. **Prompt Context**: Queen includes model assignment in worker's prompt via `--- MODEL CONTEXT ---` section
-3. **Worker Self-Reporting**: Workers echo their assigned model in JSON output for verification
-4. **Proxy Routing** (Optional): With LiteLLM proxy running, set `ANTHROPIC_MODEL` in parent shell for true model routing
+Claude Code's Task tool does not support passing environment variables to spawned workers. All workers inherit the parent session's model configuration.
 
-### Model Assignments by Caste
-
-| Caste | Model | Purpose |
-|-------|-------|---------|
-| prime | glm-5 | Long-horizon coordination, strategic planning (200K context) |
-| archaeologist | glm-5 | Historical pattern analysis across long timeframes |
-| architect | glm-5 | Pattern synthesis, documentation coordination (200K context) |
-| oracle | minimax-2.5 | Research, foresight, browse/search (76.3% BrowseComp) |
-| route_setter | kimi-k2.5 | Task decomposition, structured planning (256K context) |
-| builder | kimi-k2.5 | Code generation, refactoring (76.8% SWE-Bench) |
-| watcher | kimi-k2.5 | Validation, testing, verification |
-| scout | minimax-2.5| Research exploration, parallel sub-agent spawning |
-| chaos | kimi-k2.5 | Edge case probing, resilience testing |
-| colonizer | minimax-2.5| Environment setup, visual coding from screenshots |
-
-### Worker Model Self-Reporting
-
-All workers must include model context in their JSON output:
-
-```json
-{
-  "status": "completed",
-  "summary": "...",
-  "model_context": {
-    "assigned": "kimi-k2.5",
-    "caste": "builder",
-    "source": "caste-default",
-    "reported_at": "2026-02-15T10:30:00Z"
-  }
-}
-```
-
-This enables:
-- **Visibility**: See which model each worker used
-- **Verification**: Confirm routing is working correctly
-- **Debugging**: Detect mismatches between expected and actual
-
-### LiteLLM Proxy Integration (Optional)
-
-For true model routing through LiteLLM:
+### To Use a Specific Model
 
 ```bash
-# 1. Start proxy with your API keys
-litellm --config proxy.yaml
+# 1. Start LiteLLM proxy (if using)
+cd ~/repos/litellm-proxy && docker-compose up -d
 
-# 2. In parent shell (before starting Claude Code):
+# 2. Set environment variables before starting Claude Code:
 export ANTHROPIC_BASE_URL=http://localhost:4000
 export ANTHROPIC_AUTH_TOKEN=sk-litellm-local
-export ANTHROPIC_MODEL=kimi-k2.5  # Or your preferred default
+export ANTHROPIC_MODEL=kimi-k2.5  # or glm-5, minimax-2.5
 
-# 3. Start Claude Code - it will inherit these variables
+# 3. Start Claude Code
 claude
 ```
 
-**Note:** Claude Code's Task tool doesn't support explicit environment variable passing,
-so proxy routing relies on parent shell inheritance. The self-reporting approach works
-regardless of proxy status.
-
-### Available Models
-
-- **glm-5** (via Z_AI): Powerful reasoning for complex tasks, architecture, planning
-- **kimi-k2.5** (via Kimi): Fast code generation, refactoring, implementation
-- **minimax-2.5** (via MiniMax): Efficient validation, research, lightweight tasks
-
-### Fallback Behavior
-
-If the model profile is missing or a caste is not mapped:
-- Default to `kimi-k2.5` (fastest, most cost-effective)
-- Log a warning to the activity log
-- Continue with worker spawn
-
-### Sub-Worker Spawning
+### Available Models (via LiteLLM)
 
-When workers spawn sub-workers, they should:
-1. Check if the sub-worker's caste differs from their own
-2. If different, the sub-worker will automatically get their caste's model via the same mechanism
-3. If spawning with the same caste, the model remains the same
+| Model | Best For | Provider |
+|-------|----------|----------|
+| glm-5 | Complex reasoning, architecture, planning | Z_AI |
+| kimi-k2.5 | Fast coding, implementation | Moonshot |
+| minimax-2.5 | Validation, research, exploration | MiniMax |
 
-### Model Context in Prompts
+### Historical Note
 
-Worker prompts include a MODEL CONTEXT section that informs the worker about:
-- Which model they are running on
-- The model's strengths and optimal use cases
-- Expected task complexity
+A model-per-caste routing system was designed and implemented (archived in `.aether/archive/model-routing/`) but cannot function due to Claude Code Task tool limitations. The archive is preserved for future use if the platform adds environment variable support for subagents.
 
-This helps workers adjust their approach based on model capabilities.
+See: `git show model-routing-v1-archived` for the complete configuration.
 
 ---
 
@@ -371,9 +310,10 @@ child_name=$(bash .aether/aether-utils.sh generate-ant-name "{caste}" | jq -r '.
 # Returns: "Hammer-42", "Vigil-17", etc.
 ```
 
-**Step 3: Log the spawn**
+**Step 3: Log the spawn and update swarm display**
 ```bash
 bash .aether/aether-utils.sh spawn-log "{your_name}" "{child_caste}" "{child_name}" "{task_summary}"
+bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{child_caste}" "excavating" "{task_summary}" "{your_name}" '{"read":0,"grep":0,"edit":0,"bash":0}' 0 "fungus_garden" 10
 ```
 
 **Step 4: Use Task tool**
@@ -416,10 +356,11 @@ Return a compressed summary:
 }
 ```
 
-**Step 5: Log completion**
+**Step 5: Log completion and update swarm display**
 ```bash
 # After Task tool returns
 bash .aether/aether-utils.sh spawn-complete "{child_name}" "{status}" "{summary}"
+bash .aether/aether-utils.sh swarm-display-update "{child_name}" "{child_caste}" "completed" "{summary}" "{your_name}" '{"read":5,"grep":3,"edit":2,"bash":1}' 100 "fungus_garden" 100
 ```
 
 ---