Record the TLV keying decision as the maintainer's

2026-09-27 23:48:05 +02:00
1 changed files with 2 additions and 2 deletions
@@ -491,8 +491,8 @@ rule and an index of the titles below.
  length-prefixed Octet String, whose length octet is what ends it.

 - **A TLV input is keyed by its tag name, or by its decimal id where the table names none, and a
-  `tagId` beside the key is accepted only where it agrees.** Settled in the architecture and
-  product-owner reviews of [#30](https://gitea.larvit.se/larvit/smpp-js/pulls/30), 2026-09-27. The
+  `tagId` beside the key is accepted only where it agrees.** Maintainer's call, 2026-09-27, on the
+  architecture and product-owner reviews of [#30](https://gitea.larvit.se/larvit/smpp-js/pulls/30). The
  key is the one spelling, because a name and a `tagId` that disagreed sent the `tagId`'s tag under
  a record keyed as another. A parsed TLV carries its `tagId`, and goal 8's passthrough means a
  parsed PDU's `tlvs` relay as they are, so an agreeing copy is read past rather than refused.