aether-colony 5.3.2 → 5.4.0

package/.opencode/commands/ant/continue.md

@@ -37,7 +37,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 Bash tool: `aether load-state`
 
 If successful and goal is not null:
 1. Extract current_phase from state
@@ -52,7 +52,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: `aether unload-state` to release lock.
 
 **Error handling:**
 - If E_FILE_NOT_FOUND: "No colony initialized. Run /ant:init first." and stop
@@ -78,7 +78,7 @@ If `state != "EXECUTING"`:
 
 Run:
 ```bash
-survey_check=$(bash .aether/aether-utils.sh survey-verify 2>/dev/null || true)
+survey_check=$(aether survey-verify 2>/dev/null || true)
 survey_docs=$(ls -1 .aether/data/survey/*.md 2>/dev/null | wc -l | tr -d ' ')
 survey_latest=$(ls -t .aether/data/survey/*.md 2>/dev/null | head -1)
 if [[ -n "$survey_latest" ]]; then
@@ -187,7 +187,7 @@ Continue to Phase 5: Secrets Scan.
 3. **If spawning Probe:**
 
    a. Generate Probe name and dispatch:
-   Run using the Bash tool with description "Generating Probe name...": `probe_name=$(bash .aether/aether-utils.sh generate-ant-name "probe") && bash .aether/aether-utils.sh spawn-log "Queen" "probe" "$probe_name" "Coverage improvement: ${coverage_percent}%" && echo "{\"name\":\"$probe_name\"}"`
+   Run using the Bash tool with description "Generating Probe name...": `probe_name=$(aether generate-ant-name --caste "probe") && aether spawn-log --name "Queen" --caste "probe" --id "$probe_name" --description "Coverage improvement: ${coverage_percent}%" && echo "{\"name\":\"$probe_name\"}"`
 
    b. Display:
    ```
@@ -217,10 +217,10 @@ Continue to Phase 5: Secrets Scan.
    f. Parse Probe JSON output and log completion:
    Extract: `tests_added`, `coverage.lines`, `coverage.branches`, `coverage.functions`, `edge_cases_discovered`
 
-   Run using the Bash tool with description "Logging Probe completion...": `bash .aether/aether-utils.sh spawn-complete "$probe_name" "completed" "{probe_summary}"`
+   Run using the Bash tool with description "Logging Probe completion...": `aether spawn-complete --id "$probe_name" --status "completed" --summary "{probe_summary}"`
 
    g. Log findings to midden:
-   Run using the Bash tool with description "Logging Probe findings to midden...": `bash .aether/aether-utils.sh midden-write "coverage" "Probe generated tests, coverage: ${coverage_lines}%/${coverage_branches}%/${coverage_functions}%" "probe"`
+   Run using the Bash tool with description "Logging Probe findings to midden...": `aether midden-write "coverage" "Probe generated tests, coverage: ${coverage_lines}%/${coverage_branches}%/${coverage_functions}%" "probe"`
 
 4. **NON-BLOCKING continuation:**
    Display Probe findings summary:
@@ -369,8 +369,8 @@ The phase will NOT advance until spawning occurs.
 **CRITICAL:** Do NOT proceed to Step 1.7. Do NOT advance the phase.
 Log the violation:
 ```bash
-bash .aether/aether-utils.sh activity-log "BLOCKED" "colony" "Spawn gate failed: {task_count} tasks, 0 spawns"
-bash .aether/aether-utils.sh error-flag-pattern "no-spawn-violation" "Prime Worker completed phase without spawning specialists" "critical"
+aether activity-log "BLOCKED" "colony" "Spawn gate failed: {task_count} tasks, 0 spawns"
+aether error-flag-pattern "no-spawn-violation" "Prime Worker completed phase without spawning specialists" "critical"
 ```
 
 **HARD REJECTION - If watcher_count == 0 (no testing separation):**
