@pithy-sh/leaderboard 0.1.6 → 0.2.0

package/dist/version.generated.d.ts

@@ -3,5 +3,5 @@
 /** This package's npm name — the join key against a release feed. */
 export declare const PACKAGE_NAME = "@pithy-sh/leaderboard";
 /** This package's version, stamped from its own package.json at generation time. */
-export declare const PACKAGE_VERSION = "0.1.6";
+export declare const PACKAGE_VERSION = "0.2.0";
 //# sourceMappingURL=version.generated.d.ts.map

package/dist/version.generated.js

@@ -4,6 +4,6 @@
 /** This package's npm name — the join key against a release feed. */
 const PACKAGE_NAME = "@pithy-sh/leaderboard";
 /** This package's version, stamped from its own package.json at generation time. */
-const PACKAGE_VERSION = "0.1.6";
+const PACKAGE_VERSION = "0.2.0";
 //#endregion
 export { PACKAGE_NAME, PACKAGE_VERSION };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pithy-sh/leaderboard",
-  "version": "0.1.6",
+  "version": "0.2.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -38,11 +38,17 @@
   "dependencies": {
     "@cloudflare/workers-types": "^5.20260729.1",
     "@hono/zod-validator": "^0.9.0",
-    "@pithy-sh/core": "^0.3.0",
     "croner": "^10.0.1"
   },
+  "peerDependencies": {
+    "@pithy-sh/core": "^0.4.0",
+    "hono": "^4.13.2",
+    "kysely": "^0.29.0",
+    "zod": "^4.4.0"
+  },
   "devDependencies": {
     "@cloudflare/vitest-plugin": "^1.0.0",
+    "@pithy-sh/core": "workspace:*",
     "@pithy-sh/tsconfig": "workspace:*",
     "@types/node": "^22.15.0",
     "@vitest/coverage-v8": "^4.1.0",
@@ -54,10 +60,5 @@
     "vitest": "^4.1.0",
     "wrangler": "^4.115.0",
     "zod": "^4.4.0"
-  },
-  "peerDependencies": {
-    "hono": "^4.13.2",
-    "kysely": "^0.29.0",
-    "zod": "^4.4.0"
   }
 }

package/src/rank/wrangler.jsonc

@@ -1,8 +1,17 @@
 {
-  // The leaderboard rank-refresh worker. This is a TEMPLATE, not a wrangler env-stanza file: `pithy add
-  // leaderboard` resolves it per environment — filling the `<...>` placeholders and the cron from the
-  // adopter's `rank: { materialize }` setting — and deploys each with its own config
-  // (`wrangler deploy --config <resolved>`). The adopter authors none of it.
+  // The leaderboard rank-refresh worker. This is a TEMPLATE, not a wrangler env-stanza file: the
+  // `<...>` placeholders and the cron are meant to be filled per environment from the adopter's
+  // `rank: { materialize }` setting, and each resolved config deployed with `wrangler deploy --config
+  // <resolved>`.
+  //
+  // **Nothing in the kit does that yet, and this file is not deployed by any command.**
+  // `cli/src/capabilities/hostRegistry.ts` leaves `@pithy-sh/leaderboard` out of `HOST_WORKERS`
+  // deliberately: the rank worker ships this template and a `RankRefreshWorkflow`, but no
+  // `resolveLeaderboardConfig` and no provisioner, so there is nothing to drive — and
+  // `hostRegistry.test.ts` pins that absence so it cannot become an oversight. Filling and deploying it
+  // is an adopter's own step today. This comment said otherwise for as long as the template has
+  // existed, which is the kind of claim that sends somebody looking for a command that was never
+  // written.
   //
   // It does NOT have to be its own worker. What the refresh actually needs is three things: the
   // `RankRefreshWorkflow` class, a `scheduled()` handler that starts an instance, and a cron trigger.
@@ -14,7 +23,12 @@
   // once capped the refresh at ~64k entries per run. A Workflow step has unlimited wall-clock and burns
   // no CPU while awaiting D1, so a board of any size ranks across bounded, individually-durable steps
   // that checkpoint a keyset cursor. See `worker.entry.ts`.
-  "name": "pithy-leaderboard-rank", // resolved per env → pithy-leaderboard-rank-staging / -production
+  // A placeholder, not the deployed name. When something does resolve this template it will compose
+  // `<project>-<env>-leaderboard` — `workflowHostName` in `core/src/workflow/naming.ts` is
+  // `<project>-<env>-<capability>`, so the project leads and the environment is second, never trailing
+  // and never `production`. Worker script names are account-scoped, which is what makes the project
+  // segment load-bearing: without it a second Pithy project's deploy overwrites this one's worker.
+  "name": "pithy-leaderboard-rank",
   "main": "./worker.entry.ts",
   // The compatibility date every Worker in this repository runs on. Stated once in the repository
   // root's `compatibility.ts` and copied here because JSONC cannot import it —

package/src/version.generated.ts

@@ -13,4 +13,4 @@
 export const PACKAGE_NAME = "@pithy-sh/leaderboard";
 
 /** This package's version, stamped from its own package.json at generation time. */
-export const PACKAGE_VERSION = "0.1.6";
+export const PACKAGE_VERSION = "0.2.0";