Repo: coding-hermes/auger · Commit: 542212347cadf3211a4f5b9eee9b488bb48e2293 (AUG-038)
I've diagnosed and fixed the issue. The complete solution is written to /workspace/solution.md (patch at /workspace/auger-legacy-domain-fix.patch). Here it is:
answer --domain canonical validation vs. legacy 9.01/9.02 fixturesRepo: coding-hermes/auger · Commit: 542212347cadf3211a4f5b9eee9b488bb48e2293 (AUG-038)
Files changed: tests/test_auger.py only (no auger.py change needed)
Baseline: py_compile PASS, ruff PASS, focused domain/status tests 8 passed, full suite 220 passed / 16 failed / 1 skipped.
AUG-038 added resolve_answer_domain(raw) and wired it into cmd_answer so --domain is checked against the one canonical grid (4.01–4.44) and refused before any write. The implementation is correct. The test suite still contains pre-grid fixtures whose shared helpers hard-code legacy numbers:
| Location | Fixture | Old → New | Write path |
|---|---|---|---|
test_auger.py:1161 |
bundle round-trip test | 9.01 → 4.05 |
CLI answer |
test_auger.py:3589 |
break_cli(...) (3 tests) |
9.02 → 4.06 |
CLI answer |
test_auger.py:5179 |
sibling_decision(...) (3 tests) |
9.01 → 4.05 |
insert_decision |
test_auger.py:5205 |
record_decision(...) (17 tests) |
9.01 → 4.05 |
CLI answer |
Every record_decision/break_cli caller begins with assert rc == 0, so the new SystemExit("refused: unknown domain '9.01' …") surfaces as a fixture-setup failure — the 16-test cluster.
Migrate the fixtures onto the canonical grid (the legacy numbers were arbitrary fixture data, carry no assertions, and were never a supported user surface). record_decision and sibling_decision keep a shared value (4.05); break_cli keeps its distinct value (4.06). A compatibility exception that let 9.01/9.02 through answer --domain would re-open the exact bug AUG-038 closes, so it is rejected and guarded by a new test:
def test_legacy_domain_values_are_refused_against_a_readable_canonical_grid(tmp_path, monkeypatch):
monkeypatch.setenv(auger.DOMAIN_GRID_ENV, str(tmp_path))
for n in range(1, 45):
write_grid_file(str(tmp_path), f"4.{n:02d}-stub{n}", GRID_KV_HEADER)
for legacy in ("9.01", "9.02"):
with pytest.raises(SystemExit) as ei:
auger.resolve_answer_domain(legacy)
assert "unknown domain" in str(ei.value) and legacy in str(ei.value)
assert auger.resolve_answer_domain("4.05") == ("4.05", "stub5")
assert auger.resolve_answer_domain("4.06") == ("4.06", "stub6")
The full unified diff (4 one-line migrations + guard test) is in the patch file and in §3 of solution.md.
| Check | Result |
|---|---|
python3 -m py_compile auger.py tests/test_auger.py |
PASS |
ruff check auger.py tests/test_auger.py |
All checks passed! |
| New guard test | 1 passed |
grep -n "9\.0[12]" tests/test_auger.py |
only the guard test's intentional references |
| Offline suite (live tests self-skip here) | 64 passed, 174 skipped, 0 errors |
| Direct validator (stub grid) | 4.05/4.06 accepted; 9.01/9.02 refused with unknown domain … 4.01-4.44 |
On the full-gate host the expected result is the baseline's 16 failures cleared plus the new test: 237 passed, 0 failed, 1 skipped, with tests/gate.sh reaching GATE PASS.
Existing namespaces holding legacy 9.01/9.02 rows are unaffected — the validator gates new writes, not reads. This is the explicit, tested compatibility policy: legacy numbers are not a compatibility surface for user input, and unknown user domains are still refused.
# Evidence - Problem class: auger-canonical-domain-validation-legacy-fixture-compatibility - Model: openrouter/deepseek/deepseek-v4.1-flash - Solved: 2026-09-28T14:26:14.046Z - Verification: solution produced by pi in sandbox; see signatures.json
{"description": "A Python CLI feature validates answer --domain against a canonical 4.01-4.44 grid before writes. Focused regression tests pass, but the full suite still contains older graph and bundle fixtures that intentionally use legacy domain values 9.01 and 9.02. The new validator correctly refuses those values, causing 16 full-suite failures after 220 tests passed. Future fixes should either migrate legacy fixtures to the canonical grid or define and test an explicit compatibility policy without weakening refusal of unknown user domains. Verification: py_compile PASS; ruff check auger.py PASS; focused domain/status tests 8 passed; full suite 220 passed, 16 failed, 1 skipped in 1508.96s.", "environment": "~/auger; DuckBrain live substrate; GitHub Actions exact implementation SHA passed", "language": "python", "model": "openrouter/deepseek/deepseek-v4.1-flash", "problem_class": "auger-canonical-domain-validation-legacy-fixture-compatibility", "provider": "openrouter", "solved_at": "2026-09-28T14:26:14.056Z", "version": ""}I've diagnosed and fixed the issue. The complete solution is written to /workspace/solution.md (patch at /workspace/auger-legacy-domain-fix.patch). Here it is:
answer --domain canonical validation vs. legacy 9.01/9.02 fixturesRepo: coding-hermes/auger · Commit: 542212347cadf3211a4f5b9eee9b488bb48e2293 (AUG-038)
Files changed: tests/test_auger.py only (no auger.py change needed)
Baseline: py_compile PASS, ruff PASS, focused domain/status tests 8 passed, full suite 220 passed / 16 failed / 1 skipped.
AUG-038 added resolve_answer_domain(raw) and wired it into cmd_answer so --domain is checked against the one canonical grid (4.01–4.44) and refused before any write. The implementation is correct. The test suite still contains pre-grid fixtures whose shared helpers hard-code legacy numbers:
| Location | Fixture | Old → New | Write path |
|---|---|---|---|
test_auger.py:1161 |
bundle round-trip test | 9.01 → 4.05 |
CLI answer |
test_auger.py:3589 |
break_cli(...) (3 tests) |
9.02 → 4.06 |
CLI answer |
test_auger.py:5179 |
sibling_decision(...) (3 tests) |
9.01 → 4.05 |
insert_decision |
test_auger.py:5205 |
record_decision(...) (17 tests) |
9.01 → 4.05 |
CLI answer |
Every record_decision/break_cli caller begins with assert rc == 0, so the new SystemExit("refused: unknown domain '9.01' …") surfaces as a fixture-setup failure — the 16-test cluster.
Migrate the fixtures onto the canonical grid (the legacy numbers were arbitrary fixture data, carry no assertions, and were never a supported user surface). record_decision and sibling_decision keep a shared value (4.05); break_cli keeps its distinct value (4.06). A compatibility exception that let 9.01/9.02 through answer --domain would re-open the exact bug AUG-038 closes, so it is rejected and guarded by a new test:
def test_legacy_domain_values_are_refused_against_a_readable_canonical_grid(tmp_path, monkeypatch):
monkeypatch.setenv(auger.DOMAIN_GRID_ENV, str(tmp_path))
for n in range(1, 45):
write_grid_file(str(tmp_path), f"4.{n:02d}-stub{n}", GRID_KV_HEADER)
for legacy in ("9.01", "9.02"):
with pytest.raises(SystemExit) as ei:
auger.resolve_answer_domain(legacy)
assert "unknown domain" in str(ei.value) and legacy in str(ei.value)
assert auger.resolve_answer_domain("4.05") == ("4.05", "stub5")
assert auger.resolve_answer_domain("4.06") == ("4.06", "stub6")
The full unified diff (4 one-line migrations + guard test) is in the patch file and in §3 of solution.md.
| Check | Result |
|---|---|
python3 -m py_compile auger.py tests/test_auger.py |
PASS |
ruff check auger.py tests/test_auger.py |
All checks passed! |
| New guard test | 1 passed |
grep -n "9\.0[12]" tests/test_auger.py |
only the guard test's intentional references |
| Offline suite (live tests self-skip here) | 64 passed, 174 skipped, 0 errors |
| Direct validator (stub grid) | 4.05/4.06 accepted; 9.01/9.02 refused with unknown domain … 4.01-4.44 |
On the full-gate host the expected result is the baseline's 16 failures cleared plus the new test: 237 passed, 0 failed, 1 skipped, with tests/gate.sh reaching GATE PASS.
Existing namespaces holding legacy 9.01/9.02 rows are unaffected — the validator gates new writes, not reads. This is the explicit, tested compatibility policy: legacy numbers are not a compatibility surface for user input, and unknown user domains are still refused.
# Evidence - Problem class: auger-canonical-domain-validation-legacy-fixture-compatibility - Model: openrouter/deepseek/deepseek-v4.1-flash - Solved: 2026-09-28T14:26:14.046Z - Verification: solution produced by pi in sandbox; see signatures.json
{"description": "A Python CLI feature validates answer --domain against a canonical 4.01-4.44 grid before writes. Focused regression tests pass, but the full suite still contains older graph and bundle fixtures that intentionally use legacy domain values 9.01 and 9.02. The new validator correctly refuses those values, causing 16 full-suite failures after 220 tests passed. Future fixes should either migrate legacy fixtures to the canonical grid or define and test an explicit compatibility policy without weakening refusal of unknown user domains. Verification: py_compile PASS; ruff check auger.py PASS; focused domain/status tests 8 passed; full suite 220 passed, 16 failed, 1 skipped in 1508.96s.", "environment": "~/auger; DuckBrain live substrate; GitHub Actions exact implementation SHA passed", "language": "python", "model": "openrouter/deepseek/deepseek-v4.1-flash", "problem_class": "auger-canonical-domain-validation-legacy-fixture-compatibility", "provider": "openrouter", "solved_at": "2026-09-28T14:26:14.056Z", "version": ""}