Gladex Agent Logs

← Edit repo/tools/repo-lint
Index: repo/tools/repo-lint
===================================================================
--- repo/tools/repo-lint
+++ repo/tools/repo-lint
@@ -90,9 +90,12 @@
     0 - every linted file parses cleanly (and the committed Go module compiles)
     1 - at least one committed file fails to parse, a committed Go file does
         not compile, or the committed CHANGELOG.md repeats a version token
         (see failures[])
-    2 - invalid arguments
+    2 - invalid arguments; under `--format json` that is still ONE JSON object
+        on stdout (exit_code 2, error naming the bad argument) - never empty
+        stdin for a machine reader - while human mode keeps argparse's usage
+        prose on stderr exactly as before
     3 - cannot verify: not a git repo, unknown revision, a linter binary
         missing/timed out, or a docstring section this epilog is built from
         that is missing or empty (a lint that did not run is never a pass)
 

> build · mimo-v2.6-flash-free
← Edit repo/tools/repo-lint
Index: repo/tools/repo-lint
===================================================================
--- repo/tools/repo-lint
+++ repo/tools/repo-lint
@@ -127,8 +127,20 @@
 the definitions of the flags live in ONE place (_add_flags) read by both the
 scan and the parser, and why those three helpers sit above the epilog build:
 "never a pass" is a value, and the value has to be readable.
 
+The same rule covers the argv argparse itself rejects, which was the last
+path with no object: `--format json --timeout abc` printed usage to stderr
+and exited 2 with an EMPTY stdout, so a `| jq` consumer met jq's own parse
+error instead of our diagnosis - it could not tell a mistyped flag from a
+crash. _Parser.error picks the channel by reading --format with argparse (a
+throwaway parser carrying ONLY that flag, because the read has to survive the
+very bad --timeout that triggered it) and raises _UsageError only for json;
+main() reports it through die() with exit_code 2, so "you typed a bad flag"
+(2) stays distinct from "this could not be verified" (3). Where no format can
+be read at all - an invalid choice, an incomplete --format, anything after
+`--` - the channel stays human, because that argv named no format to honour.
+
 This tool is read-only: it never writes to the repo and never mutates git
 state (object reads only, no index/lock use, so it is safe to run while
 other shifts commit).
 """

> build · mimo-v2.6-flash-free
← Edit repo/tools/repo-lint
Index: repo/tools/repo-lint
===================================================================
--- repo/tools/repo-lint
+++ repo/tools/repo-lint
@@ -267,10 +267,10 @@
 def _now() -> str:
     return datetime.now(timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ")
 
 
-def die(p, repo, message, sha_requested, args_format):
-    """Fail closed with exit 3, still machine-readable in json mode.
+def die(p, repo, message, sha_requested, args_format, exit_code=EXIT_CANNOT):
+    """Fail closed with a non-verdict, machine-readable in json mode.
 
     THE one shape of a non-verdict in json mode: `error` carries the reason,
     `failures`/`errors` stay empty (nothing was linted, so nothing is blamed
     on a file), `go_compile` and `changelog_version` are null, `ok` is false.
@@ -278,8 +278,14 @@
     why these three definitions sit ABOVE it: at import time there is no
     parser yet, so `p` arrives as None (unused here) and the format/sha come
     from _pre_argparse instead of argparse.
 
+    `exit_code` exists for ONE caller: a usage error is the same non-verdict
+    shape but a DIFFERENT number - bad argv (2) must never read as "could not
+    verify" (3), or a machine consumer would retry a typo. Every other caller
+    takes the default, so exit 3 remains what "a lint that did not run is
+    never a pass" means.
+
     `p` is accepted for the call sites in main() and deliberately unused.
     """
     if args_format == "json":
         print(
@@ -298,18 +304,37 @@
                     "errors": [],
                     "go_compile": None,
                     "changelog_version": None,
                     "ok": False,
-                    "exit_code": EXIT_CANNOT,
+                    "exit_code": exit_code,
                 },
                 indent=2,
             )
         )
     else:
         print(f"repo-lint: ERROR {message}", file=sys.stderr)
-    return EXIT_CANNOT
+    return exit_code
 
 
+def _add_format_flag(p) -> None:
+    """The `--format` option, added to a parser - from HERE and nowhere else.
+
+    Extracted from _add_flags for one caller: the usage-error path (see
+    _format_of) needs a parser that answers `--format` and IGNORES every other
+    flag, because the read has to survive the bad `--timeout` that is the
+    whole reason it is running. Splitting the definition out would be a second
+    copy of the choices list - the drift this file keeps paying for - so the
+    choices/default/help live here and _add_flags calls this: one definition,
+    N readers, pinned by suite S16/S16b.
+    """
+    p.add_argument(
+        "--format",
+        choices=["human", "json"],
+        default="human",
+        help="output format (default: human)",
+    )
+
+
 def _add_flags(p) -> None:
     """Every non-help option, added to a parser by BOTH callers.
 
     SINGLE COPY of the flag definitions: main()'s parser and the pre-argparse

> build · mimo-v2.6-flash-free
← Edit repo/tools/repo-lint
Index: repo/tools/repo-lint
===================================================================
--- repo/tools/repo-lint
+++ repo/tools/repo-lint
@@ -344,21 +344,20 @@
     out a second time (prefix matching, --flag=value, `--` termination,
     last-wins), which is precisely the class of second copy this whole file
     keeps paying for. Both parsers are argparse, so the rules are the same
     rules by construction rather than by a test that remembers to compare them.
+
+    `--format` is delegated to _add_format_flag rather than spelled out here:
+    it is still ONE definition (this is a call, not a copy), and the separate
+    format-only reader in _format_of needs the very same object.
     """
     p.add_argument(
         "--sha",
         default="HEAD",
         help="git revision to lint (default: HEAD); any rev git accepts",
     )
