Visibility leaves dangling types

Not sure if this is a bug or not... it looks like Visibility and Warden put different priority on fields belonging to objects and interfaces. Consider:

interface Sprocket {
  size: Int # Interface implements field as public
}

type Widget implements Sprocket {
  size: Int # Object implements field as private
}

It looks like Warden would resolve Widget.size as public, because the interface would have the final say on its fields. With Visibility it seems the object field has final say and goes private.

In some ways the Visibility implementation makes sense because the more specific implementation wins, EXCEPT – we're allowing the object to renege on its interface. This turns into a footgun that allows developers to compose invalid schemas; best case scenario the more restrictive override should probably error.

I'm seeing echoes of this in other places with dangling objects and interfaces left in the schema without fields or implementations. On one hand this is a feature of faster visibility, on the other hand it's an open door for sloppy mistakes. I'm curious if there's a middle ground here that capitalizes on Visibility advantages while also enforcing strong schema guarantees, even if only in certain circumstances?

No files, tests, or entry points are named. Start by comparing how Visibility and Warden resolve interface and object fields, then examine how dangling objects, interfaces, fields, and implementations are retained. Done requires a decided middle ground that preserves Visibility's advantages while enforcing the stated schema guarantees.