code-coordinator 0.5.290__tar.gz → 0.5.291__tar.gz

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/.github/workflows/test.yml

@@ -31,6 +31,17 @@ jobs:
       # testpaths=["tests"]) was the one accidental gap. (ms-51 — Playwright,
       # never .py either — left this repo entirely with the webapp, #2009.)
       - run: pytest --ignore=tests/acceptance
+      # #2897: the Rust drift gate `tests/test_generated_rust_fixture.py`
+      # no longer byte-compares the committed `tui/src/app/types/generated.rs`
+      # (see docs/ADR_COORD_TUI_CI.md and the header comment further down
+      # this file) — this explicit step stands in for that comparison while
+      # `tui/` still lives here. `$COORD_TUI_SRC=.` names this checkout as
+      # the coord-tui root (`RUST_OUTPUT_RELPATH` keeps the `tui/` prefix for
+      # exactly this reason). One matrix leg only: the generator's output
+      # depends on `coord.serve_app.openapi_spec()`, not the Python version.
+      - name: python scripts/codegen.py --rust --check
+        if: matrix.python-version == '3.12'
+        run: COORD_TUI_SRC=. python scripts/codegen.py --rust --check
       # #2180: the cli-pytest sealed route (acceptance.drivers routes
       # "coord/**" -> cli-pytest -> tests/acceptance/ms-37) run through the
       # #2164 CI wrapper instead of a raw `pytest tests/acceptance` call, so
@@ -310,16 +321,31 @@ jobs:
   # for it to run against, and a job that installs Node to build nothing is
   # how the previous `acceptance`-on-every-push waste (#2389) started.
   #
-  # #1941: `scripts/codegen.py` also generates coord-tui's RUST wire types
-  # (`--rust`), and unlike the TS half above, `tui/` never left this repo —
-  # so that drift gate needs no separate job or `coord-web` checkout at all.
-  # It rides the ordinary `pytest --ignore=tests/acceptance` runs above, as
-  # `tests/test_generated_rust_fixture.py::
-  # test_committed_generated_rs_matches_generator_output`, the same way the
-  # TS-side `tests/test_generated_types_fixture.py` already rides them for
-  # the half of that check this repo can still make (the generator runs and
-  # covers every schema; the coord-web byte-comparison itself is that repo's
-  # own CI, per the paragraph above).
+  # #1941/#2897: `scripts/codegen.py` also generates coord-tui's RUST wire
+  # types (`--rust`). #2897 gave that half the SAME cross-repo shape as the
+  # TS half above (`--out PATH` / `$COORD_TUI_SRC`, no fallback default,
+  # docs/ADR_COORD_TUI_CI.md) — but `tui/` has not actually moved out of
+  # this repo yet, so unlike the TS byte-comparison (which is now
+  # exclusively `coord-web`'s CI job), the Rust byte-comparison has nowhere
+  # else to run yet and stays HERE, as an explicit step below rather than a
+  # pytest test:
+  #
+  #     COORD_TUI_SRC=. python scripts/codegen.py --rust --check
+  #
+  # `tests/test_generated_rust_fixture.py` itself is narrowed to what one
+  # checkout can prove — the generator runs and covers every schema — same
+  # as `tests/test_generated_types_fixture.py`; it no longer byte-compares
+  # the committed `tui/src/app/types/generated.rs`. The day coord-tui gets
+  # its own checkout + CI, delete the step below (its replacement lives in
+  # that CI, installing `code-coordinator[server]` from PyPI exactly as
+  # `coord-web`'s does) — no pytest file to un-narrow.
+  #
+  # The consumer-side INTEGER-backed-bool text-scraping guard
+  # (`coord/board_bool_guard.py`) that used to also read Rust source text
+  # here is RETIRED as of #2897, not moved — see docs/ADR_COORD_TUI_CI.md:
+  # #2895 (Phase 1 of #2894) deleted coord-tui's last direct SQL reader, so
+  # `tests/test_board_schema.py`'s DTO-level assertions are now the sole
+  # guard against that class.
 
   # #2886: a real Postgres 16 service, so `coord/sql.py`'s Postgres branches
   # (paramstyle translation, upsert idioms, `information_schema`

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.290
+Version: 0.5.291
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/code_coordinator.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.290
+Version: 0.5.291
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/code_coordinator.egg-info/SOURCES.txt

@@ -39,7 +39,6 @@ coord/approved_work.py
 coord/audit.py
 coord/auto_loop.py
 coord/block_log.py
-coord/board_bool_guard.py
 coord/board_schema.py
 coord/board_service.py
 coord/board_wire.py
