aether-colony 5.3.2 → 5.3.3

package/.aether/commands/claude/tunnels.md

@@ -1,426 +0,0 @@
-<!-- Generated from .aether/commands/tunnels.yaml - DO NOT EDIT DIRECTLY -->
----
-name: ant:tunnels
-description: "🕳️🐜🕳️ Explore tunnels (browse archived colonies, compare chambers)"
----
-
-You are the **Queen**. Browse the colony history.
-
-## Instructions
-
-### Argument Handling
-
-- No arguments: Show timeline view (Step 4)
-- One argument: Show single chamber detail with seal document (Step 3)
-- Two arguments: Compare two chambers side-by-side (Step 5)
-- More than two: "Too many arguments. Use: /ant:tunnels [chamber1] [chamber2]"
-
-### Step 1: Check for Chambers Directory
-
-Check if `.aether/chambers/` exists.
-
-If not:
-```
-TUNNELS — Colony Timeline
-
-No chambers found.
-
-Archive colonies with /ant:entomb to build the tunnel network.
-```
-Stop here.
-
-### Step 2: List All Chambers
-
-Run using the Bash tool with description "Loading chamber list...": `bash .aether/aether-utils.sh chamber-list`
-
-Parse JSON result into array of chambers.
-
-If no chambers (empty array):
-```
-TUNNELS — Colony Timeline
-
-0 colonies archived
-
-The tunnel network is empty.
-Archive colonies with /ant:entomb to preserve history.
-```
-Stop here.
-
-### Step 3: Detail View — Show Seal Document (if one argument provided)
-
-If `$ARGUMENTS` is not empty and contains exactly one argument:
-- Treat it as chamber name
-- Check if `.aether/chambers/{arguments}/` exists
-- If not found:
-  ```
-  Chamber not found: {arguments}
-
-  Run /ant:tunnels to see available chambers.
-  ```
-  Stop here.
-
-**If CROWNED-ANTHILL.md exists in the chamber:**
-
-```bash
-seal_doc=".aether/chambers/{arguments}/CROWNED-ANTHILL.md"
-```
-
-Display the header:
-```
-CHAMBER DETAILS — {chamber_name}
-```
-
-Then display the FULL content of `CROWNED-ANTHILL.md` (read and output the file contents — this IS the seal ceremony record).
-
-After the seal document, check if `colony-archive.xml` exists in the chamber:
-
-```bash
-chamber_has_xml=false
-[[ -f ".aether/chambers/{chamber_name}/colony-archive.xml" ]] && chamber_has_xml=true
-```
-
-**If `colony-archive.xml` exists in the chamber**, show footer with import option:
-```
-Chamber integrity: {hash_status from chamber-verify}
-Chamber location: .aether/chambers/{chamber_name}/
-XML Archive: colony-archive.xml found
-
-Actions:
-  1. Import signals from this colony into current colony
-  2. Return to timeline
-  3. Compare with another chamber
-
-Select an action (1/2/3)
-```
-
-Use AskUserQuestion with three options.
-
-If option 1 selected: proceed to Step 6 (Import Signals from Chamber).
-If option 2 selected: return to timeline (run /ant:tunnels).
-If option 3 selected: prompt for second chamber name then run /ant:tunnels {chamber_a} {chamber_b}.
-
-**If `colony-archive.xml` does NOT exist in the chamber**, show the existing footer unchanged:
-```
-Chamber integrity: {hash_status from chamber-verify}
-Chamber location: .aether/chambers/{chamber_name}/
-
-Run /ant:tunnels to return to timeline
-Run /ant:tunnels {chamber_a} {chamber_b} to compare chambers
-```
-
-**If CROWNED-ANTHILL.md does NOT exist (older chamber):**
-
-Display the header:
-```
-CHAMBER DETAILS — {chamber_name}
-
-(No seal document — this chamber was created before the sealing ceremony was introduced)
-```
-
-Fall back to manifest data display:
-- Read `manifest.json` and show: goal, milestone, version, phases_completed, total_phases, entombed_at
-- Show decisions count and learnings count from manifest
-- Show hash status from `chamber-verify`
-
-Footer with navigation guidance:
-```
-Run /ant:tunnels to return to timeline
-Run /ant:tunnels {chamber_a} {chamber_b} to compare chambers
-```
-
-To get the hash status, run using the Bash tool with description "Verifying chamber integrity...":
-- Run `bash .aether/aether-utils.sh chamber-verify .aether/chambers/{chamber_name}`
-- If verified: hash_status = "verified"
-- If not verified: hash_status = "hash mismatch"
-- If error: hash_status = "error"
-
-Stop here.
-
-### Step 4: Timeline View (default, no arguments)
-
-Display header:
-```
-TUNNELS — Colony Timeline
-
-{count} colonies archived
-```
-
-For each chamber in sorted list (already sorted by `chamber-list` — newest first), display as a timeline entry:
-```
-[{date}] {milestone_emoji} {chamber_name}
-           {goal (truncated to 60 chars)}
-           {phases_completed} phases | {milestone}
-```
-
-Where `milestone_emoji` is:
-- Crowned Anthill: crown emoji
-- Sealed Chambers: lock emoji
-- Other: circle emoji
-
-After the timeline entries, show:
-```
-Run /ant:tunnels <chamber_name> to view seal document
-Run /ant:tunnels <chamber_a> <chamber_b> to compare two colonies
-```
-
-Use the entombed_at field from the chamber-list JSON to extract the date (first 10 chars of ISO timestamp).
-
-Stop here.
-
-### Step 5: Chamber Comparison Mode (Two Arguments)
-
-If two arguments provided (chamber names separated by space):
-- Treat as: `/ant:tunnels <chamber_a> <chamber_b>`
-
-Check both chambers exist. If either missing:
-```
-Chamber not found: {chamber_name}
-
-Available chambers:
-{list from chamber-list}
-```
-Stop here.
-
-Run comparison using the Bash tool with description "Comparing chambers...":
-```bash
-bash .aether/utils/chamber-compare.sh compare <chamber_a> <chamber_b>
-bash .aether/utils/chamber-compare.sh stats <chamber_a> <chamber_b>
-```
-
-Display comparison header:
-```
-CHAMBER COMPARISON
-
-{chamber_a}  vs  {chamber_b}
-```
-
-Display side-by-side comparison:
-```
-+---------------------+---------------------+
-| {chamber_a}         | {chamber_b}         |
-+---------------------+---------------------+
-| Goal: {goal_a}      | Goal: {goal_b}      |
-|                     |                     |
-| {milestone_a}       | {milestone_b}       |
-| {version_a}         | {version_b}         |
-|                     |                     |
-| {phases_a} done     | {phases_b} done     |
-| of {total_a}        | of {total_b}        |
-|                     |                     |
-| {decisions_a}       | {decisions_b}       |
-| decisions           | decisions           |
-|                     |                     |
-| {learnings_a}       | {learnings_b}       |
-| learnings           | learnings           |
-|                     |                     |
-| {date_a}            | {date_b}            |
-+---------------------+---------------------+
-```
-
-Display growth metrics:
-```
-Growth Between Chambers:
-  Phases: +{phases_diff} ({phases_a} -> {phases_b})
-  Decisions: +{decisions_diff} new
-  Learnings: +{learnings_diff} new
-  Time: {time_between} days apart
-```
-
-If phases_diff > 0: show "Colony grew"
-If phases_diff < 0: show "Colony reduced (unusual)"
-If same_milestone: show "Same milestone reached"
-If milestone changed: show "Milestone advanced: {milestone_a} -> {milestone_b}"
-
-Display pheromone trail diff (new decisions/learnings in B) by running using the Bash tool with description "Analyzing pheromone differences...":
-```bash
-bash .aether/utils/chamber-compare.sh diff <chamber_a> <chamber_b>
-```
-
-Parse result and show:
-```
-New Decisions in {chamber_b}:
-  {N} new architectural decisions
-  {if N <= 5, list them; else show first 3 + "...and {N-3} more"}
-
-New Learnings in {chamber_b}:
-  {N} new validated learnings
-  {if N <= 5, list them; else show first 3 + "...and {N-3} more"}
-```
-
-If both chambers have `CROWNED-ANTHILL.md`, note:
-```
-Both colonies have seal documents. Run /ant:tunnels <name> to view individually.
-```
-
-Footer:
-```
-Run /ant:tunnels to see all chambers
-Run /ant:tunnels <chamber> to view single chamber details
-```
-
-Stop here.
-
-### Step 6: Import Signals from Chamber
-
-When user selects "Import signals" from Step 3:
-
-**Step 6.1: Check XML tools** by running using the Bash tool with description "Checking XML tools...":
-```bash
-if command -v xmllint >/dev/null 2>&1; then
-  xmllint_available=true
-else
-  xmllint_available=false
-fi
-```
-
-If xmllint not available:
-```
-Import requires xmllint. Install it first:
-  macOS: xcode-select --install
-  Linux: apt-get install libxml2-utils
-```
-Stop here (return to timeline).
-
-**Step 6.2: Extract source colony name** by running using the Bash tool with description "Extracting colony info...":
-```bash
-chamber_xml=".aether/chambers/{chamber_name}/colony-archive.xml"
-# Extract colony_id from the archive root element
-source_colony=$(xmllint --xpath "string(/*/@colony_id)" "$chamber_xml" 2>/dev/null)
-[[ -z "$source_colony" ]] && source_colony="{chamber_name}"
-```
-
-**Step 6.3: Extract pheromone section and show import preview**
-
-The combined `colony-archive.xml` contains pheromones, wisdom, and registry sections. Extract the pheromone section to a temp file before counting or importing. This prevents over-counting signals from wisdom/registry sections and ensures `pheromone-import-xml` receives the format it expects (`<pheromones>` as root element).
-
-Run using the Bash tool with description "Extracting pheromone signals...":
-```bash
-# Extract the <pheromones> section from the combined archive into a standalone temp file
-import_tmp_dir=$(mktemp -d)
-import_tmp_pheromones="$import_tmp_dir/pheromones-extracted.xml"
-
-# Use xmllint to extract the pheromones element (with its namespace)
-xmllint --xpath "//*[local-name()='pheromones']" "$chamber_xml" > "$import_tmp_pheromones" 2>/dev/null
-
-# Add XML declaration to make it a standalone well-formed document
-if [[ -s "$import_tmp_pheromones" ]]; then
-  # Portable approach: prepend declaration via temp file (avoids macOS/Linux sed -i differences)
-  { echo '<?xml version="1.0" encoding="UTF-8"?>'; cat "$import_tmp_pheromones"; } > "$import_tmp_dir/tmp_decl.xml"
-  mv "$import_tmp_dir/tmp_decl.xml" "$import_tmp_pheromones"
-fi
-
-# Count pheromone signals in extracted pheromone-only XML
-# Scoped to pheromone section only — no over-counting from wisdom/registry sections
-pheromone_count=$(xmllint --xpath "count(//*[local-name()='signal'])" "$import_tmp_pheromones" 2>/dev/null || echo "unknown")
-```
-
-Display:
-```
-IMPORT FROM COLONY: {source_colony}
-
-Source: .aether/chambers/{chamber_name}/colony-archive.xml
-Signals available: ~{pheromone_count} pheromone signals
-
-Import behavior:
-  - Signals tagged with prefix "{source_colony}:" to identify origin
-  - Additive merge — your current signals are never overwritten
-  - On conflict, your current colony wins
-
-Import these signals? (yes/no)
-```
-
-Use AskUserQuestion with yes/no options.
-
-If no: "Import cancelled." Clean up: `rm -rf "$import_tmp_dir"`. Return to timeline.
-
-**Step 6.4: Perform import**
-
-Pass the extracted pheromone-only temp file (NOT the combined `colony-archive.xml`) to `pheromone-import-xml`, along with `$source_colony` as the second argument. This ensures:
-1. `pheromone-import-xml` receives XML with `<pheromones>` as root element (the format it expects)
-2. The prefix-tagging logic prepends `${source_colony}:` to each imported signal's ID before the merge
-
-Run using the Bash tool with description "Importing pheromone signals...":
-```bash
-# Import the EXTRACTED pheromone-only XML (NOT the combined colony-archive.xml)
-# $import_tmp_pheromones has <pheromones> as root — the format pheromone-import-xml expects
-# Second argument triggers prefix-tagging — imported signal IDs become "{source_colony}:original_id"
-import_result=$(bash .aether/aether-utils.sh pheromone-import-xml "$import_tmp_pheromones" "$source_colony" 2>&1)
-import_ok=$(echo "$import_result" | jq -r '.ok // false' 2>/dev/null)
-
-if [[ "$import_ok" == "true" ]]; then
-  imported_count=$(echo "$import_result" | jq -r '.result.signal_count // 0' 2>/dev/null)
-else
-  imported_count=0
-  import_error=$(echo "$import_result" | jq -r '.error // "Unknown error"' 2>/dev/null)
-fi
-
-# Clean up temp files
-rm -rf "$import_tmp_dir"
-```
-
-**Step 6.5: Display result**
-
-If import succeeded:
-```
-SIGNALS IMPORTED
-
-Source: {source_colony}
-Imported: {imported_count} pheromone signals
-Tagged with: "{source_colony}:" prefix
-
-Your colony now carries wisdom from {source_colony}.
-Run /ant:status to see current colony state.
-```
-
-If import failed:
-```
-Import failed: {import_error}
-
-The archive may be malformed. Check:
-  .aether/chambers/{chamber_name}/colony-archive.xml
-```
-
-### Edge Cases
-
-**Malformed manifest:** show "Invalid manifest" for that chamber and skip it.
-
-**Missing COLONY_STATE.json:** show "Incomplete chamber" for that chamber.
-
-**Very long chamber list:** display all (no pagination for now).
-
-**Older chambers without CROWNED-ANTHILL.md:** Fall back to manifest data in detail view.
-
-### Step 7: 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"
-```
-
-## Implementation Notes
-
-The `chamber-list` utility returns JSON in this format:
-```json
-{
-  "ok": true,
-  "result": [
-    {
-      "name": "add-user-auth-20260214-153022",
-      "goal": "Add user authentication",
-      "milestone": "Sealed Chambers",
-      "phases_completed": 5,
-      "entombed_at": "2026-02-14T15:30:22Z"
-    }
-  ]
-}
-```
-
-Parse with jq: `jq -r '.result[] | "\(.name)|\(.goal)|\(.milestone)|\(.phases_completed)|\(.entombed_at)"'`
-
-For detail view, read manifest.json directly:
-```bash
-jq -r '.goal, .milestone, .version, .phases_completed, .total_phases, .entombed_at, (.decisions | length), (.learnings | length)' .aether/chambers/{name}/manifest.json
-```

package/.aether/commands/claude/update.md

@@ -1,132 +0,0 @@
-<!-- Generated from .aether/commands/update.yaml - DO NOT EDIT DIRECTLY -->
----
-name: ant:update
-description: "🔄🐜📦🐜🔄 Update Aether safely from the global hub (transactional)"
----
-
-You are the **Queen Ant Colony**. Update this repo's Aether system files from the global distribution hub.
-
-## Safety Rules
-
-1. Use the CLI transactional updater (`aether update`) instead of manual `cp` chains.
-2. Never overwrite colony runtime data (`.aether/data/`) or user wisdom (`.aether/QUEEN.md`).
-3. Do **not** assume version numbers are monotonic. Labels may reset; avoid "downgrade" wording.
-4. If update reports dirty managed files, stop and show recovery options unless user requested force.
-
-## Instructions
-
-### Step 1: Check Hub Availability
-
-Run using the Bash tool with description "Checking Aether hub...":
-
-```bash
-test -f ~/.aether/version.json && cat ~/.aether/version.json || echo "__NO_HUB__"
-```
-
-If output is `__NO_HUB__`, display:
-
-```
-No Aether distribution hub found at ~/.aether/
-
-To set up the hub, run:
-  npx aether-colony install
-  - or -
-  aether install
-```
-
-Stop here.
-
-Parse `version` from the JSON as `available_version`.
-
-### Step 1.5: Verify CLI Availability
-
-Run using the Bash tool with description "Checking aether CLI...":
-
-```bash
-command -v aether >/dev/null 2>&1 && echo "__CLI_OK__" || echo "__CLI_MISSING__"
-```
-
-If output is `__CLI_MISSING__`, display:
-
-```
-The transactional updater is not available because the `aether` CLI is missing.
-
-Install/update it, then retry:
-  npx aether-colony install
-  - or -
-  npm i -g aether-colony
-```
-
-Stop here.
-
-### Step 2: Parse Force Flag
-
-Treat either of these as force:
-- `--force`
-- `--force-update`
-
-Set:
-- `update_flags="--force"` when force requested
-- `update_flags=""` otherwise
-
-### Step 3: Dry-Run Preview
-
-Run using the Bash tool with description "Previewing update...":
-
-```bash
-aether update --dry-run $update_flags
-```
-
-If this fails, show the error output and stop.
-
-### Step 4: Execute Transactional Update
-
-Run using the Bash tool with description "Applying update...":
-
-```bash
-aether update $update_flags
-```
-
-This command handles:
-- checkpoint creation
-- safe sync
-- integrity verification
-- automatic rollback on failure
-
-### Step 5: Clear Version Cache
-
-
-Run using the Bash tool:
-
-
-
-```bash
-rm -f .aether/data/.version-check-cache
-```
-
-### Step 6: Display Summary
-
-Display a concise summary:
-
-```
-🔄🐜📦🐜🔄 AETHER UPDATE COMPLETE
-
-Hub version label: {available_version}
-Update mode: {normal|force}
-Colony data (.aether/data/) untouched.
-
-Note: version labels are treated as identifiers, not strict upgrade/downgrade ordering.
-```
-
-
-### Next Up
-
-Generate the state-based Next Up block by running:
-
-```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"
-```
-

package/.aether/commands/claude/verify-castes.md

@@ -1,143 +0,0 @@
-<!-- Generated from .aether/commands/verify-castes.yaml - DO NOT EDIT DIRECTLY -->
----
-name: ant:verify-castes
-description: "Verify colony caste assignments and system status"
----
-
-You are the **Queen**. Display the caste assignments and system status.
-
-## Step 1: Show Caste Assignments
-
-Display the colony caste structure as a compact table:
-
-
-```
-Aether Colony Caste System
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-
-
-CASTE ASSIGNMENTS
-────────────────────────────────────
-Caste                Slot     Active
-────────────────────────────────────
-[reasoning]
-  Archaeologist      opus     yes
-  Architect          opus     yes
-  Auditor            opus     yes
-  Gatekeeper         opus     yes
-  Measurer           opus     yes
-  Oracle             opus     yes
-  Queen              opus     yes
-  Route-setter       opus     yes
-  Sage               opus     yes
-  Tracker            opus     yes
-────────────────────────────────────
-[execution]
-  Ambassador         sonnet   yes
-  Builder            sonnet   yes
-  Chaos              sonnet   yes
-  Disciplines        sonnet   yes
-  Nest               sonnet   yes
-  Pathogens          sonnet   yes
-  Probe              sonnet   yes
-  Provisions         sonnet   yes
-  Scout              sonnet   yes
-  Weaver             sonnet   yes
-  Watcher            sonnet   yes
-────────────────────────────────────
-[inherit]
-  Chronicler         inherit  yes
-  Includer           inherit  yes
-  Keeper             inherit  yes
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-
-```
-
-Source of truth: Agent frontmatter `model:` fields in `.claude/agents/ant/*.md`.
-Caste slots come from agent frontmatter (`model:` field).
-
-## Step 2: Check System Status
-
-
-Run using the Bash tool with description "Checking colony version...": `bash .aether/aether-utils.sh version-check-cached 2>/dev/null || echo "Utils available"`
-
-
-
-Check LiteLLM proxy status:
-```bash
-curl -s http://localhost:4000/health 2>/dev/null | grep -q "healthy" && echo "✓ Proxy healthy" || echo "⚠ Proxy not running"
-```
-
-## Step 3: Show Current Model Configuration
-
-Display the active model configuration:
-
-
-```
-MODEL CONFIGURATION
-──────────────────
-
-
-Default: Claude API mode (opus -> claude-opus-4, sonnet -> claude-sonnet-4)
-
-To switch to GLM Proxy mode:
-  cp ~/.claude/settings.json.glm ~/.claude/settings.json
-  (opus -> glm-5, sonnet -> glm-5-turbo, haiku -> glm-4.5-air)
-
-To switch back to Claude API:
-  cp ~/.claude/settings.json.claude ~/.claude/settings.json
-
-```
-
-
-
-Current model mapping from agent frontmatter:
-```bash
-grep "^model:" .claude/agents/ant/*.md
-```
-
-## Step 4: Summary
-
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-System Status
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-
-Utils: ✓ Operational
-Proxy: {status from Step 2}
-Castes: 24 defined (10 opus, 11 sonnet, 3 inherit)
-Routing: Per-caste via agent frontmatter model: field
-```
-
-
-## Step 5: 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"
-```
-
-
-## Historical Note
-
-Per-caste model routing was initially attempted using environment variable
-injection at spawn time (archived in `.aether/archive/model-routing/`).
-That approach failed due to Claude Code Task tool limitations.
-
-The current approach uses agent frontmatter `model:` fields, which Claude Code
-handles natively. No Aether code intervention is required -- Claude Code reads
-the frontmatter and resolves the slot name through `ANTHROPIC_DEFAULT_*_MODEL`
-environment variables.
-
-To view the archived v1 configuration:
-```bash
-git show model-routing-v1-archived
-```