@pikku/skills 0.12.27 → 0.12.29

package/CHANGELOG.md

@@ -1,5 +1,46 @@
 # @pikku/skills
 
+## 0.12.29
+
+### Patch Changes
+
+- 96b65ae: Document how an addon ships database tables: `pikku db export`, the artifact the
+  consumer resolves through the package name, and the silent failure when it is
+  neither exported nor packed.
+- c4ee98d: **pikku-build** gains `references/design.md`: the composition doctrine that no theme can supply. An app built to the letter of the skill still came out looking like nobody had decided anything — a form at the top of every list screen, sixty identical cards each carrying two filled buttons, an "urgent" group holding half the fridge, a scaffolded login page with a Google button the app had no credentials for, and the whole thing judged against a dev database full of `Ripe peaches d193e2aa` left behind by scenario runs. The new reference names the bar (six questions a screen has to answer), the composition rules that get it there, the screens agents forget — login, navigation, empty states — and the reset-and-restart that has to happen before any of it is judged. §8 now says out loud that half of it belongs at §6, because a design pass over eight finished milestones is a repaint.
+- f99547e: Two things an agent building a vision feature had to discover by reading source. **pikku-agent** now documents `attachments`: the `data`/`url` split, that a `url` is downloaded server-side (so a caller-supplied one is an SSRF surface the runner's host allowlist exists for), that the model id — not the provider prefix — decides whether an image is read at all, and that reading a picture into typed data is the tool-free case `output` was waiting for. **pikku-fabric** gains "Reaching a model": `pikku dev` builds the `agentRunner` from a matching `OPENAI_BASE_URL`/`OPENAI_API_KEY` or `LITELLM_PROXY_URL`/`LITELLM_API_KEY` pair and otherwise 503s every agent with `AIProviderNotConfiguredError`, and `pikku fabric llm key --env` is the one command that fills either pair in from the Fabric AI gateway.
+
+## 0.12.28
+
+### Patch Changes
+
+- 591593a: Document `pikku knowledge next` in the `pikku-knowledge` skill: what the six actions mean,
+  that `reason` is machine wording never to be repeated to a person, and that `ask-user`
+  carries a separate `question` whose empty `options` list means offer free text rather than
+  invent choices.
+- 591593a: Document the two frontmatter keys a driving loop writes, in `pikku-knowledge`.
+
+  `statusAt:` and `attempts:` are bookkeeping rather than content, and an agent
+  that rewrites a note has to know not to hand-edit them — clearing `attempts:`
+  hands back a budget that exists to stop a note nothing can satisfy being
+  rewritten forever.
+
+  Also corrects the status vocabulary: it is `designing` → `proposed` →
+  `dispatched` → `built`. The skill said `proposed` → `dispatched` → `built`,
+  "nothing else", while `validate` has always accepted `designing`.
+
+- f5a8ee4: Teach `pikku-kysely` to count round trips.
+
+  The skill documented the query builder API but said nothing about how many times
+  a function body crosses the wire, so generated functions routinely awaited four
+  or five queries in series — invisible locally, a stacked latency in a deployed
+  stage. Adds the four shapes that collapse: independent reads into `Promise.all`,
+  parent-then-children into the `jsonArrayFrom` helpers already documented below
+  it, read-then-write into one `returning()`/`onConflict` statement that also
+  closes the race, and a read that only feeds the next `where` into a subquery or
+  CTE. Plus the correction that a transaction adds round trips rather than
+  removing them.
+
 ## 0.12.27
 
 ### Patch Changes