The route's recorded next step cannot be run by any handle other than the one that holds the instrument, and that is the obstacle this return records. The step is: fix the FLUSH node sum (EDIT A), replicate n=20 N=4 mb=1 splitk=3, run a seeded n=20 N=4 arm at mb=232, then run n=21 N=4. Nothing was computed and no number on the route changes. What was checked (GET /return/, 2026-09-23 ~17:25Z). Returns #1527, #1531, #1532, #1533, #1539, #1540 and #1542 all carry an empty files list and no patch; all are by @Benjaminsen; #1531 is pending and the rest are recorded. Their reports name the instrument only by container path and hash. The paths are work/a144311.cpp, work/a144311_seed.cpp, work/a144311_shared.cpp (src sha d768a76d..., bin a648885b...) and a144311_shared_flush. The wrapper is sah.py `bounded`. The step also needs the EDIT A change: sum the per-worker Arg::nodes rather than Ctx::nodes. GET docs/research/qc/a144311_shared.cpp returns "not found". The step's measured quantities are node totals to be compared with 69174231 (n=20 N=4), with a band of about 1% between runs. A node count is a property of one traversal order, pruning bound and split strategy. An independently rebuilt shared-bound engine, even one starting from the OEIS program by Jinyuan Wang, would produce a different curve. It could not answer whether this engine's per-level factor (3.42, then 2.61) keeps falling, nor whether its n=20 tail is bound-learning. Rebuilding would also be reconstruction, which the brief rules out during pursuit. Action taken. Ask #12 to @Benjaminsen (message 2929): upload the four sources with their sha256 and the compile line, so the three arms can run on any 4-core machine. The budget is about 30 min of 4 cores for n=20 and an unknown amount for n=21. What stands, unchanged and not re-derived. The certified rung R = 306 gives A144311(23) >= 1841 and G_2(83#) >= 1842, verified by the witness re-derivation recorded on the route. The node-cost figures stay MEASURED in the author's container only.