Gladex Agent Logs

 tests/test_repo_lint.sh | 6 ++++++
 1 file changed, 6 insertions(+)
=== regression progress:
-rw-r--r-- 1 root root 0 Oct  1 16:49 /tmp/opencode/m104b/regression.err
-rw-r--r-- 1 root root 0 Oct  1 16:49 /tmp/opencode/m104b/regression.json
0 /tmp/opencode/m104b/regression.json
> build · mimo-v2.6-flash-free
$ cd /data/repo && git show 97c1477 | tail -25; echo "=== last run 436 log line count / 435:"; head -2 /data/agent-logs/run-20261001-104159-435.log
commit 97c1477037afd0699b580d21bcefdde5c0d5bd98
Author: Atlas <atlas@gladex.de>
Date:   Thu Oct 1 13:27:45 2026 +0200

    run 444: 2026-10-01T11:27Z model=opencode/mimo-v2.6-flash-free

diff --git a/tests/test_repo_lint.sh b/tests/test_repo_lint.sh
index 48c7756..3819d98 100755
--- a/tests/test_repo_lint.sh
+++ b/tests/test_repo_lint.sh
@@ -451,6 +451,12 @@ run_tool "$SB/repo" --timeout 0
 assert_rc "G: --timeout 0 exits 2" 2 "$RC"
 run_tool "$SB/repo" --sha ""
 assert_rc "G: empty --sha exits 2" 2 "$RC"
+# G-sha-abbrev: abbreviated SHA (git rev-parse --short) is accepted and resolved
+ABBREV_SHA=$(g rev-parse --short HEAD)
+run_tool "$SB/repo" --sha "$ABBREV_SHA" --format json
+assert_rc "G-sha-abbrev: abbreviated SHA exits 0" 0 "$RC"
+json_ok "G-sha-abbrev: sha_resolved is the full 40-char SHA" \
+  "len(d['sha_resolved']) == 40 and d['requested_sha'] == '$ABBREV_SHA'"
 run_tool "$SB/repo" --help
 assert_rc "G: --help exits 0" 0 "$RC"
 assert_contains "G: --help documents all four exit codes" "exit codes:" "$OUT"
=== last run 436 log line count / 435:
=== run 435 at 2026-10-01T10:41:59+02:00 model=opencode/mimo-v2.6-flash-free ===

> build · mimo-v2.6-flash-free
$ cd /data/repo && git show HEAD -- tools/REGISTRY.md | head -140
commit 0cf2f9423417965cb9df706a8dffe93993dc3224
Author: Atlas <atlas@gladex.de>
Date:   Thu Oct 1 16:49:13 2026 +0200

    queue item (104): the wait class reaches its neighbours - |/& as start chars, & as terminator, plus the subshell rule that keeps the widening honest; five K-set expectations reconciled to measurement (133/5 -> 138/0), REGISTRY + changelog [0.4.156]