@@ -411,7 +411,7 @@ 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}"
+aether check-antipattern "{file_path}"
 ```
 
 Run for each file in `files_created` and `files_modified` from Prime Worker output.
@@ -520,7 +520,7 @@ If no CRITICAL issues, continue to Step 1.7.1.
    Run using the Bash tool with description "Establishing test baseline...": `test_output_before=$(npm test 2>&1 || echo "TEST_FAILED") && tests_passing_before=$(echo "$test_output_before" | grep -oE '[0-9]+ passing' | grep -oE '[0-9]+' || echo "0") && echo "Baseline: $tests_passing_before tests passing"`
 
    b. **Generate Weaver name and dispatch:**
-   Run using the Bash tool with description "Generating Weaver name...": `weaver_name=$(bash .aether/aether-utils.sh generate-ant-name "weaver") && bash .aether/aether-utils.sh spawn-log "Queen" "weaver" "$weaver_name" "Proactive refactoring" && echo "{\"name\":\"$weaver_name\"}"`
+   Run using the Bash tool with description "Generating Weaver name...": `weaver_name=$(aether generate-ant-name --caste "weaver") && aether spawn-log --name "Queen" --caste "weaver" --id "$weaver_name" --description "Proactive refactoring" && echo "{\"name\":\"$weaver_name\"}"`
 
    c. **Display:**
    ```
@@ -566,10 +566,10 @@ If no CRITICAL issues, continue to Step 1.7.1.
    ```
 
    g. **Log completion:**
-   Run using the Bash tool with description "Logging Weaver completion...": `bash .aether/aether-utils.sh spawn-complete "$weaver_name" "$weaver_status" "Refactoring $weaver_status"`
+   Run using the Bash tool with description "Logging Weaver completion...": `aether spawn-complete --id "$weaver_name" --status "$weaver_status" --summary "Refactoring $weaver_status"`
 
    h. **Log to midden:**
-   Run using the Bash tool with description "Logging refactoring activity to midden...": `bash .aether/aether-utils.sh midden-write "refactoring" "Weaver refactored files, complexity before/after: ${complexity_before}/${complexity_after}" "weaver"`
+   Run using the Bash tool with description "Logging refactoring activity to midden...": `aether midden-write "refactoring" "Weaver refactored files, complexity before/after: ${complexity_before}/${complexity_after}" "weaver"`
 
 5. **Display completion:**
    ```
@@ -598,7 +598,7 @@ Continue to Step 1.9.
 **If package.json exists:**
 
 1. Generate Gatekeeper name and log spawn:
-Run using the Bash tool with description "Generating Gatekeeper name...": `gatekeeper_name=$(bash .aether/aether-utils.sh generate-ant-name "gatekeeper") && bash .aether/aether-utils.sh spawn-log "Queen" "gatekeeper" "$gatekeeper_name" "Supply chain security audit" && echo "{\"name\":\"$gatekeeper_name\"}"`
+Run using the Bash tool with description "Generating Gatekeeper name...": `gatekeeper_name=$(aether generate-ant-name --caste "gatekeeper") && aether spawn-log --name "Queen" --caste "gatekeeper" --id "$gatekeeper_name" --description "Supply chain security audit" && echo "{\"name\":\"$gatekeeper_name\"}"`
 
 2. Display:
 ```
@@ -620,7 +620,7 @@ Gatekeeper mission: Perform supply chain security audit on this codebase.
 5. Parse Gatekeeper JSON output and log completion:
 Extract: `security.critical`, `security.high`, `status`
 
-Run using the Bash tool with description "Logging Gatekeeper completion...": `bash .aether/aether-utils.sh spawn-complete "$gatekeeper_name" "completed" "{gatekeeper_summary}"`
+Run using the Bash tool with description "Logging Gatekeeper completion...": `aether spawn-complete --id "$gatekeeper_name" --status "completed" --summary "{gatekeeper_summary}"`
 
 **Gate Decision Logic:**
 
@@ -648,7 +648,7 @@ Gatekeeper: {high_count} high-severity issues found
 Security warnings logged to midden for later review.
 Proceeding with caution...
 ```
