MGS1016: workspace-local Go replace directives drifted

A Go module requires a module declared by another project in this workspace, but its go.mod does not replace that dependency at the relative project path.

Magus derives only replacements whose left-hand module path belongs to this workspace. Replacements for upstream forks, vendored patches, and other external modules are left untouched.

Resolution

Run the owning project's generate target with the write charm:

magus run generate:rw <project>

The target runs go mod edit; magus never writes go.mod directly.

rw rather than relock, even though the file written is go.mod. The replacements are derived from the workspace layout on disk, and go mod edit "reads only go.mod; it does not look up information about the modules involved", so the same tree always yields the same bytes. relock is for writes whose result depends on what a registry serves, such as go mod tidy.