aether-colony 1.1.0

package/.aether/docs/known-issues.md

@@ -0,0 +1,233 @@
+# Known Issues and Workarounds
+
+Documented issues from Oracle research findings. These are known limitations and bugs in the Aether system.
+
+---
+
+## Fixed Issues
+
+### Checkpoint Allowlist System (Fixed 2026-02-15)
+
+**Issue:** Build checkpoint could stash user work (TO-DOs.md, dreams, Oracle specs)
+
+**Root Cause:** `git stash` touched files outside system allowlist, stashing 1,145 lines of user work
+
+**Fix:** Explicit allowlist system implemented
+- Created `.aether/data/checkpoint-allowlist.json` defining safe system files
+- Added `checkpoint-check` helper to `.aether/aether-utils.sh`
+- Updated `build.md` (Claude and OpenCode) to use allowlist
+- User data (`.aether/data/`, `.aether/dreams/`, `TO-DOs.md`) is never touched
+- Warning displayed if user files are present during checkpoint
+
+**System Files (Safe):**
+- `.aether/aether-utils.sh`, `.aether/workers.md`, `.aether/docs/**/*.md`
+- `.claude/commands/ant/**/*.md`, `.claude/commands/st/**/*.md`
+- `.opencode/commands/ant/**/*.md`, `.opencode/agents/**/*.md`
+- `bin/**/*`
+
+**User Data (Never Touch):**
+- `.aether/data/`, `.aether/dreams/`, `.aether/oracle/`
+- `TO-DOs.md`, `COLONY_STATE.json`, `.env`, `*.log`
+
+---
+
+## Critical Issues (Fix Immediately)
+
+### BUG-005: Missing lock release in flag-auto-resolve — FIXED (Phase 16)
+**Location:** `.aether/aether-utils.sh:1022`
+**Severity:** HIGH
+**Status:** FIXED — Fixed in Phase 16: unified trap pattern (`trap 'release_lock 2>/dev/null || true' EXIT`) applied across all flag commands ensures lock release on all exit paths including jq failure.
+**Symptom:** If jq command fails during flag resolution, lock is never released
+**Impact:** Deadlock on flags.json if jq fails (malformed JSON, disk full, etc.)
+**Workaround:** ~~Restart the colony session if commands hang on flag operations~~ — no longer needed
+**Regression test:** `tests/bash/test-lock-lifecycle.sh` — test_flag_auto_resolve_jq_failure_releases_lock
+
+### BUG-011: Missing error handling in flag-auto-resolve jq — FIXED (Phase 16)
+**Location:** `.aether/aether-utils.sh:1022`
+**Severity:** HIGH
+**Status:** FIXED — Fixed in Phase 16: unified trap pattern across all flag commands. See BUG-005.
+**Symptom:** jq failure during auto-resolve not handled
+**Impact:** Combined with BUG-005, causes deadlock
+**Fix:** ~~Add `|| { release_lock; json_err ... }` pattern~~ — implemented via EXIT trap
+
+---
+
+## Medium Priority Issues
+
+### BUG-002: Missing release_lock in flag-add error path — FIXED (Phase 16)
+**Location:** `.aether/aether-utils.sh:814`
+**Severity:** MEDIUM
+**Status:** FIXED — Fixed in Phase 16: trap-based EXIT cleanup (`trap 'release_lock 2>/dev/null || true' EXIT`) ensures lock release on all exit paths including jq failure. Trap is cleared on the success path.
+**Symptom:** If acquire_lock succeeds but jq fails, lock is never released
+**Impact:** Potential deadlock on file operations
+**Regression test:** `tests/bash/test-lock-lifecycle.sh` — test_flag_add_jq_failure_releases_lock
+
+### BUG-003: Race condition in backup creation — FIXED (Phase 16)
+**Location:** `.aether/utils/atomic-write.sh:75`
+**Severity:** MEDIUM
+**Status:** FIXED — Backup is now created BEFORE JSON validation in both `atomic_write` and `atomic_write_from_file`. Verified in Phase 16 with regression tests confirming backup contains pre-write content.
+**Symptom:** Backup created AFTER temp file validation but BEFORE atomic move
+**Impact:** If process crashes between validation and backup, inconsistent state
+**Regression test:** `tests/bash/test-lock-lifecycle.sh` — test_atomic_write_backup_before_validate, test_atomic_write_from_file_backup_before_validate
+
+### BUG-004: Missing error code in flag-acknowledge
+**Location:** `.aether/aether-utils.sh:930`
+**Severity:** MEDIUM
+**Symptom:** Uses hardcoded string instead of `$E_VALIDATION_FAILED`
+**Impact:** Inconsistent error handling
+**Fix:** Change to `json_err "$E_VALIDATION_FAILED" "Usage: ..."`
+
+### BUG-006: No lock release on JSON validation failure
+**Location:** `.aether/utils/atomic-write.sh:66`
+**Severity:** MEDIUM
+**Symptom:** If JSON validation fails, temp file cleaned but lock not released
+**Impact:** Lock remains held if caller had acquired it
+**Fix:** Document lock ownership contract clearly
+
+### BUG-007: 17+ instances of missing error codes
+**Location:** `.aether/aether-utils.sh` various lines
+**Severity:** MEDIUM
+**Symptom:** Commands use hardcoded strings instead of error constants
+**Impact:** Inconsistent error handling, harder programmatic processing
+**Fix:** Standardize all to use `json_err "$E_*" "message"` pattern
+
+### BUG-008: Missing error code in flag-add jq failure
+**Location:** `.aether/aether-utils.sh:856`
+**Severity:** HIGH
+**Symptom:** Lock released but error code missing on jq failure
+**Impact:** Error response lacks proper error code
+**Fix:** Change to `json_err "$E_JSON_INVALID" "Failed to add flag"`
+
+### BUG-009: Missing error codes in file checks
+**Location:** `.aether/aether-utils.sh:899, 933`
+**Severity:** MEDIUM
+**Symptom:** File not found errors use hardcoded strings
+**Impact:** Inconsistent with other file not found errors
+**Fix:** Use `json_err "$E_FILE_NOT_FOUND" "..."`
+
+### BUG-010: Missing error codes in context-update
+**Location:** `.aether/aether-utils.sh:1758+`
+**Severity:** MEDIUM
+**Symptom:** Various error paths lack error code constants
+**Impact:** Inconsistent error handling
+
+### BUG-012: Missing error code in unknown command
+**Location:** `.aether/aether-utils.sh:2947`
+**Severity:** LOW
+**Symptom:** Unknown command handler uses bare string
+**Impact:** Inconsistent error response
+
+---
+
+## Architecture Issues
+
+### ISSUE-001: Inconsistent error code usage
+**Location:** Multiple locations
+**Severity:** MEDIUM
+**Description:** Some `json_err` calls use hardcoded strings instead of constants
+**Pattern:** Commands added early use strings; later commands use constants
+
+### ISSUE-002: Missing exec error handling — FIXED (Phase 18-02)
+**Location:** `.aether/aether-utils.sh:2132-2144`
+**Severity:** LOW
+**Description:** `model-get` and `model-list` use `exec` without fallback
+**Impact:** If exec fails, script continues to unknown command handler
+**Status:** FIXED — Phase 18-02: subprocess error handling added to model-get and model-list with structured E_* error codes on failure.
+
+### ISSUE-003: Incomplete help command — FIXED (Phase 18-03)
+**Location:** `.aether/aether-utils.sh:106-111`
+**Severity:** LOW
+**Description:** Help command missing newer commands like queen-*, view-state-*, swarm-timing-*
+**Impact:** Users cannot discover all available commands
+**Status:** FIXED — Phase 18-03: help command sections key added with all command groups including Queen Commands, Model Routing, Swarm Operations, and all newer commands.
+
+### ISSUE-004: Template path hardcoded to staging directory — FIXED (Phase 20)
+**Location:** `.aether/aether-utils.sh:2689`
+**Severity:** MEDIUM
+**Status:** FIXED — Phase 20: stale staging template path removed from queen-init lookup array. Template is now found via hub path (`~/.aether/system/templates/`) or dev repo path (`.aether/templates/`) or legacy hub fallback.
+**Description:** queen-init used a staging directory path that did not exist in npm installs
+**Impact:** ~~queen-init will fail when Aether is installed as npm package~~
+**~~Workaround:~~** ~~Use git clone instead of npm install~~ — no longer needed
+
+### ISSUE-005: Potential infinite loop in spawn-tree
+**Location:** `.aether/aether-utils.sh:402-448`, `spawn-tree.sh:222-263`
+**Severity:** LOW
+**Description:** Edge case with circular parent chain could cause issues
+**Mitigation:** Safety limit of 5 exists
+
+### ISSUE-006: Fallback json_err incompatible
+**Location:** `.aether/aether-utils.sh:65-72`
+**Severity:** LOW
+**Description:** Fallback json_err doesn't accept error code parameter
+**Impact:** If error-handler.sh fails to load, error codes are lost
+
+### ISSUE-007: Feature detection race condition — FIXED (Phase 18-01)
+**Location:** `.aether/aether-utils.sh:33-45`
+**Severity:** LOW
+**Description:** Feature detection runs before error handler fully sourced
+**Status:** FIXED — Phase 18-01 (ARCH-09): feature detection block moved after fallback json_err definition (line 68 -> 81) so all fallback infrastructure available when feature detection runs.
+
+---
+
+## Architecture Gaps
+
+### GAP-001: No schema version validation — FIXED (Phase 18-04)
+**Description:** Commands assume state structure without validating version
+**Impact:** Silent failures when state structure changes
+**Status:** FIXED — Phase 18-04: `_migrate_colony_state` added to validate-state colony; auto-migrates pre-3.0 state files to v3.0 (additive only), notifies via W_MIGRATED warning; corrupt state files backed up before error.
+
+### GAP-002: No cleanup for stale spawn-tree entries — FIXED (Phase 18-01)
+**Description:** spawn-tree.txt grows indefinitely
+**Impact:** File could grow very large over many sessions
+**Status:** FIXED — Phase 18-01: `_rotate_spawn_tree` added to session-init; rotates spawn-tree.txt on each session start with timestamped archives; 5-archive cap; in-place truncation preserves tail -f file handles.
+
+### GAP-003: No retry logic for failed spawns — RESOLVED (Phase 18-02)
+**Description:** Task tool calls don't have retry logic
+**Impact:** Transient failures cause build failures
+**Status:** RESOLVED — User decision: fail-fast with rich error context (Phase 18-02). Retry logic adds complexity without clear benefit; subprocess errors now emit structured E_* codes with actionable Try: suggestions, allowing callers to decide on retry strategy.
+
+### GAP-004: Missing queen-* documentation — FIXED (Phase 18-03)
+**Description:** No docs for queen-init, queen-read, queen-promote
+**Impact:** Users cannot discover wisdom feedback loop
+**Status:** FIXED — Phase 18-03: queen-commands.md created in .aether/docs/; help command sections key added with Queen Commands section listing all three commands with descriptions.
+
+### GAP-005: No validation of queen-read JSON output — FIXED (Phase 18-04)
+**Description:** queen-read builds JSON but doesn't validate before returning
+**Impact:** Could return malformed response
+**Status:** FIXED — Phase 18-04: Two validation gates added to queen-read: Gate 1 validates METADATA JSON before --argjson use; Gate 2 validates assembled result before json_ok. Both emit E_JSON_INVALID with actionable Try: suggestion.
+
+### GAP-006: Missing queen-* command documentation — FIXED (Phase 18-03)
+**Description:** Duplicate of GAP-004 - no documentation exists
+**Impact:** Commands are undiscoverable
+**Status:** FIXED — Phase 18-03: See GAP-004.
+
+### GAP-007: No error code standards documentation
+**Description:** Error codes exist but aren't documented
+**Impact:** Developers don't know which codes to use
+
+### GAP-008: Missing error path test coverage
+**Description:** Error handling paths not tested
+**Impact:** Bugs in error handling go undetected
+
+### GAP-009: context-update has no file locking — FIXED (Phase 16)
+**Description:** Race condition possible during concurrent context updates
+**Status:** FIXED — Fixed in Phase 16: context-update wraps all 11 action handlers in a single acquire_lock/release_lock pair. Lock is held for the duration of the update and released on both success and error paths via EXIT trap. force-unlock subcommand added for emergency recovery.
+**Impact:** Potential data corruption
+**Regression test:** `tests/bash/test-lock-lifecycle.sh` — test_context_update_acquires_lock, test_force_unlock_clears_locks
+
+### GAP-010: Missing error code standards documentation
+**Description:** Duplicate of GAP-007
+
+---
+
+## Workarounds Summary
+
+| Issue | Workaround |
+|-------|------------|
+| ~~Lock-related deadlocks (BUG-005, BUG-002)~~ | ~~Restart colony session~~ — FIXED in Phase 16 |
+| ~~Template path issue (ISSUE-004)~~ | ~~Use git clone instead of npm~~ — FIXED in Phase 20 |
+| Missing command docs (GAP-004) | Read source code directly |
+
+---
+
+*Generated from Oracle Research findings - 2026-02-15*

