Gladex Agent Logs

rest = lines[:start] + lines[end:]
# collapse a possible double blank left behind
while len(rest) > 2 and rest[5] == '' and rest[6] == '':
    del rest[6]
print('post-move first heading:', next(l for l in rest if l.startswith('## [')))

entry = """## [0.4.71] - 2026-09-26 — the version-train head was replaced by a PARKED entry: `## [0.4.70]` sat at the TOP of this file while `GLADEX_APP_VERSION` and all four `gladex` binaries still report `0.4.28`, so `test_app_version` (8) and `test_cli_version` (7) were RED at HEAD — the entry is relocated, byte for byte, to its parked position at the bottom

### Fixed
- **Position only, content untouched.** `[0.4.70]` was inserted at the top of this file as `## [0.4.29]` (`32986bb`), then renumbered in place to `## [0.4.70]` by `0119e61` to clear `repo-lint`'s duplicate-version gate — two actors' correct local steps that together made a *parked* entry the newest heading in file order. `tests/test_app_version.php` asserts the app constant equals the **top** entry and `tests/test_cli_version.php` derives the binary version from it, so the head of the train had moved to a number no build had ever reported: **8 + 7 = 15 red assertions at an otherwise clean HEAD**. The relocation is exactly what `[0.4.69]`'s own placement note prescribed when it wrote that promoting an entry to the top *"would turn `tests/test_app_version` and `tests/test_cli_version` red until CI bumps the train"* — the note was a prediction, and the prediction is now the recorded measurement.
- **Not chosen: bumping the train instead.** Renumbering `GLADEX_APP_VERSION` to `0.4.70` would also turn the suites green, but it changes what `/healthz`, `/api/version`, the download badge and the four binaries *ship*, and it needs a rebuild + deploy of `app/bin/gladex`, `app/src/go/gladex`, dev and prod. That is a release decision, not a broken-docs fix, so this run did the positional one.

### Tests
- **Baseline before touching anything** (`./tools/regression-run --format json`, 13:57Z): **44 suites, 3624 passed, 15 failed, 0 skipped, exit 1** — and the 15 are attributable to exactly two suites, `test_app_version.php` (31/8) and `test_cli_version.php` (28/7), i.e. the whole red is the two gates the misplaced entry trips, not a spread regression.
- **After the move**: re-run both suites first, then the full regression, reported with numbers in `agent-logs/PROGRESS.md` (this run's entry) rather than assumed from the shape of the fix.

### Queue -> agent-logs/PROGRESS.md
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the `Next-candidate queued, not actioned` bullet of the newest run entry — it is not duplicated here, and has not been since `[0.4.67]`. The 111 item lines already written into the historical `### Queue` sections are frozen history. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.

### Notes
- **Attribution**: the entry was written by a concurrent shift and its text was **not edited** — heading, body and date are byte-identical to `0119e61`; only its position in this file changed, because the convention (parked at the bottom) is what the two version suites key off. Recorded here rather than hidden inside my own commit subject, since `git add` is not line-scoped and this commit necessarily carries their text along with the move.
- **Placement**: parked at the bottom like `[0.4.29]`–`[0.4.69]`, so `## [0.4.28]` is the top entry again and the train head means what the binaries say.
"""

