From 5df797de470ae0e1e11858083863726f0e1d0fe6 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 17:17:28 -0800 Subject: [PATCH 1/5] chore(quest): claim quest/m1/ffi-refusals/own-pin.md Quest-Claim: 2affd1073e87f27c From 9433d0d39f78c0245e78162d365c8aa222665dd1 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 17:28:39 -0800 Subject: [PATCH 2/5] chore(ffi): the exporter pins moq on its own The exporter's `moq_rev` read rust2-ts's pin, so its moq bump waited on rind building for wasm32, which only the translator needs. It now holds the revision itself, starting at the same one, so nothing else moves. Co-Authored-By: Claude Haiku 5.5 --- ffi/justfile | 6 +++--- quest/m1/ffi-refusals/README.md | 7 +++---- quest/m1/ffi-refusals/moq-pin.md | 19 ++++++++++--------- quest/m1/ffi-refusals/own-pin.md | 22 ---------------------- ts/justfile | 4 ++-- 5 files changed, 18 insertions(+), 40 deletions(-) delete mode 100644 quest/m1/ffi-refusals/own-pin.md diff --git a/ffi/justfile b/ffi/justfile index fc4c72ddd..1402ef026 100644 --- a/ffi/justfile +++ b/ffi/justfile @@ -10,9 +10,9 @@ set shell := ["bash", "-euo", "pipefail", "-c"] cargo_shim := if env("RUST2_CARGO_SHIM", "") == "" { "" } else { env("RUST2_CARGO_SHIM") + ":" } export PATH := if env("RUST2_TS_TOOLCHAIN", "") == "" { env("PATH") } else { cargo_shim + env("RUST2_TS_TOOLCHAIN") / "bin:" + env("PATH") } -# The moq revision these recipes export by default: `just ts`'s, so both follow one moq. -# just's own path is quoted wherever bash runs it: on Windows, its backslashes are escapes. -moq_rev := shell(quote(just_executable()) + " --justfile ../ts/justfile --evaluate moq_rev") +# The moq revision these recipes export by default. It is the exporter's own pin, apart from +# the model fixture's in ts/fixtures/model/Cargo.toml, so bumping one does not wait on the other. +moq_rev := "ffcb7cd9748422daa30e935ec464108b5a8ebb71" # swift-collections 1.7.5, whose `UniqueArray` the generated Swift imports. swift_collections_rev := "f96b909e1a9e469620bc5037c1e24e00153f376f" diff --git a/quest/m1/ffi-refusals/README.md b/quest/m1/ffi-refusals/README.md index cf3ebae85..9b6bcca28 100644 --- a/quest/m1/ffi-refusals/README.md +++ b/quest/m1/ffi-refusals/README.md @@ -66,10 +66,9 @@ items, 41 of them in moq-tokio, and 6 types. Decided with the maintainer on 2026-11-12, in the quest audit: -- ✅ The exporter pins moq on its own, apart from rust2-ts's pin - ([own pin](/quest/m1/ffi-refusals/own-pin.md)), so its bump no longer waits on rind - building for wasm32, which only the translator needs. Rejected: one pin for both, at the - cost of two revisions to bump. +- ✅ The exporter pins moq on its own, apart from rust2-ts's pin, so its bump no longer + waits on rind building for wasm32, which only the translator needs. Rejected: one pin for + both, at the cost of two revisions to bump. - The last per-construct child landed in [#710](https://github.com/moq-dev/rust2/pull/710), yet the Goal is not reached: the 2026-11-11 nightly census diff --git a/quest/m1/ffi-refusals/moq-pin.md b/quest/m1/ffi-refusals/moq-pin.md index 310523dbc..f02653443 100644 --- a/quest/m1/ffi-refusals/moq-pin.md +++ b/quest/m1/ffi-refusals/moq-pin.md @@ -44,12 +44,12 @@ re-export and re-exports `Guard`, and `pub use kio;`), `lite::version::Version`, which was already unreachable at the pin, and moq-tokio's `quic::driver` items, which the narrowed stand-in drops. -Then bump the pin in `ts/fixtures/model/Cargo.toml`, which `ts/justfile`'s `moq_rev` reads, -and report the census before and after. The last bump -([#390](https://github.com/moq-dev/rust2/pull/390)) also changed `ffi/moq/ffi.toml`, every -`ffi/moq/moq.*`, and rust2-ts's model fixture, bench, and expected output, which share the -pin: run `just ts census` too, and update the count in the -[model epic](/quest/m2/ts-model/README.md). +Then bump both pins: the exporter's `moq_rev` in `ffi/justfile`, and rust2-ts's in +`ts/fixtures/model/Cargo.toml`, which `ts/justfile`'s `moq_rev` reads. Report the census +before and after. The last bump ([#390](https://github.com/moq-dev/rust2/pull/390)) also +changed `ffi/moq/ffi.toml`, every `ffi/moq/moq.*`, and rust2-ts's model fixture, bench, and +expected output, which then shared one pin: run `just ts census` too, and update the count +in the [model epic](/quest/m2/ts-model/README.md). Decided with the maintainer on 2026-11-09: bump to moq's current main now, and narrow the Goal to the two moq-owned types. Rejected: wait for moq to fix the rest first. Not landed: @@ -69,8 +69,10 @@ returns that are not `Clone`. ## Waiting -- moq-dev/moq: `rind` builds for wasm32. moq-net depends on `rind`, whose md5 inline asm has - no wasm32 arm, so `just ts moq ` fails at moq's `main`. Done when it passes there. +- moq-dev/moq: `rind` builds for wasm32, which only rust2-ts's pin in + `ts/fixtures/model/Cargo.toml` needs, not the exporter's in `ffi/justfile`. moq-net depends + on `rind`, whose md5 inline asm has no wasm32 arm, so `just ts moq ` fails at + moq's `main`. Done when it passes there. The fix merged in rind's `main` ([moq-dev/rind#543](https://github.com/moq-dev/rind/pull/543)) and ships in rind 0.4.0. Its release PR ([moq-dev/rind#511](https://github.com/moq-dev/rind/pull/511)) stays unmerged on purpose, @@ -88,6 +90,5 @@ returns that are not `Clone`. ## Required -- [Own pin](/quest/m1/ffi-refusals/own-pin.md) - the exporter's pin moves without rust2-ts's, which ends the wait on `rind` for wasm32 - [`NonZero`](/quest/m1/ffi-refusals/nonzero.md) - 15 of the 36 errors at moq's `main` - [Every refusal at moq's main](/quest/m1/ffi-refusals/moq-main.md) - the rest of them, so the bump adds no exclude diff --git a/quest/m1/ffi-refusals/own-pin.md b/quest/m1/ffi-refusals/own-pin.md deleted file mode 100644 index 932ebae83..000000000 --- a/quest/m1/ffi-refusals/own-pin.md +++ /dev/null @@ -1,22 +0,0 @@ -# [XS] The exporter pins moq on its own - -## Goal - -[rust2-ffi](/ffi/README.md)'s moq recipes read a moq revision of their own, so the -exporter's pin moves without rust2-ts's. Today `ffi/justfile`'s `moq_rev` evaluates -`ts/justfile`'s, which reads it from `ts/fixtures/model/Cargo.toml`, so -[the bump](/quest/m1/ffi-refusals/moq-pin.md) waits on moq building for wasm32, which -only the translator needs. - -## Plan - -Decided with the maintainer on 2026-11-12, in the quest audit: ✅ two pins. Rejected: one -pin for both. - -- `ffi/justfile` holds the 40-character revision itself, starting at today's shared one, - so nothing else changes in this PR. The binding benchmark and `go/justfile`'s bench - recipe follow whichever pin their recipe already reads; say which in the PR. -- This PR removes the bump's `Waiting` item on `rind` building for wasm32, and moves that - wait to wherever rust2-ts's own bump is planned, or records that none is. - -Public API: none. diff --git a/ts/justfile b/ts/justfile index 0ba95cdf8..1041c2207 100644 --- a/ts/justfile +++ b/ts/justfile @@ -19,8 +19,8 @@ bindgen := "fixtures/bindgen/Cargo.toml" # The WebCodecs fixture, its own workspace like the wasm-bindgen fixture, behind web-sys's unstable APIs. encoder := "fixtures/encoder/Cargo.toml" -# The moq revision `moq` and `census` translate and `just ffi` exports by default: the one -# the model fixture builds. Read without taplo, which the nightly's runners outside Nix lack. +# The moq revision `moq` and `census` translate by default: the one the model fixture builds. +# The exporter has its own pin in ffi/justfile. Read without taplo, which the nightly's runners outside Nix lack. moq_rev_match := replace_regex(read(model), '(?s).*\nmoq-net = \{[^\n]*\brev = "([0-9a-f]{40})".*', '$1') moq_rev := if moq_rev_match =~ '^[0-9a-f]{40}$' { moq_rev_match } else { error("no moq-net rev in " + model) } From 2a8a1ba1c564d236a5674ee7a51bdd681fb9cb7c Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 17:44:21 -0800 Subject: [PATCH 3/5] chore(quest): split the moq pin bump, rust2-ts's into its own quest The maintainer chose the split on 2026-11-12: the exporter's pin bumps in moq-pin.md, and rust2-ts's pin bumps in m2/ts-model/moq-pin.md, which carries the rind 0.4 wait. The exporter's bump no longer waits on rind. Also drops the stale 'just ffi' from the model manifest's pin comment. Co-Authored-By: Claude Haiku 5.5 --- quest/m1/ffi-export/README.md | 4 +-- quest/m1/ffi-refusals/moq-pin.md | 35 +++++++++++--------------- quest/m2/ts-model/README.md | 5 ++++ quest/m2/ts-model/moq-pin.md | 43 ++++++++++++++++++++++++++++++++ ts/README.md | 2 +- ts/fixtures/model/Cargo.toml | 2 +- 6 files changed, 66 insertions(+), 25 deletions(-) create mode 100644 quest/m2/ts-model/moq-pin.md diff --git a/quest/m1/ffi-export/README.md b/quest/m1/ffi-export/README.md index 95937ca12..4c86fcf71 100644 --- a/quest/m1/ffi-export/README.md +++ b/quest/m1/ffi-export/README.md @@ -79,8 +79,8 @@ Decided with the maintainer on 2026-11-12, in the quest audit: - ✅ The epic's closing work is a child, [ship](/quest/m1/ffi-export/ship.md), which alone requires [the refusals epic](/quest/m1/ffi-refusals/README.md). Rejected: the epic requiring it, as [#701](https://github.com/moq-dev/rust2/pull/701) left it, since an - epic's `Required` holds back every child, so none could start until moq's pin bump, - which waits on a rind release the maintainer holds. + epic's `Required` holds back every child, so none could start until moq's pin bump, which + then waited on a rind release the maintainer held. - ✅ Every change that breaks the C ABI or a generated API is a child here, so it lands before moq pins: [the fused async start](/quest/m1/ffi-export/async-start.md), [owned buffers](/quest/m1/ffi-export/owned-bufs.md), diff --git a/quest/m1/ffi-refusals/moq-pin.md b/quest/m1/ffi-refusals/moq-pin.md index f02653443..740826890 100644 --- a/quest/m1/ffi-refusals/moq-pin.md +++ b/quest/m1/ffi-refusals/moq-pin.md @@ -1,8 +1,8 @@ -# [S] Bump the moq pin past its re-export and reachability fixes +# [S] Bump the exporter's moq pin past its re-export and reachability fixes ## Goal -The moq pin moves to moq's current `main`, whose crates re-export no whole crate, moq's own +The exporter's moq pin moves to moq's current `main`, whose crates re-export no whole crate, moq's own included. `just ffi census` there lists no whole-crate re-export refusal. Its "type not reachable from the crate root" refusals are `kio::Pending` and `lite::version::Version`, which the exporter change below exports, and moq-quic's stats and varint types under moq-tokio's `quic::driver`, @@ -33,7 +33,8 @@ At `ffcb7cd9`, `container::Producer::modify` returns moq-mux's session side also drops `quic::driver`. Decided with the maintainer on 2026-11-07, in the quest audit: one pin bump for both, since -each is an XS bump of the same pin line. Rejected: one bump per moq quest. +each is an XS bump of the same pin line. Rejected: one bump per moq quest. Superseded on +2026-11-12 by the split below. Both of moq's fixes merged on 2026-11-09: [moq-dev/moq#8247](https://github.com/moq-dev/moq/pull/8247) dropped every whole-crate @@ -44,12 +45,11 @@ re-export and re-exports `Guard`, and `pub use kio;`), `lite::version::Version`, which was already unreachable at the pin, and moq-tokio's `quic::driver` items, which the narrowed stand-in drops. -Then bump both pins: the exporter's `moq_rev` in `ffi/justfile`, and rust2-ts's in -`ts/fixtures/model/Cargo.toml`, which `ts/justfile`'s `moq_rev` reads. Report the census -before and after. The last bump ([#390](https://github.com/moq-dev/rust2/pull/390)) also -changed `ffi/moq/ffi.toml`, every `ffi/moq/moq.*`, and rust2-ts's model fixture, bench, and -expected output, which then shared one pin: run `just ts census` too, and update the count -in the [model epic](/quest/m2/ts-model/README.md). +Then bump the exporter's `moq_rev` in `ffi/justfile`, and report the census before and +after. The last bump ([#390](https://github.com/moq-dev/rust2/pull/390)) also changed +`ffi/moq/ffi.toml`, every `ffi/moq/moq.*`, and rust2-ts's model fixture, bench, and expected +output, which then shared one pin. rust2-ts's pin moves in +[its own quest](/quest/m2/ts-model/moq-pin.md), so its census count is updated there. Decided with the maintainer on 2026-11-09: bump to moq's current main now, and narrow the Goal to the two moq-owned types. Rejected: wait for moq to fix the rest first. Not landed: @@ -60,6 +60,11 @@ not reach by its defining path, such as `kio::Pending` and `lite::version::Versi whose defining path is itself private stays refused (rejected: (b) moq makes both reachable). This quest makes the exporter change, in `ffi/src/collect.rs`, before the bump. +Decided with the maintainer on 2026-11-12, when the exporter's pin was split off: ✅ split the +bump, the exporter's pin here and rust2-ts's in [its own quest](/quest/m2/ts-model/moq-pin.md), +so this bump no longer waits on rind building for wasm32. Rejected: keep one bump for both +pins, which holds the exporter behind rind. + Measured on 2026-11-12 at moq's `main` `6936f0a`: `just ffi moq-cpp` fails the export with 36 errors, which the bump fixes in `ffi/moq/ffi.toml` or the exporter: 15 on the foreign type `std::num::NonZero` (such as `Client::with_peer_hop`), 11 stale excludes naming nothing @@ -69,18 +74,6 @@ returns that are not `Clone`. ## Waiting -- moq-dev/moq: `rind` builds for wasm32, which only rust2-ts's pin in - `ts/fixtures/model/Cargo.toml` needs, not the exporter's in `ffi/justfile`. moq-net depends - on `rind`, whose md5 inline asm has no wasm32 arm, so `just ts moq ` fails at - moq's `main`. Done when it passes there. - The fix merged in rind's `main` ([moq-dev/rind#543](https://github.com/moq-dev/rind/pull/543)) - and ships in rind 0.4.0. Its release PR - ([moq-dev/rind#511](https://github.com/moq-dev/rind/pull/511)) stays unmerged on purpose, - as rind's `quest/m2/api/release-0.4.md` decides, until the CPU-check removal, the benchmark - refresh, and moq's move are ready (reconfirmed by the maintainer on 2026-11-12); then - [moq-dev/moq#8432](https://github.com/moq-dev/moq/pull/8432) moves moq to rind 0.4. Check: - `cargo search rind` shows 0.4.0. On 2026-11-12 moq `c681b7a` still locks rind 0.3.1, and - rind 0.3.2, tagged 2026-11-08, predates the fix. - moq-dev/moq: moq-tokio builds without tripping `recursion_depth_exceeding_limit` (an overflow proving `Send` on `Instrumented<...>`), which `just ffi moq-cpp ` denies. Done when it passes at moq's `main`. Still failing on 2026-11-12 at moq `c681b7a`, at diff --git a/quest/m2/ts-model/README.md b/quest/m2/ts-model/README.md index 247ab04bf..870f4ef91 100644 --- a/quest/m2/ts-model/README.md +++ b/quest/m2/ts-model/README.md @@ -8,6 +8,11 @@ calls (kio, with its clock, and moq-pattern), as it translates the codec today, ## Plan +Decided with the maintainer on 2026-11-12, when the exporter's pin was split off: ✅ the model +fixture's moq pin bumps in its own quest, [moq-pin](/quest/m2/ts-model/moq-pin.md), apart from +the exporter's, and that quest updates this epic's census count. Rejected: one bump for both +pins, which holds the exporter behind rind. + Decided with the maintainer on 2026-11-09, in the quest audit: ✅ WASM ships, and the translation must beat it. [rust2-wasm](/quest/m2/wasm/README.md) is moq's browser route, and its gate compares this translation against it; moq adopts the translation only where diff --git a/quest/m2/ts-model/moq-pin.md b/quest/m2/ts-model/moq-pin.md new file mode 100644 index 000000000..f76d8be9a --- /dev/null +++ b/quest/m2/ts-model/moq-pin.md @@ -0,0 +1,43 @@ +# [XS] Bump rust2-ts's moq pin + +## Goal + +The model fixture's moq pin, the revision `ts/justfile`'s `moq_rev` reads, moves to moq's +current `main`, so `just ts moq` and `just ts census` measure the model there and the model +epic's census count is current. The exporter's pin moves on its own, in +[its bump](/quest/m1/ffi-refusals/moq-pin.md). + +## Plan + +Decided with the maintainer on 2026-11-12, when the exporter's pin was split off: ✅ rust2-ts's +pin bumps here, apart from the exporter's, so the exporter's bump no longer waits on rind +building for wasm32. Rejected: one bump for both pins, which holds the exporter behind rind. + +- Set `rev` in `ts/fixtures/model/Cargo.toml` to moq's `main`, then run `cargo update -p moq-net` + there, as its comment says. +- Run `just ts moq ` and `just ts census`. Regenerate `expected/`, and any `ts/bench` + file the new moq API changes, as the last bump ([#390](https://github.com/moq-dev/rust2/pull/390)) + did for this pin. +- Update the census count in the [model epic](/quest/m2/ts-model/README.md) from the census at + the new pin. +- Touches no `ffi/` file: the exporter's bump owns those. + +Public API: none. The translator's output changes only where moq's API does. + +## Waiting + +- moq-dev/moq: `rind` builds for wasm32. moq-net depends on `rind`, whose md5 inline asm has + no wasm32 arm, so `just ts moq ` fails at moq's `main`. Done when it passes there. + The fix merged in rind's `main` ([moq-dev/rind#543](https://github.com/moq-dev/rind/pull/543)) + and ships in rind 0.4.0. Its release PR + ([moq-dev/rind#511](https://github.com/moq-dev/rind/pull/511)) stays unmerged on purpose, + as rind's `quest/m2/api/release-0.4.md` decides, until the CPU-check removal, the benchmark + refresh, and moq's move are ready (reconfirmed by the maintainer on 2026-11-12); then + [moq-dev/moq#8432](https://github.com/moq-dev/moq/pull/8432) moves moq to rind 0.4. Check: + `cargo search rind` shows 0.4.0. On 2026-11-12 moq `c681b7a` still locks rind 0.3.1, and + rind 0.3.2, tagged 2026-11-08, predates the fix. + +## Related + +- [The exporter's moq pin](/quest/m1/ffi-refusals/moq-pin.md) - the same moq `main`, bumped on its own pin + diff --git a/ts/README.md b/ts/README.md index 134e04106..d78043044 100644 --- a/ts/README.md +++ b/ts/README.md @@ -1288,7 +1288,7 @@ so adding, removing, or reordering a case changes no other case's inputs. Bun bundles a caller of `Decoder.u8` and `Decoder.new` through `import * as Decoder`, which must keep only those and what they call. - `model` depends on moq-net at the moq pin, its `rev`, which `just ts moq` and - `just ts census` check out too, and translates with it as one program. It is a + `just ts census` check out, and translates with it as one program. It is a workspace of its own, so its lockfile keeps moq's checkout out of the package's inputs. Its harness runs what of the model translates with nothing refused or bound, `Timestamp` and `Timescale`: their constructors, conversions, `u128` reads, sums, differences, diff --git a/ts/fixtures/model/Cargo.toml b/ts/fixtures/model/Cargo.toml index 25d64251e..fe008e0db 100644 --- a/ts/fixtures/model/Cargo.toml +++ b/ts/fixtures/model/Cargo.toml @@ -15,7 +15,7 @@ publish = false crate-type = ["lib", "cdylib"] [dependencies] -# The moq pin, which `just ts moq`, `just ts census`, and `just ffi` check out too; bumping it is +# The moq pin, which `just ts moq` and `just ts census` check out; bumping it is # `cargo update -p moq-net` after this rev. Without `async`, the model builds without a runtime. moq-net = { git = "https://github.com/moq-dev/moq", rev = "ffcb7cd9748422daa30e935ec464108b5a8ebb71", default-features = false } From a9e679829a7109db7bf3b5230a6c27838df24650 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 17:57:29 -0800 Subject: [PATCH 4/5] chore(quest): drop a stray tag, and the exporter bump's stale rind note The new ts-model quest ended with a stray closing tag. The exporter's bump still said its pin waited on 'just ts moq', which is the translator's wait. Co-Authored-By: Claude Haiku 5.5 --- quest/m1/ffi-refusals/moq-pin.md | 4 +++- quest/m2/ts-model/moq-pin.md | 1 - 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/quest/m1/ffi-refusals/moq-pin.md b/quest/m1/ffi-refusals/moq-pin.md index 740826890..cb78eb241 100644 --- a/quest/m1/ffi-refusals/moq-pin.md +++ b/quest/m1/ffi-refusals/moq-pin.md @@ -53,7 +53,9 @@ output, which then shared one pin. rust2-ts's pin moves in Decided with the maintainer on 2026-11-09: bump to moq's current main now, and narrow the Goal to the two moq-owned types. Rejected: wait for moq to fix the rest first. Not landed: -moq's `main` fails `just ts moq` and `just ffi moq-cpp`, so the bump waits on Waiting. +moq's `main` fails `just ts moq` and `just ffi moq-cpp`, so the bump waits on Waiting. The +split on 2026-11-12 moved the `just ts moq` failure to +[its own quest](/quest/m2/ts-model/moq-pin.md), so this bump waits on `just ffi moq-cpp` alone. Decided 2026-11-11 (maintainer, /quest-unblock): ✅ (a) rust2 exports a type the crate root does not reach by its defining path, such as `kio::Pending` and `lite::version::Version`; a type diff --git a/quest/m2/ts-model/moq-pin.md b/quest/m2/ts-model/moq-pin.md index f76d8be9a..ee9caa54d 100644 --- a/quest/m2/ts-model/moq-pin.md +++ b/quest/m2/ts-model/moq-pin.md @@ -40,4 +40,3 @@ Public API: none. The translator's output changes only where moq's API does. ## Related - [The exporter's moq pin](/quest/m1/ffi-refusals/moq-pin.md) - the same moq `main`, bumped on its own pin - From 32a001108e1a9f01d6eb1ec3d6bfcc4cba737dcb Mon Sep 17 00:00:00 2001 From: Luke Curley <432854+kixelated@users.noreply.github.com> Date: Fri, 13 Nov 2026 15:24:29 -0800 Subject: [PATCH 5/5] docs(quest): link #390 in rust2 itself, not moq-dev/rust2 Co-Authored-By: Claude Haiku 5.5 --- quest/m2/ts-model/moq-pin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/quest/m2/ts-model/moq-pin.md b/quest/m2/ts-model/moq-pin.md index ee9caa54d..249b01490 100644 --- a/quest/m2/ts-model/moq-pin.md +++ b/quest/m2/ts-model/moq-pin.md @@ -16,7 +16,7 @@ building for wasm32. Rejected: one bump for both pins, which holds the exporter - Set `rev` in `ts/fixtures/model/Cargo.toml` to moq's `main`, then run `cargo update -p moq-net` there, as its comment says. - Run `just ts moq ` and `just ts census`. Regenerate `expected/`, and any `ts/bench` - file the new moq API changes, as the last bump ([#390](https://github.com/moq-dev/rust2/pull/390)) + file the new moq API changes, as the last bump ([#390](https://github.com/kixel-ai/rust2/pull/390)) did for this pin. - Update the census count in the [model epic](/quest/m2/ts-model/README.md) from the census at the new pin.