package/.aether/docs/pheromones.md

@@ -0,0 +1,205 @@
+# Pheromone Signals -- User Guide
+
+Pheromones are how you communicate with the colony. Instead of micromanaging individual ants, you emit chemical signals that influence their behavior. Signals have a TTL (time-to-live) and priority level. By default, signals last until the current phase completes.
+
+## How Pheromones Work
+
+- **You emit** signals using `/ant:focus`, `/ant:redirect`, `/ant:feedback`
+- **The colony also emits** signals automatically after builds (FEEDBACK after every phase, REDIRECT when error patterns recur)
+- **Signals expire** based on their `expires_at` field -- default is `"phase_end"` (lasts until phase completes)
+- **Optional TTL** -- use `--ttl` flag for wall-clock expiration (e.g., `--ttl 2h` for 2 hours)
+- **Priority levels** determine worker attention: high (REDIRECT), normal (FOCUS), low (FEEDBACK)
+- **Expired signals** are filtered on read -- no cleanup process needed
+
+Run `/ant:status` at any time to see all active pheromones.
+
+---
+
+## FOCUS -- Guide Attention
+
+**Command:** `/ant:focus "<area>"`
+**Priority:** normal | **Default expiration:** end of phase
+
+**What it does:** Tells the colony "pay extra attention here." Workers read FOCUS signals and weight this area higher in their task execution.
+
+### When to use FOCUS
+
+**Scenario 1: Steering the next build phase**
+You're about to run `/ant:build 3` and Phase 3 has tasks touching both the API layer and the database layer. You know the database schema is fragile:
+
+```
+/ant:focus "database schema -- handle migrations carefully"
+/ant:build 3
+```
+
+**Scenario 2: Time-limited focus**
+You want attention on auth for the next 2 hours, then let it fade:
+
+```
+/ant:focus "auth middleware correctness" --ttl 2h
+```
+
+**Scenario 3: Directing colonization**
+You're colonizing a new project and want the colonizer to pay special attention to testing:
+
+```
+/ant:focus "test framework and coverage gaps"
+/ant:colonize
+```
+
+### When NOT to use FOCUS
+
+- Don't stack 5+ FOCUS signals -- the colony can't prioritize everything
+- Don't FOCUS on things the colony already handles (like "write good code") -- be specific
+- Don't FOCUS after a phase completes if you're about to `/clear` context -- emit it fresh before the next build
+
+---
+
+## REDIRECT -- Warn Away
+
+**Command:** `/ant:redirect "<pattern to avoid>"`
+**Priority:** high | **Default expiration:** end of phase
+
+**What it does:** Acts as a hard constraint. Workers with high priority signal awareness will actively avoid the specified pattern. This is the strongest signal type.
+
+### When to use REDIRECT
+
+**Scenario 1: Preventing a known bad approach**
+Your project uses Next.js Edge Runtime, and you know `jsonwebtoken` doesn't work there:
+
+```
+/ant:redirect "Don't use jsonwebtoken -- use jose library instead (Edge Runtime compatible)"
+/ant:build 2
+```
+
+**Scenario 2: Long-lived constraint**
+You want to enforce a constraint across multiple phases (24 hours):
+
+```
+/ant:redirect "No global mutable state -- use request-scoped context" --ttl 1d
+```
+
+**Scenario 3: Steering away from a previous failure**
+Phase 1 tried to use synchronous file reads and caused performance issues:
+
+```
+/ant:redirect "No synchronous file I/O -- use async fs/promises"
+```
+
+### When NOT to use REDIRECT
+
+- Don't REDIRECT for preferences -- use it for hard constraints ("will break" not "I don't like")
+- Don't REDIRECT on vague patterns ("don't write bad code") -- be specific
+- Don't use REDIRECT when FOCUS would suffice
+
+---
+
+## FEEDBACK -- Adjust Course
+
+**Command:** `/ant:feedback "<observation>"`
+**Priority:** low | **Default expiration:** end of phase
+
+**What it does:** Provides gentle course correction. Unlike FOCUS (attention) or REDIRECT (avoidance), FEEDBACK adjusts the colony's approach based on your observations.
+
+### When to use FEEDBACK
+
+**Scenario 1: Mid-project course correction**
+After building Phase 2, you notice the code is over-engineered:
+
+```
+/ant:feedback "Code is too abstract -- prefer simple, direct implementations over clever abstractions"
+```
+
+**Scenario 2: Positive reinforcement**
+Phase 3 produced clean, well-tested code. You want more of the same:
+
+```
+/ant:feedback "Great test coverage in Phase 3 -- maintain this level of testing"
+```
+
+**Scenario 3: Quality emphasis shift**
+You're noticing the code lacks error handling:
+
+```
+/ant:feedback "Need more error handling -- happy path works but edge cases are unhandled"
+```
+
+### When NOT to use FEEDBACK
+
+- Don't use FEEDBACK for hard constraints -- that's REDIRECT's job
+- Don't use FEEDBACK before the colony has produced anything
+- Don't emit multiple conflicting FEEDBACK signals
+
+---
+
+## Auto-Emitted Pheromones
+
+The colony emits pheromones automatically during builds. You don't need to manage these:
+
+- **FEEDBACK after every phase:** build.md (Step 7b) emits a FEEDBACK pheromone summarizing what worked and what failed
+- **REDIRECT on error patterns:** If errors.json has recurring flagged patterns, build.md and continue.md auto-emit REDIRECT signals
+- **FEEDBACK from global learnings:** When colonizing a new project, colonize.md injects relevant global learnings as FEEDBACK pheromones
+
+Auto-emitted signals have their `source` field set to indicate origin: `"worker:builder"`, `"worker:continue"`, or `"global:inject"`.
+
+---
+
+## Signal Combinations
+
+Pheromones combine. Workers check all active signals and respond accordingly:
+
+| Combination | Effect |
+|-------------|--------|
+| FOCUS + FEEDBACK | Workers concentrate on the focused area and adjust approach based on feedback |
+| FOCUS + REDIRECT | Workers prioritize the focused area while avoiding the redirected pattern |
+| FEEDBACK + REDIRECT | Workers adjust approach (feedback) and avoid specific patterns (redirect) |
+| All three | Full steering: attention (FOCUS), avoidance (REDIRECT), and adjustment (FEEDBACK) |
+
+**Priority processing:** Workers check high priority signals first, then normal, then low.
+
+---
+
+## TTL Options
+
+By default, signals expire at phase end (`expires_at: "phase_end"`). Use `--ttl` flag for wall-clock expiration:
+
+```
+/ant:focus "database schema"              # expires at phase end
+/ant:focus "API layer" --ttl 2h           # expires in 2 hours
+/ant:redirect "No JWT" --ttl 1d           # expires in 1 day
+/ant:feedback "keep tests simple" --ttl 30m  # expires in 30 minutes
+```
+
+**Duration format:** `<number><unit>` where unit is:
+- `m` = minutes (e.g., `30m`)
+- `h` = hours (e.g., `2h`)
+- `d` = days (e.g., `1d`)
+
+---
+
+## Pause-Aware TTL
+
+When the colony is paused (`paused_at` timestamp recorded):
+
+- **Wall-clock TTLs** are extended by the pause duration on resume
+- **Phase-scoped signals** (`expires_at: "phase_end"`) are unaffected by pause
+
+This ensures signals don't expire while you're away from the project.
+
+---
+
+## Quick Reference
+
+| Signal | Command | Priority | Default Expiration | Use for |
+|--------|---------|----------|-------------------|---------|
+| FOCUS | `/ant:focus "<area>"` | normal | phase end | "Pay attention to this" |
+| REDIRECT | `/ant:redirect "<avoid>"` | high | phase end | "Don't do this" |
+| FEEDBACK | `/ant:feedback "<note>"` | low | phase end | "Adjust based on this" |
+
+**Rule of thumb:**
+- Before a build: FOCUS + REDIRECT to steer
+- After a build: FEEDBACK to adjust
+- For hard constraints: REDIRECT (high priority)
+- For gentle nudges: FEEDBACK (low priority)
+- For attention: FOCUS (normal priority)
+- For short-lived signals: use `--ttl` flag