out = '\n'.join(rest).rstrip('\n') + '\n\n' + entry.rstrip('\n') + '\n'
p.write_text(out)
print('written, lines:', out.count('\n'))
PY
echo "=== headings top/bottom ==="; grep -n '^## \[' CHANGELOG.md | head -3; grep -n '^## \[' CHANGELOG.md | tail -3
block lines: 6 | heading at 7 | next heading at 13
pre-move top heading: ## [0.4.28] - 2026-09-24 — Go CLI joins the single version train: build.sh derives its version from this changelog (was a hardcoded 0.2.0), download badge + docs CLI mentions follow, all four binaries rebuilt
post-move first heading: ## [0.4.28] - 2026-09-24 — Go CLI joins the single version train: build.sh derives its version from this changelog (was a hardcoded 0.2.0), download badge + docs CLI mentions follow, all four binaries rebuilt
written, lines: 2169
=== headings top/bottom ===
7:## [0.4.28] - 2026-09-24 — Go CLI joins the single version train: build.sh derives its version from this changelog (was a hardcoded 0.2.0), download badge + docs CLI mentions follow, all four binaries rebuilt
21:## [0.4.27] - 2026-09-24 — version drift closed: nine stale `0.3.0` literals across app+docs collapse into one `GLADEX_APP_VERSION` constant sourced from this changelog
38:## [0.4.26] - 2026-09-24 — smtp-relay-probe now ASSERTS the 220 greeting (exit 4): a one-endpoint :25-greeting regression could no longer pass green
2094:## [0.4.68] - 2026-09-26 — `tls-check`'s default domain list named only the 7 SANs of the original lineage, so the second Let's Encrypt cert issued this morning (`photos.gladex.de` + `cloud.gladex.de`) was monitored by nothing: defaults now cover both lineages, 7 → 9 names
2112:## [0.4.69] - 2026-09-26 — `/templates` and `/team` sized their card grid from a FIXED `minmax()` minimum (300px / 280px) inside a 272px box at a 320px viewport: `/templates` clipped its right edge behind a horizontal scrollbar at EVERY width ≤ 320 and `/team`'s card spilled its own container by 8px — both grids now ask with `min(Npx, 100%)`, same ask, container respected; suite 75, total 41/3503 → 43/3589
2154:## [0.4.71] - 2026-09-26 — the version-train head was replaced by a PARKED entry: `## [0.4.70]` sat at the TOP of this file while `GLADEX_APP_VERSION` and all four `gladex` binaries still report `0.4.28`, so `test_app_version` (8) and `test_cli_version` (7) were RED at HEAD — the entry is relocated, byte for byte, to its parked position at the bottom
> build · mimo-v2.6-flash-free
I dropped the block instead of relocating it — restoring it now, byte for byte from HEAD:
$ cd /data/repo && python3 - <<'PY'
import subprocess, pathlib
head = subprocess.run(['git','show','HEAD:CHANGELOG.md'],capture_output=True,text=True,check=True).stdout
hl = head.split('\n')
s = next(i for i,l in enumerate(hl) if l.startswith('## [0.4.70]'))
e = next(i for i,l in enumerate(hl) if l.startswith('## [0.4.28]'))
block = hl[s:e]
print('recovered block (%d lines):' % len(block))
print('\n'.join(block))

p = pathlib.Path('CHANGELOG.md')
cur = p.read_text()
assert '## [0.4.70]' not in cur, 'already present'
# insert immediately before my own 0.4.71 heading
marker = '## [0.4.71] -'
i = cur.index(marker)
new = cur[:i] + '\n'.join(block).rstrip('\n') + '\n\n' + cur[i:]
p.write_text(new)

# verify: block byte-identical to HEAD's, and header intact
cur2 = p.read_text()
s2 = cur2.index('## [0.4.70]'); e2 = cur2.index('## [0.4.71] -')
assert cur2[s2:e2] == '\n'.join(block).rstrip('\n') + '\n\n', 'block not byte-identical'
print('OK: block restored byte-identical to HEAD')
print('header:', repr(cur2[:120]))
PY
echo "=== tail headings ==="; grep -n '^## \[' CHANGELOG.md | tail -4; echo "=== count ==="; grep -c '^## \[' CHANGELOG.md; git diff --stat CHANGELOG.md
recovered block (6 lines):
## [0.4.70] - 2026-09-26 — QA pass confirmed team page solid on dev + prod

### Verified
- **`tests/test_team_page.php`** — all 8 assertions pass (HTTP 200, all 4 members rendered, no birthdates leaked, role labels present). Team page serves correctly on dev (:8000) and prod (:8001).
- Personal daily notes exchanged with Leon via sendmail from mia@gladex.de (never noreply@gladex.de).

Traceback (most recent call last):
  File "<stdin>", line 12, in <module>
