DB: Add Collab tables for recording Recip's and Topic's Accept activities

th/models

@@ -588,11 +588,12 @@ Collab
 
 -------------------------------- Collab topic --------------------------------
 
-CollabRoleLocal
-    collab CollabId
-    role   RoleId
-
-    UniqueCollabRoleLocal collab
+-- Removed for now, until I figure out whether/how to federate custom roles
+--CollabRoleLocal
+--    collab CollabId
+--    role   RoleId
+--
+--    UniqueCollabRoleLocal collab
 
 CollabTopicLocalRepo
     collab CollabId
@@ -612,6 +613,16 @@ CollabTopicLocalLoom
 
     UniqueCollabTopicLocalLoom collab
 
+CollabTopicAccept
+    collab CollabId
+    accept OutboxItemId
+
+    UniqueCollabTopicAcceptCollab collab
+    UniqueCollabTopicAcceptAccept accept
+
+-- Do we need this for S2S? Or is this just for the Client, to decide which
+-- Grant URI to use as the 'capability'? If latter, look into removing this
+-- table...
 CollabTopicRemote
     collab CollabId
     topic  RemoteObjectId
@@ -644,12 +655,26 @@ CollabRecipLocal
 
     UniqueCollabRecipLocal collab
 
+CollabRecipLocalAccept
+    collab CollabRecipLocalId
+    accept OutboxItemId
+
+    UniqueCollabRecipLocalAcceptCollab collab
+    UniqueCollabRecipLocalAcceptAccept accept
+
 CollabRecipRemote
     collab CollabId
     actor  RemoteActorId
 
     UniqueCollabRecipRemote collab
 
+CollabRecipRemoteAccept
+    collab CollabRecipRemoteId
+    accept RemoteActivityId
+
+    UniqueCollabRecipRemoteAcceptCollab collab
+    UniqueCollabRecipRemoteAcceptAccept accept
+
 -------------------------------- Collab reason -------------------------------
 
 CollabFulfillsLocalTopicCreation