@@ -296,6 +295,7 @@ deploy/coord-web-dist-build.timer
 deploy/coord-web-rollback.sh
 deploy/coord-web.service
 deploy/node-shim.sh
+docs/ADR_COORD_TUI_CI.md
 docs/ADR_COORD_WEB_ACCEPTANCE_SUITE.md
 docs/ADR_COORD_WEB_CI.md
 docs/ADR_COORD_WEB_DIST.md

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/code_coordinator.egg-info/scm_file_list.json

@@ -33,7 +33,6 @@
     "coord/audit.py",
     "coord/auto_loop.py",
     "coord/block_log.py",
-    "coord/board_bool_guard.py",
     "coord/board_schema.py",
     "coord/board_service.py",
     "coord/board_wire.py",
@@ -288,6 +287,7 @@
     "deploy/coord-web-rollback.sh",
     "deploy/coord-web.service",
     "deploy/node-shim.sh",
+    "docs/ADR_COORD_TUI_CI.md",
     "docs/ADR_COORD_WEB_ACCEPTANCE_SUITE.md",
     "docs/ADR_COORD_WEB_CI.md",
     "docs/ADR_COORD_WEB_DIST.md",

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/code_coordinator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.5.290",
+  "tag": "0.5.291",
   "distance": 0,
-  "node": "gd9ef2036c79e6b93ba2c92ee4c1a1756d509370f",
+  "node": "g408957bf4d2de2370d4e9df055a80c1680a697a2",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-29"

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/coord/board_schema.py