diff --git a/tools/REGISTRY.md b/tools/REGISTRY.md
index 30ea29e..2fb4c97 100644
--- a/tools/REGISTRY.md
+++ b/tools/REGISTRY.md
@@ -3561,7 +3561,7 @@ bash tests/test_detached_children.sh
 ```
 
 **Exit codes**:
-- `0` - all 116 assertions pass
+- `0` - all 138 assertions pass
 - `1` - one or more assertions failed, the registry is absent, or the sandbox could not be created (a refusal is never a green run)
 
 **Hermeticity**: no network, no live service, no runtime state — only the
@@ -3577,11 +3577,11 @@ live tree is never written, each copy is `rm -rf`d as soon as its control
 finishes, and each child suite cleans up its own `detchild.*` sandbox — so peak
 disc is one control copy (~3.3 MB).
 
-**116 assertions, 0 failed** — counted by tallying the section's own `PASS:`
-lines: **A 33, B 20, C 3, K 60** (sums to 116). Runtime ≈ 3 m 6 s (was ≈ 10 s
-before `[0.4.151]`: each of the K controls runs the whole **56**-assertion
-child suite, 15 × ≈ 10 s).
-- **A (33)** the census. Non-vacuity (a real tool set, every section naming a
+**138 assertions, 0 failed** — counted by tallying the section's own `PASS:`
+lines: **A 41, B 26, C 3, K 68** (sums to 138). Runtime ≈ 4 m 6 s (was ≈ 3 m 6 s
+before `[0.4.156]`: each of the K controls runs the whole **70**-assertion
+child suite, 17 × ≈ 10 s).
+- **A (41)** the census. Non-vacuity (a real tool set, every section naming a
   file), then the finding itself: exactly one tool puts a child in a foreign
   session (`regression-run`) and it carries the guard its construct owes;
   exactly one backgrounds a child (`go-compile-drift-verify`) and waits for it
@@ -3620,8 +3620,20 @@ child suite, 15 × ≈ 10 s).
   the terminator class widened), that same wait reads as **waited** (**A31**),
   and `wait; echo done` over three children stays a **bare** wait (**A32** — a
   tail that eats the separator reads `echo done` as two job names and covers
-  two of the three).
-- **B (20)** the primitive, measured rather than assumed: the wait-shape
+  two of the three). Then, since `[0.4.156]`, queue item **(104)** — the
+  neighbour-character plants, because the widened class now accepts `|` and
+  `&` on the START side and `&` on the terminator side: `true&&wait` **is** in
+  the census's WAIT records (**A33**), `true|wait` **is** too (**A34**), and
+  `wait&&echo done` **is** under a terminator that previously matched nothing
+  (**A35**); the `&&` file reads as **waited** (**A36** — an `&&`-joined wait
+  is this shell's own wait, and bash blocks on it) with its three children
+  still covered by what stays a **bare** wait (**A37**), while three pipeline
+  shapes read as **not** waited (**A38** `true|wait`, **A39** `true | wait`,
+  **A40** `wait | true`) — the direction the widening must NOT buy, since bash
+  runs a pipeline's `wait` in a subshell with an empty job table, and **A39 in
+  particular was a false positive before this step** (the spaced spelling
+  already matched the old class and read as waited).
+- **B (26)** the primitive, measured rather than assumed: the wait-shape
   fixture's child is observed **alive while the bound is still running**
   (non-vacuity — checking after the bound only ever proves the bound worked,
   which is the mistake the first draft of this suite made and reported as its
@@ -3639,29 +3651,36 @@ child suite, 15 × ≈ 10 s).
   reap. Since `[0.4.152]` the (101) shape is run end to end too (**B18–B20**):
   the reader's verdict on the `wait;` file is *waited*, the fixture exits **0**
   (its wait really completed instead of orphaning the child), and the child it
-  waited for is **gone**.
+  waited for is **gone**. Since `[0.4.156]` the (104) shapes are run end to end
+  as well (**B21–B26**), in both directions at once: the reader's verdict on
+  the `&&` file is *waited* and the process agrees (fixture exits **0** in ~1 s,
+  child gone), while its verdict on the pipeline file is *not* waited and the
+  process agrees too (fixture exits **0 immediately**, `sleep 61` still alive
+  and asserted so) — the measured half of the subshell rule, without which the
+  widened start class would have bought a false positive on that very file.
 - **C (3)** the rule rather than the instance: no tool creates a foreign
   session without owning the cleanup for it, exactly one tool needs that guard
   today, and no fixture process outlives the suite.
-- **K (60)** the fifteen mutation controls below, **executed** — queue item
-  **(100)**, `[0.4.151]`, with two more added by **(101)**, `[0.4.152]`.
+- **K (68)** the seventeen mutation controls below, **executed** — queue item
+  **(100)**, `[0.4.151]`, two more added by **(101)**, `[0.4.152]`, and two
+  more by **(104)**, `[0.4.156]`.
   Every figure this section has recorded since
   `[0.4.126]` used to be prose: `grep -rn "test_detached_children" tests/
   tools/` found exactly two hits (the suite and this section), the file had no
   in-file control section, and the patches were last re-run *by hand* in
   sandboxes on 2026-09-30 — evidence, not automation, so a reader changing a
-  plant would rot the table in silence. Section K runs all fifteen on every
+  plant would rot the table in silence. Section K runs all seventeen on every
   invocation in four steps, **`Kn a`–`Kn d`** each: plant ONE mutation in a
   fresh copy of `tests/` + `tools/` under `$SB/ctl/` (the live tree is never
   written) and assert it **applied** — a plant that did not take comes back
   0 red, the exact mistake `[0.4.126]` made twice; assert the child ran the
-  **whole** 56-assertion suite (`passed + failed == 56`, so a child that died
+  **whole** 70-assertion suite (`passed + failed == 70`, so a child that died
   early cannot be read as "few reds"); assert its `FAIL` labels are **exactly**
   the documented set **in order** (not "at least these", so a mutation that
   reddens something nobody predicted fails too); assert the exit code is `1`
   when something is red and `0` for the untouched copy. The child runs with
   `DETCHILD_CONTROLS=skip`, so a control cannot recurse into itself — that
-  skip is what keeps every child at 56. Two of the three plant helpers were
+  skip is what keeps every child at 70. Two of the three plant helpers were
   broken by their own section when it was written and the plants caught them:
   `awk -v sub=` dies in gawk (`sub` is a builtin) and the section quotes every
   pattern it plants, so the plants' `exactly one match` guard counted the
@@ -3684,9 +3703,32 @@ an untouched copy → **0 red / 42**. Two more, one per direction of the
 **1 red (`A15`)**, and an **over-strict pairing** where a bare `wait` covers
 only one child → **1 red (`A16`)**. **All seven were re-run and re-measured on
 2026-09-30 at 42 assertions** — the six historical figures hold unchanged, and
-the untouched copy is 42/0 (section K's K5 measures it at **0 red / 56**, the
-child's own count since `[0.4.153]`; it read 50 from `[0.4.145]` and 42
-before that).
+the untouched copy is 42/0 (section K's K5 measures it at **0 red / 70**, the
+child's own count since `[0.4.156]`; it read 56 from `[0.4.152]`, 50 from
+`[0.4.145]` and 42 before that).
+- **Five rows re-measured and two controls added since `[0.4.156]` (queue item
+  (104)) — all seventeen run at 138 assertions, measured 2026-10-01, child
+  70**: the **pre-(84) last-vs-last reader** now reads **9 red
+  (`A15 A27 A28 A29 A38 A39 A40 B14 B24`)**, 61/9 — it asks only whether a
+  WAIT record follows the last `&`, and a pipeline's wait prints one, so it has
+  no subshell rule to lose; the **over-strict pairing** now reads **3 red
+  (`A16 A32 A37`)**, 67/3 — A37 is the third instance of its own subject, a
+  bare wait over three children, this time closed by `&&`; the **pre-(86)
+  counting reader** now reads **9 red
+  (`A26 A27 A32 A37 A38 A39 A40 B14 B24`)**, 61/9 — neither the operator cut
+  nor the subshell rule was ever in it; the **operator cut removed** now reads
+  **3 red (`A29 A37 A40`)**, 67/3 — the cut is also what sets `op`, i.e. what
+  flags a left-hand subshell wait, so A40 is the cut's own casualty and not a
+  stray; and **K14** now reads **6 red (`A30 A31 A32 A35 A37 B18`)**, 64/6 —
+  A35/A37 join because their waits are closed by `&`, the terminator K14
+  narrows away. **K15 stays at 1 red (`A32`)**, 69/1: A37 does **not** join it
+  (measured, not assumed — the operator cut fires on the leading `&` whether
+  the tail hands it back or not), which is why the `&` half of the hand-back
+  class is queued as **(107)** instead of being documented as covered. The two
+  new controls: **K16** puts both live readers back on the pre-(104) class →
+  **6 red (`A33 A34 A35 A36 A37 B21`)**, 64/6, and **K17** deletes the subshell
+  rule → **4 red (`A38 A39 A40 B24`)**, 66/4. The twelve older rows are
+  unchanged at their measured sets, and the untouched copy is **0 red / 70**.
 - **Two rows re-measured and two controls added since `[0.4.152]` (queue item
   (101)) — all fifteen run at 116 assertions, measured 2026-10-01**: the
   **over-strict pairing** now reads **2 red (`A16 A32`)**, 54/2 — a bare
@@ -3741,6 +3783,27 @@ before that).
   non-containing tokens (`LIVE_GROUP_SET` / `install_guard_handler`), after
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -3726,10 +3726,11 @@
   the tail hands it back or not), which is why the `&` half of the hand-back
   class is queued as **(107)** instead of being documented as covered. The two
   new controls: **K16** puts both live readers back on the pre-(104) class →
   **6 red (`A33 A34 A35 A36 A37 B21`)**, 64/6, and **K17** deletes the subshell
-  rule → **4 red (`A38 A39 A40 B24`)**, 66/4. The twelve older rows are
-  unchanged at their measured sets, and the untouched copy is **0 red / 70**.
+  rule → **4 red (`A38 A39 A40 B24`)**, 66/4. The ten rows neither changed nor
+  added here (**K1–K5, K8, K9, K11, K12, K15**) are unchanged at their
+  measured sets, and the untouched copy is **0 red / 70**.
 - **Two rows re-measured and two controls added since `[0.4.152]` (queue item
   (101)) — all fifteen run at 116 assertions, measured 2026-10-01**: the
   **over-strict pairing** now reads **2 red (`A16 A32`)**, 54/2 — a bare
   `wait` closed by a separator over three children is the same subject and A32

> build · mimo-v2.6-flash-free

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

[Thu Oct  1 16:55:24 2026] 127.0.0.1:55454 Accepted
[Thu Oct  1 16:55:24 2026] 127.0.0.1:55454 Closing
[Thu Oct  1 16:55:24 2026] 127.0.0.1:55464 Accepted
[Thu Oct  1 16:55:25 2026] 127.0.0.1:55464 Closing
[Thu Oct  1 16:55:25 2026] 127.0.0.1:50048 Accepted
[Thu Oct  1 16:55:25 2026] 127.0.0.1:50048 Closing
[Thu Oct  1 16:56:06 2026] 127.0.0.1:47254 Accepted
[Thu Oct  1 16:56:06 2026] 127.0.0.1:47254 Closing
[Thu Oct  1 16:56:06 2026] 127.0.0.1:47258 Accepted
[Thu Oct  1 16:56:06 2026] 127.0.0.1:47258 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47264 Accepted
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47264 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47280 Accepted
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47280 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47294 Accepted
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47294 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47298 Accepted
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47298 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47300 Accepted
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47300 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47310 Accepted
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47310 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47316 Accepted
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47316 Closing
[Thu Oct  1 16:56:07 2026] 127.0.0.1:47330 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47330 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47342 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47342 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47356 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47356 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47368 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47368 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47376 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47376 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47388 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47388 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47392 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47392 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47408 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47408 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47420 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47420 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47422 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47422 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47434 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47434 Closing
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47450 Accepted
[Thu Oct  1 16:56:08 2026] 127.0.0.1:47450 Closing
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57278 Accepted
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57278 Closing
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57284 Accepted
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57284 Closing
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57300 Accepted
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57300 Closing
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57304 Accepted
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57304 Closing
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57314 Accepted
[Thu Oct  1 16:56:54 2026] 127.0.0.1:57314 Closing
[Thu Oct  1 16:57:04 2026] 127.0.0.1:41988 Accepted