Unexpected Fields in Journal Actions

Here I describe an observation which concerns me but I don't yet know how to even understand it much less resolve it as an issue. This comes from Maha who had considerable trouble editing over a slow connection during Happening 1, especially before the reorganization of the TextEditor to reduce the rate it posts Actions. The problem is exposed by her experimenting with the Grep Plugin. These searches should not have returned any pages. But they did!

I examined the first page identified. Caring and Learning.

Yes, Grep did find an 'add' with the specified site field. My question is, how did this get here? Was there a sequence of activities that could compose this Action in the client? What is it? Or, worse, could the server have constructed this Action out of slow or out of order Action puts?

{
  "type": "add",
  "id": "696e8741eb388066",
  "item": {
    "type": "paragraph",
    "id": "696e8741eb388066",
    "text": "4. You can only threaten people with things they care about. "
  },
  "after": "3f67311374a3e987",
  "site": "maha.uk.fedwikihappening.net",
  "date": 1419487782704
},

A brief inspection shows an even more mystifying 'create' in newpage on chrome. How does one fork a create?

{
  "type": "create",
  "item": {
    "title": "newpage on chrome",
    "story": []
  },
  "site": "maha.uk.fedwikihappening.net",
  "date": 1418278528925,
  "fork": "maha.uk.fedwikihappening.net"
}

fedwiki / wiki-server

Unexpected Fields in Journal Actions #88