Implement mattertimesync: one-shot Matter time synchronization CLIHEADmain

A standalone CLI Matter controller that joins Matter devices' existing
setups as a secondary administrator (multi-admin) and sets their clocks
via the standard Time Synchronization cluster. Built on matter.js 0.17.6
using the CommissioningController API. One-shot runs from a systemd
timer, no daemon: being a secondary controller is fabric membership, not
a running process, so each invocation loads the persisted keys,
discovers the device via operational DNS-SD, opens a fresh CASE session,
does its work, and exits.

- TypeScript scaffold: strict tsc, oxlint, prettier, vitest (66 tests:
  Matter epoch conversion, config validation, IANA timezone offsets and
  exact DST transition search, atomic state writes, pairing-code
  parsing, clock-delta reporting, capability planning against the
  captured device fixture)
- Validated JSON configuration with bigint-safe values; unknown fields
  rejected loudly
- Persistent controller fabric with the same identity across restarts.
  The fabric doubles as the device registry: every node commissioned
  onto it is kept in sync, and membership changes only through
  commission and decommission, so no separate device list can drift
- On-network multi-admin commissioning from a manual or QR pairing code;
  any number of devices, one per-device pairing code each. A device
  already on the fabric rejects re-commissioning via fabric conflict
- sync, validated against real hardware (IKEA ALPSTUGA air quality
  monitor over Thread, commissioned alongside Apple Home): refuses to
  run unless the host is NTP-synchronized, then per node reads utcTime,
  reports the correction with direction ("device clock was 1m 23s
  behind", handling unset clocks in exact bigint microseconds), writes
  SetUTCTime, SetTimeZone (standard offset plus IANA name), and
  SetDSTOffset (transition list bounded by the device's capacity), and
  verifies by reading the clock back. Capability-driven throughout:
  UTC-only devices degrade gracefully, cluster-less devices are skipped
  with a warning. Devices whose firmware encodes Unix-epoch time on the
  wire are detected by the exact 946684800s shift and reported
  corrected. Note matter.js's TlvEpochUs API convention: values are
  Unix-epoch microseconds at the API boundary; the library converts to
  Matter epoch on the wire
- Commands: nodes, inspect (human/JSON; also reads the fabric table
  fabric-unfiltered, matching our own entry by fabric ID plus root
  public key and flagging likely-stale orphans; strictly read-only,
  since this tool never uses its admin rights against other fabrics'
  entries), status, and decommission (each device drops our fabric
  while staying paired to its primary ecosystem; targets all devices
  unless --node narrows it)
- Logs (service and matter.js library, plain format) go to stderr;
  stdout carries only command output, so --json (available on nodes,
  inspect, sync, status, fabrics) is always clean parseable JSON with
  64-bit values as decimal strings. Node's node:sqlite
  ExperimentalWarning is filtered before matter.js loads
- systemd oneshot service (dedicated non-root user, hardening) plus
  hourly timer with randomized delay
- Deployment as a single esbuild bundle (mattertimesync.mjs, ~4.5 MB):
  all runtime deps are pure JavaScript, so the target needs only
  Node 20+, with no npm, registry access, or build toolchain. The Bun
  sqlite driver stays external behind its runtime guard and node:sqlite
  is aliased to a lazy shim so the bundle runs under plain Node. npm
  pack remains an alternative install path

1 files changed, 133 insertions, 0 deletions

diff --git a/test/sync.test.ts b/test/sync.test.ts
new file mode 100644
index 0000000..d48f286
--- /dev/null
+++ b/test/sync.test.ts
@@ -0,0 +1,133 @@
+import { describe, expect, it } from "vitest";
+import {
+  MATTER_EPOCH_UNIX_SECONDS,
+  compareDeviceClock,
+  currentMatterUtcMicroseconds,
+  formatDurationMicros,
+  formatMatterMicros,
+  matterMicrosToUnixMillis,
+  unixMillisToMatterMicros,
+} from "../src/sync.js";
+
+describe("Matter epoch conversion", () => {
+  it("maps 2000-01-01T00:00:00Z to 0 microseconds", () => {
+    const unixMs = BigInt(Date.parse("2000-01-01T00:00:00Z"));
+    expect(unixMillisToMatterMicros(unixMs)).toBe(0n);
+  });
+
+  it("maps 2000-01-01T00:00:01Z to 1,000,000 microseconds", () => {
+    const unixMs = BigInt(Date.parse("2000-01-01T00:00:01Z"));
+    expect(unixMillisToMatterMicros(unixMs)).toBe(1_000_000n);
+  });
+
+  it("keeps the Unix epoch conversion exact", () => {
+    expect(unixMillisToMatterMicros(0n)).toBe(-MATTER_EPOCH_UNIX_SECONDS * 1_000_000n);
+    expect(unixMillisToMatterMicros(0n)).toBe(-946_684_800_000_000n);
+  });
+
+  it("keeps current dates exact through bigint round-trips", () => {
+    const unixMs = BigInt(Date.parse("2026-07-26T20:00:00.123Z"));
+    const micros = unixMillisToMatterMicros(unixMs);
+    expect(micros).toBe((unixMs - 946_684_800_000n) * 1_000n);
+    expect(matterMicrosToUnixMillis(micros)).toBe(unixMs);
+  });
+
+  it("stays exact beyond JavaScript number precision", () => {
+    // Microsecond timestamps pass Number.MAX_SAFE_INTEGER around year 2285;
+    // conversion must not degrade there, proving no number arithmetic occurs.
+    const unixMs = BigInt(Date.parse("2300-01-01T00:00:00.001Z"));
+    const micros = unixMillisToMatterMicros(unixMs);
+    expect(micros > BigInt(Number.MAX_SAFE_INTEGER)).toBe(true);
+    expect(matterMicrosToUnixMillis(micros)).toBe(unixMs);
+  });
+
+  it("computes the current time via the injected clock", () => {
+    const nowMs = Date.parse("2026-07-26T20:00:00Z");
+    const micros = currentMatterUtcMicroseconds(() => nowMs);
+    expect(micros).toBe(unixMillisToMatterMicros(BigInt(nowMs)));
+  });
+
+  it("formats Matter microseconds as an ISO instant", () => {
+    expect(formatMatterMicros(0n)).toBe("2000-01-01T00:00:00.000Z");
+    expect(formatMatterMicros(1_000_000n)).toBe("2000-01-01T00:00:01.000Z");
+  });
+});
+
+describe("formatDurationMicros", () => {
+  it("scales units with magnitude", () => {
+    expect(formatDurationMicros(0n)).toBe("0us");
+    expect(formatDurationMicros(999n)).toBe("999us");
+    expect(formatDurationMicros(412_000n)).toBe("412ms");
+    expect(formatDurationMicros(3_200_000n)).toBe("3.2s");
+    expect(formatDurationMicros(59_000_000n)).toBe("59s");
+    expect(formatDurationMicros(125_000_000n)).toBe("2m 5s");
+    expect(formatDurationMicros(3_840_000_000n)).toBe("1h 4m");
+    // 90,061 seconds = 1d 1h 1m 1s; seconds are dropped once days appear.
+    expect(formatDurationMicros(90_061_000_000n)).toBe("1d 1h 1m");
+  });
+
+  it("rejects negative durations", () => {
+    expect(() => formatDurationMicros(-1n)).toThrow();
+  });
+});
+
+describe("compareDeviceClock", () => {
+  // compareDeviceClock operates on Unix-epoch microseconds (matter.js convention).
+  const host = BigInt(Date.parse("2026-07-26T20:00:00.000Z")) * 1_000n;
+
+  it("reports an unset device clock", () => {
+    const comparison = compareDeviceClock(null, host);
+    expect(comparison.deviceTime).toBeNull();
+    expect(comparison.deltaMicroseconds).toBeNull();
+    expect(comparison.hostTime).toBe("2026-07-26T20:00:00.000Z");
+    expect(comparison.description).toBe("device clock was unset");
+  });
+
+  it("reports a device clock behind the host", () => {
+    const comparison = compareDeviceClock(host - 83_000_000n, host);
+    expect(comparison.deviceTime).toBe("2026-07-26T19:58:37.000Z");
+    expect(comparison.deltaMicroseconds).toBe(-83_000_000n);
+    expect(comparison.description).toBe("device clock was 1m 23s behind");
+  });
+
+  it("reports a device clock ahead of the host", () => {
+    const comparison = compareDeviceClock(host + 5_500_000n, host);
+    expect(comparison.deltaMicroseconds).toBe(5_500_000n);
+    expect(comparison.description).toBe("device clock was 5.5s ahead");
+  });
+
+  it("treats sub-second deltas as in sync but still reports them", () => {
+    const comparison = compareDeviceClock(host - 412_000n, host);
+    expect(comparison.description).toBe("device clock was within 1s of host time (412ms behind)");
+  });
+
+  it("detects a device that encodes Unix-epoch time on the wire (wrong epoch bug)", () => {
+    // Such firmware decodes to exactly 946,684,800s ahead at the matter.js
+    // API boundary. The raw delta stays exact; the effective delta folds
+    // the shift out.
+    const wrong = host + 946_684_800n * 1_000_000n + 1_400_000n;
+    const comparison = compareDeviceClock(wrong, host);
+    expect(comparison.epochShifted).toBe(true);
+    expect(comparison.deltaMicroseconds).toBe(946_684_800_000_000n + 1_400_000n);
+    expect(comparison.effectiveDeltaMicroseconds).toBe(1_400_000n);
+    expect(comparison.deviceTime).toBe("2026-07-26T20:00:01.400Z");
+    expect(comparison.description).toBe(
+      "device encodes Unix-epoch time on the wire (off-spec); corrected, its clock was 1.4s ahead",
+    );
+  });
+
+  it("does not fold out large errors that are not the epoch shift", () => {
+    // 30 days past the shift window: a genuinely broken clock, not epoch bug.
+    const wrong = host + 946_684_800n * 1_000_000n + 30n * 86_400n * 1_000_000n;
+    const comparison = compareDeviceClock(wrong, host);
+    expect(comparison.epochShifted).toBe(false);
+    expect(comparison.effectiveDeltaMicroseconds).toBe(comparison.deltaMicroseconds);
+    expect(comparison.description).toContain("ahead");
+  });
+
+  it("keeps spec-compliant comparisons unshifted", () => {
+    const comparison = compareDeviceClock(host - 83_000_000n, host);
+    expect(comparison.epochShifted).toBe(false);
+    expect(comparison.effectiveDeltaMicroseconds).toBe(-83_000_000n);
+  });
+});