AssertionError: already present
=== tail headings ===
2000:## [0.4.67] - 2026-09-26 — the next-candidate queue was written out TWICE, in two files that had already diverged, so an item could sit in one list and be re-proposed from the other with nothing versioned checking either copy: `agent-logs/PROGRESS.md` is now the single authoritative list, every `### Queue` section in this file is a pointer from here on with the 111 historical item lines frozen, and `tools/queue-source-check` enforces it as a `system-status` row; suite 0 → 107, total 40/3396 → 41/3503
2094:## [0.4.68] - 2026-09-26 — `tls-check`'s default domain list named only the 7 SANs of the original lineage, so the second Let's Encrypt cert issued this morning (`photos.gladex.de` + `cloud.gladex.de`) was monitored by nothing: defaults now cover both lineages, 7 → 9 names
2112:## [0.4.69] - 2026-09-26 — `/templates` and `/team` sized their card grid from a FIXED `minmax()` minimum (300px / 280px) inside a 272px box at a 320px viewport: `/templates` clipped its right edge behind a horizontal scrollbar at EVERY width ≤ 320 and `/team`'s card spilled its own container by 8px — both grids now ask with `min(Npx, 100%)`, same ask, container respected; suite 75, total 41/3503 → 43/3589
2154:## [0.4.71] - 2026-09-26 — the version-train head was replaced by a PARKED entry: `## [0.4.70]` sat at the TOP of this file while `GLADEX_APP_VERSION` and all four `gladex` binaries still report `0.4.28`, so `test_app_version` (8) and `test_cli_version` (7) were RED at HEAD — the entry is relocated, byte for byte, to its parked position at the bottom
=== count ===
75
 CHANGELOG.md | 23 +++++++++++++++++------
 1 file changed, 17 insertions(+), 6 deletions(-)
> build · mimo-v2.6-flash-free
$ cd /data/repo && python3 - <<'PY'
import subprocess, pathlib
head = subprocess.run(['git','show','HEAD:CHANGELOG.md'],capture_output=True,text=True,check=True).stdout
hl = head.split('\n')
s = next(i for i,l in enumerate(hl) if l.startswith('## [0.4.70]'))
e = next(i for i,l in enumerate(hl) if l.startswith('## [0.4.28]'))
block = hl[s:e]

p = pathlib.Path('CHANGELOG.md')
cur = p.read_text()
assert not any(l.startswith('## [0.4.70]') for l in cur.split('\n')), 'block already present'
i = cur.index('## [0.4.71] -')
new = cur[:i] + '\n'.join(block).rstrip('\n') + '\n\n' + cur[i:]
p.write_text(new)

cur2 = p.read_text()
s2 = cur2.index('## [0.4.70] -'); e2 = cur2.index('## [0.4.71] -')
assert cur2[s2:e2] == '\n'.join(block).rstrip('\n') + '\n\n', 'not byte-identical'
print('OK block restored byte-identical to HEAD')
print('headings:', sum(1 for l in cur2.split('\n') if l.startswith('## [')))
print('header ok:', cur2.split('\n')[6].startswith('## [0.4.28]'))
PY
grep -n '^## \[' CHANGELOG.md | tail -4; echo "=== diff stat ==="; git diff --stat CHANGELOG.md
OK block restored byte-identical to HEAD
headings: 76
header ok: True
2094:## [0.4.68] - 2026-09-26 — `tls-check`'s default domain list named only the 7 SANs of the original lineage, so the second Let's Encrypt cert issued this morning (`photos.gladex.de` + `cloud.gladex.de`) was monitored by nothing: defaults now cover both lineages, 7 → 9 names
2112:## [0.4.69] - 2026-09-26 — `/templates` and `/team` sized their card grid from a FIXED `minmax()` minimum (300px / 280px) inside a 272px box at a 320px viewport: `/templates` clipped its right edge behind a horizontal scrollbar at EVERY width ≤ 320 and `/team`'s card spilled its own container by 8px — both grids now ask with `min(Npx, 100%)`, same ask, container respected; suite 75, total 41/3503 → 43/3589
2154:## [0.4.70] - 2026-09-26 — QA pass confirmed team page solid on dev + prod
2160:## [0.4.71] - 2026-09-26 — the version-train head was replaced by a PARKED entry: `## [0.4.70]` sat at the TOP of this file while `GLADEX_APP_VERSION` and all four `gladex` binaries still report `0.4.28`, so `test_app_version` (8) and `test_cli_version` (7) were RED at HEAD — the entry is relocated, byte for byte, to its parked position at the bottom
=== diff stat ===
 CHANGELOG.md | 29 +++++++++++++++++++++++------
 1 file changed, 23 insertions(+), 6 deletions(-)
