docs(masque): Define connector contracts

docs/designs/README.md

@@ -10,6 +10,7 @@ These documents explain decisions and planned work. Their status describes imple
 | [Looking Glass backend service](looking-glass-service.md) | Proposed implementation contract; authentication scaffolding does not enable service execution | [Current fabric-api](../fabric-api/README.md)                                            |
 | [Shared DNS64](dns64/README.md)                           | Proposed; end-to-end validation outstanding                                                    | [NAT configuration](../nat/configuration.md) for implemented translation                 |
 | [Latency-aware routing](latency-aware-routing.md)         | Exploratory proposal                                                                           | [Router configuration](../router/configuration.md) for available settings                |
-| [MASQUE gateway](masque-gateway.md)                       | Exploratory proposal; external references may describe historical designs                      | [Gateway configuration](../gateway/configuration.md) for the implemented XDP/DSR gateway |
+| [MASQUE gateway](masque-gateway.md)                       | Superseded for #970 by the connector contract                                                  | [Gateway configuration](../gateway/configuration.md) for the implemented XDP/DSR gateway |
+| [MASQUE connector](masque/contract.md)                    | Proposed contract; [acceptance checks](masque/acceptance.md) not yet run                       | [Provider contract](../edge/provider-contract.md) for the implemented foundation         |
 
 When implementing a proposal, move the available interface or operating procedure into its component guide and update this status. Retain decisions and alternatives here. Keep measurements tied to their revision and environment in the [evidence archive](../archive/README.md), rather than presenting old results as current readiness.

docs/designs/galactic-edge.md

@@ -86,7 +86,7 @@ Consider a service that connects an external site to a tenant's VPC. It establis
 
 The provider requests an attachment for the tenant and reachability for the prefix. Galactic Edge verifies the grant, prepares the isolated connection, and enables forwarding and routing only when their prerequisites hold. Return traffic follows the published prefix to the attachment; the provider delivers it to the external site.
 
-A second service using a different protocol follows the same lifecycle. This is the reuse requirement in [#992](https://github.com/datum-cloud/galactic/issues/992), illustrated through an abstract provider. The [MASQUE proposal (#970)](https://github.com/datum-cloud/galactic/issues/970) is one potential consumer; its transport requirements are outside this design.
+A second service using a different protocol follows the same lifecycle. This is the reuse requirement in [#992](https://github.com/datum-cloud/galactic/issues/992), illustrated through an abstract provider. The [MASQUE connector contract](masque/contract.md) defines the #970 consumer: client authority, retained /96 allocations and transport sessions. Its [acceptance matrix](masque/acceptance.md) separates foundation evidence from MASQUE integration checks; those transport requirements remain outside this foundation design.
 
 ### Risks and Mitigations
 

docs/designs/masque-gateway.md

@@ -1,5 +1,7 @@
 # MASQUE Gateway Architecture
 
+> For the #970 implementation, this proposal is superseded by the [MASQUE connector contract](masque/contract.md) and [acceptance matrix](masque/acceptance.md). The resource model, client work and transport scope below are historical context.
+
 Status: proposed. This exploratory design is separate from the implemented XDP/DSR galactic-gateway and is not deployment guidance. References to external client and connector architectures are historical context, not verified current integrations.
 
 ## Executive Summary