feat!: la famille ORM est publiee enveloppee, et le ng publie cesse de rendre des promesses

packages/polyfill/test/vocabulary.test.ts

@@ -40,8 +40,20 @@ const TARGET_WORDS = new Set([
   // acts the target performs
   "create", "subscribe", "unsubscribe", "query", "update", "post", "share", "open",
   "fetch", "init", "watch", "sparql", "ng", "orm", "type", "types",
+  // `insert` is the ORM's own verb for adding an object without a subscription
+  // (`sdk/js/orm/src/connector/insertObject.ts`), and SPARQL's for the query it builds.
+  "insert",
   // RDF / SPARQL terms the engine's own query paths use
   "subject", "base", "schema", "connected", "identity", "identities",
+  // `rdf` names the ORM half that speaks triples, as against the JSON-CRDT one - the two
+  // subscription classes the SDK exports are `RdfOrmSubscription` and
+  // `DiscreteOrmSubscription`, and the config the first one takes is `RdfOrmConfig`.
+  "rdf",
+  // `object` is the ORM's OWN noun for one shape-typed record: `getObjects`,
+  // `insertObject`, `removeObject` and `signalObject` in `sdk/js/orm/src/`, and
+  // `SparqlBuilder::remove_object` in the engine. It is also RDF's third triple position,
+  // which the engine's query paths use for the same word.
+  "object", "objects",
   // `publisher` is upstream's word for a pub/sub role on a topic (`as_publisher`,
   // `publisher_advert`, 126 occurrences in the engine). Our own "publish a document" is
   // banned as ambiguous, but that ban never reaches upstream's term — see the traps