@ai-matrx/records 0.47.0 → 0.48.0

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog — @ai-matrx/records
 
+## 0.48.0
+
+**A portal principal carries the link the office copies for them.** (lane TAILS-5.)
+
+* **`PortalPrincipal.accept_path`** — `/invitations/portal/accept/<token>`, the same path
+  `custom.portal_invite` hands back when somebody is asked, read off the same `iam.invitations`
+  row and never re-templated. `custom.portal_card` carries it per person as of the migration
+  `tails5b_the_portal_card_carries_the_link.sql`.
+* **`null` is an answer, not an absence.** It is null when they have already followed the link,
+  when the office took it back (a revoke withdraws the invitation in the same statement), when
+  it expired, or when they arrived through the server's own magic-link route, which binds
+  without an invitation at all. A screen that meets `null` says so in words — it never draws a
+  dead control.
+* **Why it exists**: PORTAL-BIND left this named — *"the office's own copy-link is one line
+  short"*. The door answered the office once, with one sentence and one link, and the moment
+  that sentence scrolled away the link was gone: the panel redraws from `portal_card`, which
+  knew somebody was "invited and waiting" and had no way to say what they were waiting on. So
+  texting a customer their link — which INVITE-DELIVERY measured as the ORDINARY case, not the
+  fallback — meant inviting them a second time to see it again.
+
+**Consumer action:** none. `accept_path` is a new field on an existing answer; nothing that
+reads `PortalPrincipal` today has to change. A surface that offers a copy-link must handle the
+`null` case with a sentence.
+
 ## 0.47.0
 
 **A refusal this package does not recognise no longer becomes a sentence about this package.**