+    _add_format_flag(p)
     p.add_argument(
-        "--format",
-        choices=["human", "json"],
-        default="human",
-        help="output format (default: human)",
-    )
-    p.add_argument(
         "--timeout",
         type=float,
         default=10.0,
         help="per-command timeout in seconds (default: 10)",
@@ -374,8 +373,40 @@
         ),
     )
 
 
+def _format_of(argv) -> str:
+    """The format this argv asks for, read by argparse before argparse runs.
+
+    Exists for ONE reason: when argparse REJECTS the argv, its error() has no
+    parsed values to consult and must still decide which stream to answer -
+    usage prose on stderr for a human, this tool's JSON object for a machine.
+    Deciding that with `if "--format json" in argv` would be argparse's rules
+    written out a second time (the `--flag=value` form, the unique-prefix
+    `--form`, `--` termination, last-wins), so it parses instead.
+
+    The parser carries ONLY --format, and that is load-bearing: given
+    `--timeout abc --format json` a full parser aborts at the bad float and
+    never reaches the flag whose job is to say how to report the abort. With
+    every other option unknown, argparse simply collects them as extras and
+    the read completes wherever the flag sits.
+
+    "human" is the honest answer for an argv this read cannot complete -
+    `--format yaml` (the choices list rejects it), `--format` with no value,
+    or anything after `--`, where the token is a positional and not a flag at
+    all. None of those named a readable format, so none is invented; the
+    human channel is argparse's own, unchanged.
+    """
+    p = argparse.ArgumentParser(add_help=False, prog="repo-lint")
+    _add_format_flag(p)
+    try:
+        with contextlib.redirect_stderr(io.StringIO()):
+            args, _extra = p.parse_known_args(argv)
+    except SystemExit:
+        return "human"
+    return args.format
+
+
 def _pre_argparse():
     """(format, sha) exactly as argparse would parse them, before argparse runs.
 
     Exists for ONE caller: the epilog refusal, which fires at import while

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

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

[Fri Sep 25 20:54:44 2026] 127.0.0.1:35742 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35742 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35748 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35748 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35764 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35764 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35774 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35774 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35778 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35780 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35778 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35780 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35788 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35788 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35804 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35804 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35818 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35818 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35832 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35832 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35840 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35840 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35846 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35856 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35846 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:35856 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:47514 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:47514 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:47530 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:47530 Closing
[Fri Sep 25 20:54:44 2026] 127.0.0.1:47544 Accepted
[Fri Sep 25 20:54:44 2026] 127.0.0.1:47544 Closing
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47556 Accepted
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47556 Closing
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47558 Accepted
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47558 Closing
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47568 Accepted
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47568 Closing
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47582 Accepted
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47582 Closing
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47596 Accepted
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47596 Closing
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47612 Accepted
[Fri Sep 25 20:54:45 2026] 127.0.0.1:47612 Closing
[Fri Sep 25 20:54:46 2026] 127.0.0.1:47616 Accepted
[Fri Sep 25 20:54:46 2026] 127.0.0.1:47616 Closing
[Fri Sep 25 20:54:46 2026] 127.0.0.1:47618 Accepted
[Fri Sep 25 20:54:46 2026] 127.0.0.1:47618 Closing
[Fri Sep 25 20:54:46 2026] 127.0.0.1:47632 Accepted
[Fri Sep 25 20:54:46 2026] 127.0.0.1:47632 Closing
[Fri Sep 25 20:56:18 2026] 127.0.0.1:41236 Accepted
[Fri Sep 25 20:56:18 2026] 127.0.0.1:41236 Closing
[Fri Sep 25 20:56:25 2026] 127.0.0.1:34978 Accepted
[Fri Sep 25 20:56:26 2026] 127.0.0.1:34978 Closing
[Fri Sep 25 20:56:42 2026] 127.0.0.1:53658 Accepted
[Fri Sep 25 20:56:42 2026] 127.0.0.1:53658 Closing
[Fri Sep 25 21:07:18 2026] 127.0.0.1:60578 Accepted
[Fri Sep 25 21:07:18 2026] 127.0.0.1:60578 Closing
[Fri Sep 25 21:07:19 2026] 127.0.0.1:60580 Accepted