-Run using the Bash tool with description "Logging high-severity warnings...": `bash .aether/aether-utils.sh midden-write "security" "High CVEs found: $high_count" "gatekeeper"`
+Run using the Bash tool with description "Logging high-severity warnings...": `aether midden-write "security" "High CVEs found: $high_count" "gatekeeper"`
 Continue to Step 1.9.
 
 - **If clean (no critical or high):**
@@ -662,7 +662,7 @@ Continue to Step 1.9.
 **Code quality audit -- runs on every `/ant:continue` for consistent coverage.**
 
 1. Generate Auditor name and log spawn:
-Run using the Bash tool with description "Generating Auditor name...": `auditor_name=$(bash .aether/aether-utils.sh generate-ant-name "auditor") && bash .aether/aether-utils.sh spawn-log "Queen" "auditor" "$auditor_name" "Code quality audit" && echo "{\"name\":\"$auditor_name\"}"`
+Run using the Bash tool with description "Generating Auditor name...": `auditor_name=$(aether generate-ant-name --caste "auditor") && aether spawn-log --name "Queen" --caste "auditor" --id "$auditor_name" --description "Code quality audit" && echo "{\"name\":\"$auditor_name\"}"`
 
 2. Display:
 ```
@@ -687,7 +687,7 @@ Auditor mission: Perform comprehensive code quality audit on this codebase.
 6. Parse Auditor JSON output and log completion:
 Extract: `findings.critical`, `findings.high`, `findings.medium`, `findings.low`, `findings.info`, `overall_score`, `dimensions_audited`
 
-Run using the Bash tool with description "Logging Auditor completion...": `bash .aether/aether-utils.sh spawn-complete "$auditor_name" "completed" "{auditor_summary}"`
+Run using the Bash tool with description "Logging Auditor completion...": `aether spawn-complete --id "$auditor_name" --status "completed" --summary "{auditor_summary}"`
 
 **Gate Decision Logic:**
 
@@ -709,7 +709,7 @@ Critical Findings:
 
 The phase will NOT advance with critical quality issues.
 ```
-Run using the Bash tool with description "Logging critical quality block...": `bash .aether/aether-utils.sh error-flag-pattern "auditor-critical-findings" "$critical_count critical quality issues found" "critical"`
+Run using the Bash tool with description "Logging critical quality block...": `aether error-flag-pattern "auditor-critical-findings" "$critical_count critical quality issues found" "critical"`
 **CRITICAL:** Do NOT proceed to Step 1.10. Stop here.
 
 - **Else if `overall_score < 60`:**
@@ -727,7 +727,7 @@ Required Actions:
 
 The phase will NOT advance with quality score below 60.
 ```
-Run using the Bash tool with description "Logging quality score block...": `bash .aether/aether-utils.sh error-flag-pattern "auditor-quality-score" "Score $overall_score below threshold 60" "critical"`
+Run using the Bash tool with description "Logging quality score block...": `aether error-flag-pattern "auditor-quality-score" "Score $overall_score below threshold 60" "critical"`
 **CRITICAL:** Do NOT proceed to Step 1.10. Stop here.
 
 - **Else if `findings.high > 0`:**
@@ -740,7 +740,7 @@ Auditor: Quality score {overall_score}/100 -- PASSED with warnings
 Quality warnings logged to midden for later review.
 Proceeding with caution...
 ```
-Run using the Bash tool with description "Logging high-quality warnings...": `bash .aether/aether-utils.sh midden-write "quality" "High severity issues: $high_count (score: $overall_score)" "auditor"`
+Run using the Bash tool with description "Logging high-quality warnings...": `aether midden-write "quality" "High severity issues: $high_count (score: $overall_score)" "auditor"`
 Continue to Step 1.10.
 
 - **If clean (score >= 60, no critical):**
