@pikku/schedule 0.12.5 → 0.12.7

package/CHANGELOG.md

@@ -1,3 +1,121 @@
+## 0.12.7
+
+### Patch Changes
+
+- 266e3bc: One door per name: `@pikku/core/ecosystem/*` and the package root are gone
+
+  `@pikku/core` published every module twice. `ecosystem/http` re-exported
+  `./http`, `ecosystem/services` re-exported `./services`, and a name was
+  reachable through either — so every addition had to be made in two places, and a
+  consumer's import said nothing about what it actually used. The package root was
+  the same problem at a larger scale: a single barrel of 206 names that no bundler
+  could take apart, and the one specifier that revealed nothing at all.
+
+  Both are deleted. Every name now lives on the subpath that owns it, and every
+  import carries that subpath — `@pikku/core/http`, `@pikku/core/services`,
+  `@pikku/core/errors`, `@pikku/core/types`.
+
+  Deleting the facades meant the raw subpaths had to become a superset of them,
+  which they were not: the facade tree had accumulated 25 names with no raw home
+  and about 26 more filed under a different area than the module they came from.
+  Those names moved to the area that owns them, and three areas were published as
+  new entry points rather than left on a root that is going away — `./types` (the
+  shared type surface, the largest single destination), `./state` and
+  `./classification`.
+
+  `./classification` is one door onto one subject: what a value is and how it must
+  be handled. Its three halves would each have been an entry point — the brands
+  and manifest types, the stored-form helpers (`hashToken`, `unsafeAsSealed` and
+  friends), and `SecretValue` — split by whether a name happens to be a type or a
+  value, which is the same defect as the facades. The duration and versioned-id
+  helpers went to `./utils`, which already published, and `PikkuRequest` went to
+  `./function`: it is the transport-agnostic request base, not an HTTP one — HTTP
+  has `PikkuHTTPAbstractRequest`, and the only thing outside core that extends
+  `PikkuRequest` is Azure's timer request.
+
+  `./types` inherited the root barrel's habit before it inherited its contents, so
+  the names with an owner elsewhere were moved off it. The middleware types and the
+  five middleware factories — `pikkuMiddleware`, `pikkuMiddlewareFactory`,
+  `pikkuChannelMiddleware`, `pikkuChannelMiddlewareFactory` and
+  `pikkuAgentMiddleware`, runtime values on a types entry point — are now
+  `@pikku/core/middleware`; the function meta types are `@pikku/core/function`;
+  `SerializedError` is `@pikku/core/errors`; and the generic TypeScript helpers
+  (`MakeRequired`, `PickRequired`, `PickOptional`, `RequireAtLeastOne`,
+  `JSONPrimitive`, `JSONValue`) are `@pikku/core/utils`. What is left on `./types`
+  is the vocabulary the wirings share, which no single module owns.
+
+  `pikku` was itself a root barrel — `export * from '@pikku/core'` — and
+  now exports only the services it bundles.
+
+  One module survives at the old specifier, and only for the bootstrap:
+  `packages/cli` is generated by the _published_ CLI pinned in its `build.sh`, and
+  that CLI still writes a bare `@pikku/core` into the files it generates for the
+  CLI itself. `bootstrap-compat/root.ts` carries the eight types it names, a test
+  in core fails if that list grows, and it goes when the pin moves to a CLI
+  released from this branch. The adapter names the pinned CLI reaches for —
+  `pikkuState` and `CreateWireServices` — are rewritten to `@pikku/core/state` and
+  `@pikku/core/types` by the same `build.sh` patch pass, so no second shim is
+  needed for them.
+
+  A guard test keeps the root shut: it parses imports and rejects a bare
+  `@pikku/core` rather than grepping for it, because several tests hold a user's
+  file as a template literal, where `import … from '@pikku/core'` is fixture text
+  rather than an import this repo makes.
+
+  An agent scaffold a project generated under an older CLI is refreshed rather
+  than left to fail: `pikku all` already deleted one importing an entry point
+  `@pikku/core` no longer publishes, and the `#pikku` hub joins that list.
+  Without it a project that scaffolds the agent endpoint but
+  declares no agents keeps the old file forever — the generator that would rewrite
+  it only runs when agents exist, and the file being present is what stops it
+  being regenerated as missing.
+
+  `pikku new addon` also wrote a tsconfig `paths` map naming only the deleted hub.
+  An addon's `imports` map points into `dist`, so `paths` is what resolves
+  `#pikku/<leaf>` for the addon's own source build — it now names the two leaf
+  patterns, in both the addon and its test harness.
+
+- 786dae5: Bump every dependency whose latest release is a major across the monorepo, and
+  port the code the majors broke: `cookie` 2's `parseCookie`/`stringifySetCookie`
+  API in `@pikku/core` and the three runtime HTTP adapters, and assistant-ui 0.15's
+  store client in `@pikku/assistant-ui`.
+- 6eef0a0: Bump every dependency to its latest compatible minor/patch across the monorepo.
+- Updated dependencies [7722ceb]
+- Updated dependencies [375c1ff]
+- Updated dependencies [02a70cd]
+- Updated dependencies [aeef159]
+- Updated dependencies [a281de6]
+- Updated dependencies [266e3bc]
+- Updated dependencies [02a70cd]
+- Updated dependencies [786dae5]
+- Updated dependencies [6eef0a0]
+- Updated dependencies [3561d67]
+- Updated dependencies [a91c433]
+- Updated dependencies [02a70cd]
+- Updated dependencies [9537f74]
+- Updated dependencies [2b57ca8]
+- Updated dependencies [266e3bc]
+- Updated dependencies [9fce0f1]
+- Updated dependencies [83683a0]
+- Updated dependencies [456c88b]
+- Updated dependencies [456c88b]
+- Updated dependencies [c127273]
+  - @pikku/core@0.12.85
+
+## 0.12.6
+
+### Patch Changes
+
+- 6794681: Publish the ecosystem surface as per-area sub-barrels under `@pikku/core/ecosystem/*`, and point generated code, the CLI, the inspector and the runtime adapters at them.
+
+  348 names that only generated code, the toolchain or a runtime adapter ever imports now have a second home on `@pikku/core/ecosystem/<area>` — one sub-barrel per area, matching how core already publishes its entrypoints, so no single barrel grows without bound and a consumer only pulls in the area it uses.
+
+  This step is additive: every name is still exported from the entrypoint it was published from before, so nothing downstream breaks. Removing them from the app-facing barrels is a later change, and needs a release carrying `./ecosystem/*` first.
+
+- Updated dependencies [7406bfe]
+- Updated dependencies [6794681]
+  - @pikku/core@0.12.84
+
 ## 0.12.5
 
 ### Patch Changes

