Consume polyfill-surface, and declare what this package relies on

Pulls @ng-eventually/polyfill's engagement, version-pinned, and declares
back what this package actually consumes — the contract pair that lets the
two repositories coordinate without either reading the other's source.

The declaration is the channel: its Frictions and Needs are standing
requests the provider drains. The one that decides this package's shape:
modifying and removing a record have no published path that is both
shape-typed and awaitable, so Refine's update and deleteOne have nowhere
to land. Reading, creating and both live channels do have one.

The engagement describes 1.0.0-dev.14 and no tag carries it, so the pin is
the branch it is authored on and `against:` is the commit it resolved to.

.project/contracts.yaml

@@ -0,0 +1,28 @@
+# Inter-repo contracts. `publish:` is this project's engagement toward its counterparts —
+# listing a leaf here IS the act of publishing it.
+#
+# This project is a CONSUMER of one interface: `polyfill-surface`, the API
+# `@ng-eventually/polyfill` offers an application. The pair lives in an interface folder
+# inside the concept whose territory it governs — the pulled engagement beside this
+# project's own declaration of what it consumes.
+#
+# `pullFrom:` is a CANONICAL remote identity, because this file travels with the branch.
+# Per-developer local access lives in `.project/contracts.local.yaml`, which is gitignored
+# and must never be committed.
+
+publish:
+  # paths are relative to `.project/`
+  refine-providers-eventually: concepts/refine-binding/polyfill-surface/usage_refine-providers-eventually.md
+
+consume:
+  - contract: polyfill-surface
+    type: git
+    pullFrom: git@gitea.reconnexion.apps.gueraud.net:Reconnexion/ng-eventually.git/.project/concepts/app-contract/polyfill-surface/contract_polyfill-surface.md
+    # The Change policy names the pin regime — a tag carrying the package name
+    # (`polyfill/vX.Y.Z`), since that repo publishes two engagements — and names
+    # `1.0.0-dev.14` as what to pin. That tag does not exist: only `polyfill/v1.0.0-dev.2`
+    # and `-dev.3` are posted, so the announced version is not referenceable. Pinned on the
+    # branch the engagement is authored on until the tag is cut; declared as a friction in
+    # `usage_refine-providers-eventually.md`, not worked around.
+    ref: caps-p1a-and-virtual-user-boundary
+    into: concepts/refine-binding/polyfill-surface/