@pikku/skills 0.12.20 → 0.12.22

package/CHANGELOG.md

@@ -1,5 +1,65 @@
 # @pikku/skills
 
+## 0.12.22
+
+### Patch Changes
+
+- 5ace170: Fix the `#pikku` import specifiers the skills teach.
+
+  Twenty-five examples across ten skills named a leaf that does not export the
+  symbol — `pikkuAuth`/`pikkuPermission`/`addGlobalPermission` from `#pikku/function`
+  (they are in `#pikku/auth`), `addHTTPMiddleware` from `#pikku/http` (`#pikku/middleware`),
+  `pikkuServices`/`pikkuWireServices` from `#pikku/function` (`#pikku/setup`),
+  `pikkuWorkflowFunc` from `#pikku/function` (`#pikku/workflow`), `pikkuScenario` and
+  friends from `#pikku/scenario` and from `#pikku/workflow/pikku-workflow-types.gen.js`
+  (`#pikku/scenarios`), and `defineSystemRole` from a bare `#pikku` (`#pikku/scopes`).
+
+  `pikku-addon` also claimed an addon authors against `#pikku/addon/function` and
+  `#pikku/addon/setup`. It does not: `pikku new addon` writes an `imports` map that
+  points `#pikku/*` at the addon's own `.pikku/addon/` tree, so an addon uses the
+  same subpaths an application does. The `addon` segment is the package's business,
+  never part of a specifier.
+
+  An agent following these wrote a file that took schema generation red —
+  `Package import specifier "#pikku" is not defined in package .../packages/functions/package.json`
+  — which is a failure the example, not the agent, was responsible for.
+
+## 0.12.21
+
+### Patch Changes
+
+- 77ae071: `pikku fabric report` sends a finding — something about pikku that cost an agent time — to fabric. It needs a login but no linked project: a finding is about the framework rather than about anyone's project, and the reports worth having most come from checkouts that have nothing to name.
+
+  The finding can be given as JSON on stdin (`--stdin`) instead of as flags. Half the fields are prose, and prose carries apostrophes, quotes, backticks and newlines — every one a shell metacharacter before it is a character in a sentence — so an error message pasted into `--error` used to break the command at its first newline. The same schema validates either path.
+
+  Nothing is written to the repo, so nothing goes stale on an abandoned branch, and the terminal prints exactly what left the machine. Reporting never fails a build.
+
+  A finding that cannot be sent is held in `~/.fabric/findings` rather than dropped: logged out, unlinked, or fabric unreachable are the states a finding is most likely to be describing, and a scaffold that never got far enough to log in is exactly the thing worth hearing about. The queue drains on the next report that succeeds, keeps the project each finding was filed against, and is bounded at 100. `pikku fabric findings list`, `flush` and `clear` inspect and control it.
+
+  The resolved `@pikku/*` versions are read off the installed tree rather than out of `package.json`, since a range says nothing about what actually ran. A skewed tree and a package resolving through a workspace or link are both flagged, because either is a reason to read the finding differently.
+
+  The `pikku-feature` skill now tells an agent when to file one: work around it first, investigate only when there is no workaround, report at the depth already reached, and never patch pikku itself from inside a project that is using it.
+
+- 32d1280: Prefix the better-auth plugin factories with `pikku`: `pikkuActor`, `pikkuBan`,
+  `pikkuFabric`, `pikkuDelegatedAuth` and `pikkuCredentialOAuth`.
+
+  A `betterAuth({ plugins: [...] })` array mixes this package's plugins with
+  better-auth's own, and until now nothing at the call site told them apart —
+  `plugins: [actor(...), ban(), fabric(...), organization()]` reads as four
+  plugins from one place when only the last is better-auth's. The prefix says
+  which package a plugin came from where it is actually wired.
+
+  The old names are still exported as deprecated aliases bound to the same
+  functions, so no import has to change. Nothing about the plugins themselves
+  moved: the `id` each registers under — `pikku-ban`, `actor`, `fabric`,
+  `delegated-auth`, `credential-oauth` — is unchanged, so no deployed database or
+  session is affected.
+
+  The pieces that read a plugin's _export_ name rather than its id accept both:
+  `PLUGIN_REGISTRY` is keyed under the prefixed and the bare name, and the
+  `pikku validate` ban/actor checks and the `scaffold.userAdmin` ban check count
+  either spelling as wired. Their messages now point at the new names.
+
 ## 0.12.20
 
 ### Patch Changes