package/dist/in-memory-scheduler-service.d.ts

@@ -1,5 +1,6 @@
-import type { CoreUserSession, ScheduledTaskInfo, ScheduledTaskSummary } from '@pikku/core';
-import { SchedulerService } from '@pikku/core';
+import type { CoreUserSession } from '@pikku/core/types';
+import type { ScheduledTaskInfo, ScheduledTaskSummary } from '@pikku/core/services';
+import { SchedulerService } from '@pikku/core/services';
 /**
  * In-memory SchedulerService implementation.
  * Uses CronJob for recurring tasks and setTimeout for delayed RPCs.

package/dist/in-memory-scheduler-service.js

@@ -1,7 +1,9 @@
 import { CronJob } from 'cron';
-import { SchedulerService, parseDurationString } from '@pikku/core';
-import { pikkuState, getSingletonServices } from '@pikku/core/ecosystem';
-import { runScheduledTask, getScheduledTasks } from '@pikku/core/scheduler';
+import { SchedulerService } from '@pikku/core/services';
+import { parseDurationString } from '@pikku/core/utils';
+import { pikkuState, getSingletonServices } from '@pikku/core/state';
+import { runScheduledTask } from '@pikku/core/scheduler';
+import { getScheduledTasks } from '@pikku/core/scheduler';
 import { rpcService } from '@pikku/core/rpc';
 const getLogger = () => {
     return pikkuState(null, 'package', 'singletonServices').logger;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pikku/schedule",
-  "version": "0.12.5",
+  "version": "0.12.7",
   "description": "In-memory scheduler service for Pikku cron wirings",
   "author": "yasser.fadl@gmail.com",
   "license": "MIT",
@@ -19,10 +19,10 @@
     "prepublishOnly": "yarn build"
   },
   "peerDependencies": {
-    "@pikku/core": "^0.12.80"
+    "@pikku/core": "^0.12.85"
   },
   "devDependencies": {
-    "@types/node": "^24.11.0",
+    "@types/node": "^24.13.3",
     "typescript": "^6.0.3"
   },
   "engines": {
@@ -30,7 +30,7 @@
   },
   "dependencies": {
     "cron": "^4.4.0",
-    "cron-schedule": "^5.0.4"
+    "cron-schedule": "^6.0.0"
   },
   "exports": {
     ".": {
@@ -39,4 +39,4 @@
       "default": "./dist/index.js"
     }
   }
-}
+}

package/src/in-memory-scheduler-service.test.ts

@@ -1,6 +1,6 @@
 import { describe, test } from 'node:test'
 import assert from 'node:assert/strict'
-import { pikkuState } from '@pikku/core/ecosystem'
+import { pikkuState } from '@pikku/core/state'
 import { addFunction } from '@pikku/core/function'
 
 import { InMemorySchedulerService } from './in-memory-scheduler-service.js'

package/src/in-memory-scheduler-service.ts

@@ -1,12 +1,14 @@
 import { CronJob } from 'cron'
+import type { CoreUserSession } from '@pikku/core/types'
 import type {
-  CoreUserSession,
   ScheduledTaskInfo,
   ScheduledTaskSummary,
-} from '@pikku/core'
-import { SchedulerService, parseDurationString } from '@pikku/core'
-import { pikkuState, getSingletonServices } from '@pikku/core/ecosystem'
-import { runScheduledTask, getScheduledTasks } from '@pikku/core/scheduler'
+} from '@pikku/core/services'
+import { SchedulerService } from '@pikku/core/services'
+import { parseDurationString } from '@pikku/core/utils'
+import { pikkuState, getSingletonServices } from '@pikku/core/state'
+import { runScheduledTask } from '@pikku/core/scheduler'
+import { getScheduledTasks } from '@pikku/core/scheduler'
 import { rpcService } from '@pikku/core/rpc'
 
 interface DelayedTask {