@@ -287,10 +287,12 @@ BOARD_PROJECTIONS: dict[str, type] = {
 #: therefore ship as ``0``/``1``.  Their DTO fields are annotated ``int`` on
 #: purpose; ``tests/test_board_schema.py`` asserts the generated JSON Schema
 #: types them ``integer`` and never ``boolean``, so the wire shape survives a
-#: storage-engine swap (Postgres would make these real ``BOOLEAN``s).  This is
-#: the DTO-level counterpart of ``coord/board_bool_guard.py``'s consumer-side
-#: check against the real Rust wire structs (``tui/src/app/types.rs`` and,
-#: since #1941, its generated ``types/generated.rs`` sibling).
+#: storage-engine swap (Postgres would make these real ``BOOLEAN``s).  This
+#: WAS the DTO-level counterpart of ``coord/board_bool_guard.py``'s consumer-
+#: side check against the real Rust wire structs (``tui/src/app/types.rs``
+#: and its generated ``types/generated.rs`` sibling, #1941); that
+#: text-scraping check is retired as of #2897 (docs/ADR_COORD_TUI_CI.md) —
+#: this assertion is now the sole remaining guard.
 INTEGER_BACKED_BOOLEANS: frozenset[str] = frozenset(
     {"is_interactive", "review_scoped", "hold_after", "no_acceptance"}
 )

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/coord/board_wire.py

@@ -113,7 +113,8 @@ TRUNCATION_NOTICE = "\n… [truncated on the /board wire — full text: detail e
 # two: `coord/**` and `tui/**`). Lines carrying it survive the body cut; see
 # `_machine_readable_residue`. Kept in sync with the Rust side by
 # tests/test_board_wire.py::test_allowed_glob_marker_matches_the_rust_parser,
-# the same cross-language guard posture as coord/board_bool_guard.py.
+# the same cross-language-guard posture the now-retired coord/board_bool_
+# guard.py used (#2897, docs/ADR_COORD_TUI_CI.md).
 #
 # Measured cost of the retention: ZERO on today's live board — 0 of 781
 # issue bodies carry the marker (the house `## Files` convention is a bare

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/coord/usage.py

@@ -380,9 +380,9 @@ def fetch_usage_rows(
     :class:`~coord.models.Assignment` instances — the aggregator consumes the
     daemon ``/board`` ``assignments`` shape directly, including
     ``is_interactive``, which is a real DB/wire column but (deliberately,
-    #748/#632 — see :mod:`coord.board_bool_guard`) not an ``Assignment``
-    dataclass field, so converting through ``Assignment`` would silently
-    drop it.
+    #748/#632 — see ``coord.board_schema.INTEGER_BACKED_BOOLEANS`` and
+    ``tests/test_board_schema.py``) not an ``Assignment`` dataclass field, so
+    converting through ``Assignment`` would silently drop it.
 
     Remote reads the same ``/board`` endpoint ``coord status`` polls. Local
     reads the sqlite DB directly via ``SqliteStore.list_assignments()``

code_coordinator-0.5.291/docs/ADR_COORD_TUI_CI.md

@@ -0,0 +1,217 @@
+# ADR: coord-tui's CI shape, and retiring the bool guard
+
+**Status:** Accepted
+**Date:** 2026-08-28
+**Issue:** #2897 (Phase 3 of #2894). Depends on #2895
+([Phase 1 of #2894](#phase-1-landed-what-it-changed) — landed).
+
+## Context
+
+`tui/` has not moved out of this repo yet. What #2897 has to decide is the
+*shape* the eventual coord-tui checkout's CI will need, so that when the move
+does happen it does not also have to invent this from scratch — the same
+sequencing #2009/#2006 used for the webapp (design first, in
+[`docs/ADR_COORD_WEB_CI.md`](ADR_COORD_WEB_CI.md), move second).
+
+Two Python gates in this repo currently read Rust source text or write to a
+fixed, checked-in Rust path, both of which assume one checkout:
+
+1. **The generator.** `scripts/codegen.py --rust` writes
+   `tui/src/app/types/generated.rs` — a hard-coded in-repo path, unlike its
+   TS half (`--out PATH` / `$COORD_WEB_SRC`, #2009) which already had to
+   solve this when the webapp moved to `coord-web`.
+2. **The bool guard.** `coord/board_bool_guard.py` regex-scrapes
+   `tui/src/app/types.rs` (+ its generated sibling) for plain `bool` struct
+   fields and cross-references them against a freshly-migrated SQLite
+   schema, closing the #632/#546/#628 blank-board class: a SQLite `INTEGER`
+   column deserialized into a strict Rust `bool` fails the *entire*
+   `BoardPayload` parse the first time it is `0`. This needs **both** a Rust
+   source tree and a live DB schema — the harder half to give a cross-repo
+   shape, because after a split those two things live in different repos.
+
+### Phase 1 landed: what it changed
+
+#2895 (Phase 1 of #2894, landed immediately ahead of this issue) deleted
+coord-tui's last direct SQL reader: `tui/src/app/data.rs` used to open
+`~/.coord/coord.db` read-only and hand-roll the board projection SQL — a raw
+column list, typed by rusqlite's own `FromSql`, entirely outside the JSON
+wire contract. `rusqlite` is gone from `tui/Cargo.toml`; every board read now
+goes through `coord serve`'s HTTP `/board` endpoint. That direct-SQL path
+never actually had the #632 boolean bug (rusqlite converts an `INTEGER`
+column to a Rust `bool` in-driver, no JSON in between) — but it meant the Rust
+binary had two categories of "consumer of column types": the hand-rolled SQL
+path, and the generated wire-struct path. Phase 1 leaves exactly one: the
+generated wire structs in `tui/src/app/types/generated.rs` (+ any hand-added
+mirror in `types.rs`), populated *only* from the `/board` JSON.
+
+That fact is what makes the bool-guard decision below tractable now, and is
+why this story is sequenced after Phase 1 rather than before it.
+
+## Decision 1 — the generator: mirror the TS half exactly
+
+`scripts/codegen.py --rust` now takes `--out PATH`, and resolves
+`$COORD_TUI_SRC` (a checkout root whose `tui/` holds coord-tui's crate) when
+`--out` is absent — the same two-rung resolution `resolve_output_path` already
+gave the TS half, implemented as `resolve_rust_output_path`. **No fallback
+default**, for the identical reason #2009 gave: silently writing a
+hard-coded path that a future checkout no longer contains would either
+recreate a dead directory nobody consumes, or, worse, report "up to date"
+against a file that does not exist — wrong in exactly the direction that
+looks like success.
+
+```bash
+# today, while tui/ still lives in this repo:
+COORD_TUI_SRC=. python scripts/codegen.py --rust --check
+# a real future coord-tui checkout:
+COORD_TUI_SRC=~/src/coord-tui python scripts/codegen.py --rust
+```
+
+`RUST_OUTPUT_RELPATH` keeps the `tui/` prefix (`<root>/tui/src/app/types/
+generated.rs`), unlike the TS `OUTPUT_RELPATH` (no `webapp/` prefix) — because
+today `$COORD_TUI_SRC` names *this* checkout, whose crate lives under `tui/`,
+and coord-tui's own eventual root layout is the still-open "move" story's
+decision, not this one's. If that story flattens the layout, updating one
+constant is the entire fix.
+
+### The drift gate splits the same way #2009 split the TS one
+
+- **Stays here:** `tests/test_generated_rust_fixture.py`, narrowed to what
+  one checkout can prove — the generator runs, produces well-formed output
+  (no accidental rustdoc doctests, see #1941's original incident), and
+  covers every schema in the served `/board` spec. This is the exact same
+  narrowing `tests/test_generated_types_fixture.py` got in #2009.
+- **Moves to coord-tui's CI**, once it exists: the byte-comparison of the
+  committed `generated.rs` against `generate_rust()`'s output right now —
+  `coord-web`'s equivalent already does this with
+  `python scripts/codegen.py --check --out src/api/generated.ts`. Until that
+  CI exists, `.github/workflows/test.yml`'s `test` job runs
+  `COORD_TUI_SRC=. python scripts/codegen.py --rust --check` directly as an
+  interim step (not a pytest test) — deletable in one line the day coord-tui
+  CI takes over, with zero pytest file to un-narrow.
+
+### Which `coord` that CI installs, and why (mirrors ADR_COORD_WEB_CI.md)
+
+Once coord-tui's CI exists and runs the byte-comparison above, it needs
+`scripts/codegen.py` — i.e. a `coord` install — on its runner, the same
+cross-repo-contract shape #2006 solved for `coord-web`. The answer here is
+**identical, for the identical reasons**, not a new decision:
+
+- **`pip install 'code-coordinator[server]'`, tracking latest, never an
+  exact pin.** `scripts/codegen.py --rust` imports `coord.serve_app`, which
+  imports Starlette at module scope — gated behind the `server` extra
+  (#1237) — so the bare distribution is not enough; `ModuleNotFoundError`
+  the moment `--rust` is used. And per [ADR_COORD_WEB_CI](ADR_COORD_WEB_CI.md)
+  part 1, an exact pin answers "does this compile against the coord we froze
+  in March", not "does this compile against the coord people actually have"
+  — the wrong question, answered green while a real drift ships.
+- **`code-coordinator`, never the `claude-coordinator` tombstone** (#2106) —
+  same trap, same fix, see that ADR's part 2.
+- A `>=` floor documenting the oldest `coord` whose `--rust`/`--out`/
+  `$COORD_TUI_SRC` flags the CI job relies on is encouraged, same as there.
+
+### What a red coord-tui CI job means
+
+Copying [ADR_COORD_WEB_CI's section verbatim in spirit](ADR_COORD_WEB_CI.md#what-a-red-coord-web-ci-job-means),
+because the failure shape is the same contract, just Rust instead of
+TypeScript: when coord-tui's drift-gate job fails on a PR that touched no
+Rust wire code, there are exactly two legitimate readings, and one forbidden
+response.
+
+1. **`coord.board_schema`'s wire contract changed** (a field added, removed,
+   or retyped on one of the seven `/board` projections) **without
+   regenerating.** This is a genuine contract break and the red is
+   *correct* — regenerate `generated.rs` from the new `code-coordinator`
+   release and commit the result.
+2. **A bad `code-coordinator` release** changed what `scripts/codegen.py
+   --rust` emits for an unrelated reason (a bug in the generator itself).
+   Yank/fix the release. Do **not** exact-pin coord-tui's CI to route around
+   it — that trades a loud, dated outage for the silent, undated kind.
+
+The forbidden response, same as the web ADR: silencing the job
+(`continue-on-error`, deleting the install step, pinning to last-known-green
+and walking away). That is exactly how a drift gate rots unnoticed.
+
+## Decision 2 — the bool guard: retire it (option 1 of 3)
+
+Three options were on the table:
+
+1. **Retire it.** If Phase 1 leaves no Rust consumer of column types outside
+   the generated wire structs, the text-scraping check has no subject, and
+   `tests/test_board_schema.py`'s DTO assertions are the guard that remains.
+2. **Move it to coord-tui's CI**, running against its own sources plus a
+   schema obtained from the daemon's OpenAPI spec rather than a live DB.
+3. **Keep it here** against a vendored copy of the Rust types. Rejected on
+   sight: a vendored copy is a mirror, and mirrors are exactly what this
+   program has spent its "Phase A" removing everywhere else (`GOAL.md`,
+   `docs/ARCHITECTURE.md`).
+
+**Decision: (1), retire it.** Phase 1 (#2895) landed first, confirming the
+premise: `rusqlite` is gone from `tui/Cargo.toml`, and `tui/src/app/data.rs`
+no longer opens a database at all. The *only* Rust consumer of `/board`
+column types left is `tui/src/app/types/generated.rs` (+ any hand mirror in
+`types.rs`), and that consumer is now doubly closed off from ever receiving
+an unguarded bool, independent of the retired scrape:
+
+- `tests/test_board_schema.py::test_integer_backed_booleans_are_declared_
+  integers` asserts every column in `board_schema.INTEGER_BACKED_BOOLEANS`
+  serializes as a JSON `integer` in the served spec, never `boolean`.
+- `tests/test_board_schema.py::test_no_board_dto_field_is_typed_bool` is the
+  **blanket** form: *no* board DTO field is ever typed JSON `boolean`,
+  because nothing in SQLite can produce one. Given that, `scripts/codegen.py`'s
+  own mechanical mapping (`rust_type_from_schema`) can *never* auto-emit a
+  Rust `bool` for a board wire field — a JSON `type: boolean` schema is the
+  only input that maps to `bool`, and the DTO layer guarantees no such input
+  exists.
+
+That closes the mechanical path completely: a future
+`ALTER TABLE ... ADD COLUMN x INTEGER` meant as a flag, added correctly to
+`board_schema.py` per its own convention (an `int`-typed dataclass field,
+registered in `INTEGER_BACKED_BOOLEANS` if it is genuinely boolean-shaped),
+can *never* reach the wire as a JSON boolean and can *never* be
+mechanically generated as an unguarded Rust `bool`. The only residual risk —
+a hand-authored `RUST_FIELD_OVERRIDES` entry in `scripts/codegen.py` that
+mistypes an `INTEGER`-backed field as plain `bool` — is a one-file, human-
+reviewed diff in *this* repo, not a drift class a text scrape across two
+repos could catch any more cheaply than ordinary review already does.
+
+Option (2) was rejected because it buys nothing options (1) doesn't already
+cover: the OpenAPI-derived schema it would compare against is exactly the
+same DTO-level information `test_board_schema.py` already asserts, just
+re-fetched a second time from a different vantage point, at the cost of a
+new schema-from-OpenAPI-spec plumbing path and a second repo's CI job to
+keep green. Cheapest, and the honest reading of the seam.
+
+`coord/board_bool_guard.py` is deleted. `tests/test_board_fixture.py` keeps
+only its fixture-freshness half (`test_board_sample_fixture_is_up_to_date`,
+`test_board_sample_fixture_parses_as_representative_payload`) — unrelated to
+the bool guard, never read Rust source text, and stays exactly as before.
+
+## Consequences
+
+- `scripts/codegen.py --rust` requires `--out PATH` or `$COORD_TUI_SRC`; no
+  argument and no env var is a refusal (exit 2), not a guess.
+- `tests/test_generated_rust_fixture.py` no longer byte-compares a
+  checked-in `tui/` path — it proves the generator runs and covers every
+  schema, mirroring `tests/test_generated_types_fixture.py`.
+- `.github/workflows/test.yml`'s `test` job runs
+  `COORD_TUI_SRC=. python scripts/codegen.py --rust --check` as an explicit
+  step, standing in for the byte-comparison gate until coord-tui's own CI
+  exists to take it over.
+- `coord/board_bool_guard.py` is deleted. The #632 blank-board class stays
+  closed by `tests/test_board_schema.py`'s DTO-level assertions
+  (`INTEGER_BACKED_BOOLEANS` + the blanket no-JSON-boolean check) — one
+  guard instead of two, at the layer where the invariant is actually
+  enforceable mechanically.
+- Standing up coord-tui's own CI workflow (the byte-comparison job, and
+  whatever `cargo test`/acceptance jobs it needs) remains open — that is the
+  still-separate "move" story's job, same posture #2006/#2009 took for
+  `coord-web`.
+
+## Rejected alternatives
+
+See "Decision 2" above for the bool-guard options. For the generator split,
+the rejected alternatives are the same ones #2009 already rejected for the
+TS half (an exact-pin coord-tui CI install, a git-ref install instead of
+PyPI, asserting the pin from inside coord-tui's own CI) — see
+[ADR_COORD_WEB_CI](ADR_COORD_WEB_CI.md#rejected-alternatives) for the
+reasoning, which applies unchanged.

{code_coordinator-0.5.290 → code_coordinator-0.5.291}/scripts/codegen.py

@@ -55,26 +55,57 @@ Usage:
     # exit 1 (no write) if that file is stale
     COORD_WEB_SRC=~/src/coord-web .venv/bin/python scripts/codegen.py --check
 
-#1941 — THIS SCRIPT ALSO GENERATES coord-tui's RUST WIRE TYPES. Unlike the TS
-half above, `tui/` still lives in *this* repo, so there is no cross-repo
-`--out`/env-var story: the Rust output path is a fixed, checked-in file,
-`tui/src/app/types/generated.rs`. The source of truth is a *different*
-OpenAPI document than the TS path reads — `coord.serve_app.openapi_spec()`
-(the daemon app, port 7435), not `coord.dashboard.server.openapi_spec()` (the
-dashboard app, port 7434) — because `GET /board`, the endpoint the TUI
-actually polls, is specified there, from the seven explicit wire DTOs in
-`coord/board_schema.py` (#1849). See `generate_rust()` below for the
-mechanical schema-walk + hand-curated-override split, which mirrors
-`ENUM_OVERRIDES`/`_ENUM_BLOCK` above but at the level of individual struct
-fields rather than whole enum types (Rust's richer type system — visibility,
-`#[serde(rename/default/deserialize_with)]`, custom deserializers for the
-INTEGER-backed-boolean guard — needs a finer-grained override point than TS
-did).
-
-    # regenerate tui/src/app/types/generated.rs
-    .venv/bin/python scripts/codegen.py --rust
+#1941 (extended by #2897) — THIS SCRIPT ALSO GENERATES coord-tui's RUST WIRE
+TYPES, and as of #2897 the Rust half is cross-repo capable the SAME SHAPE as
+the TS half above. `tui/` still lives in *this* repo today, but the eventual
+split (tracked separately — this story produces the shape, not the move)
+means the destination can't stay a fixed, checked-in path either: it is named
+explicitly by `--out PATH` or by `$COORD_TUI_SRC` pointing at a checkout root
+whose `tui/` holds coord-tui's crate, with the same no-fallback-default
+reasoning as `resolve_output_path` above — a guess is always wrong
+post-split, and under `--check` it is wrong in the direction that reports
+success. Today `$COORD_TUI_SRC=.` (this checkout's own root) reproduces the
+old fixed-path behaviour exactly (`<root>/tui/src/app/types/generated.rs`,
+i.e. `tui/src/app/types/generated.rs`).
+
+The source of truth is a *different* OpenAPI document than the TS path reads
+— `coord.serve_app.openapi_spec()` (the daemon app, port 7435), not
+`coord.dashboard.server.openapi_spec()` (the dashboard app, port 7434) —
+because `GET /board`, the endpoint the TUI actually polls, is specified
+there, from the seven explicit wire DTOs in `coord/board_schema.py` (#1849).
+See `generate_rust()` below for the mechanical schema-walk + hand-curated-
+override split, which mirrors `ENUM_OVERRIDES`/`_ENUM_BLOCK` above but at the
+level of individual struct fields rather than whole enum types (Rust's richer
+type system — visibility, `#[serde(rename/default/deserialize_with)]`,
+custom deserializers for the INTEGER-backed-boolean guard — needs a
+finer-grained override point than TS did).
+
+The drift GATE splits the same way #2009 split the TS one (docs/
+ADR_COORD_TUI_CI.md, #2897): what stays here is
+`tests/test_generated_rust_fixture.py`, narrowed to what one checkout can
+prove — the generator runs, produces well-formed output, and covers every
+schema in the served `/board` spec. The byte-for-byte comparison against a
+committed `generated.rs` belongs to coord-tui's own CI once it exists,
+installing `code-coordinator[server]` from PyPI to get this script — the same
+shape `docs/ADR_COORD_WEB_CI.md` (#2006) already gave the TS half, just not
+stood up yet (standing it up is the still-open "move" story's job, not
+this one's).
+
+The producer-side INTEGER-backed-boolean guard that used to cross-reference
+the Rust source text against a live SQLite schema (`coord/board_bool_guard.py`)
+is RETIRED as of #2897 — see `docs/ADR_COORD_TUI_CI.md` for the reasoning.
+Short version: #2895 (Phase 1 of #2894) deleted coord-tui's last direct SQL
+reader, so the structs this file generates are now the *only* Rust consumer
+of column types, and they are already pinned int-vs-bool by the DTO-level
+assertion in `tests/test_board_schema.py` (`board_schema.INTEGER_BACKED_BOOLEANS`).
+The text-scraping half had no remaining subject once that was true.
+
+    # today, while tui/ still lives in this repo:
+    COORD_TUI_SRC=. .venv/bin/python scripts/codegen.py --rust
     # exit 1 (no write) if that file is stale
-    .venv/bin/python scripts/codegen.py --rust --check
+    COORD_TUI_SRC=. .venv/bin/python scripts/codegen.py --rust --check
+    # or name the file directly
+    .venv/bin/python scripts/codegen.py --rust --out tui/src/app/types/generated.rs
 """
 
 from __future__ import annotations
@@ -90,17 +121,26 @@ from coord.serve_app import openapi_spec as board_openapi_spec
 
 REPO_ROOT = Path(__file__).resolve().parent.parent
 
-#: Fixed, in-repo destination for the generated Rust wire types (#1941).
-#: Unlike `OUTPUT_RELPATH` above, `tui/` never left this repo, so there is no
-#: cross-repo destination ambiguity to resolve — no `--out`, no env var.
-RUST_OUTPUT_PATH = REPO_ROOT / "tui" / "src" / "app" / "types" / "generated.rs"
-
 #: Path of the emitted file RELATIVE to a `coord-web` checkout's root.
 OUTPUT_RELPATH = Path("src") / "api" / "generated.ts"
 
 #: Env var naming a `coord-web` checkout root, used when `--out` is absent.
 OUTPUT_ENV_VAR = "COORD_WEB_SRC"
 
+#: Path of the emitted file RELATIVE to a `$COORD_TUI_SRC` checkout root
+#: (#2897) — i.e. `<root>/tui/src/app/types/generated.rs`. The `tui/` prefix
+#: stays even though the TS analogue (`OUTPUT_RELPATH`) has no `webapp/`
+#: prefix: today `$COORD_TUI_SRC` names *this* checkout (its coord-tui crate
+#: lives under `tui/`), and the eventual split hasn't decided coord-tui's own
+#: root layout yet — that decision belongs to the still-open "move" story,
+#: not this one.
+RUST_OUTPUT_RELPATH = Path("tui") / "src" / "app" / "types" / "generated.rs"
+
+#: Env var naming a checkout root whose `tui/` holds coord-tui's crate,
+#: used when `--out` is absent (#2897). `$COORD_TUI_SRC=.` (this checkout's
+#: own root) reproduces today's old fixed-path behaviour exactly.
+RUST_OUTPUT_ENV_VAR = "COORD_TUI_SRC"
+
 
 class OutputPathError(Exception):
     """No destination was named — see :func:`resolve_output_path`."""
@@ -126,6 +166,31 @@ def resolve_output_path(explicit: str | Path | None = None) -> Path:
         f"{OUTPUT_RELPATH}). See this script's module docstring."
     )
 
+
+def resolve_rust_output_path(explicit: str | Path | None = None) -> Path:
+    """Where to write/check ``generated.rs``: ``--out`` > ``$COORD_TUI_SRC``.
+
+    Mirrors ``resolve_output_path`` above, for the Rust half (#2897). Raises
+    :class:`OutputPathError` when neither is set, rather than guessing:
+    `tui/` still lives in this repo today, but silently falling back to that
+    fixed path would either recreate a dead directory nobody consumes once
+    coord-tui moves out, or, worse, report "up to date" against a file that
+    is not the one actually named — the same failure shape #2009 called out
+    for the TS half. Pass ``COORD_TUI_SRC=.`` to reproduce today's old
+    fixed-path behaviour explicitly.
+    """
+    if explicit is not None:
+        return Path(explicit).expanduser()
+    root = os.environ.get(RUST_OUTPUT_ENV_VAR)
+    if root:
+        return Path(root).expanduser() / RUST_OUTPUT_RELPATH
+    raise OutputPathError(
+        "no destination for generated.rs. Pass --out PATH or set "
+        f"${RUST_OUTPUT_ENV_VAR} to a coord-tui checkout root (the file is "
+        f"written to its {RUST_OUTPUT_RELPATH}) — e.g. $COORD_TUI_SRC=. for "
+        "this checkout's own tui/. See this script's module docstring."
+    )
+
 # Schemas to emit as TS interfaces, in display order — purely cosmetic (TS
 # `interface` declarations are hoisted, so forward references within
 # generated.ts are legal regardless of order). Anything present in the spec
@@ -1174,7 +1239,7 @@ RUST_HEADER = """\
 //! `coord/board_schema.py` (#1849) — #1941. Regenerate after any field change:
 //!
 //! ```text
-//! .venv/bin/python scripts/codegen.py --rust
+//! COORD_TUI_SRC=<coord-tui checkout root> .venv/bin/python scripts/codegen.py --rust
 //! ```
 //!
 //! (The fence is load-bearing, and `text` is the load-bearing part of *it*:
@@ -1183,17 +1248,21 @@ RUST_HEADER = """\
 //! that command as an indented block, or in a bare ``` fence, breaks
 //! `cargo test --doc` with `error: expected item, found `.``.)
 //!
-//! `tests/test_generated_rust_fixture.py` fails CI if this file drifts from what
-//! the generator produces right now, so a stale checkout can't merge — the Rust
-//! equivalent of `tests/test_generated_types_fixture.py` on the TS side.
+//! #2897: the destination is named explicitly (`--out PATH` / `$COORD_TUI_SRC`
+//! — see this script's module docstring), the same shape #2009 gave the TS
+//! half. `tests/test_generated_rust_fixture.py` proves the generator runs and
+//! covers every schema; the byte-for-byte freshness check against *this file
+//! as committed* is coord-tui's own CI job once it exists
+//! (`docs/ADR_COORD_TUI_CI.md`) rather than a test in this repo.
 //!
 //! **Every field defaults.** `/board` is one JSON payload: a single type
 //! mismatch on a single field fails the *entire* `BoardPayload` parse and
 //! blanks every TUI panel — the #632/#546/#628 failure class this repo has
-//! been bitten by three times (see `coord/board_bool_guard.py`). INTEGER-backed
-//! boolean columns (`is_interactive`, `hold_after`, `no_acceptance`,
-//! `review_scoped`) stay typed as an integer, or go through a coercing
-//! deserializer — never a plain `bool` — for the same reason.
+//! been bitten by three times. INTEGER-backed boolean columns
+//! (`is_interactive`, `hold_after`, `no_acceptance`, `review_scoped`) stay
+//! typed as an integer, or go through a coercing deserializer — never a
+//! plain `bool` — for the same reason (`coord/board_schema.py`'s
+//! `INTEGER_BACKED_BOOLEANS`, asserted int-typed by `tests/test_board_schema.py`).
 //!
 //! Field types for anything already consumed by the TUI are hand-pinned in
 //! `RUST_FIELD_OVERRIDES` (`scripts/codegen.py`) to match this file's
@@ -1223,27 +1292,37 @@ def generate_rust() -> str:
 
 
 def _main_rust(args: list[str]) -> int:
+    try:
+        output_path = resolve_rust_output_path(_parse_out(args))
+    except OutputPathError as exc:
+        print(str(exc), file=sys.stderr)
+        return 2
     content = generate_rust()
     if "--check" in args:
-        if not RUST_OUTPUT_PATH.exists():
+        # #2897: a MISSING file is a hard failure, not "stale vs empty" —
+        # mirrors the TS `--check` path's reasoning below. Absence usually
+        # means --out/$COORD_TUI_SRC is pointing somewhere that is not a
+        # coord-tui checkout, and treating that as ordinary staleness would
+        # send an operator off to regenerate into the wrong directory.
+        if not output_path.exists():
             print(
-                f"{RUST_OUTPUT_PATH} does not exist — run `python scripts/codegen.py "
-                "--rust` to generate it.",
+                f"{output_path} does not exist — is --out/${RUST_OUTPUT_ENV_VAR} "
+                "pointing at a coord-tui checkout?",
                 file=sys.stderr,
             )
             return 1
-        if RUST_OUTPUT_PATH.read_text() != content:
+        if output_path.read_text() != content:
             print(
-                f"{RUST_OUTPUT_PATH} is stale — run `python scripts/codegen.py --rust` "
-                "to regenerate.",
+                f"{output_path} is stale — run `python scripts/codegen.py "
+                f"--rust --out {output_path}` to regenerate.",
                 file=sys.stderr,
             )
             return 1
-        print(f"{RUST_OUTPUT_PATH} is up to date.")
+        print(f"{output_path} is up to date.")
         return 0
-    RUST_OUTPUT_PATH.parent.mkdir(parents=True, exist_ok=True)
-    RUST_OUTPUT_PATH.write_text(content)
-    print(f"wrote {RUST_OUTPUT_PATH}")
+    output_path.parent.mkdir(parents=True, exist_ok=True)
+    output_path.write_text(content)
+    print(f"wrote {output_path}")
     return 0
 
 
@@ -1262,9 +1341,9 @@ def _parse_out(args: list[str]) -> str | None:
 def main(argv: list[str] | None = None) -> int:
     args = sys.argv[1:] if argv is None else argv
     if "--rust" in args:
-        # #1941: the Rust path has a fixed in-repo destination (no --out/env
-        # var story — see RUST_OUTPUT_PATH's docstring), so it skips the
-        # TS-only path resolution below entirely.
+        # #2897: the Rust path is now cross-repo capable the same shape as
+        # the TS path below (--out / $COORD_TUI_SRC, no fallback default) —
+        # see resolve_rust_output_path's docstring.
         return _main_rust(args)
     try:
         output_path = resolve_output_path(_parse_out(args))