aether-colony 2.0.0

package/runtime/verification-loop.md

@@ -0,0 +1,159 @@
+# Verification Loop Discipline
+
+## Purpose
+
+A comprehensive 6-phase quality check that runs before phase advancement or PR creation. Complements the core Verification Discipline (evidence before claims) with systematic quality gates.
+
+## When to Invoke
+
+- After completing a phase (via `/ant:continue`)
+- Before creating a PR
+- After significant refactoring
+- After major changes (every 15 minutes in long sessions)
+
+## The 6 Phases
+
+### Phase 1: Build Verification
+
+```bash
+# Detect and run build command
+npm run build 2>&1 | tail -30
+# OR: pnpm build, cargo build, go build ./..., python -m build
+```
+
+**Gate:** If build fails, STOP. Fix before continuing.
+
+### Phase 2: Type Check
+
+```bash
+# TypeScript
+npx tsc --noEmit 2>&1 | head -30
+
+# Python
+pyright . 2>&1 | head -30
+
+# Go
+go vet ./... 2>&1 | head -30
+```
+
+**Gate:** Report all type errors. Fix critical ones before continuing.
+
+### Phase 3: Lint Check
+
+```bash
+# JavaScript/TypeScript
+npm run lint 2>&1 | head -30
+
+# Python
+ruff check . 2>&1 | head -30
+
+# Go
+golangci-lint run 2>&1 | head -30
+```
+
+**Gate:** Report warnings. Fix errors before continuing.
+
+### Phase 4: Test Suite
+
+```bash
+# Run tests with coverage
+npm run test -- --coverage 2>&1 | tail -50
+
+# Python
+pytest --cov=. 2>&1 | tail -50
+```
+
+Report:
+- Total tests: X
+- Passed: X
+- Failed: X
+- Coverage: X% (target: 80%+)
+
+**Gate:** If tests fail, STOP. Fix before continuing.
+
+### 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\|TODO.*REMOVE" --include="*.ts" --include="*.tsx" --include="*.js" src/ 2>/dev/null | head -10
+```
+
+Report:
+- Potential secrets: X
+- Debug artifacts: X
+
+**Gate:** Fix exposed secrets immediately. Debug artifacts are warnings.
+
+### Phase 6: Diff Review
+
+```bash
+# Show what changed
+git diff --stat
+git diff HEAD~1 --name-only
+```
+
+Review each changed file for:
+- Unintended changes (files touched that shouldn't be)
+- Missing error handling
+- Potential edge cases
+- Leftover debugging code
+
+**Gate:** Review before advancing. Flag concerns.
+
+## Verification Report Format
+
+After running all phases, produce a verification report:
+
+```
+VERIFICATION LOOP REPORT
+========================
+
+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, Z% coverage)
+Phase 5: Security   [PASS/FAIL] (X issues)
+Phase 6: Diff       [X files changed]
+
+Overall: [READY/NOT READY] for advancement
+
+Issues to Fix:
+1. ...
+2. ...
+```
+
+## Command Detection
+
+Detect project type and commands automatically:
+
+| File | Build | Test | Types | Lint |
+|------|-------|------|-------|------|
+| `package.json` | `npm run build` | `npm test` | `npx tsc --noEmit` | `npm run lint` |
+| `Cargo.toml` | `cargo build` | `cargo test` | (built-in) | `cargo clippy` |
+| `go.mod` | `go build ./...` | `go test ./...` | `go vet ./...` | `golangci-lint run` |
+| `pyproject.toml` | `python -m build` | `pytest` | `pyright .` | `ruff check .` |
+| `Makefile` | `make build` | `make test` | (check targets) | `make lint` |
+
+## Skip Conditions
+
+If command doesn't exist for project:
+- Skip that phase
+- Note "N/A" in report
+- Don't fail the loop
+
+## Integration with Hooks
+
+This discipline provides comprehensive review. Hooks catch issues immediately during development. Use both:
+- Hooks: Real-time feedback
+- Verification Loop: Comprehensive gate before advancement
+
+## Why This Matters
+
+- Catches issues before they compound
+- Ensures consistent quality gates
+- Prevents shipping broken code
+- Creates audit trail of verification
+- Builds confidence in phase completion

package/runtime/verification.md

@@ -0,0 +1,116 @@
+# Verification Discipline
+
+## The Iron Law
+
+```
+NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
+```
+
+If you haven't run the verification command in this message, you cannot claim it passes.
+
+## The Gate Function
+
+```
+BEFORE claiming any status or expressing satisfaction:
+
+1. IDENTIFY: What command proves this claim?
+2. RUN: Execute the FULL command (fresh, complete)
+3. READ: Full output, check exit code, count failures
+4. VERIFY: Does output confirm the claim?
+   - If NO: State actual status with evidence
+   - If YES: State claim WITH evidence
+5. ONLY THEN: Make the claim
+
+Skip any step = lying, not verifying
+```
+
+## Common Failures
+
+| Claim | Requires | Not Sufficient |
+|-------|----------|----------------|
+| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
+| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
+| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
+| Task complete | Success criteria verified | "I wrote the code" |
+| Phase ready | All tasks verified | Prime Worker reports success |
+
+## Red Flags - STOP
+
+When you catch yourself:
+- Using "should", "probably", "seems to"
+- Expressing satisfaction before verification ("Great!", "Done!")
+- About to report completion without running checks
+- Trusting spawn reports without independent verification
+- Relying on partial verification
+- **ANY wording implying success without having run verification**
+
+## Rationalization Prevention
+
+| Excuse | Reality |
+|--------|---------|
+| "Should work now" | RUN the verification |
+| "I'm confident" | Confidence ≠ evidence |
+| "Just this once" | No exceptions |
+| "Spawn said success" | Verify independently |
+| "Partial check is enough" | Partial proves nothing |
+
+## Verification Patterns
+
+**Tests:**
+```
+✅ [Run test command] → [See: 34/34 pass] → "All tests pass"
+❌ "Should pass now" / "Looks correct"
+```
+
+**Build:**
+```
+✅ [Run build] → [See: exit 0] → "Build succeeds"
+❌ "Code compiles" (without running build)
+```
+
+**Task Completion:**
+```
+✅ Re-read success criteria → Verify each with evidence → Report with proof
+❌ "Tasks done, phase complete"
+```
+
+**Spawn Verification:**
+```
+✅ Spawn reports success → Check files exist → Run tests → Report actual state
+❌ Trust spawn report blindly
+```
+
+## Phase Advancement Gate
+
+Before `/ant:continue` advances to next phase:
+
+1. **Build Check**: Run project build command (if exists)
+2. **Test Check**: Run test suite, capture pass/fail counts
+3. **Success Criteria**: Line-by-line verification of phase criteria
+4. **Evidence Required**: Each criterion needs specific proof
+
+```
+Phase {N} Verification
+======================
+
+Build: {command} → {exit code}
+Tests: {command} → {pass}/{total} ({fail} failures)
+
+Success Criteria:
+  ✅ Criterion 1: {evidence}
+  ✅ Criterion 2: {evidence}
+  ❌ Criterion 3: {what's missing}
+
+Verdict: PASS / FAIL
+```
+
+If ANY criterion fails verification, phase cannot advance.
+
+## Why This Matters
+
+- False completion claims break trust
+- Unverified code ships bugs
+- Time wasted on rework from premature advancement
+- Colony integrity depends on honest reporting
+
+**Evidence before claims, always.**