@squirreljetpack/im-dynamic 0.2.10 → 0.3.0

package/CHANGELOG.md

@@ -1,3 +1,84 @@
+## [0.3.0] - 2026-11-03
+
+### 🚀 Features
+
+- Sync creates are driven by `sync_schema.json`: a push that creates an
+  entity carries every field of its kind, so no peer ever builds a
+  half-filled row.
+- The outbox coalesces per cell (`UNIQUE(entity_id, field)`): repeated
+  offline edits to the same field update the queued row in place instead
+  of queueing a chain of writes.
+- The server pre-validates each create (existence cell, required fields
+  and links, timestamp) and reports the failures as per-event verdicts
+  with a typed reason. `target_deleted` is new; a reason this build does
+  not know deserializes as `unknown` instead of failing the response.
+- Deleting a mood keeps the tracker entries logged against it: their
+  `mood` link is cleared and the rows stay, matching the sync cascade.
+  Deleting a task still deletes its completions.
+- `im :sync` offers to re-create content another device deleted from a
+  snapshot taken before the row was removed, and asks once per entity
+  after every push of the run.
+
+### 🐛 Bug Fixes
+
+- `sync_once` lands the outbox, the domain rows, the cursor and the
+  verdict reconciliation in one transaction, so an interrupted push
+  cannot leave a half-applied batch.
+- The existence cell folds monotonically: a stale create can no longer
+  resurrect an entity another device deleted, and a create the server
+  rejected leaves no cells behind in the log.
+- `clock_ahead` restamps the device forward against the server clock and
+  resets its last emitted stamp, so later edits from that device keep
+  winning last-writer-wins.
+- Editing a mood's body or a tracker's mood link queues only the cells
+  that changed.
+- Pull is bounded and reports `has_more`, so a long log pages instead of
+  arriving in one response.
+
+### 💥 Breaking changes
+
+- `tracker.time` is required: a create without it is rejected as
+  `shape`.
+- `_sync_events` carries its coalescing uniqueness in the table
+  definition and no longer stores `image`. Databases from earlier builds
+  are not migrated: delete the database file and sign in to rebuild from
+  the log.
+
+## [0.2.11] - 2026-11-02
+
+### 🚀 Features
+
+- `im :c mm` opens the matchmaker render config (`mm.toml`) in
+  `$VISUAL`/`$EDITOR`, alongside the config, `moods` and `colors` targets.
+- Log entries (moods, trackers, todo completions) store the UTC offset and
+  the location string (the system IANA name, or empty when it has none) in
+  effect where they were written. The today view groups log entities by their
+  recorded **civil day** and renders their recorded civil time; ordering stays
+  absolute. Mood/tracker previews show the differing location and wall-clock
+  shift under the timestamp; task previews append the same parts inline to
+  `last:` as `prev:`.
+- Tracker interval anchors are unzoned civil datetimes resolved in the current
+  local zone. Replace-mode slots and cumulative sums assign foreign logs by
+  their recorded wall clock, so an entry stays in the same civil slot when
+  viewed from another zone.
+- Replace-mode null trackers store their absolute seconds from the interval
+  start in the entry payload; color and the strict when-zone use that stored
+  position.
+- Explicit todo completions join the today view on their civil completion day.
+  `B` now merges explicitly completed scheduled tasks on that day instead of on
+  an overlapping availability window.
+
+### 💥 Breaking changes
+
+- Sync vocabulary is version 4: `tz_offset` (required int) and `location`
+  (required text; empty when the system has no name) on mood, tracker and
+  completion. Pre-v4 creates lack the
+  location or offset and are intentionally unbuildable; reset the sync log
+  when replaying one.
+- Databases from earlier builds are not migrated. Delete the database file and
+  sign in to rebuild from the log. Tracker configs must drop the `Z`/numeric
+  offset from interval anchors.
+
 ## [0.2.10] - 2026-10-31
 
 ### 🚀 Features

package/README.md

@@ -76,8 +76,8 @@ Usage:
                                                         (optionally attached to a mood)
 
   im ! [name] [@<time>]                          create a task (interactive without a name)
-  im ! %[<interval>] [[:]name]                   create a recurring task (interactive)
-  im ! @[<time>] [:<name>] [%<duration>]         scheduled a task (interactive if partial)
+  im ! %[interval] [[:]name]                   create a recurring task (interactive)
+  im ! @[time] [:<name>] [%<duration>]         scheduled a task (interactive if partial)
   im +[task] [count]                             edit or update a task by its reference
                                                         (see `im -vh`)
 
@@ -96,11 +96,11 @@ Trackers and grids:
 
 Other:
   im :tool embed|mood|clear|..                   (see `im :tool --help`)
-  im :tool config | :c [moods|colors]            open the config in $VISUAL / $EDITOR
+  im :tool config | :c [moods|colors|mm]         open the config in $VISUAL / $EDITOR
   im -                                           browse trackers
   im :db prune|backfill|doctor                   database utilities
 
-  im :sync [register|login|status|logout]        setup/manage/run sync 
+  im :sync [register|login|status|logout]        setup/authenticate/run sync 
 
 
 Flags:
@@ -149,10 +149,14 @@ Trackers are defined in your configuration (`im :tool config`); each `[tracker.<
 section is logged through `im -<name> <value>` (no value for `null` trackers):
 
 - Kinds: `text`, `integer`, `float`, `duration` (strings like `6m 30s`), `null` (timestamp/count markers — requires an interval).
-- `interval = { anchor = "2026-01-01T00:00:00-04:00", span = "1 day" }` bins
-  entries into calendar slots. By default, a new log in a slot
-  replaces the slot's previous entry; `interval.cumulative = true` keeps every log and
-  the slot's grid dot shows the aggregate.
+- `interval = { anchor = "2026-01-01T00:00:00", span = "1 day" }` bins
+  entries into calendar slots. The anchor is an unzoned civil datetime (no `Z`
+  or numeric offset) resolved in your current local zone. By default, a new log
+  in a slot replaces the slot's previous entry; `interval.cumulative = true`
+  keeps every log and the slot's grid dot shows the aggregate. Logs record the
+  UTC offset and location string (the system IANA name, or empty) they were
+  written in, so they stay on their recorded civil day and interval slot when
+  viewed from another zone.
 
 ## FAQ
 

package/npm-shrinkwrap.json

@@ -18,7 +18,7 @@
       },
       "hasInstallScript": true,
       "name": "@squirreljetpack/im-dynamic",
-      "version": "0.2.10"
+      "version": "0.3.0"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -47,5 +47,5 @@
     }
   },
   "requires": true,
-  "version": "0.2.10"
+  "version": "0.3.0"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/Squirreljetpack/im/releases/download/v0.2.10"
+    "https://github.com/Squirreljetpack/im/releases/download/v0.3.0"
   ],
   "bin": {
     "im-dynamic": "run-im-dynamic.js"
@@ -87,7 +87,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.2.10",
+  "version": "0.3.0",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"