[QuentinBisson]

The weekly fork-ledger collect reported 31 refs on 23 ledger files that merged or closed upstream while the files still say open or to-file. Each ref was read against its file:

• workerpools-ateom-exports-nothing-when-ate-controller: ateworker no longer exports to localhost:4317 without a relay or endpoint, and takes its own exporter settings agent-substrate/substrate#2189, ours, merged 2026-10-19 (a62e8989), outcome open to merged; it drops at the re-pin onto a commit containing it.
• actors-run-as-their-images-user-workdir: atelet: make durable-dir volumes writable by non-root containers agent-substrate/substrate#1906 merged (97de17b1) covers the durable-dir commit only; the exit now names what remains (as#1918, open).
• resources-deepequal-unchanged-value-check-generated-declarat: Propagate ctx into memorypullcache image pulls agent-substrate/substrate#231 was a wrong ref (a memorypullcache fix) and is removed; no upstream item proposes the change.
• The other 20 files: the moved refs are related work or dependencies, not the changes' exits, so outcomes stay; podmonitors-six-workloads-that-serve-metrics records that as#1781 was re-filed as feat(helm): add PodMonitors for the workloads that serve metrics kagent-dev/substrate#46.

Every touched file is re-verified 2026-10-20 with one History sentence. No carried commit, status or other file changes; fork-ledger validate --complete passes.

• Tests pass
• Appropriate changes to documentation are included in the PR