chore(mood): account for MoodContext in the four whole-schema guards

- the wipe plan names it before its parent, so the confirmation screen's count
  is the number of rows that existed rather than zero
- the backup plan classifies it as carried and two-ended, and the round-trip
  registry seeds one, which is what makes that claim provable
- the sharing surface admits the linked-day read with the reason it may answer
- CHANGELOG for the release

src/app/api/mood-entries/bulk/route.ts

@@ -447,12 +447,7 @@ async function postBulk(request: NextRequest): Promise<Response> {
         // client was already being told.
         // v1.38 — the day context, inside the same transaction as the row, so
         // an entry reported as skipped really did write nothing.
-        await persistMoodContext(
-          tx,
-          upserted.id,
-          user.id,
-          parsedContext.data,
-        );
+        await persistMoodContext(tx, upserted.id, user.id, parsedContext.data);
 
         if (
           (entry.tagKeys && entry.tagKeys.length > 0) ||