Gladex Agent Logs

> build · mimo-v2.6-flash-free
$ cd /data/repo && cat >> CHANGELOG.md <<'EOF'

## [0.4.33] - 2026-09-24 — domain-availability-check: an OFFLINE machine certified every domain as free, `--timeout` was a no-op and exit 4 was unreachable

### Fixed
- **A machine with no network at all reported `gladex.de` as `AVAILABLE (confidence: 100%)`, exit 0** — reproduced pre-fix with `unshare -n domain-availability-check --format human gladex.de`. `check_dns()` read `socket.getaddrinfo()` failure (`EAI_AGAIN`) exactly like an authoritative "no records" answer, so the DNS leg always cast an "available" vote; RDAP and whois, having failed too, cast nothing; 1 vote in 1 → 100% confidence, exit 0. The same run with all three lookups failing on purpose (dig rc 9 + curl rc 28 + whois failure) gave the same answer. This is the Phase-0 gate tool — the one the brief requires to "run green on your 3 proposed names before you request any domain" — i.e. the one whose verdict precedes spending the investor's money.
- **Exit 4 ("Network/timeout error") was unreachable**: `sys.exit()` could only ever emit 2/0/3, and exit 1 was undocumented. A network failure therefore surfaced as exit 3 ("all taken/unknown"), and a network failure that left DNS looking empty surfaced as exit 0.
- **`--timeout` was a documented no-op**: curl got no `--max-time`, dig got no `+time` (its calls sat behind a hardcoded 10 s `run_cmd` cap), whois likewise, and A/AAAA went through the OS resolver, which cannot be given a deadline at all. Measured pre-fix: `--timeout 1` with a hanging curl → **6129 ms**; `--timeout 0` accepted; `--help` advertised `--timeout TIMEOUT` with no exit-code table.
- Evidence rules are now explicit (in the tool's docstring, `--help` and REGISTRY): a **failed check is never a vote** (`error` ∈ `timeout|network|tool_missing|bad_response|http_error`, excluded from the verdict, counted in `checks_failed`, surfaced as `coverage`); DNS *presence* of records still decides "taken" on its own, but DNS *absence* no longer decides "free" — a positive verdict needs an authoritative RDAP/whois confirmation or a run where all three checks completed, otherwise it is downgraded to `available: null` + `network_error: true` (exit 4). Exit precedence: `2` bad args > `0` confirmed > `4` undetermined-after-failure > `3`.
- A/AAAA now resolve through `dig +short +time=N +tries=1` (first failed query ends the DNS check) instead of `getaddrinfo()`: only dig takes a deadline, and only its exit code separates "resolver answered *no records*" (rc 0) from "the query never completed" (rc 9). curl/whois/RDAP-5xx failures are classified rather than swallowed; `rdap.url` is recorded so consumers can see which source answered.

### Added
- **`tests/test_domain_availability.sh`** — **140 assertions, 5 mutations, hermetic**: dig/curl/whois are scenario-driven stubs on PATH (no network touched), plus one offline case inside `unshare -n` (deterministic *because* it has no network). Covers the arg/`--help` contract incl. the exit-code table, `--timeout` validation (`0`/negative → 2), JSONL/human contracts and the new top-level keys, source evidence (DENIC vs rdap.org, `--max-time`/`+time`/`+tries` reaching each tool), the **`3` vs `4` split**, per-source failure classification, `--timeout` bounding a check that hangs 6 s, and static guards (no `getaddrinfo`, every dig call carries `+time=`, no credential/paid-API strings, contract fields present in REGISTRY). Written first and run against the unfixed tool → **61 passed / 77 failed**, every failure mapping to one of the three defects; after the fix → **140/140**.
- Mutations detected + surgical: **M1** exit 4 folded back into 3, **M2** curl `--max-time` hardcoded, **M3** dig `+time` hardcoded, **M4** failed checks allowed to vote again (the original defect), **M5** positive-verdict downgrade defeated — each precondition-asserted to occur exactly once, must RUN and give the wrong verdict, and re-checked as still-correct on a clean run.
- Live after the fix: `gladex.de` → `TAKEN` exit 3; `qovix.de`/`qovai.de` → `AVAILABLE` confidence 100 %, coverage 1.0, exit 0 (the brief's 3-names proof still green); offline → `UNKNOWN`, `checks failed: 3/3`, exit 4.

### Placement (deliberate — same as `[0.4.29]`–`[0.4.32]`, which sit immediately above this one)
Parked at the bottom of an otherwise newest-first file on purpose. Promoting it to the top would make it the version-train head while `GLADEX_APP_VERSION` and all four `gladex` binaries still report `0.4.28`, turning `tests/test_app_version` and `tests/test_cli_version` red until CI bumps the train and rebuilds. That bump is main-loop work and is not part of this fix.
EOF
echo "CHANGELOG appended"; tail -4 CHANGELOG.md | head -2
CHANGELOG appended
- Live after the fix: `gladex.de` → `TAKEN` exit 3; `qovix.de`/`qovai.de` → `AVAILABLE` confidence 100 %, coverage 1.0, exit 0 (the brief's 3-names proof still green); offline → `UNKNOWN`, `checks failed: 3/3`, exit 4.
> build · mimo-v2.6-flash-free
Now the PROGRESS.md entry:
$ cd /data/repo && cat >> agent-logs/PROGRESS.md <<'EOF'

## 2026-09-24T17:55Z main-loop run — STEP 0 clear; domain-availability-check: an OFFLINE machine certified every domain as free, --timeout was a no-op, exit 4 unreachable — 140 assertions, 5 mutations

- **STEP 0**: 0 unread `investor_to_agent` on dev AND prod (dev: 24 rows all
  read; prod: 0 unread); `INBOX.md` 67 `##` entries, every one `~~HANDLED~~`
  (0 unhandled). No investor replies owed this run. Dispatcher mailboxes
  (`mailboxes/*`) hold 0 pending assignments — nothing to adopt, nothing routed.
- **Defect the step exists for** (5th of the same class: system-status, dns-verify,
  budget-show, tls-check — "documented contract not honored, zero tests"): the
  **Phase-0 gate tool** `domain-availability-check` — the one the brief requires
  to "run green on your 3 proposed names **before you request any domain**", i.e.
  the verdict that precedes spending the investor's money — had ZERO tests and
  every documented promise was fiction. Pre-fix evidence, all captured this run:
  (1) **an offline machine said yes**: `unshare -n domain-availability-check
  --format human gladex.de` → `gladex.de: AVAILABLE (confidence: 100%)`, exit 0,
  for a domain we OWN. `check_dns()` read the OS-resolver failure (`EAI_AGAIN`)
  identically to an authoritative "no records", so DNS always cast an "available"
  vote while RDAP/whois (also dead) cast none → 1/1 = 100% confidence. Same answer
  with every lookup failing on purpose (dig rc 9 + curl rc 28 + whois failure).
  (2) **exit 4 ("Network/timeout error") was unreachable** — `sys.exit()` could
  only emit 2/0/3 — so a network failure surfaced as exit 3 ("all taken/unknown")
  or, worse, exit 0. (3) **`--timeout` was a no-op**: curl had no `--max-time`,
  dig no `+time`, whois a hardcoded 10 s, A/AAAA through the unbounded OS
  resolver → measured `--timeout 1` against a hanging curl = **6129 ms**;
  `--timeout 0` was accepted.
- **Step taken (test-first)**: `tests/test_domain_availability.sh` written FIRST,
  run against the unfixed tool → **61 passed / 77 failed**, every failure mapping
  1:1 to the three defects (offline→AVAILABLE, `checks_failed`/`coverage`/
  `network_error` absent, no `--max-time`/`+time` in argv, hangs running out their
  6 s, `--timeout 0` accepted, no exit-code table in `--help`, REGISTRY fields
  undocumented). Then the fix → **140 passed / 0 failed**.
- **Contract now**: a **failed check is never a vote** — each check carries
  `error` ∈ `timeout|network|tool_missing|bad_response|http_error`, is excluded
  from the verdict, counted in `checks_failed` and surfaced as `coverage`.
  DNS *presence* of records still decides "taken" alone (so exit 3 stays 3 when a
  redundant check failed); DNS *absence* no longer decides "free" — a positive
  verdict needs an authoritative RDAP/whois confirmation or a run where all three
  checks completed, else it is downgraded to `available: null` +
  `network_error: true` (exit 4). Precedence `2` > `0` > `4` > `3`. A/AAAA moved
  from `getaddrinfo()` to `dig +short +time=N +tries=1` (only dig takes a deadline
  and its rc 0 vs rc 9 separates "answered no records" from "never completed";
  first failed query ends the DNS check); curl gets `--max-time`, whois is bounded
  by the subprocess cap; RDAP 5xx and unparseable bodies are failures, not
  verdicts; `rdap.url` recorded. `--timeout 0`/negative/garbage → exit 2.
- **Mutations (5, each precondition-asserted + surgical-checked)**: M1 exit 4
  folded back into 3; M2 curl `--max-time` hardcoded; M3 dig `+time` hardcoded;
  M4 failed checks vote again (the original defect — also breaks the
  `checks_failed` counter, caught twice); M5 the positive-verdict downgrade
  defeated (failure accounting left intact → caught only by the verdict, which is
  what proves the two rules are independent).
- **Live**: `gladex.de` → `TAKEN` exit 3 (DNS+RDAP+whois agree); the brief's 3
  names → `qovix.de`/`qovai.de` `AVAILABLE` confidence 100%, coverage 1.0,
  exit 0 (Phase-0 proof still green); offline → `UNKNOWN`, `checks failed: 3/3
  (coverage: 0%)`, **exit 4** — the exact command that used to print AVAILABLE.
- **Full regression: 26 suites, 1104 assertions, 0 failed** (11 shell = 623:
  budget 49, dns 40, domain 140, identity 28, promote 67, repo-lint 77, smtp 38,
  source-sync 30, mx_soa 31, unread 24, tls 99 + 15 PHP = 481). `repo-lint` on
  HEAD → exit 0 (107 linted); `bash -n` + `py_compile` clean on both files.
- **Docs**: REGISTRY §domain-availability-check rewritten (exit codes, evidence
  rules, JSON schema with the new fields, 140-assertion suite); CHANGELOG
  `[0.4.33]` parked at the BOTTOM with the placement note (train head stays
  `0.4.28` → `test_app_version`/`test_cli_version` stay green); DOMAIN.md's
  verification transcript replaced with the real current output (it claimed
  parenthetical NS/status details the tool never emitted) + the offline case.
- **Safety**: model spend **0.00** (`*-free` only), no secrets/personal data in
  prompts or commits, no DNS write, no service restart, **prod untouched** (live
  invocations read-only; `unshare -n` only creates a throwaway netns), no money
  moved (BUDGET unchanged: 1.50 spent / 3.50 remaining). Repo-wide grep found no
  callers of `domain-availability-check` outside docs → the exit-code change
  cannot break an existing script.
- **Still blocked (investor-owned)**: NEEDS-INVESTOR **#57 public investor-route
  gating A/B/C** and **SOA MNAME** (`a.misconfigured.dns.server.invalid.`) —
  cannot proceed unilaterally.
EOF
echo "PROGRESS appended"; wc -l agent-logs/PROGRESS.md
PROGRESS appended
4731 agent-logs/PROGRESS.md
> build · mimo-v2.6-flash-free
$ cd /data/repo && for f in tests/test_app_version.php tests/test_cli_version.php tests/test_changelog_api.php tests/test_source_sync_check.sh; do
  if [[ "$f" == *.php ]]; then out=$(php "$f" 2>&1); else out=$(bash "$f" 2>&1); fi
  rc=$?
  printf '%-40s rc=%s  %s\n' "$f" "$rc" "$(printf '%s\n' "$out" | grep -E 'passed|FAILURES' | tail -1)"
done
tests/test_app_version.php               rc=0  === Results: 39 passed, 0 failed ===
tests/test_cli_version.php               rc=0  === Results: 35 passed, 0 failed ===
tests/test_changelog_api.php             rc=0  === Results: 78 passed, 0 failed ===
tests/test_source_sync_check.sh          rc=0  source-sync-check suite: 30 passed, 0 failed
> build · mimo-v2.6-flash-free
$ cd /data/repo && git status --short && git add -A && git status --short && git commit -q -m "domain-availability-check: an OFFLINE machine certified every domain as free (resolver failure read as authoritative \"no records\"), --timeout was a no-op, exit 4 unreachable — 140-assertion hermetic suite written first (61/77 red), 5 mutations; REGISTRY contract rewrite + CHANGELOG 0.4.33 parked + DOMAIN.md transcript + PROGRESS" && git log --oneline -3
M CHANGELOG.md
 M DOMAIN.md
 M agent-logs/PROGRESS.md
 M tools/REGISTRY.md
 M tools/domain-availability-check
?? tests/test_domain_availability.sh
M  CHANGELOG.md
M  DOMAIN.md
M  agent-logs/PROGRESS.md
A  tests/test_domain_availability.sh
M  tools/REGISTRY.md
M  tools/domain-availability-check
358558f domain-availability-check: an OFFLINE machine certified every domain as free (resolver failure read as authoritative "no records"), --timeout was a no-op, exit 4 unreachable — 140-assertion hermetic suite written first (61/77 red), 5 mutations; REGISTRY contract rewrite + CHANGELOG 0.4.33 parked + DOMAIN.md transcript + PROGRESS
2ef0ca0 repo-lint: first check that lints COMMITTED git blobs at a pinned --sha — HEAD 219fd8f shipped a PHP parse error while every worktree suite stayed green (tool + 77-assertion hermetic suite, 3 mutations; REGISTRY/CHANGELOG 0.4.32 parked/PROGRESS)
c7f16a0 identity dispatcher shift 2026-09-24T16:54Z
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/repo-lint; echo "repo-lint rc=$?"; echo "=== push ==="; git push origin main 2>&1 | tail -5; echo "push_rc=$?"; git ls-remote origin main 2>&1 | head -2
repo-lint  repo=/data/repo  sha=358558fac3 (HEAD)  files=159  linted=108  skipped=51
  linted:   bash=16  go=43  json=11  php=27  python=11
  skipped:  binary=2  empty=5  no_shebang=4  unsupported_ext=40
result: all 108 linted file(s) parse clean (exit 0)
repo-lint rc=0
=== push ===
To git://git.gladex.de/gladex.git
   2ef0ca0..358558f  main -> main
push_rc=0
358558fac376a45277d4966b6e94a3ec50fa0fae	refs/heads/main
> build · mimo-v2.6-flash-free
$ sqlite3 /opt/startup/dev/data/messages.db "SELECT count(*) FROM messages WHERE direction='investor_to_agent' AND read=0;"; sqlite3 /opt/startup/prod/data/messages.db "SELECT count(*) FROM messages WHERE direction='investor_to_agent' AND read=0;"; grep -c "^## " /data/repo/INBOX.md; grep "^## " /data/repo/INBOX.md | grep -vc "HANDLED"
0
0
65
0
$ cd /data/repo && bash tests/test_domain_availability.sh 2>&1 | tail -3
ok   - M5 surgical: mutant still exits 0 when RDAP confirms free

=== Results: 140 passed, 0 failed ===
> build · mimo-v2.6-flash-free
Final green confirmation (140/0) and STEP 0 re-verified at end of run. One factual slip in my PROGRESS entry to correct (INBOX has 65 `##` entries, not 67):
$ cd /data/repo && python3 - <<'PY'
import pathlib
p = pathlib.Path("agent-logs/PROGRESS.md"); s = p.read_text()
old = "(dev: 24 rows all\n  read; prod: 0 unread); `INBOX.md` 67 `##` entries, every one `~~HANDLED~~`"
new = "(dev: 24 rows all\n  read; prod: 0 unread); `INBOX.md` 65 `##` entries, every one `~~HANDLED~~`"
assert s.count(old) == 1, f"occurrences: {s.count(old)}"
p.write_text(s.replace(old, new))
print("corrected 67 -> 65")
PY
git add -A && git commit -q -m "docs: PROGRESS — correct INBOX entry count (65, not 67) in this run's STEP 0 line" && git push origin main 2>&1 | tail -2; git log --oneline -1
corrected 67 -> 65
To git://git.gladex.de/gladex.git
   358558f..ddc9632  main -> main
ddc9632 docs: PROGRESS — correct INBOX entry count (65, not 67) in this run's STEP 0 line
> build · mimo-v2.6-flash-free
Run complete. Summary:

## STEP 0 (answered first)
- **0 unread** `investor_to_agent` rows on dev *and* prod; **0 unhandled** entries in `INBOX.md` (65 `##` entries, all `~~HANDLED~~`) → no investor replies owed. Re-verified at end of run: still 0/0.
- Dispatcher mailboxes: 0 pending assignments.

## This run's step — 5th instance of the "documented contract, zero tests" class
`domain-availability-check` is the **Phase‑0 gate tool** (brief: *"must run green on your 3 proposed names before you request any domain"*) and it was entirely untested. Pre-fix evidence captured this run:

| Defect | Measured pre-fix |
|---|---|
| Offline machine says yes | `unshare -n … gladex.de` → **`AVAILABLE (confidence: 100%)`, exit 0** — a domain we *own*. Resolver failure (`EAI_AGAIN`) read as authoritative "no records", RDAP/whois dead cast no votes → 1/1 = 100% |
| exit 4 unreachable | `sys.exit()` emitted only 2/0/3; network failure surfaced as exit 3 or 0 |
| `--timeout` no-op | hanging curl with `--timeout 1` → **6129 ms**; `--timeout 0` accepted; no `--max-time`/`+time` anywhere |

**Test-first:** `tests/test_domain_availability.sh` written first → **61 passed / 77 failed** against the unfixed tool (every failure maps to those three defects) → fix → **140 passed / 0 failed**, with **5 mutations** (exit-4 fold, curl/dig deadline removed, failures voting again, downgrade rule defeated), each precondition-asserted and surgical-checked.

**New contract:** a failed check is never a vote (`error` + `checks_failed` + `coverage`); DNS *presence* still decides "taken", DNS *absence* no longer decides "free" (positive verdicts need RDAP/whois confirmation or full coverage → otherwise `available: null`, `network_error: true`, **exit 4**); A/AAAA moved to `dig +time=N +tries=1`; precedence `2 > 0 > 4 > 3`.

**Live:** `gladex.de` → TAKEN rc3 · `qovix.de`/`qovai.de` → AVAILABLE, coverage 1.0, rc0 (Phase‑0 proof still green) · offline → `UNKNOWN, checks failed: 3/3`, **rc4**.

## Verification & landing
- **Full regression: 26 suites, 1104 assertions, 0 failed** (964 + 140 new)
- `repo-lint` on the new HEAD → exit 0 (108 linted)
- Docs: REGISTRY §domain-availability-check rewritten, CHANGELOG `[0.4.33]` parked at bottom (train head stays 0.4.28), DOMAIN.md transcript replaced with real output, PROGRESS entry appended
- Commits `358558f` + `ddc9632` **pushed** (remote HEAD verified)
- **Spend 0.00** (`*-free` only), no secrets, no DNS writes, no restarts, prod untouched

**Still blocked (investor-owned):** NEEDS‑INVESTOR **#57 public investor‑route gating A/B/C** and **SOA MNAME** — cannot proceed unilaterally.
exit=0

Select another run log from the list above. Only files matching run-YYYYMMDD-HHMMSS-N.log are readable.

[Fri Sep 25 01:34:56 2026] 127.0.0.1:49504 Accepted
[Fri Sep 25 01:34:56 2026] 127.0.0.1:49504 Closing
[Fri Sep 25 01:34:56 2026] 127.0.0.1:49508 Accepted
[Fri Sep 25 01:34:56 2026] 127.0.0.1:49508 Closing
[Fri Sep 25 01:34:56 2026] 127.0.0.1:49522 Accepted
[Fri Sep 25 01:34:56 2026] 127.0.0.1:49522 Closing
[Fri Sep 25 01:34:56 2026] 127.0.0.1:49536 Accepted
[Fri Sep 25 01:34:57 2026] 127.0.0.1:49536 Closing
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60400 Accepted
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60400 Closing
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60408 Accepted
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60408 Closing
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60422 Accepted
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60422 Closing
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60428 Accepted
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60428 Closing
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60442 Accepted
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60442 Closing
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60446 Accepted
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60446 Closing
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60462 Accepted
[Fri Sep 25 01:37:40 2026] 127.0.0.1:60462 Closing
[Fri Sep 25 01:42:50 2026] 127.0.0.1:37798 Accepted
[Fri Sep 25 01:42:50 2026] 127.0.0.1:37798 Closing
[Fri Sep 25 01:42:50 2026] 127.0.0.1:37802 Accepted
[Fri Sep 25 01:42:50 2026] 127.0.0.1:37802 Closing
[Fri Sep 25 01:42:51 2026] 127.0.0.1:37814 Accepted
[Fri Sep 25 01:42:51 2026] 127.0.0.1:37814 Closing
[Fri Sep 25 01:42:51 2026] 127.0.0.1:37818 Accepted
[Fri Sep 25 01:42:51 2026] 127.0.0.1:37818 Closing
[Fri Sep 25 01:42:54 2026] 127.0.0.1:37824 Accepted
[Fri Sep 25 01:42:54 2026] 127.0.0.1:37824 Closing
[Fri Sep 25 01:42:55 2026] 127.0.0.1:44098 Accepted
[Fri Sep 25 01:42:55 2026] 127.0.0.1:44098 Closing
[Fri Sep 25 01:42:55 2026] 127.0.0.1:44106 Accepted
[Fri Sep 25 01:42:55 2026] 127.0.0.1:44106 Closing
[Fri Sep 25 01:43:00 2026] 127.0.0.1:44120 Accepted
[Fri Sep 25 01:43:00 2026] 127.0.0.1:44120 Closing
[Fri Sep 25 01:43:00 2026] 127.0.0.1:44134 Accepted
[Fri Sep 25 01:43:00 2026] 127.0.0.1:44134 Closing
[Fri Sep 25 01:43:00 2026] 127.0.0.1:44150 Accepted
[Fri Sep 25 01:43:00 2026] 127.0.0.1:44150 Closing
[Fri Sep 25 01:43:04 2026] 127.0.0.1:44164 Accepted
[Fri Sep 25 01:43:04 2026] 127.0.0.1:44164 Closing
[Fri Sep 25 01:43:04 2026] 127.0.0.1:38886 Accepted
[Fri Sep 25 01:43:04 2026] 127.0.0.1:38886 Closing
[Fri Sep 25 01:43:05 2026] 127.0.0.1:38896 Accepted
[Fri Sep 25 01:43:05 2026] 127.0.0.1:38896 Closing
[Fri Sep 25 01:43:09 2026] 127.0.0.1:38912 Accepted
[Fri Sep 25 01:43:09 2026] 127.0.0.1:38912 Closing
[Fri Sep 25 01:43:10 2026] 127.0.0.1:38918 Accepted
[Fri Sep 25 01:43:10 2026] 127.0.0.1:38918 Closing
[Fri Sep 25 01:43:10 2026] 127.0.0.1:38934 Accepted
[Fri Sep 25 01:43:10 2026] 127.0.0.1:38934 Closing
[Fri Sep 25 01:43:30 2026] 127.0.0.1:53584 Accepted
[Fri Sep 25 01:43:30 2026] 127.0.0.1:53584 Closing
[Fri Sep 25 01:43:30 2026] 127.0.0.1:53596 Accepted
[Fri Sep 25 01:43:30 2026] 127.0.0.1:53596 Closing
[Fri Sep 25 01:43:30 2026] 127.0.0.1:53610 Accepted