Gladex Agent Logs

 BADSHAPE=$(request date-shape date-shape@gladex.de |
   sed 's#"birthdate":"1990-01-01"#"birthdate":"1990-1-1"#')
 run_stdin "$LIVE" "$BADSHAPE" propose

> build · mimo-v2.6-flash-free
$ cd /data/repo && bash tests/test_hire_agent.sh 2>&1 | grep -E "^FAIL|suite:"; echo "rc=${PIPESTATUS[0]}"
hire-agent suite: 154 passed, 0 failed
rc=0
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -n "Exit codes" tests/test_registry_coverage.sh | head -20; echo "---"; grep -n "hire-agent\|exit-code table\|EXITCODE\|exitcode" tests/test_registry_coverage.sh | head -40
20:# half the claim: `**Exit codes**` existing says nothing about whether the
686:          # `**Exit codes**` block AND that block must list a code 2. A
689:          if printf '%s\n' "$sec" | grep -q '^\*\*Exit codes'; then
699:              | sed -n '/^\*\*Exit codes\*\*/,/^[*#]/s/^- `\([0-9][0-9]*\)`.*/\1/p' \
800:            | sed -n '/^\*\*Exit codes\*\*/,/^[*#]/p' \
1457:tools/ has a tools/REGISTRY.md section carrying Purpose, Usage and Exit codes,
1774:# --- C5/C6/C7 one missing field each: Usage, Purpose, Exit codes ------------
1926:sect "$D/tools/REGISTRY.md" budget-show | grep -q '^\*\*Exit codes' \
1927:  && ok "C15a plant: the section still carries its Exit codes heading" \
1928:  || fail "C15a plant: the section still carries its Exit codes heading"
2099:    printf 'Usage: version-check [--format human|json]\n\nOptions:\n  --format human|json   Output format (default: human)\n\nExit codes:\n  2  Invalid arguments\n'
2374:sect "$D/tools/REGISTRY.md" healthcheck | sed -n '/^\*\*Exit codes\*\*/,/^[*#]/p' \
2378:sect "$D/tools/REGISTRY.md" healthcheck | sed -n '/^\*\*Exit codes\*\*/,/^[*#]/p' \
3928:# proves every section has an `**Exit codes**` field and D proves this suite
3942:assert_eq "E3 every tool's Exit codes table was read (heading present)" \
---
661:      # probe and the exit-code table below — a suite's own table is D's.
1533:  E  the exit-code tables are true, not merely present (one bounded probe per
2482:# --- `hire-agent` grew the `Options:` section the bootstrap `--help` rule asks
3927:# E — the exit-code tables are TRUE, not merely present. (64): section A
4064:# option list, section E reads the exit-code table, F reads the regression
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -6968,9 +6968,10 @@
 **Exit codes**:
 - `0` - Success: help printed, a request was staged, `review` ran and found the
   request **VALID**, or `list` printed
 - `1` - The **request** is not usable: `validate()` reported an error (id shape,
-  name, birthdate, `<id>@gladex.de` address, role, `*-free` model on the
+  name, birthdate (a `YYYY-MM-DD` shape **and** a day the calendar actually
+  has), `<id>@gladex.de` address, role, `*-free` model on the
   allowlist, personality, working style, responsibilities, `mailbox`/`shifts`
   not `true`, the `status` enum, an undocumented field, a non-object request),
   stdin was not JSON, the id already exists (**never overwritten**), `review`
   named no staged request, that file is not JSON, or `review` found the staged

> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -7015,8 +7015,15 @@
   `REQUEST-FORMAT.md` does not document is **refused, not stripped** — silently
   deleting a field would leave a human approving bytes they never saw.
 - **Free models only.** A model not on the allowlist is a validation failure
   (exit 1), not a warning.
+- **A birthdate is a date, not a date-shaped string.** Since `[0.4.301]` the
+  `YYYY-MM-DD` shape must be *and* the value must name a day the calendar
+  actually has (`_calendar_date()` → `date.fromisoformat`), because the regex
+  alone is satisfied by `2026-99-99`, `2026-02-30` and `1900-02-29`. It is
+  deliberately **not** a "not in the future" rule: that verdict would depend on
+  the wall clock, so the same request would read INVALID one day and VALID the
+  next, while the shape + calendar check answers identically whenever asked.
 - **Never overwrites.** An id that is already staged exits 1 with `EXISTS:` and
   leaves the existing file untouched.
 
 ## test_onboarding_baseline.php

> build · mimo-v2.6-flash-free
$ cd /data/repo && awk 'length($0)>0{print length($0)}' CHANGELOG.md | sort -rn | head -5; echo "=== token>70 ==="; awk '{for(i=1;i<=NF;i++) if(length($i)>70) print length($i), $i}' CHANGELOG.md | sort -rn | head -10; echo "=== test head ==="; sed -n '1,60p' tests/test_changelog_mobile.php
2752
2580
2448
2392
2345
=== token>70 ===
76 `mailboxes/reviewer-to-main/VERDICT-20260926-000744-promote-contrast-fix.md`
75 `mailboxes/main-to-reviewer/REVIEW-20260926-000744-promote-contrast-fix.md`
71 `/tmp/opencode/run789-{repo-lint.log,cacheshow.json,ss.json,time.txt}`.
71 `/data/shared/backups/messages-{dev,prod}-preTsFix-20260923-230104.db`.
=== test head ===
<?php
/**
 * `/changelog` must fit the narrowest viewport we support — and the fix must
 * not move a single box where it already fitted.
 *
 * Defect (queued by the 2026-09-26 mobile sweep as "/changelog and /docs
 * `<pre>` overflow", measured properly on 2026-09-27): the changelog page was
 * the ONLY page in the app whose stylesheet had no `pre` rule at all, and it
 * is also the only page that renders fenced blocks from a file that grows
 * every shift. Two mechanisms pushed it sideways, and BOTH were measured in
 * Chrome for Testing 154.0.8037.57 on 2026-09-27 before anything was edited:
 *
 *   1. `pre` is `white-space: pre` (UA default), so its longest line is its
 *      min-content. The stylesheet gave the block no scroll box, so the line
 *      laid out at its full 1158.4px inside a 241px container and the
 *      DOCUMENT took the overflow. Measured `documentElement.scrollWidth`
 *      against `clientWidth`, i.e. horizontal scrollbar in px:
 *          305 -> 885    320 -> 870    360 -> 830    414 -> 776
 *          768 -> 424   1200 -> 208
 *      The 768 and 1200 rows are the point: this was never only a phone bug.
 *      The page is 700px wide at every viewport >= 768 and its longest fenced
 *      line is 1158.4px, so the desktop was broken too.
 *
 *   2. `.container` is a flex item (`body { display: flex }`) whose content
 *      holds prose with unbreakable tokens — a backticked 76-character
 *      `mailboxes/reviewer-to-main/VERDICT-...md` path measured **584.5px**
 *      wide on 2026-09-27; `[0.4.194]` then wrote an 88-char REGISTRY_COVERAGE
 *      triple that this build measured at **752.67px** — past the 682px desktop
 *      line, so it was split (see `TOKEN_PX` below) and the longest token is the
 *      76-char path again at 584.5px.
 *      `overflow-wrap` was `normal` everywhere, so it ran off the page
 *      (invisible to an element scan: overflowing inline TEXT belongs to no
 *      element rect, so the usual "who is past the edge" probe reports
 *      nothing and only `scrollWidth` sees it). The `.version-row` was a
 *      third, smaller instance: `82.73 (badge) + 12 (gap) + 204.5
 *      (longest .version-date min-content) = 299.23px` in a 241px row — and
 *      32 + 299.23 = 331.23, exactly the 331.3px right edge Chrome reported.
 *
 * The fix, three declarations in the changelog stylesheet of `app.php`:
 *   - `.container { ...; overflow-wrap: anywhere; }` — ONE declaration on the
 *     wrapper instead of one per text rule, so a `### ` heading added next
 *     week inherits the guard instead of reintroducing the defect. It is a
 *     *shrink-to-fit* guard: it only engages when a word does not fit its
 *     line, and it collapses the content-based minimum of every descendant,
 *     which is what lets `.version-date` shrink beside its badge.
 *   - `pre { overflow-x: auto; ...panel... }` — the block owns its own scroll
 *     box, as `/docs` and `/log` already do. The background/border are the
 *     same `#12121a` panel `/docs` paints, so a scrollable block reads as a
 *     block rather than as prose that happens to be cut off.
 *   - `.version-tag { white-space: nowrap; }` — the guard FOR the guard.
 *     `anywhere` is inherited, and without this the badge is allowed to shrink
 *     and break: measured, "v0.4.86" rendered 53.59x56 (two lines) instead of
 *     82.73x24. A badge is exactly the thing `anywhere` must not touch.
 *
 * What this suite will NOT allow: a fix that reflows the page. `body`,
 * `.container`, `.version-header`, `.version-tag`, `.version-date`,
 * `.changelog-desc`, `.changelog-item`, `.section-label` and
 * `h1.changelog-title` are asserted declaration by declaration against the
 * values they had BEFORE the fix, and `.version-header` is explicitly barred
 * from gaining `flex-wrap` — that was tried, and it stacks the summary under
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -n "### Queue\|### Fixed\|### Tests\|### Review\|### Scope\|missing" tests/test_changelog_api.php | head -30; echo "=== run now ==="; php tests/test_changelog_api.php 2>&1 | tail -3; php tests/test_changelog_mobile.php 2>&1 | tail -3
7: *     `### Notes`, `### Verified`, `### Security`, `### Tests`,
165:            if (!array_key_exists($k, $a)) { $ok = false; $detail = "{$r['version']}: missing section '$k'"; break 2; }
=== run now ===
  PASS: a heading the API cannot parse is reported as unparseable, not counted as an entry

=== Results: 86 passed, 0 failed ===
  PASS: the prod environment answered /changelog (this section cannot skip everything)

=== Results: 125 passed, 0 failed, 0 skipped ===
> build · mimo-v2.6-flash-free
→ Read repo/tests/test_changelog_api.php [offset=140, limit=45]
> build · mimo-v2.6-flash-free
$ cd /data/repo && cat >> CHANGELOG.md <<'ENTRY'
## [0.4.301] - 2026-10-11 — `tools/hire-agent` now checks that a `birthdate` names a day the calendar has: the `YYYY-MM-DD` regex alone staged `2026-99-99`, `2026-02-30` and `1900-02-29`, so `_calendar_date()` adds `date.fromisoformat` — `tests/test_hire_agent.sh` **120 → 154 assertions** with one negative control, reviewer **APPROVE**

### Fixed
- **`validate()` accepted any `YYYY-MM-DD`-shaped string as a birthdate** (Pip's gap 3, `mailboxes/scout-notes/` + `2026-10-02-hire-agent-validation.md` §E): the regex counts digits — it does not know months, days-per-month, or that 1900 was not a leap year — so `2026-99-99`, the note's own example, staged as happily as `1990-01-01` and a request carrying a day that never existed reached the operator's queue as `VALID`. The shape rule is untouched and still reports its own message; only when the shape *passes* does the new `_calendar_date()` helper ask `datetime.date.fromisoformat` whether the string names a real day, and a `ValueError` becomes an `INVALID` refusal naming the birthdate and nothing else. The helper only reads a string — it stores nothing anywhere, in or out of `hiring/queue/`.
- **Deliberately NOT a "not in the future" rule** — the other half of the note's sentence, recorded as a decision rather than skipped in silence: that verdict depends on the wall clock, so the same request would read INVALID today and VALID tomorrow, while shape + calendar answers identically whenever it is asked. Only `[0.4.301]`'s own `elif` does this work, which is exactly what control U deletes.

### Tests
- **`tests/test_hire_agent.sh` 120 → 154 passed / 0 failed.** New section **T**: five impossible dates (`2026-99-99`, `2026-02-30`, `2026-13-01`, `0000-00-00`, `1900-02-29`), each under its **own** id so no variant's outcome can be decided by whether an earlier one staged, each refused with `assert_only_error` on the calendar rule, no traceback and nothing written; `1900-02-29` is the fixture that proves the **calendar** is consulted — a non-leap century is not a thing a regex gets right by accident. Plus: a `1990-1-1` value still fails the **shape** rule (not the new one), `2000-02-29` — a leap day that exists — still stages, a **hand-edited** queue file carrying `2026-99-99` reviews INVALID with exit 1, and one assertion **per live staged proposal** that the tightening reddens nothing (ids read from the directory, never spelled into this file — the HR guard's rule). Control **U**: the single `elif` stripped from an `ast.parse`d copy and `1900-02-29` then stages; the copy writes only into the sandbox, the live tool's md5 is unchanged, and the live tool refuses the plant again.
- **Neighbours green after the edit:** `bash tests/test_registry_coverage.sh` **464 / 0**, `php tests/test_changelog_mobile.php` **125 / 0**, `php tests/test_changelog_api.php` **86 / 0**. `./tools/regression-run --list` still discovers **99** suites — no suite file was added, the 100th stays reserved for `GETTING_STARTED.md` `keep`.

### Review
- **Reviewer gate run, as the queue required for a tool-script change: `VERDICT: APPROVE`**, requested from `mailboxes/main-to-reviewer/` + `REVIEW-20261011T103000-hire-agent-birthdate.md` and persisted as `mailboxes/reviewer-to-main/` + `VERDICT-20261011T103000-hire-agent-birthdate.md` (reviewer model `nemotron-3-ultra-free`, cost **0.00 EUR**).

### Scope
- **Four paths + this entry:** `tools/hire-agent` (the import, `_calendar_date()`, one `elif`), `tests/test_hire_agent.sh` (section T + control U), `tools/REGISTRY.md` (the exit-1 list and a new `Rules the tool obeys` bullet, which no longer described shape-only validation), `CHANGELOG.md`. **Nothing under `app/src/php` or `examples/workflows` touched → no promote and nothing to promote**; dev and prod untouched, both **0.4.28**, both already matching the repo. **`hiring/queue/` untouched** — both proposals stay `status=proposed`, because approving or withdrawing one is the investor's move. **No `rm`**, no unit restarted, no `systemctl`, no timer changed, no crontab change, no DNS write, no mail sent, no paid API, no API key configured; spend **0.00**, free `*-free` models only.

### Queue
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the newest run entry's `Queue — next small step` bullet — it is not duplicated here, and has not been since `[0.4.67]`. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
ENTRY
grep -c '^## \[' CHANGELOG.md; awk 'length($0)>0{print length($0)}' CHANGELOG.md | sort -rn | head -3; echo "=== long tokens in new entry ==="; tail -25 CHANGELOG.md | awk '{for(i=1;i<=NF;i++) if(length($i)>76) print length($i), $i}'
306
2752
2580
2448
=== long tokens in new entry ===
> build · mimo-v2.6-flash-free
$ cd /data/repo && for t in "bash tests/test_hire_agent.sh" "php tests/test_changelog_mobile.php" "php tests/test_changelog_api.php" "bash tests/test_registry_coverage.sh"; do echo "--- $t"; $t 2>&1 | grep -E "^FAIL|Results|suite:" | tail -6; done
--- bash tests/test_hire_agent.sh
hire-agent suite: 154 passed, 0 failed
--- php tests/test_changelog_mobile.php
=== Results: 125 passed, 0 failed, 0 skipped ===
--- php tests/test_changelog_api.php
=== Results: 86 passed, 0 failed ===
--- bash tests/test_registry_coverage.sh


Command exceeded timeout of 300000 ms. Retry with a larger timeout if the command is expected to take longer.
> build · mimo-v2.6-flash-free

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

[Sun Oct 11 05:40:04 2026] 127.0.0.1:57108 Accepted
[Sun Oct 11 05:40:04 2026] 127.0.0.1:57108 Closing
[Sun Oct 11 05:40:49 2026] 127.0.0.1:57150 Accepted
[Sun Oct 11 05:40:49 2026] 127.0.0.1:57150 Closing
[Sun Oct 11 05:43:07 2026] 127.0.0.1:55256 Accepted
[Sun Oct 11 05:43:07 2026] 127.0.0.1:55256 Closing
[Sun Oct 11 05:43:47 2026] 127.0.0.1:43918 Accepted
[Sun Oct 11 05:43:47 2026] 127.0.0.1:43918 Closed without sending a request; it was probably just an unused speculative preconnection
[Sun Oct 11 05:43:47 2026] 127.0.0.1:43918 Closing
[Sun Oct 11 05:43:49 2026] 127.0.0.1:43932 Accepted
[Sun Oct 11 05:43:49 2026] 127.0.0.1:43932 Closed without sending a request; it was probably just an unused speculative preconnection
[Sun Oct 11 05:43:49 2026] 127.0.0.1:43932 Closing
[Sun Oct 11 05:44:27 2026] 127.0.0.1:56142 Accepted
[Sun Oct 11 05:44:27 2026] 127.0.0.1:56142 Closed without sending a request; it was probably just an unused speculative preconnection
[Sun Oct 11 05:44:27 2026] 127.0.0.1:56142 Closing
[Sun Oct 11 05:44:28 2026] 127.0.0.1:56152 Accepted
[Sun Oct 11 05:44:28 2026] 127.0.0.1:56152 Closed without sending a request; it was probably just an unused speculative preconnection
[Sun Oct 11 05:44:28 2026] 127.0.0.1:56152 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39658 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39658 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39664 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39664 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39670 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39670 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39678 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39678 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39686 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39686 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39694 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39694 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39702 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39702 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39716 Accepted
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39716 Closing
[Sun Oct 11 05:45:12 2026] 127.0.0.1:39730 Accepted
[Sun Oct 11 05:45:13 2026] 127.0.0.1:39730 Closing
[Sun Oct 11 05:45:13 2026] 127.0.0.1:39740 Accepted
[Sun Oct 11 05:45:13 2026] 127.0.0.1:39740 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53946 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53946 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53954 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53954 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53956 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53956 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53958 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53958 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53972 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53972 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53980 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53980 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53990 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:53990 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:54004 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:54004 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:54006 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:54006 Closing
[Sun Oct 11 05:46:05 2026] 127.0.0.1:54020 Accepted
[Sun Oct 11 05:46:05 2026] 127.0.0.1:54020 Closing
[Sun Oct 11 05:46:59 2026] 127.0.0.1:47976 Accepted