v0.2.8

slingshot-entity 0.2.6, slingshot-community 0.2.7.

Every delete event published an empty payload. A route declaring event: { payload: [...] } on delete resolves those fields from the op result, and neither delete handler supplied the record. Both paths now read the record before deleting and publish it.

updateScore had no caller. thread.score and thread.reactionSummary stayed 0 and {} forever, so sorting by score was inert. Reaction add/remove now invoke it.

Consumers on the emoji vocabulary: emojiWeights defaults to {}, so emoji are counted in reactionSummary but score 0 until weighted — e.g. scoring: { emojiWeights: { '👍': 1 } }.