@@ -786,7 +786,7 @@ The phase will NOT advance with fabricated metrics.
 
 **CRITICAL:** Do NOT proceed. Log the violation:
 ```bash
-bash .aether/aether-utils.sh error-flag-pattern "fabricated-tdd" "Prime Worker reported TDD metrics without creating test files" "critical"
+aether error-flag-pattern "fabricated-tdd" "Prime Worker reported TDD metrics without creating test files" "critical"
 ```
 
 **If tests_added == 0 or test files exist matching claims:**
@@ -832,7 +832,7 @@ Please describe the issues so they can be addressed:
 
 Use AskUserQuestion to get issue details. Log to errors.records:
 ```bash
-bash .aether/aether-utils.sh error-add "runtime" "critical" "{user_description}" {phase}
+aether error-add "runtime" "critical" "{user_description}" {phase}
 ```
 
 Do NOT proceed to Step 2.
@@ -868,12 +868,12 @@ Continue to Step 1.12.
 
 First, auto-resolve any flags eligible for resolution now that verification has passed:
 ```bash
-bash .aether/aether-utils.sh flag-auto-resolve "build_pass"
+aether flag-auto-resolve "build_pass"
 ```
 
 Then check for remaining blocking flags:
 ```bash
-bash .aether/aether-utils.sh flag-check-blockers {current_phase}
+aether flag-check-blockers {current_phase}
 ```
 
 Parse result for `blockers`, `issues`, and `notes` counts.
@@ -975,7 +975,7 @@ Update COLONY_STATE.json:
 
    Run using the Bash tool with description "Recording learning observations...":
    ```bash
-   colony_name=$(bash .aether/aether-utils.sh colony-name 2>/dev/null | jq -r '.result.name // ""')
+   colony_name=$(aether colony-name 2>/dev/null | jq -r '.result.name // ""')
    [[ -z "$colony_name" ]] && colony_name="unknown"
 
    # Get learnings from the current phase
@@ -985,7 +985,7 @@ Update COLONY_STATE.json:
      echo "$current_phase_learnings" | jq -r '.learnings[]?.claim // empty' 2>/dev/null | while read -r claim; do
        if [[ -n "$claim" ]]; then
          # Default wisdom_type to "pattern" (threshold: 3 observations)
-         bash .aether/aether-utils.sh memory-capture "learning" "$claim" "pattern" "worker:continue" 2>/dev/null || true
+         aether memory-capture "learning" "$claim" "pattern" "worker:continue" 2>/dev/null || true
        fi
      done
      echo "Recorded observations for threshold tracking"
@@ -1061,7 +1061,7 @@ 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`
+Run using the Bash tool with description "Validating colony state...": `aether validate-state colony`
 
 ### Step 2.1: Auto-Emit Phase Pheromones (SILENT)
 
@@ -1079,7 +1079,7 @@ After learning extraction completes in Step 2, auto-emit a FEEDBACK signal summa
 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" \
+aether pheromone-write --type FEEDBACK --content "$phase_feedback" \
   --strength 0.6 \
   --source "worker:continue" \
   --reason "Auto-emitted on phase advance: captures what worked and what was learned" \
@@ -1099,7 +1099,7 @@ flagged_patterns=$(jq -r '.errors.flagged_patterns[]? | select(.count >= 2) | .p
 For each pattern returned by the above query, emit a REDIRECT signal:
 
 ```bash
-bash .aether/aether-utils.sh pheromone-write REDIRECT "$pattern_text" \
+aether pheromone-write --type REDIRECT --content "$pattern_text" \
   --strength 0.7 \
   --source "system" \
   --reason "Auto-emitted: error pattern recurred across 2+ phases" \
@@ -1109,7 +1109,7 @@ bash .aether/aether-utils.sh pheromone-write REDIRECT "$pattern_text" \
 Also capture each recurring pattern as a resolution candidate:
 
 ```bash
-bash .aether/aether-utils.sh memory-capture \
+aether memory-capture \
   "resolution" \
   "$pattern_text" \
   "pattern" \
@@ -1122,7 +1122,7 @@ If `errors.flagged_patterns` doesn't exist or is empty, skip silently.
 
 After auto-emission, expire all signals with `expires_at == "phase_end"`:
 
