Port from Go

A construct mapping and a boundary, nothing else

This skill maps Go semantics and owns the Go boundary; process is /port-to-rust. Go syntax maps almost mechanically and the runtime model does not, so the easy-looking translation is where the port goes wrong.

The end state, and why Go usually lands on A

/port-to-rust names three end states; Go ports land on A — no bindings — far more often than Python or JavaScript ports do, because the cost of the alternative is cgo and a Go system almost always already has a boundary to strangle at. A default, not a rule: B is real when the deliverable is a Go-importable package; C when a leaf function moves before its callers.

The seam is usually a process, not a function call