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/concepts/refine-binding/_overview.md

@@ -0,0 +1,27 @@
+---
+type: overview
+summary: How a Refine application's resources are bound to NextGraph documents through the eventual SDK — and what that binding may rely on
+triggers:
+  keywords: [refine, provider, dataProvider, authProvider, liveProvider, resource, getList, getOne, shapeTypes, shape, scope, store, polyfill, eventually]
+  paths:
+    - "src/**"
+    - "package.json"
+    - "examples/**"
+vocabulary:
+  - term: resource
+    gloss: Refine's name for a data type an application declares and lists — bound here to one SHEX shape
+  - term: binding
+    gloss: the translation this package performs between a Refine resource and NextGraph documents
+    not: [adapter, bridge, glue]
+---
+
+# refine-binding — Refine's resources over NextGraph's documents
+
+This package binds a [Refine](https://refine.dev/core/) application to NextGraph through `@ng-eventually/polyfill`, which stands in for the NextGraph SDK that has not shipped yet. It is a sibling of `@ng-org/refine-providers`, which binds the same application to the SDK **as it is today**; both have a legitimate existence, and an application may move from one to the other.
+
+The distinguishing rule: **nothing here compensates for the current state of NextGraph.** Capability isolation, identity, inboxes, sharing, the state of any deployed broker — all of that is the polyfill's to carry. What belongs here is only the translation between Refine's model and NextGraph's: what a resource is, what an id is, where a document is placed, and what a listing may legitimately contain.
+
+## Read first
+
+- `polyfill-surface/contract_polyfill-surface` — the engagement this package consumes (pulled, version-pinned).
+- `polyfill-surface/usage_refine-providers-eventually` — what this package actually relies on, and what it still needs.