-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`
+Run using the Bash tool with description "Maintaining pheromone memory...": `aether pheromone-expire --phase-end-only 2>/dev/null && aether eternal-init 2>/dev/null`
 
 ### Step 2.1.5: Check for Promotion Proposals
 
@@ -1132,7 +1132,7 @@ After extracting learnings, check for observations that have met promotion thres
 
 1. **Check for proposals:**
    ```bash
-   proposals=$(bash .aether/aether-utils.sh learning-check-promotion 2>/dev/null || echo '{"proposals":[]}')
+   proposals=$(aether learning-check-promotion 2>/dev/null || echo '{"proposals":[]}')
    proposal_count=$(echo "$proposals" | jq '.proposals | length')
    ```
 
@@ -1142,7 +1142,7 @@ After extracting learnings, check for observations that have met promotion thres
 
    ```bash
    if [[ "$proposal_count" -gt 0 ]]; then
-     bash .aether/aether-utils.sh learning-approve-proposals
+     aether learning-approve-proposals
    fi
    # If no proposals, silently skip without notice
    ```
@@ -1211,7 +1211,7 @@ If no `CHANGELOG.md` exists, `changelog-append` creates one automatically.
 **Step 2.3.1: Collect plan data**
 
 ```bash
-bash .aether/aether-utils.sh changelog-collect-plan-data "{phase_identifier}" "{plan_number}"
+aether changelog-collect-plan-data "{phase_identifier}" "{plan_number}"
 ```
 
 Parse the returned JSON to extract `files`, `decisions`, `worked`, and `requirements` arrays.
@@ -1227,7 +1227,7 @@ If the command fails (e.g., no plan file found), fall back to collecting data ma
 **Step 2.3.2: Append changelog entry**
 
 ```bash
-bash .aether/aether-utils.sh changelog-append \
+aether changelog-append \
   "$(date +%Y-%m-%d)" \
   "{phase_identifier}" \
   "{plan_number}" \
@@ -1249,7 +1249,7 @@ After the phase is advanced and changelog updated, suggest a commit to preserve
 
 1. **Generate the commit message:**
 ```bash
-bash .aether/aether-utils.sh generate-commit-message "milestone" {phase_id} "{phase_name}" "{one_line_summary}"
+aether generate-commit-message --type "milestone" --phase {phase_id} --subject "{phase_name}" "{one_line_summary}"
 ```
 Parse the returned JSON to extract `message` and `files_changed`.
 
@@ -1350,18 +1350,18 @@ After phase advancement is complete, update `.aether/CONTEXT.md`:
 
 **Log the activity:**
 ```bash
-bash .aether/aether-utils.sh context-update activity "continue" "Phase {prev_id} completed, advanced to {next_id}" "---"
+aether context-update activity "continue" "Phase {prev_id} completed, advanced to {next_id}" "---"
 ```
 
 **Update the phase:**
 ```bash
-bash .aether/aether-utils.sh context-update update-phase {next_id} "{next_phase_name}" "YES" "Phase advanced, ready to build"
+aether context-update update-phase {next_id} "{next_phase_name}" "YES" "Phase advanced, ready to build"
 ```
 
 **Log any decisions from this session:**
 If any architectural decisions were made during verification, also run:
 ```bash
-bash .aether/aether-utils.sh context-update decision "{decision_description}" "{rationale}" "Queen"
+aether context-update decision "{decision_description}" "{rationale}" "Queen"
 ```
 
 ### Step 2.7: Project Completion
@@ -1433,4 +1433,4 @@ Output:
 
 Update the session tracking file to enable `/ant:resume` after context clear:
 
-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}"`
+Run using the Bash tool with description "Saving session state...": `aether session-update --command "/ant:continue" --worker "/ant:build {next_id}" --summary "Phase {prev_id} completed, advanced to Phase {next_id}"`

package/.opencode/commands/ant/council.md

