pub fn generated_harness_migration(name: &str) -> Option<&'static str>Expand description
The typed harness path that replaced a removed global, from the generated
projection of harn_vm::stdlib::harness_migration_for_builtin.
harn-parser compiles below harn-vm, so it cannot query the registry;
make gen-harness-migrations emits the table and
make check-harness-migrations keeps it from drifting.
This is the fallback, not the first answer. The hand-written tables
above it encode migration decisions the registry cannot express, because the
registry is keyed by name and some legacy globals collide with unrelated
typed methods — the ambient read_file migrated to harness.fs.read_text,
but a different harness.tools.read_file also exists, and that is what a
name lookup finds. removed_global_replacement composes the sources in
the right order; HARNESS_MIGRATION_DISAGREEMENTS is the audited list.