package/.aether/docs/queen-commands.md

@@ -0,0 +1,97 @@
+# Queen Commands Reference
+
+The queen-* commands manage the QUEEN.md wisdom file — a persistent cross-colony knowledge base that accumulates philosophies, patterns, redirects, stack wisdom, and decrees across sessions.
+
+For the QUEEN.md file format and wisdom feedback loop, see [QUEEN-SYSTEM.md](./QUEEN-SYSTEM.md).
+
+## Commands
+
+### queen-init
+
+**Purpose:** Initialize a new QUEEN.md from the system template.
+
+**Usage:**
+```bash
+bash .aether/aether-utils.sh queen-init
+```
+
+**Returns:** JSON with creation status, file path, and template source.
+
+**Example output:**
+```json
+{"ok":true,"result":{"created":true,"path":".aether/docs/QUEEN.md","source":"~/.aether/system/docs/QUEEN.md.template"}}
+```
+
+**Behavior:**
+- If QUEEN.md already exists, returns `{"created":false}` without overwriting
+- Searches for template in: hub system path, then local .aether/templates/
+- Creates `.aether/docs/` directory if it doesn't exist
+
+---
+
+### queen-read
+
+**Purpose:** Read QUEEN.md wisdom as structured JSON for worker priming.
+
+**Usage:**
+```bash
+bash .aether/aether-utils.sh queen-read
+```
+
+**Returns:** JSON with metadata, wisdom sections, and priming flags.
+
+**Example output:**
+```json
+{"ok":true,"result":{"metadata":{...},"wisdom":{"philosophies":"...","patterns":"...","redirects":"...","stack_wisdom":"...","decrees":"..."},"priming":{"has_philosophies":true,...}}}
+```
+
+**Behavior:**
+- Extracts METADATA JSON block from `<!-- METADATA ... -->` comment
+- Parses each wisdom section (Philosophies, Patterns, Redirects, Stack Wisdom, Decrees)
+- Returns priming flags indicating which sections have content
+- Returns E_JSON_INVALID if METADATA block contains malformed JSON
+- Returns E_FILE_NOT_FOUND if QUEEN.md doesn't exist
+
+---
+
+### queen-promote
+
+**Purpose:** Promote a validated learning to QUEEN.md wisdom.
+
+**Usage:**
+```bash
+bash .aether/aether-utils.sh queen-promote <type> <content> <colony_name>
+```
+
+**Arguments:**
+
+| Argument | Required | Description |
+|----------|----------|-------------|
+| type | Yes | Wisdom category: `philosophy`, `pattern`, `redirect`, `stack`, `decree` |
+| content | Yes | The wisdom text to add |
+| colony_name | Yes | Name of the colony contributing the wisdom |
+
+**Returns:** JSON confirming the promotion with details.
+
+**Behavior:**
+- Appends the wisdom entry to the appropriate section in QUEEN.md
+- Includes attribution (colony name) and timestamp
+- Updates the METADATA block's stats
+
+---
+
+## For Contributors
+
+The queen commands are part of the colony lifecycle:
+
+1. **Colony startup:** `/ant:colonize` calls `queen-init` to ensure QUEEN.md exists
+2. **Worker priming:** `/ant:swarm` calls `queen-read` to inject wisdom into worker prompts
+3. **Colony end:** `/ant:seal` can call `queen-promote` to persist learnings
+
+### Adding a New Queen Command
+
+1. Add the case block in `aether-utils.sh` (alongside existing `queen-*` blocks)
+2. Add it to the flat `commands` array in the `help)` case block
+3. Add it to the "Queen Commands" section in help's `sections` JSON
+4. Update this file with usage documentation
+5. Add tests in `tests/bash/test-aether-utils.sh`

package/.aether/exchange/colony-registry.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<colony-registry xmlns="http://aether.colony/schemas/registry/1.0"
+                 version="1.0.0"
+                 generated_at="2026-02-18T01:48:47Z">
+  <colony id="Remove Aether developing Aether self-reference while preserving findings" status="active" created_at="2026-02-15T15:59:13Z">
+    <name>Remove Aether developing Aether self-reference while preserving findings</name>
+  </colony>
+  <colony id="v1.1 Bug Fixes &amp; Update System Repair" status="active" created_at="unknown">
+    <name>v1.1 Bug Fixes &amp; Update System Repair</name>
+  </colony>
+</colony-registry>