@@ -31,7 +31,7 @@ When `--deliberate "<proposal>"` is passed, run a structured Advocate/Challenger
 
 Run using the Bash tool with description "Checking deliberation budget...":
 ```bash
-bash .aether/aether-utils.sh council-budget-check
+aether council-budget-check
 ```
 
 Parse result. If `allowed` is `false`:
@@ -47,7 +47,7 @@ Stop here.
 
 Run using the Bash tool with description "Opening deliberation...":
 ```bash
-bash .aether/aether-utils.sh council-deliberate --proposal "<proposal>"
+aether council-deliberate --proposal "<proposal>"
 ```
 
 Capture `deliberation_id` from `result.id`.
@@ -71,7 +71,7 @@ Spawn an Advocate scout to argue **in favor** of the proposal.
 
 Record the argument:
 ```bash
-bash .aether/aether-utils.sh council-advocate \
+aether council-advocate \
   --deliberation-id "<deliberation_id>" \
   --argument "<advocate_argument>"
 ```
@@ -90,7 +90,7 @@ Spawn a Challenger scout to argue **against** the proposal.
 
 Record the argument:
 ```bash
-bash .aether/aether-utils.sh council-challenger \
+aether council-challenger \
   --deliberation-id "<deliberation_id>" \
   --argument "<challenger_argument>"
 ```
@@ -109,7 +109,7 @@ Spawn a Sage scout to synthesize both positions and provide a recommendation.
 
 Record the sage synthesis:
 ```bash
-bash .aether/aether-utils.sh council-sage \
+aether council-sage \
   --deliberation-id "<deliberation_id>" \
   --synthesis "<synthesis>" \
   --recommendation "<recommendation>"

package/.opencode/commands/ant/data-clean.md

@@ -23,7 +23,7 @@ You are the **Queen Ant Colony**. Run the data cleaner to scan for and remove te
 
 Run using the Bash tool with description "Scanning colony data for test artifacts...":
 ```bash
-bash .aether/aether-utils.sh data-clean --dry-run
+aether data-clean --dry-run
 ```
 
 Display the output to the user. This shows artifact counts per data file without modifying anything.
@@ -52,7 +52,7 @@ If user says no, display "No changes made." and skip to Step 5.
 
 If user confirmed, run using the Bash tool with description "Removing test artifacts...":
 ```bash
-bash .aether/aether-utils.sh data-clean --confirm
+aether data-clean --confirm
 ```
 
 ### Step 4: Summary

package/.opencode/commands/ant/dream.md

@@ -228,7 +228,7 @@ Colony status: /ant:status
 
 
 ```bash
-bash .aether/aether-utils.sh activity-log "DREAM" "Dreamer" "Dream session: {N} observations, {concerns} concerns, {pheromones} pheromone suggestions"
+aether activity-log "DREAM" "Dreamer" "Dream session: {N} observations, {concerns} concerns, {pheromones} pheromone suggestions"
 ```
 
 

package/.opencode/commands/ant/entomb.md

@@ -194,7 +194,7 @@ version=$(jq -r '.version // "3.0"' .aether/data/COLONY_STATE.json)
 
 Create the chamber:
 ```bash
-bash .aether/aether-utils.sh chamber-create \
+aether chamber-create \
   ".aether/chambers/{chamber_name}" \
   ".aether/data/COLONY_STATE.json" \
   "{goal}" \
@@ -212,7 +212,7 @@ Export combined XML archive to the chamber. This is a HARD REQUIREMENT — entom
 
 ```bash
 chamber_dir=".aether/chambers/$chamber_name"
-xml_result=$(bash .aether/aether-utils.sh colony-archive-xml "$chamber_dir/colony-archive.xml" 2>&1)
+xml_result=$(aether colony-archive-xml --output "$chamber_dir/colony-archive.xml" 2>&1)
 xml_ok=$(echo "$xml_result" | jq -r '.ok // false' 2>/dev/null)
 
 if [[ "$xml_ok" != "true" ]]; then
@@ -248,7 +248,7 @@ done
 
 Run verification:
 ```bash
