fix(tasks): a cycle chip counts its days left whether ticked or not

It printed the unticked days left, so ticking a cycle off dropped its
figure by one, and on the last day read 0d. Tasks now carry daysLeft, the
period's days from today, and the chip prints that. Found in the
whole-branch review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

test/task.test.ts

@@ -1,6 +1,7 @@
 import { describe, expect, test } from "bun:test";
 import { RESERVED_ID_SEGMENTS } from "../src/shared/custom.ts";
 import { nextResetMs } from "../src/shared/daily.ts";
+import { goalCount } from "../src/shared/goal.ts";
 import { mintTaskId, TaskSchema, taskCaption, taskStatus, type Task } from "../src/shared/task.ts";
 
 /**
@@ -171,3 +172,14 @@ describe("a task on another server's clock", () => {
     expect(after.periodStart).toBe("2026-10-08");
   });
 });
+
+describe("a cycle chip's days left", () => {
+  test("is the days left in the cycle, ticked or not", () => {
+    const t = task({ period: { unit: "cycle", days: 14, from: "2026-10-16" }, measure: { kind: "days", required: 1 } });
+    const at = (logged: string[], day: string) =>
+      goalCount(taskStatus({ task: t, region: "europe", now: noon(day), logged }));
+    expect(at([], "2026-10-20")).toBe("0/1 · 10d");
+    expect(at(["2026-10-20"], "2026-10-20")).toBe("1/1 · 10d");
+    expect(at(["2026-10-29"], "2026-10-29")).toBe("1/1 · 1d");
+  });
+});