v0.2.6 calendar-anniversary billing

startos/versions/index.ts

@@ -6,8 +6,9 @@ import { v_0_2_2 } from './v0.2.2'
 import { v_0_2_3 } from './v0.2.3'
 import { v_0_2_4 } from './v0.2.4'
 import { v_0_2_5 } from './v0.2.5'
+import { v_0_2_6 } from './v0.2.6'
 
 export const versionGraph = VersionGraph.of({
-  current: v_0_2_5,
-  other: [v_0_2_4, v_0_2_3, v_0_2_2, v_0_2_1, v_0_2_0, v_0_1_0],
+  current: v_0_2_6,
+  other: [v_0_2_5, v_0_2_4, v_0_2_3, v_0_2_2, v_0_2_1, v_0_2_0, v_0_1_0],
 })

startos/versions/v0.2.6.ts

@@ -0,0 +1,19 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+import { configFile } from '../file-models/config.json'
+
+export const v_0_2_6 = VersionInfo.of({
+  version: '0.2.6:0',
+  releaseNotes: {
+    en_US:
+      'Calendar-anniversary billing replaces calendar-month resets. A user who first activates on the 17th now renews on the 17th of every subsequent month (clamps to last day for shorter months — Jan 31 → Feb 28/29 → Mar 31, standard Stripe-style edge-case handling). Pre-existing credit rows migrate transparently on startup. The admin dashboard JSON now surfaces last_renewal_at + anniversary_day so you can audit when each install renews.',
+  },
+  migrations: {
+    // No config-side migration needed — the ledger migrates itself
+    // when initCredits() runs on first boot of this version. Rows
+    // with the legacy { month: "YYYY-MM" } shape get a
+    // last_renewal_at anchored at the first of that month so they
+    // don't unexpectedly re-issue credits.
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})