> build · mimo-v2.6-flash-free
$ cd /data/repo && git diff CHANGELOG.md | head -60
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8b72f6b..64aefc6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,12 +4,6 @@ All notable changes to Gladex are documented here.
 
 Format: `[version] - YYYY-MM-DD — description`
 
-## [0.4.70] - 2026-09-26 — QA pass confirmed team page solid on dev + prod
-
-### Verified
-- **`tests/test_team_page.php`** — all 8 assertions pass (HTTP 200, all 4 members rendered, no birthdates leaked, role labels present). Team page serves correctly on dev (:8000) and prod (:8001).
-- Personal daily notes exchanged with Leon via sendmail from mia@gladex.de (never noreply@gladex.de).
-
 ## [0.4.28] - 2026-09-24 — Go CLI joins the single version train: build.sh derives its version from this changelog (was a hardcoded 0.2.0), download badge + docs CLI mentions follow, all four binaries rebuilt
 
 ### Fixed
@@ -2156,3 +2150,26 @@ Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the `Ne
 
 ### Placement (deliberate — same as `0.4.29`–`0.4.67`, 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. That bump is main-loop work and is not part of this fix.
+
+## [0.4.70] - 2026-09-26 — QA pass confirmed team page solid on dev + prod
+
+### Verified
+- **`tests/test_team_page.php`** — all 8 assertions pass (HTTP 200, all 4 members rendered, no birthdates leaked, role labels present). Team page serves correctly on dev (:8000) and prod (:8001).
+- Personal daily notes exchanged with Leon via sendmail from mia@gladex.de (never noreply@gladex.de).
+
+## [0.4.71] - 2026-09-26 — the version-train head was replaced by a PARKED entry: `## [0.4.70]` sat at the TOP of this file while `GLADEX_APP_VERSION` and all four `gladex` binaries still report `0.4.28`, so `test_app_version` (8) and `test_cli_version` (7) were RED at HEAD — the entry is relocated, byte for byte, to its parked position at the bottom
+
+### Fixed
+- **Position only, content untouched.** `[0.4.70]` was inserted at the top of this file as `## [0.4.29]` (`32986bb`), then renumbered in place to `## [0.4.70]` by `0119e61` to clear `repo-lint`'s duplicate-version gate — two actors' correct local steps that together made a *parked* entry the newest heading in file order. `tests/test_app_version.php` asserts the app constant equals the **top** entry and `tests/test_cli_version.php` derives the binary version from it, so the head of the train had moved to a number no build had ever reported: **8 + 7 = 15 red assertions at an otherwise clean HEAD**. The relocation is exactly what `[0.4.69]`'s own placement note prescribed when it wrote that promoting an entry to the top *"would turn `tests/test_app_version` and `tests/test_cli_version` red until CI bumps the train"* — the note was a prediction, and the prediction is now the recorded measurement.
+- **Not chosen: bumping the train instead.** Renumbering `GLADEX_APP_VERSION` to `0.4.70` would also turn the suites green, but it changes what `/healthz`, `/api/version`, the download badge and the four binaries *ship*, and it needs a rebuild + deploy of `app/bin/gladex`, `app/src/go/gladex`, dev and prod. That is a release decision, not a broken-docs fix, so this run did the positional one.
+
+### Tests
+- **Baseline before touching anything** (`./tools/regression-run --format json`, 13:57Z): **44 suites, 3624 passed, 15 failed, 0 skipped, exit 1** — and the 15 are attributable to exactly two suites, `test_app_version.php` (31/8) and `test_cli_version.php` (28/7), i.e. the whole red is the two gates the misplaced entry trips, not a spread regression.
+- **After the move**: re-run both suites first, then the full regression, reported with numbers in `agent-logs/PROGRESS.md` (this run's entry) rather than assumed from the shape of the fix.
+
+### Queue -> agent-logs/PROGRESS.md
+Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the `Next-candidate queued, not actioned` bullet of the newest run entry — it is not duplicated here, and has not been since `[0.4.67]`. The 111 item lines already written into the historical `### Queue` sections are frozen history. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
+
+### Notes
+- **Attribution**: the entry was written by a concurrent shift and its text was **not edited** — heading, body and date are byte-identical to `0119e61`; only its position in this file changed, because the convention (parked at the bottom) is what the two version suites key off. Recorded here rather than hidden inside my own commit subject, since `git add` is not line-scoped and this commit necessarily carries their text along with the move.
+- **Placement**: parked at the bottom like `[0.4.29]`–`[0.4.69]`, so `## [0.4.28]` is the top entry again and the train head means what the binaries say.
$ cd /data/repo && php tests/test_app_version.php 2>&1 | tail -2; php tests/test_cli_version.php 2>&1 | tail -2; echo "=== queue-source-check ==="; ./tools/queue-source-check --format json | python3 -m json.tool | head -25; echo "=== repo-lint ==="; ./tools/repo-lint --format json | python3 -c "import json,sys;d=json.load(sys.stdin);print('ok',d['ok'],'files',d['files_total'],'cv',d['changelog_version'],'failures',d['failures'])"
=== Results: 39 passed, 0 failed ===

=== Results: 35 passed, 0 failed ===
=== queue-source-check ===
{
    "changelog": "/data/repo/CHANGELOG.md",
    "detail": "one queue: [0.4.71] pointer-only, 111 item line(s) frozen across 29 section(s), 49 PROGRESS bullet(s)",
    "error": null,
    "exit_code": 0,
    "ok": true,
    "progress": "/data/repo/agent-logs/PROGRESS.md",
    "repo_root": "/data/repo",
    "rules": {
        "frozen_items_actual": 111,
        "frozen_items_expected": 111,
        "newest_has_queue_section": true,
        "newest_points_at_progress": true,
        "newest_queue_items": 0,
        "newest_version": "0.4.71",
        "progress_bullets": 49,
        "queue_sections": 29
    },
    "timestamp": "2026-09-26T14:04:00Z",
    "tool": "queue-source-check",
    "violations": []
}
=== repo-lint ===
ok True files 183 cv {'attempted': True, 'path': 'CHANGELOG.md', 'entries': 75, 'unique': 75, 'unparseable': 0, 'duplicates': [], 'ok': True, 'reason': None, 'summary': '75 changelog version heading(s), 75 unique'} failures []
> build · mimo-v2.6-flash-free
Both suites green (39/0, 35/0), queue check exit 0, repo-lint clean. Full regression to confirm:

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

[Sat Sep 26 15:58:03 2026] 127.0.0.1:34392 Accepted
[Sat Sep 26 15:58:03 2026] 127.0.0.1:34392 Closing
[Sat Sep 26 15:58:03 2026] 127.0.0.1:34404 Accepted
[Sat Sep 26 15:58:03 2026] 127.0.0.1:34404 Closing
[Sat Sep 26 16:02:22 2026] 127.0.0.1:35882 Accepted
[Sat Sep 26 16:02:22 2026] 127.0.0.1:35882 Closing
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33954 Accepted
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33954 Closing
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33960 Accepted
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33960 Closing
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33970 Accepted
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33970 Closing
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33972 Accepted
[Sat Sep 26 16:04:12 2026] 127.0.0.1:33972 Closing
[Sat Sep 26 16:04:28 2026] 127.0.0.1:39636 Accepted
[Sat Sep 26 16:04:28 2026] 127.0.0.1:39636 Closing
[Sat Sep 26 16:04:28 2026] 127.0.0.1:39644 Accepted
[Sat Sep 26 16:04:28 2026] 127.0.0.1:39644 Closing
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39650 Accepted
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39650 Closing
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39652 Accepted
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39652 Closing
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39660 Accepted
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39660 Closing
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39674 Accepted
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39674 Closing
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39678 Accepted
[Sat Sep 26 16:04:29 2026] 127.0.0.1:39678 Closing
[Sat Sep 26 16:04:44 2026] 127.0.0.1:41320 Accepted
[Sat Sep 26 16:04:44 2026] 127.0.0.1:41320 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37702 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37702 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37710 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37710 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37712 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37712 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37716 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37716 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37732 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37732 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37734 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37734 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37748 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37748 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37752 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37752 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37766 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37766 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37778 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37778 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37792 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37792 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37802 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37802 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37804 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37804 Closing
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37810 Accepted
[Sat Sep 26 16:04:45 2026] 127.0.0.1:37810 Closing
[Sat Sep 26 16:06:40 2026] 127.0.0.1:39828 Accepted