-bash .aether/aether-utils.sh chamber-verify ".aether/chambers/{chamber_name}"
+aether chamber-verify --path ".aether/chambers/{chamber_name}"
 ```
 
 If verification fails, display error and stop:

package/.opencode/commands/ant/export-signals.md

@@ -29,7 +29,7 @@ Parse `$normalized_args`:
 
 Run using the Bash tool with description "Exporting pheromone signals to XML...":
 ```bash
-bash .aether/aether-utils.sh pheromone-export-xml "<output_path>"
+aether pheromone-export-xml --output "<output_path>"
 ```
 
 Parse the returned JSON:

package/.opencode/commands/ant/feedback.md

@@ -70,8 +70,8 @@ Write COLONY_STATE.json.
 
 **Write pheromone signal and update context:**
 ```bash
-bash .aether/aether-utils.sh pheromone-write FEEDBACK "$normalized_args" --strength 0.7 --reason "User feedback guidance" 2>/dev/null || true
-bash .aether/aether-utils.sh context-update constraint feedback "$normalized_args" "user" 2>/dev/null || true
+aether pheromone-write --type FEEDBACK --content "$normalized_args" --strength 0.7 --reason "User feedback guidance" 2>/dev/null || true
+aether context-update --section constraint --key feedback --content "$normalized_args" "user" 2>/dev/null || true
 ```
 
 ### Step 3: Confirm

package/.opencode/commands/ant/flag.md

@@ -57,7 +57,7 @@ Stop here.
 
 Run:
 ```bash
-bash .aether/aether-utils.sh flag-add "{type}" "{title}" "{description}" "manual" {phase_or_null}
+aether flag-add --severity "{type}" --title "{title}" --description "{description}" --source "manual" --phase {phase_or_null}
 ```
 
 Parse the result for the flag ID.

package/.opencode/commands/ant/flags.md

@@ -39,7 +39,7 @@ Examples:
 If `--resolve` was provided:
 
 ```bash
-bash .aether/aether-utils.sh flag-resolve "{flag_id}" "{resolution_message}"
+aether flag-resolve --id "{flag_id}" --message "{resolution_message}"
 ```
 Output:
 ```
@@ -54,7 +54,7 @@ Stop here.
 If `--ack` was provided:
 
 ```bash
-bash .aether/aether-utils.sh flag-acknowledge "{flag_id}"
+aether flag-acknowledge --id "{flag_id}"
 ```
 Output:
 ```
@@ -71,7 +71,7 @@ Stop here.
 Run:
 
 ```bash
-bash .aether/aether-utils.sh flag-list {options}
+aether flag-list {options}
 ```
 
 Parse result for flags array.

package/.opencode/commands/ant/focus.md

@@ -46,8 +46,8 @@ Write constraints.json.
 
 **Write pheromone signal and update context:**
 ```bash
-bash .aether/aether-utils.sh pheromone-write FOCUS "$normalized_args" --strength 0.8 --reason "User directed colony attention" 2>/dev/null || true
-bash .aether/aether-utils.sh context-update constraint focus "$normalized_args" "user" 2>/dev/null || true
+aether pheromone-write --type FOCUS --content "$normalized_args" --strength 0.8 --reason "User directed colony attention" 2>/dev/null || true
+aether context-update --section constraint --key focus --content "$normalized_args" "user" 2>/dev/null || true
 ```
 
 ### Step 3: Confirm

package/.opencode/commands/ant/import-signals.md

@@ -42,7 +42,7 @@ Verify the XML file exists. If not -> "File not found: <path>", stop.
 
 Run using the Bash tool with description "Importing pheromone signals from XML...":
 ```bash
-bash .aether/aether-utils.sh pheromone-import-xml "<xml_path>" "<colony_prefix>"
+aether pheromone-import-xml --input "<xml_path>" --colony "<colony_prefix>"
 ```
 
 Parse the returned JSON: