@quickback-dev/cli 0.10.16 → 0.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (253) hide show
  1. package/dist/commands/compile.d.ts.map +1 -1
  2. package/dist/commands/compile.js +40 -2
  3. package/dist/commands/compile.js.map +1 -1
  4. package/dist/docs/content.d.ts.map +1 -1
  5. package/dist/docs/content.js +15 -10
  6. package/dist/docs/content.js.map +1 -1
  7. package/dist/index.js +1 -1
  8. package/dist/index.js.map +1 -1
  9. package/dist/skill/SKILL.md +142 -1051
  10. package/dist/skill/agents/quickback-specialist/AGENT.md +36 -0
  11. package/dist/skill/docs/changelog.md +1225 -0
  12. package/dist/skill/docs/compiler/claude-code-skill.md +312 -0
  13. package/dist/skill/docs/compiler/cloud-compiler/authentication.md +63 -0
  14. package/dist/skill/docs/compiler/cloud-compiler/cli.md +307 -0
  15. package/dist/skill/docs/compiler/cloud-compiler/endpoints.md +78 -0
  16. package/dist/skill/docs/compiler/cloud-compiler/index.md +65 -0
  17. package/dist/skill/docs/compiler/cloud-compiler/local-compiler.md +115 -0
  18. package/dist/skill/docs/compiler/cloud-compiler/troubleshooting.md +76 -0
  19. package/dist/skill/docs/compiler/config/agents.md +144 -0
  20. package/dist/skill/docs/compiler/config/auth.md +109 -0
  21. package/dist/skill/docs/compiler/config/bindings.md +176 -0
  22. package/dist/skill/docs/compiler/config/domains.md +149 -0
  23. package/dist/skill/docs/compiler/config/index.md +419 -0
  24. package/dist/skill/docs/compiler/config/output.md +338 -0
  25. package/dist/skill/docs/compiler/config/providers.md +248 -0
  26. package/dist/skill/docs/compiler/config/security.md +255 -0
  27. package/dist/skill/docs/compiler/config/single-tenant.md +128 -0
  28. package/dist/skill/docs/compiler/config/variables.md +157 -0
  29. package/dist/skill/docs/compiler/definitions/access.md +445 -0
  30. package/dist/skill/docs/compiler/definitions/actions.md +884 -0
  31. package/dist/skill/docs/compiler/definitions/concepts.md +52 -0
  32. package/dist/skill/docs/compiler/definitions/feature.md +164 -0
  33. package/dist/skill/docs/compiler/definitions/firewall.md +285 -0
  34. package/dist/skill/docs/compiler/definitions/guards.md +241 -0
  35. package/dist/skill/docs/compiler/definitions/index.md +219 -0
  36. package/dist/skill/docs/compiler/definitions/masking.md +241 -0
  37. package/dist/skill/docs/compiler/definitions/read.md +220 -0
  38. package/dist/skill/docs/compiler/definitions/schema.md +697 -0
  39. package/dist/skill/docs/compiler/definitions/validation.md +35 -0
  40. package/dist/skill/docs/compiler/definitions/views.md +292 -0
  41. package/dist/skill/docs/compiler/getting-started/claude-code.md +126 -0
  42. package/dist/skill/docs/compiler/getting-started/full-example.md +431 -0
  43. package/dist/skill/docs/compiler/getting-started/hand-crafted.md +178 -0
  44. package/dist/skill/docs/compiler/getting-started/index.md +192 -0
  45. package/dist/skill/docs/compiler/getting-started/patterns.md +225 -0
  46. package/dist/skill/docs/compiler/getting-started/template-blog.md +280 -0
  47. package/dist/skill/docs/compiler/getting-started/template-cloudflare.md +260 -0
  48. package/dist/skill/docs/compiler/getting-started/template-empty.md +112 -0
  49. package/dist/skill/docs/compiler/getting-started/templates.md +111 -0
  50. package/dist/skill/docs/compiler/index.md +85 -0
  51. package/dist/skill/docs/compiler/targets/hono-api/cloudflare.md +94 -0
  52. package/dist/skill/docs/compiler/targets/hono-api/database/d1.md +246 -0
  53. package/dist/skill/docs/compiler/targets/hono-api/database/index.md +16 -0
  54. package/dist/skill/docs/compiler/targets/hono-api/database/neon.md +144 -0
  55. package/dist/skill/docs/compiler/targets/hono-api/database/using-d1.md +39 -0
  56. package/dist/skill/docs/compiler/targets/hono-api/index.md +37 -0
  57. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/actions-api.md +323 -0
  58. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/batch-operations.md +357 -0
  59. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/caching.md +105 -0
  60. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/crud.md +652 -0
  61. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/errors.md +224 -0
  62. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/index.md +37 -0
  63. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/openapi.md +203 -0
  64. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/query-params.md +199 -0
  65. package/dist/skill/docs/compiler/targets/hono-api/using-the-api/views-api.md +161 -0
  66. package/dist/skill/docs/compiler/targets/index.md +47 -0
  67. package/dist/skill/docs/compiler/targets/supabase-rls/index.md +55 -0
  68. package/dist/skill/docs/compiler/targets/supabase-rls/limitations.md +48 -0
  69. package/dist/skill/docs/compiler/targets/supabase-rls/mappings.md +99 -0
  70. package/dist/skill/docs/compiler/targets/supabase-rls/setup.md +88 -0
  71. package/dist/skill/docs/compiler/troubleshooting.md +120 -0
  72. package/dist/skill/docs/index.md +77 -0
  73. package/dist/skill/docs/stack/account-ui/customization.md +378 -0
  74. package/dist/skill/docs/stack/account-ui/environment-variables.md +325 -0
  75. package/dist/skill/docs/stack/account-ui/features/admin.md +76 -0
  76. package/dist/skill/docs/stack/account-ui/features/api-keys.md +22 -0
  77. package/dist/skill/docs/stack/account-ui/features/avatars.md +37 -0
  78. package/dist/skill/docs/stack/account-ui/features/cli-authorize.md +21 -0
  79. package/dist/skill/docs/stack/account-ui/features/index.md +291 -0
  80. package/dist/skill/docs/stack/account-ui/features/organizations.md +29 -0
  81. package/dist/skill/docs/stack/account-ui/features/passkeys.md +31 -0
  82. package/dist/skill/docs/stack/account-ui/features/passwordless.md +28 -0
  83. package/dist/skill/docs/stack/account-ui/features/sessions.md +20 -0
  84. package/dist/skill/docs/stack/account-ui/hooks.md +209 -0
  85. package/dist/skill/docs/stack/account-ui/index.md +147 -0
  86. package/dist/skill/docs/stack/account-ui/library-usage.md +257 -0
  87. package/dist/skill/docs/stack/account-ui/standalone.md +149 -0
  88. package/dist/skill/docs/stack/account-ui/with-quickback.md +160 -0
  89. package/dist/skill/docs/stack/account-ui/worker.md +362 -0
  90. package/dist/skill/docs/stack/auth/api-keys.md +15 -0
  91. package/dist/skill/docs/stack/auth/device-auth.md +14 -0
  92. package/dist/skill/docs/stack/auth/index.md +64 -0
  93. package/dist/skill/docs/stack/auth/jwt-optimization.md +245 -0
  94. package/dist/skill/docs/stack/auth/plugins/aws-ses.md +127 -0
  95. package/dist/skill/docs/stack/auth/plugins/combo-auth.md +74 -0
  96. package/dist/skill/docs/stack/auth/plugins/index.md +340 -0
  97. package/dist/skill/docs/stack/auth/plugins/upgrade-anonymous.md +155 -0
  98. package/dist/skill/docs/stack/auth/security.md +455 -0
  99. package/dist/skill/docs/stack/auth/using-auth.md +39 -0
  100. package/dist/skill/docs/stack/cms/actions.md +199 -0
  101. package/dist/skill/docs/stack/cms/components.md +479 -0
  102. package/dist/skill/docs/stack/cms/connecting.md +199 -0
  103. package/dist/skill/docs/stack/cms/dashboard.md +39 -0
  104. package/dist/skill/docs/stack/cms/index.md +158 -0
  105. package/dist/skill/docs/stack/cms/inline-editing.md +136 -0
  106. package/dist/skill/docs/stack/cms/pages.md +275 -0
  107. package/dist/skill/docs/stack/cms/record-layouts.md +151 -0
  108. package/dist/skill/docs/stack/cms/schema-format.md +437 -0
  109. package/dist/skill/docs/stack/cms/schema-registry.md +200 -0
  110. package/dist/skill/docs/stack/cms/security.md +203 -0
  111. package/dist/skill/docs/stack/cms/table-views.md +142 -0
  112. package/dist/skill/docs/stack/index.md +65 -0
  113. package/dist/skill/docs/stack/queues/handlers.md +317 -0
  114. package/dist/skill/docs/stack/queues/index.md +56 -0
  115. package/dist/skill/docs/stack/queues/using-queues.md +192 -0
  116. package/dist/skill/docs/stack/realtime/durable-objects.md +488 -0
  117. package/dist/skill/docs/stack/realtime/index.md +73 -0
  118. package/dist/skill/docs/stack/realtime/partyserver-rooms.md +146 -0
  119. package/dist/skill/docs/stack/realtime/using-realtime.md +211 -0
  120. package/dist/skill/docs/stack/storage/index.md +17 -0
  121. package/dist/skill/docs/stack/storage/kv.md +204 -0
  122. package/dist/skill/docs/stack/storage/r2.md +232 -0
  123. package/dist/skill/docs/stack/storage/using-kv.md +70 -0
  124. package/dist/skill/docs/stack/storage/using-r2.md +55 -0
  125. package/dist/skill/docs/stack/vector/embeddings.md +554 -0
  126. package/dist/skill/docs/stack/vector/index.md +44 -0
  127. package/dist/skill/docs/stack/vector/using-embeddings.md +186 -0
  128. package/dist/skill/docs/stack/webhooks/inbound.md +186 -0
  129. package/dist/skill/docs/stack/webhooks/index.md +36 -0
  130. package/dist/skill/docs/stack/webhooks/outbound.md +281 -0
  131. package/package.json +1 -1
  132. package/src/skill/SKILL.md +142 -1051
  133. package/src/skill/agents/quickback-specialist/AGENT.md +36 -0
  134. package/src/skill/docs/changelog.md +1225 -0
  135. package/src/skill/docs/compiler/claude-code-skill.md +312 -0
  136. package/src/skill/docs/compiler/cloud-compiler/authentication.md +63 -0
  137. package/src/skill/docs/compiler/cloud-compiler/cli.md +307 -0
  138. package/src/skill/docs/compiler/cloud-compiler/endpoints.md +78 -0
  139. package/src/skill/docs/compiler/cloud-compiler/index.md +65 -0
  140. package/src/skill/docs/compiler/cloud-compiler/local-compiler.md +115 -0
  141. package/src/skill/docs/compiler/cloud-compiler/troubleshooting.md +76 -0
  142. package/src/skill/docs/compiler/config/agents.md +144 -0
  143. package/src/skill/docs/compiler/config/auth.md +109 -0
  144. package/src/skill/docs/compiler/config/bindings.md +176 -0
  145. package/src/skill/docs/compiler/config/domains.md +149 -0
  146. package/src/skill/docs/compiler/config/index.md +419 -0
  147. package/src/skill/docs/compiler/config/output.md +338 -0
  148. package/src/skill/docs/compiler/config/providers.md +248 -0
  149. package/src/skill/docs/compiler/config/security.md +255 -0
  150. package/src/skill/docs/compiler/config/single-tenant.md +128 -0
  151. package/src/skill/docs/compiler/config/variables.md +157 -0
  152. package/src/skill/docs/compiler/definitions/access.md +445 -0
  153. package/src/skill/docs/compiler/definitions/actions.md +884 -0
  154. package/src/skill/docs/compiler/definitions/concepts.md +52 -0
  155. package/src/skill/docs/compiler/definitions/feature.md +164 -0
  156. package/src/skill/docs/compiler/definitions/firewall.md +285 -0
  157. package/src/skill/docs/compiler/definitions/guards.md +241 -0
  158. package/src/skill/docs/compiler/definitions/index.md +219 -0
  159. package/src/skill/docs/compiler/definitions/masking.md +241 -0
  160. package/src/skill/docs/compiler/definitions/read.md +220 -0
  161. package/src/skill/docs/compiler/definitions/schema.md +697 -0
  162. package/src/skill/docs/compiler/definitions/validation.md +35 -0
  163. package/src/skill/docs/compiler/definitions/views.md +292 -0
  164. package/src/skill/docs/compiler/getting-started/claude-code.md +126 -0
  165. package/src/skill/docs/compiler/getting-started/full-example.md +431 -0
  166. package/src/skill/docs/compiler/getting-started/hand-crafted.md +178 -0
  167. package/src/skill/docs/compiler/getting-started/index.md +192 -0
  168. package/src/skill/docs/compiler/getting-started/patterns.md +225 -0
  169. package/src/skill/docs/compiler/getting-started/template-blog.md +280 -0
  170. package/src/skill/docs/compiler/getting-started/template-cloudflare.md +260 -0
  171. package/src/skill/docs/compiler/getting-started/template-empty.md +112 -0
  172. package/src/skill/docs/compiler/getting-started/templates.md +111 -0
  173. package/src/skill/docs/compiler/index.md +85 -0
  174. package/src/skill/docs/compiler/targets/hono-api/cloudflare.md +94 -0
  175. package/src/skill/docs/compiler/targets/hono-api/database/d1.md +246 -0
  176. package/src/skill/docs/compiler/targets/hono-api/database/index.md +16 -0
  177. package/src/skill/docs/compiler/targets/hono-api/database/neon.md +144 -0
  178. package/src/skill/docs/compiler/targets/hono-api/database/using-d1.md +39 -0
  179. package/src/skill/docs/compiler/targets/hono-api/index.md +37 -0
  180. package/src/skill/docs/compiler/targets/hono-api/using-the-api/actions-api.md +323 -0
  181. package/src/skill/docs/compiler/targets/hono-api/using-the-api/batch-operations.md +357 -0
  182. package/src/skill/docs/compiler/targets/hono-api/using-the-api/caching.md +105 -0
  183. package/src/skill/docs/compiler/targets/hono-api/using-the-api/crud.md +652 -0
  184. package/src/skill/docs/compiler/targets/hono-api/using-the-api/errors.md +224 -0
  185. package/src/skill/docs/compiler/targets/hono-api/using-the-api/index.md +37 -0
  186. package/src/skill/docs/compiler/targets/hono-api/using-the-api/openapi.md +203 -0
  187. package/src/skill/docs/compiler/targets/hono-api/using-the-api/query-params.md +199 -0
  188. package/src/skill/docs/compiler/targets/hono-api/using-the-api/views-api.md +161 -0
  189. package/src/skill/docs/compiler/targets/index.md +47 -0
  190. package/src/skill/docs/compiler/targets/supabase-rls/index.md +55 -0
  191. package/src/skill/docs/compiler/targets/supabase-rls/limitations.md +48 -0
  192. package/src/skill/docs/compiler/targets/supabase-rls/mappings.md +99 -0
  193. package/src/skill/docs/compiler/targets/supabase-rls/setup.md +88 -0
  194. package/src/skill/docs/compiler/troubleshooting.md +120 -0
  195. package/src/skill/docs/index.md +77 -0
  196. package/src/skill/docs/stack/account-ui/customization.md +378 -0
  197. package/src/skill/docs/stack/account-ui/environment-variables.md +325 -0
  198. package/src/skill/docs/stack/account-ui/features/admin.md +76 -0
  199. package/src/skill/docs/stack/account-ui/features/api-keys.md +22 -0
  200. package/src/skill/docs/stack/account-ui/features/avatars.md +37 -0
  201. package/src/skill/docs/stack/account-ui/features/cli-authorize.md +21 -0
  202. package/src/skill/docs/stack/account-ui/features/index.md +291 -0
  203. package/src/skill/docs/stack/account-ui/features/organizations.md +29 -0
  204. package/src/skill/docs/stack/account-ui/features/passkeys.md +31 -0
  205. package/src/skill/docs/stack/account-ui/features/passwordless.md +28 -0
  206. package/src/skill/docs/stack/account-ui/features/sessions.md +20 -0
  207. package/src/skill/docs/stack/account-ui/hooks.md +209 -0
  208. package/src/skill/docs/stack/account-ui/index.md +147 -0
  209. package/src/skill/docs/stack/account-ui/library-usage.md +257 -0
  210. package/src/skill/docs/stack/account-ui/standalone.md +149 -0
  211. package/src/skill/docs/stack/account-ui/with-quickback.md +160 -0
  212. package/src/skill/docs/stack/account-ui/worker.md +362 -0
  213. package/src/skill/docs/stack/auth/api-keys.md +15 -0
  214. package/src/skill/docs/stack/auth/device-auth.md +14 -0
  215. package/src/skill/docs/stack/auth/index.md +64 -0
  216. package/src/skill/docs/stack/auth/jwt-optimization.md +245 -0
  217. package/src/skill/docs/stack/auth/plugins/aws-ses.md +127 -0
  218. package/src/skill/docs/stack/auth/plugins/combo-auth.md +74 -0
  219. package/src/skill/docs/stack/auth/plugins/index.md +340 -0
  220. package/src/skill/docs/stack/auth/plugins/upgrade-anonymous.md +155 -0
  221. package/src/skill/docs/stack/auth/security.md +455 -0
  222. package/src/skill/docs/stack/auth/using-auth.md +39 -0
  223. package/src/skill/docs/stack/cms/actions.md +199 -0
  224. package/src/skill/docs/stack/cms/components.md +479 -0
  225. package/src/skill/docs/stack/cms/connecting.md +199 -0
  226. package/src/skill/docs/stack/cms/dashboard.md +39 -0
  227. package/src/skill/docs/stack/cms/index.md +158 -0
  228. package/src/skill/docs/stack/cms/inline-editing.md +136 -0
  229. package/src/skill/docs/stack/cms/pages.md +275 -0
  230. package/src/skill/docs/stack/cms/record-layouts.md +151 -0
  231. package/src/skill/docs/stack/cms/schema-format.md +437 -0
  232. package/src/skill/docs/stack/cms/schema-registry.md +200 -0
  233. package/src/skill/docs/stack/cms/security.md +203 -0
  234. package/src/skill/docs/stack/cms/table-views.md +142 -0
  235. package/src/skill/docs/stack/index.md +65 -0
  236. package/src/skill/docs/stack/queues/handlers.md +317 -0
  237. package/src/skill/docs/stack/queues/index.md +56 -0
  238. package/src/skill/docs/stack/queues/using-queues.md +192 -0
  239. package/src/skill/docs/stack/realtime/durable-objects.md +488 -0
  240. package/src/skill/docs/stack/realtime/index.md +73 -0
  241. package/src/skill/docs/stack/realtime/partyserver-rooms.md +146 -0
  242. package/src/skill/docs/stack/realtime/using-realtime.md +211 -0
  243. package/src/skill/docs/stack/storage/index.md +17 -0
  244. package/src/skill/docs/stack/storage/kv.md +204 -0
  245. package/src/skill/docs/stack/storage/r2.md +232 -0
  246. package/src/skill/docs/stack/storage/using-kv.md +70 -0
  247. package/src/skill/docs/stack/storage/using-r2.md +55 -0
  248. package/src/skill/docs/stack/vector/embeddings.md +554 -0
  249. package/src/skill/docs/stack/vector/index.md +44 -0
  250. package/src/skill/docs/stack/vector/using-embeddings.md +186 -0
  251. package/src/skill/docs/stack/webhooks/inbound.md +186 -0
  252. package/src/skill/docs/stack/webhooks/index.md +36 -0
  253. package/src/skill/docs/stack/webhooks/outbound.md +281 -0
@@ -0,0 +1,1225 @@
1
+ # Changelog
2
+
3
+ Release notes for the Quickback compiler, CLI, and platform.
4
+
5
+ ---
6
+
7
+ ## v0.11.0 — May 5, 2026
8
+
9
+ ### OAuth Provider plugin (MCP-ready)
10
+
11
+ Quickback can now act as a standards-compliant OAuth 2.1 + OIDC authorization server via [`@better-auth/oauth-provider`](https://better-auth.com/docs/plugins/oauth-provider). Enable it with `plugins: ["oauthProvider"]` in your auth config — the compiler auto-includes Better Auth's `jwt` plugin (the OAuth provider delegates access-token signing to it) and the Account SPA gains a `/consent` page for the standard authorization-code flow.
12
+
13
+ This replaces Better Auth's deprecated `mcp` plugin and gives every future MCP client (Cursor, Claude Desktop, claude.ai connectors, custom tooling) RFC 7591 dynamic client registration + the well-known discovery documents they need to bootstrap themselves. See [Auth Plugins → OAuth Provider](/stack/auth/plugins#oauth-provider-mcp-ready).
14
+
15
+ ### API key auth via query parameter
16
+
17
+ The auth middleware now accepts API keys as `?api_key=...` or `?key=...` query parameters in addition to the `x-api-key` header. The header takes precedence when both are sent. This unblocks clients that can't inject custom headers — most notably claude.ai's MCP connector, which previously returned zero tools because every list/call attempt was unauthenticated.
18
+
19
+ The query-param form lands in access logs and `Referer` headers; prefer the header whenever the client supports it. See [Auth Plugins → API Keys](/stack/auth/plugins#api-keys).
20
+
21
+ ### PartyServer rooms + realtime URL split (breaking)
22
+
23
+ The realtime URL space is reorganized so the names match what each primitive does:
24
+
25
+ - **`/realtime/v1/*` → `/broadcast/v1/*`** — the existing org-wide Broadcaster (Postgres-changes fan-out, ws-ticket auth) moves to its semantically accurate prefix. Same code, same behavior, just a different mount point.
26
+ - **`/realtime/<binding>/<room-id>` is the new mount for [PartyServer](/stack/realtime/partyserver-rooms) rooms** — bidirectional, per-room (per-document) Durable Objects with presence and lifecycle hooks. Auto-mounted via `hono-party` whenever a project declares any in-worker DO via `bindings.durableObjects[].from`. Use these for collaborative editing, live cursors, and per-room state.
27
+
28
+ **Breaking changes** — recompile + redeploy required:
29
+
30
+ - The `REALTIME_URL` runtime env var is renamed to `BROADCAST_URL` (used by the org member-update broadcast hook in separate-mode realtime). If you set this via `wrangler secret put REALTIME_URL`, re-set it as `BROADCAST_URL`.
31
+ - The auth-ui SPA helpers `getRealtimeWsUrl()` / `getRealtimeTicketUrl()` are renamed to `getBroadcastWsUrl()` / `getBroadcastTicketUrl()`. The `appConfig.routes.api.realtime` field is renamed to `appConfig.routes.api.broadcast`.
32
+ - WebSocket subscribers that hardcoded `/realtime/v1/websocket` or `/realtime/v1/ws-ticket` need to be updated to `/broadcast/v1/...`. The bundled CMS and Account SPAs handle this automatically; custom clients need a one-line change.
33
+
34
+ **Pre-installed deps in the compiler image:** `partyserver`, `partysocket`, and `hono-party` are now cached in `/deps/node_modules` so opt-in collab projects compile without an extra `npm install` step. `Y-PartyServer` (Yjs CRDT support) stays opt-in.
35
+
36
+ **Recipe:** see the new [PartyServer Rooms](/stack/realtime/partyserver-rooms) doc page and the `examples/recruitment` interview-room demo for an end-to-end example with presence and live notes.
37
+
38
+ ---
39
+
40
+ ## v0.10.20 — May 4, 2026
41
+
42
+ ### In-worker Durable Objects via `bindings.durableObjects[].from`
43
+
44
+ `bindings.durableObjects` previously only emitted the binding declaration — useful for cross-worker DOs (`scriptName: "other-worker"`), but not enough for app-owned classes that live in this worker's source. Authors had to hand-edit `src/index.ts` (to add `export { ItemStream } from './...'`) and `wrangler.toml` (to add the `[[migrations]]` block) on every compile.
45
+
46
+ Adding `from` flips the entry into in-worker mode and the compiler does both:
47
+
48
+ ```ts
49
+ durableObjects: [
50
+ {
51
+ name: "ITEM_STREAM",
52
+ className: "ItemStream",
53
+ from: "features/loops/lib/ItemStream", // module path under src/
54
+ },
55
+ ]
56
+ ```
57
+
58
+ Generates:
59
+ - `src/index.ts`: `export { ItemStream } from './features/loops/lib/ItemStream';` — wrangler resolves the binding by class export.
60
+ - `wrangler.toml`: a `[[migrations]]` block with `tag = "qb-do-ItemStream"` and `new_sqlite_classes = ["ItemStream"]`.
61
+ - `CloudflareBindings`: `ITEM_STREAM: DurableObjectNamespace` so `c.env.ITEM_STREAM.idFromName(...)` typechecks.
62
+
63
+ Where the class file lives: in-worker DO classes go under `quickback/lib/` or `quickback/features/<feature>/lib/` — both copy verbatim into the generated `src/` tree on every compile (the rest of `src/` is wiped). The `from` value is the resulting `src/`-relative path with no `./` prefix and no `.ts` suffix.
64
+
65
+ `from` and `scriptName` are mutually exclusive — the compiler rejects entries that set both. Cross-worker entries (`scriptName` set) skip the re-export and the migration block; the exporting worker owns its own migration table.
66
+
67
+ `migrationTag` (default `qb-do-${className}`) is stable across regenerations and **must never be removed or renamed once deployed** — wrangler tracks applied tags and will reject deploys that try to walk them back. `useSqlite` defaults to `true`; set to `false` for legacy KV-backed DOs.
68
+
69
+ See [Bindings → Durable Objects](/compiler/config/bindings#durableobjects) for the full reference.
70
+
71
+ ---
72
+
73
+ ## v0.10.19 — May 4, 2026
74
+
75
+ ### Fix: bundled-SPA auth survives `wrangler dev` on custom_domain projects
76
+
77
+ `wrangler dev` rewrites the configured `custom_domain` host in **every** response header value (Location, Content-Security-Policy, X-…) to the local hostname, with a case-sensitive substring matcher. That mangles the CSP `connect-src` for projects with `domain: "api.example.com"` + bundled CMS / Account SPAs:
78
+
79
+ ```
80
+ # Compiled (correct)
81
+ connect-src 'self' https://api.example.com …
82
+
83
+ # Served by wrangler dev (mangled)
84
+ connect-src 'self' https://localhost:8787 …
85
+ ```
86
+
87
+ Result: the bundled SPA's hardcoded `VITE_QUICKBACK_API_URL` fetches get blocked in dev because the CSP only allows localhost. Reported by Loop on the 0.10.18 thread; verified end-to-end with a minimal `wrangler@4.85.0 dev --local` repro.
88
+
89
+ The compiler now emits the SPA-baked-origin literal in `connect-src` with the host's first letter capitalised (`https://Api.example.com`). CSP host-source matching is ASCII case-insensitive per CSP3, so browsers accept it for connections to `https://api.example.com`; wrangler's case-sensitive matcher misses it. The case-shift is applied at compile time and only to URLs whose host matches the configured `custom_domain` — other origins (localhost, third-party hosts) are unchanged.
90
+
91
+ `TRUSTED_ORIGINS` keeps its lowercase prod entries: it's consumed by the CORS `isTrustedOrigin` check via `Array.includes()` against the browser-supplied Origin header (always lowercase). The CSP fix only needs to land on the SPA-baked literal — that's the entry the SPA's hardcoded fetch needs covered.
92
+
93
+ If wrangler ships a fix for the response-header rewrite, the case-shifted source remains a valid CSP entry that browsers match identically — no follow-up needed in user code.
94
+
95
+ **Action required:** none. Recompile (`quickback compile`) to pick up the fix.
96
+
97
+ ---
98
+
99
+ ## v0.10.18 — May 2, 2026
100
+
101
+ ### `experimentalRemote` — share deployed D1 with `wrangler dev`
102
+
103
+ Per-binding `experimental_remote = true` flag emitted into the generated `wrangler.toml`. Useful for "share prod auth in dev, keep feature writes sandboxed":
104
+
105
+ ```ts
106
+ providers: {
107
+ database: defineDatabase("cloudflare-d1", {
108
+ splitDatabases: true,
109
+ experimentalRemote: {
110
+ auth: true, // wrangler dev reads/writes deployed AUTH_DB
111
+ features: false, // (default) features stays local
112
+ audit: false,
113
+ webhooks: false,
114
+ files: false,
115
+ },
116
+ }),
117
+ }
118
+ ```
119
+
120
+ Keys are logical binding names — `auth` flips the flag on the `AUTH_DB` binding, `features` flips it on `DB` (or the legacy single-DB binding), `audit` / `webhooks` / `files` follow the same pattern. Off by default; only enable for databases you intend to share.
121
+
122
+ ### Google OAuth + signup ToS
123
+
124
+ The Account SPA now wires Google OAuth end-to-end when `auth.providers.auth.config.socialProviders.google.enabled: true`. The compiler bakes the right `VITE_ENABLE_GOOGLE_OAUTH` flag into the SPA's `.env` so the social-login button renders only when the provider is enabled — no more dead buttons.
125
+
126
+ Signup flow gains a Terms-of-Service checkbox gate (configurable via the Account SPA's branding config).
127
+
128
+ ### CLI compile auth gate + device-auth redirect fix
129
+
130
+ - `quickback compile` now requires authentication for cloud-compiler runs (closes the unauth public-compile path).
131
+ - The device-flow `/cli/authorize` page was sending `?returnTo=` to login, but `signup.tsx` and the `_authenticated` middleware only read `?redirect=` — so a user who clicked "Create one" from `/login` lost the return URL. Standardized on `?redirect=` everywhere.
132
+
133
+ ### Skill restructure (Claude Code skill)
134
+
135
+ The bundled Claude Code skill was reorganized for clarity:
136
+
137
+ - `SKILL.md` is now a thin orientation pointer, not a 600-line dump
138
+ - Reference docs split into `Compiler` and `Stack` sections
139
+ - Docs bundled as **files** the model navigates with `Read` / `Glob` rather than via `quickback docs <topic>` shell calls — same content, fewer tool calls per lookup
140
+ - Tightened against audit gaps surfaced by red-team review
141
+
142
+ Run `quickback claude install` to pick up the new skill layout.
143
+
144
+ ---
145
+
146
+ ## v0.10.17 — May 2, 2026
147
+
148
+ ### Security fix: CSP auto-config no longer widens `default-src`
149
+
150
+ When 0.10.15's auto-config was asked to add a value to a directive the user hadn't declared (e.g. `https://fonts.googleapis.com` → `style-src` when only `default-src` was set), it incorrectly pushed the value into `default-src` itself. Because CSP3 fall-back semantics make `default-src` the fallback for `script-src`, `img-src`, `media-src`, and others, this widened the attack surface to every directive that fell back to it — a `style-src`-only host became reachable from `script-src`.
151
+
152
+ 0.10.17 fixes the logic: missing target directives are now **scaffolded** with the user's `default-src` values as baseline, then extended with the auto-config addition. `default-src` stays clean. The new directive (e.g. `style-src`) covers exactly the styles the SPA needs and nothing else.
153
+
154
+ Before (0.10.16):
155
+ ```
156
+ default-src 'self' https://fonts.googleapis.com https://fonts.gstatic.com @trustedOrigins https://api.example.com
157
+ ```
158
+
159
+ After (0.10.17):
160
+ ```
161
+ default-src 'self'
162
+ style-src 'self' 'unsafe-inline' https://fonts.googleapis.com
163
+ font-src 'self' https://fonts.gstatic.com
164
+ connect-src 'self' @trustedOrigins https://api.example.com
165
+ ```
166
+
167
+ **Action required:** recompile (`quickback compile`) to regenerate the security middleware with the corrected scaffolding. Configs that already declared each `*-src` directive explicitly were unaffected by the bug — the regression only surfaced when users wrote `defaultSrc: ['@self']` and let auto-config fill in the rest.
168
+
169
+ The user-side workaround from 0.10.16 (declaring each directive with `['@self']` to force scaffold) is no longer needed in 0.10.17 — the compiler does the right thing automatically.
170
+
171
+ ---
172
+
173
+ ## v0.10.16 — May 2, 2026
174
+
175
+ ### CSP auto-config now covers SPA-baked-in API origins
176
+
177
+ When the bundled CMS or Account SPA is enabled, the compiler already inlines the API URL into the SPA bundle as a string literal at build time (`VITE_QUICKBACK_API_URL=https://${unifiedDomain}`). That hardcoded URL is what the SPA actually fetches — regardless of which origin is currently serving the page. CSP `connect-src` must allow it explicitly.
178
+
179
+ 0.10.16's auto-config picks up every domain the compiler already knows about — `config.domain`, the inferred `quickback.{baseDomain}`, `cms.domain`, `account.domain`, the admin domain — and adds `https://${each}` to `connectSrc` whenever a bundled SPA is enabled.
180
+
181
+ The motivating case: running the SPA on `localhost:5173` while it's still baked against `https://quickback.your-app.com`. Pre-0.10.16 the localhost CSP's `'self'` blocked the prod URL; users were patching it manually. Now it just works.
182
+
183
+ ```
184
+ [security] auto-added https://quickback.loop.kardoe.com to csp.connectSrc — account: true → bundled Account SPA → SPA bundle hardcodes https://quickback.loop.kardoe.com as VITE_QUICKBACK_API_URL / etc.
185
+ ```
186
+
187
+ `@trustedOrigins` (the CORS allowlist) is unchanged — it still gets added independently. The two cover different things: `@trustedOrigins` permits CORS-allowed sibling subdomains; the new SPA-baked addition permits the exact URL the SPA's compiled bundle hardcodes.
188
+
189
+ Combined with 0.10.15's bundled-SPA defaults, most projects can now write the minimal:
190
+
191
+ ```ts
192
+ security: {
193
+ csp: {
194
+ defaultSrc: ['@self'],
195
+ scriptSrc: ['@self'],
196
+ objectSrc: ['@none'],
197
+ upgradeInsecureRequests: true,
198
+ },
199
+ }
200
+ ```
201
+
202
+ …and the compiler fills in styleSrc font hosts, fontSrc gstatic, connectSrc trusted origins, and connectSrc SPA-baked URLs.
203
+
204
+ ---
205
+
206
+ ## v0.10.15 — May 2, 2026
207
+
208
+ ### CSP auto-config — bundled-SPA origins added automatically
209
+
210
+ When `security.csp` is set, the compiler now widens directives **additively** based on the project's enabled features. The four rules:
211
+
212
+ | Trigger | Auto-added | Directive |
213
+ |---|---|---|
214
+ | `cms: true` OR `account: true` | `'unsafe-inline'`, `https://fonts.googleapis.com` | `styleSrc` |
215
+ | `cms: true` OR `account: true` | `https://fonts.gstatic.com` | `fontSrc` |
216
+ | `csp` set (always) | `@trustedOrigins` | `connectSrc` |
217
+
218
+ Anything you already wrote stays — auto-config never removes or overrides. Every applied addition prints to stderr at compile so the magic is visible:
219
+
220
+ ```
221
+ [security] auto-added 'unsafe-inline' to csp.styleSrc — account: true → bundled Account SPA → inline style attributes from Tailwind / TanStack Router
222
+ [security] auto-added @trustedOrigins to csp.connectSrc — CORS-trusted origins must be reachable from XHR/fetch (matches cors() allowlist)
223
+ ```
224
+
225
+ The recipe in [the security docs](/compiler/config/security#example-paste-in-csp-for-a-quickback-spa-project) becomes ~5 lines shorter — most projects no longer need to list `fonts.googleapis.com` / `fonts.gstatic.com` / `@trustedOrigins` themselves. **Loop's CSP shrinks dramatically** after recompiling against this version.
226
+
227
+ **Opt-out:** `security: { cspAutoConfig: false, csp: { ... } }` for projects fronted by a CDN that injects its own CSP, or teams that want strict from-scratch control.
228
+
229
+ **Smart fallback:** if you set `defaultSrc` but omit the target directive (e.g. `defaultSrc: ['@self']` and nothing for `connectSrc`), the addition lands in `defaultSrc` rather than creating a sibling directive — CSP fall-back semantics mean a sibling would *narrow* your intent, so we preserve the broader fallback.
230
+
231
+ ### Troubleshooting table for CSP violations
232
+
233
+ The security docs page now includes a [Troubleshooting CSP violations](/compiler/config/security#troubleshooting-csp-violations) table mapping browser console errors back to the directive that needs widening. Useful when auto-config is disabled or the project has a non-bundled SPA hitting third-party origins.
234
+
235
+ ### Out of scope (deferred)
236
+
237
+ - **Per-request CSP nonces** (`@nonce` sentinel implementation) — Phase 2 / 0.10.16. Sentinel still errors at compile in 0.10.15.
238
+ - **`revocationCheck: 'kv'` for `auth.jwt`** — schema accepts it, runtime still errors at compile. Slipped from 0.10.15 to 0.10.16.
239
+ - **Public R2 host auto-add to `imgSrc`** — most R2 access today goes through the worker so the SPA fetches from `'@self'`. Will revisit once we have a clean way to discover public-bucket hosts at compile.
240
+
241
+ ---
242
+
243
+ ## v0.10.14 — May 1, 2026
244
+
245
+ ### `auth.jwt` — JWT bearer-token fast-path config
246
+
247
+ Quickback's bearer-token JWT (the one minted by the auth middleware and consumed by the fast-path on every subsequent request) is now configurable. The most-tuned knob is `expiresIn` — drop it to bound the post-revocation replay window without affecting browser SPAs, which auto-refresh via `set-auth-token` on every authed call:
248
+
249
+ ```ts
250
+ auth: {
251
+ jwt: {
252
+ expiresIn: 30, // 30s post-revocation replay window
253
+ issuer: 'my-api', // iss claim (verified on the way back in)
254
+ audience: 'partner-svc', // aud claim
255
+ secretEnv: 'CUSTOM_JWT_SECRET', // override BETTER_AUTH_SECRET if you need the JWT secret rotated independently
256
+ },
257
+ }
258
+ ```
259
+
260
+ `revocationCheck: 'kv'` (KV-denylist consult on every fast-path verify, ~5-15ms edge-cached, no D1 hit) is reserved in the schema today but **deferred to 0.10.15** — setting it errors at compile so the migration path is explicit. `'none'` (today's behaviour, 0 cost, replay bound by TTL) stays the default.
261
+
262
+ See [the docs page](/compiler/config/auth) for the full knob list and tuning recommendations.
263
+
264
+ ### MCP admin endpoints hidden from non-admin `tools/list`
265
+
266
+ Better Auth admin endpoints (`/admin/list-users`, `/admin/ban-user`, `/admin/impersonate-user`, etc. — 9 in total) now carry `x-access: { userRole: ['admin'] }` in the generated OpenAPI spec, which means the MCP server's existing access-filter automatically drops them from `tools/list` for callers without an admin token. Anonymous and member-role callers no longer see admin tooling enumerated through MCP; admin endpoints still exist on the HTTP surface (Better Auth gates them server-side regardless).
267
+
268
+ ### Declarative `security` config block
269
+
270
+ Every security response-header (`Content-Security-Policy`, `Cross-Origin-Opener-Policy`, `Cross-Origin-Embedder-Policy`, `Cross-Origin-Resource-Policy`, `X-Frame-Options`, `Strict-Transport-Security`, `Referrer-Policy`, `Permissions-Policy`) is now configurable from `quickback.config.ts`. Loop's `postcompile-patch.mjs` (which re-injected a fuller CSP and COOP after every `quickback compile`) can now be deleted in favour of:
271
+
272
+ ```ts
273
+ security: {
274
+ csp: {
275
+ defaultSrc: ['@self'],
276
+ scriptSrc: ['@self'],
277
+ styleSrc: ['@self', '@unsafe-inline'],
278
+ frameAncestors: ['@none'],
279
+ objectSrc: ['@none'],
280
+ upgradeInsecureRequests: true,
281
+ },
282
+ coop: 'same-origin',
283
+ }
284
+ ```
285
+
286
+ `@`-prefixed sentinels (`@self`, `@none`, `@unsafe-inline`, `@unsafe-eval`, `@trustedOrigins`, `@nonce`) save users from awkward `"'self'"` quoting and let `@trustedOrigins` resolve to the same allowlist `cors()` uses. Unknown sentinels throw at compile rather than silently stringify into the wire CSP.
287
+
288
+ The compiler runs lint rules over the resolved config — errors for `@nonce` (deferred to 0.10.15), `@unsafe-inline + @nonce` (silently broken), and sentinel-only directives that would resolve to nothing at runtime; warnings for `@unsafe-inline` in `script-src`, wildcard sources, missing `default-src`, HSTS preload-list misconfiguration, etc.
289
+
290
+ Defaults preserve 0.10.13 behaviour byte-for-byte — adding the block without setting any field is a no-op.
291
+
292
+ See [the docs page](/compiler/config/security) for the full reference.
293
+
294
+ ### HSTS no longer pins `localhost` to HTTPS
295
+
296
+ The generated middleware now skips `Strict-Transport-Security` when the request hostname is `localhost`, `127.0.0.1`, or `*.localhost`. Without this gate, `wrangler dev` would pin the developer's browser to HTTPS for `max-age` seconds — observable across every project on that machine since HSTS keys on hostname, not port. Affects every project running locally.
297
+
298
+ ### Out of scope (deferred)
299
+
300
+ - **Per-request CSP nonces** — Phase 2 / 0.10.15. Sentinel exists at config-validation level so users can author their final CSP today knowing it'll start working when nonces ship.
301
+ - **Asset-hash CSP** for inline `<style>` and `<script>` blocks emitted by the bundled SPAs — Phase 3.
302
+ - **Per-route CSP overrides** (e.g. one looser policy for `/admin`) — single global CSP for now.
303
+
304
+ ---
305
+
306
+ ## v0.10.13 — May 1, 2026
307
+
308
+ ### Clickjacking protection on every generated Worker
309
+
310
+ Every Worker now emits two clickjacking-defence headers on every
311
+ response:
312
+
313
+ - `Content-Security-Policy: frame-ancestors 'self' <TRUSTED_ORIGINS…>`
314
+ - `X-Frame-Options: SAMEORIGIN`
315
+
316
+ The CSP allowlist is sourced from the same `TRUSTED_ORIGINS` constant
317
+ that gates CORS, so users configure their domains in one place
318
+ (`auth.trustedOrigins` / `auth.trustedOriginDefaults` in
319
+ `quickback.config.ts`) and both CORS and frame-ancestors stay in
320
+ lockstep. `'self'` is always allowed so an app's own SPAs can frame
321
+ their own routes (e.g. an account login popover hosted on the same
322
+ origin).
323
+
324
+ Modern browsers obey `frame-ancestors` and ignore `X-Frame-Options`
325
+ when both are set; the legacy header is included for clients that
326
+ don't speak CSP3. The CSP intentionally only sets `frame-ancestors` —
327
+ adding `script-src` / `default-src` would need a much wider audit
328
+ across SPA assets, inline scripts, and third-party embeds, so that's
329
+ left as a follow-up.
330
+
331
+ Recompile (`quickback compile`) and redeploy to pick this up — no
332
+ config change needed unless you want to allow extra cross-origin
333
+ iframe embeds, in which case add them to `auth.trustedOrigins`.
334
+
335
+ ---
336
+
337
+ ## v0.10.12 — May 1, 2026
338
+
339
+ ### Bundled-docs sync for the MCP recon fix
340
+
341
+ Patch release that re-bundles the CLI's offline docs (consulted by the
342
+ Claude Code skill, Cursor rules, and other AI assistants) so they
343
+ reflect the corrected `tools/list` access-filter behavior and CORS
344
+ posture shipped in v0.10.11. The `compiler/config/agents.mdx` page
345
+ itself was already corrected on the docs site immediately after the
346
+ 0.10.11 release; this bump propagates that text into the bundle inside
347
+ `@quickback-dev/cli`.
348
+
349
+ No runtime or compiler behavior change — re-running `quickback compile`
350
+ against this version produces the same output as v0.10.11.
351
+
352
+ ---
353
+
354
+ ## v0.10.11 — May 1, 2026
355
+
356
+ ### MCP `tools/list` is now access-filtered + recon-tightened
357
+
358
+ The generated MCP-over-HTTP server (`src/routes/mcp.ts`) had three holes
359
+ that turned a standard pentest into trivial recon:
360
+
361
+ 1. `tools/list` returned the entire tool catalogue to anyone — including
362
+ admin-only endpoints — without checking auth or roles. Tool
363
+ descriptions also leaked sentences like `[UNSAFE] bypasses tenant
364
+ scoping and requires elevated access` verbatim.
365
+ 2. The endpoint set `Access-Control-Allow-Origin: *` so any origin could
366
+ pull the catalogue from a browser.
367
+ 3. Unauthenticated `GET /mcp` enumerated every tool name in its
368
+ discovery payload.
369
+
370
+ Fix:
371
+
372
+ - Each tool now carries sanitised access metadata (`_access` covering
373
+ `roles` / `userRole` / `or` / `and`, plus `_public` for `PUBLIC`
374
+ pseudo-role or empty `security`). `tools/list` filters against the
375
+ caller's `ctx` — unauth callers see only `_public` tools, authed
376
+ callers see only role-gated tools they pass. Record predicates and
377
+ function-form access (opaque at list time) are dropped.
378
+ - Wildcard CORS removed entirely. The parent app's `cors()` middleware
379
+ (origin allowlist via `TRUSTED_ORIGINS` + `BETTER_AUTH_URL`) now
380
+ applies uniformly to `/mcp`, same as every other route.
381
+ - `[UNSAFE] ... bypasses tenant scoping ...` flavour text is gone.
382
+ `annotations.destructiveHint` and `_unsafe` remain — those are the
383
+ spec-correct signals for clients to warn users.
384
+ - Unauthenticated `GET /mcp` no longer lists tool names. Inventory is
385
+ only available via the access-filtered `tools/list`.
386
+
387
+ This filter is recon-mitigation, not a security boundary: `tools/call`
388
+ still re-enters the Hono app and runs every middleware (auth, firewall,
389
+ access, guards, masking), so hiding a tool from list never weakens the
390
+ underlying gate.
391
+
392
+ Known follow-up: Better Auth admin endpoints (`ban-user`, `create-user`,
393
+ `impersonate-user`, etc.) don't yet emit `x-access` in the OpenAPI spec,
394
+ so any logged-in user still sees them in `tools/list` (the actual call
395
+ is still gated by the admin plugin). Tracked separately.
396
+
397
+ ---
398
+
399
+ ## v0.10.10 — April 29, 2026
400
+
401
+ ### Reject reserved keys inside `access.record` at compile time
402
+
403
+ `access.record` is a flat field map evaluated as implicit AND between
404
+ entries — keys must be column names. Putting `and: [...]` (or `or` /
405
+ `roles` / `userRole`) inside `record` was a real-world footgun: the
406
+ runtime treated the literal string `"and"` as a column lookup, the
407
+ predicate failed on every row, and the caller got a silent `403` /
408
+ empty list with nothing pointing at the misuse. The TypeScript type
409
+ couldn't catch this — `RecordConditions` is an open-ended index
410
+ signature, so any key parses.
411
+
412
+ The compiler now walks every access node attached to a resource (CRUD
413
+ ops, `read.access`, view access, masking `show` / `query`, action
414
+ access) and throws a clear migration error when `record` contains a
415
+ reserved key:
416
+
417
+ - `and` / `or` inside `record` → use the top-level `and` / `or`
418
+ sibling: `{ and: [{ record: { ... } }, { record: { ... } }] }`
419
+ - `roles` / `userRole` inside `record` → put them at the access node
420
+ alongside `record`: `{ roles: [...], record: { ... } }`
421
+
422
+ The error names the exact origin (`crud.update.access`,
423
+ `actions.focus.access.or[1]`, etc.) so the fix lands in the right place.
424
+
425
+ ---
426
+
427
+ ## v0.10.9 — April 29, 2026
428
+
429
+ ### Role hierarchy now expands in record-based action access
430
+
431
+ `auth.roleHierarchy: ['member', 'admin', 'owner']` plus
432
+ `access: { roles: ['member+'] }` on a record-based action used to
433
+ silently 403 valid callers. The standalone-action route generator
434
+ inlined the expanded role list as a JSON literal, but the
435
+ record-based generator read the access config back through the
436
+ runtime `actions['name'].access` import — the user's source, where
437
+ the unexpanded `'member+'` shorthand still lived. The runtime did
438
+ literal string matching against `ctx.roles`, so an `owner` calling
439
+ the action got `['member+'] !== 'owner'` and was rejected.
440
+
441
+ Fixed: record-based action routes now inline the expanded list the
442
+ same way standalone routes do. `input` and `execute` still flow
443
+ through the runtime import (closures aren't serializable); only the
444
+ access config is lifted to a JSON literal so the compile-time
445
+ expansion actually reaches the matcher.
446
+
447
+ A regression test (`role-hierarchy-action-routes.test.ts`) locks the
448
+ behavior in — it asserts that `member+` never reaches the route
449
+ output and that the access config is no longer read from
450
+ `actions[name].access` at runtime.
451
+
452
+ ---
453
+
454
+ ## v0.10.8 — April 29, 2026
455
+
456
+ ### Audit support on postgres targets, plus a generated-API quality pass
457
+
458
+ **Audit on PG.** Until this release, `audit_events` only existed on cloudflare-d1 — projects on Neon (or any postgres target) silently skipped audit logging on `unsafe:` and `PUBLIC`-role actions, and hard delete was hard-blocked. Postgres has no equivalent of D1's separate-database binding model, but it has native schemas — so the audit table now lives in a dedicated `audit` schema in the same database as features (`drizzle.pgSchema('audit')`). The `hasSecurityAudit` gate accepts D1 OR any PG dialect; the `auditDatabaseId` requirement only fires for D1 (which still uses the separate-binding model). The recruitment example wires `auditDatabaseId` so the recompile path stays green.
459
+
460
+ **`auditDatabaseId` is now a compile-time requirement** (D1 only). Previously, projects with unsafe/PUBLIC actions but no audit id silently produced a `database_id = "local-audit"` placeholder in production `wrangler.toml`; Cloudflare's worker upload step then rejected it with code 10021 *after* assets and migrations had already run. The compile-time error names the exact `wrangler d1 create <project>-audit` command and the `auditDatabaseId` config key where the returned id goes.
461
+
462
+ ### Five fixes from a Loop integration ticket pass
463
+
464
+ **Action input → OpenAPI / MCP.** `defineAction({ input: z.object({...}) })` schemas now flow into `requestBody` on the OpenAPI operation and `inputSchema.properties` / `_bodyFields` on the MCP tool list. Simple `z.object` shapes are extracted at compile time; for discriminated unions, refinements, recursive schemas, and bare-identifier references (`input: createPersonInput`), the compiler runs your action file through Zod 4's native `z.toJSONSchema()` during compilation — full-fidelity output with no static translator to maintain. Pre-fix, every action came out as a no-arg endpoint, which gutted typed SDK generation and made MCP useless for actions that take parameters.
465
+
466
+ **OpenAPI fidelity.** Three surgical fixes that strict validators (zod, openapi-typescript, openapi-fetch) had been complaining about:
467
+ - Response schemas now emit `required[]` for every non-nullable column, so generated SDKs treat them as guaranteed-present rather than optional.
468
+ - `text(_, { enum: [...] })` columns emit as closed `{ type: "string", enum: [...] }`, narrowing to literal unions.
469
+ - `id` only claims `format: "uuid"` when the project's `generateId` actually produces UUIDs. cuid2 / prefixed / nanoid / serial generators get plain `{ type: "string" }` — strict validators stop rejecting responses against their own spec.
470
+
471
+ **Mask auto-detector now checks the column exists.** The auto-mask predicate used to be unconditionally `show: { or: 'owner', roles: ['admin'] }` — including for tables with no owner column at all (no `userId` / `ownerId` and no `q.scope('owner')`). The generated mask function would reference a non-existent column and fail under TypeScript checks. The auto-detector now verifies the resolved owner column exists in the parsed schema before emitting the `or` clause; when it doesn't, the rule falls back to roles-only and the compiler emits a warning so the behavior is transparent.
472
+
473
+ **Error code consistency.** The generated CRUD layer was emitting raw codes (`'UNAUTHORIZED'`, `'NOT_NULL_VIOLATION'`, `'UNIQUE_VIOLATION'`, `'INSERT_FAILED'`, `'UPDATE_FAILED'`) that were never in the `QuickbackErrorCode` enum, so consumers couldn't switch exhaustively on `code`. New `database` layer + `DB_NOT_NULL_VIOLATION` / `DB_UNIQUE_VIOLATION` / `DB_INSERT_FAILED` / `DB_UPDATE_FAILED` / `NOT_FOUND` codes are now in the enum, the routes use `AuthErrors.missing()` / `DatabaseErrors.*()` helpers throughout, and the OpenAPI `Error` component emits `code` as a closed enum sourced from the canonical `QUICKBACK_ERROR_CODES` list. Generated SDKs can now `switch` on `code` without a default branch swallowing unknown values. See [API errors](/compiler/targets/hono-api/using-the-api/errors#database).
474
+
475
+ **Dropped dead `auditFields` preamble from action route generators.** The audit wrapper's `Proxy` already hard-stamps `createdAt` / `createdBy` / `modifiedAt` / `modifiedBy` on every INSERT and `modifiedAt` / `modifiedBy` on every UPDATE — the `auditFields` const the route preamble built was never read. Dropped from `standalone.ts` / `record-based.ts` and from the `ActionExecutorParams` JSDoc. Migrated 7 example handlers (drop `modifiedAt: auditFields!.modifiedAt` from `.set` payloads — the wrapper handles it). Note: `.onConflictDoUpdate({ set })` is *not* intercepted by the wrapper, so `upsertBatch`-style handlers keep an explicit `modifiedAt: now`.
476
+
477
+ ---
478
+
479
+ ## One file per action: greenfield action authoring
480
+
481
+ Action authoring collapses to a single shape. Each action is its own file under `<feature>/actions/<name>.ts` using `defineAction({...})`. The filename is the action name AND the URL segment.
482
+
483
+ ```typescript
484
+ // features/applications/actions/advance.ts
485
+ import { z } from "zod";
486
+ import { defineAction } from "../.quickback/define-action";
487
+ import { applications } from "../applications";
488
+
489
+ export default defineAction({
490
+ description: "Move an application forward in the pipeline",
491
+ input: z.object({ nextStatus: z.enum(["screening", "interview", "offer"]) }),
492
+ access: { roles: ["owner", "admin"] },
493
+ transition: {
494
+ field: "status",
495
+ via: "nextStatus",
496
+ fromTo: { applied: ["screening"], screening: ["interview"], interview: ["offer"] },
497
+ },
498
+ async execute({ db, record, input, auditFields, whereTransition }) { /* … */ },
499
+ });
500
+ ```
501
+
502
+ `defineAction` is imported from a generated per-feature helper at `<feature>/.quickback/define-action.ts` — types `record`, `input`, and audit fields without manual annotations. The directory says what `:id` mounts to; the imports say what the body reads or writes.
503
+
504
+ **Discovery rules:**
505
+ - `actions/<name>.ts` binds to the feature's primary table (the `<feature>.ts` file at the feature root).
506
+ - `actions/<table>/<name>.ts` binds to the sibling table file `<table>.ts` — for multi-table features.
507
+ - Setting `path:` makes the action standalone (custom URL, no record fetch, no firewall preload).
508
+ - Tableless features (no top-level `*.ts` files) require every action to be standalone.
509
+ - Action names are unique per `(bindTable, name)` pair — sibling-bound actions on different tables may share a verb (e.g. `actions/episodes/publish.ts` + `actions/shows/publish.ts` mount at `/episodes/:id/publish` and `/shows/:id/publish` and don't collide). Standalone actions are unique per `(method, path)`.
510
+ - Files under `<feature>/lib/` are copied verbatim for feature-local helpers; `quickback/lib/` is exposed via the `~/lib/*` alias for cross-feature shared code (with a one-way import rule enforced at compile time).
511
+
512
+ **Retired** (rejected at load time with migration guidance):
513
+
514
+ - `actions.ts` (bundled multi-action file)
515
+ - `_feature.ts` (shared preamble + tableless actions)
516
+ - `handlers/` directory + `handler:` string ref
517
+ - `defineActions(table, {…})` and `defineActions(null, {…})`
518
+ - `export default { actions: {…} }`
519
+ - Colocated `defineActions` inside table files
520
+ - `standalone: true` flag (presence of `path:` is the new signal)
521
+ - `*-actions.ts` / `*.actions.ts` filename patterns
522
+
523
+ The phantom-`unsafe` regex bug that flattened nested `unsafe: { … }` blocks into a fake top-level action is gone — the parser now reads action files as real TS modules with real imports, so type inference, jump-to-definition, and rename refactoring all work end-to-end.
524
+
525
+ The CLI loader rejects retired primitives at load time with batched migration errors. Existing projects need to be migrated by hand to the new shape before recompiling.
526
+
527
+ See the [Actions docs](/compiler/definitions/actions) for the full reference.
528
+
529
+ ---
530
+
531
+ ## Multi-table actions per feature
532
+
533
+ Features used to support exactly one `defineActions(table, …)` call via `actions.ts`, which forced unnatural feature splits whenever multiple tables in the same feature needed actions (a podcast feature with `episodes`, `shows`, `seasons`, `collections`, etc.). One feature directory can now own actions on multiple tables across three discovery modes:
534
+
535
+ - **Colocated** (canonical) — `<table>.ts` containing both `defineTable` and `defineActions(<table>, …)`. One file per entity. Default for new features.
536
+ - **`actions.ts`** (existing) — single primary-table actions file at feature root. Unchanged behaviour.
537
+ - **`actions/<table>.ts`** — per-table action files for teams that want strict schema/behavior separation or need to break an import cycle.
538
+
539
+ Plus the universal `_feature.ts` slot (at feature root) for **non-table-bound feature-level actions** (`export default { actions: { … } }` shape) and **shared Zod schemas** that get prepended once to the merged actions module so every sibling action sees them. Allowed in any of the three modes — orthogonal to table binding.
540
+
541
+ The decision flowchart: *one table with actions → colocate. Multiple tables with actions → colocate each. Hit a cycle or want strict separation → `actions/<table>.ts`. Want schema/actions split for a single-table feature → `actions.ts`. Non-table actions → always `_feature.ts`.*
542
+
543
+ Conflicts are batched and printed once before the compiler aborts — no "fix one, recompile, fix the next" loop. The CLI hard-errors when a feature mixes `actions.ts` with table-bound mode, when the same table has its `defineActions` declared in two places, when an `actions/<x>.ts` first-arg doesn't match the basename, or when `_feature.ts` contains `defineActions(table, …)`. Legacy `*-actions.ts` / `*.actions.ts` filenames in a feature dir trigger a soft warning naming the offending paths.
544
+
545
+ Within the legacy bundled `actions.ts` DSL, action names had to be unique within a feature — the runtime module merged every source into one keyspace, so colliding `publish` actions on `episodes` and `shows` would have silently overwritten each other. The retired `actions.ts` shape is no longer accepted, so this constraint is gone: the current one-file-per-action layout keys uniqueness per `(bindTable, name)` pair, and the codegen aggregator mangles the JS map key per bind-table while keeping the URL segment bare. Sibling-bound `actions/episodes/publish.ts` and `actions/shows/publish.ts` mount at `/episodes/:id/publish` and `/shows/:id/publish` and compile cleanly.
546
+
547
+ Inline `execute:` bodies must be arrow functions (`execute: async (ctx) => { … }`). `async function` and plain `function` shapes were silently misparsed by the route emitter — they now hard-error at parse time pointing at the canonical arrow form, with a suggestion to use `handler:` for callers who genuinely need a named function declaration.
548
+
549
+ `handlers/` walks recursively now — `handlers/<table>/<action>.ts` is the canonical layout. A new `lib/` directory under each feature gets copied verbatim into the output for feature-local helpers.
550
+
551
+ Migration: existing `actions.ts` projects compile bit-identically — the legacy single-table path is unchanged. Legacy `*-actions.ts` filenames produce a soft warning and silently aren't picked up; rename to `<table>.ts` (colocated), `actions/<table>.ts`, or single `actions.ts`.
552
+
553
+ ---
554
+
555
+ ## Firewall: named-scope shape restored, auto-detection synonyms widened
556
+
557
+ The named-scope firewall shape (`firewall: { organization: { column: 'tenant_id' } }`) is back as a co-equal user-facing input alongside the predicate array. DSL v2 step 8 had walled it off, but the internal architecture still kept named-scope around for the route + scoped-db generators — so re-accepting it at the input boundary is a thin coercion layer, not an architectural change.
558
+
559
+ ```typescript
560
+ // All three are now valid; all compile to the same predicate array internally.
561
+ firewall: { organization: { column: 'tenant_id' } } // named-scope (compact)
562
+ firewall: { owner: { column: 'account_user_id' } }
563
+ firewall: { exception: true }
564
+ firewall: [
565
+ { field: 'organizationId', equals: 'ctx.activeOrgId' },
566
+ { field: 'deletedAt', isNull: true },
567
+ ] // predicate array (explicit)
568
+ ```
569
+
570
+ Pick the form that reads better — named-scope for the common one-line case, predicate array when you need custom `in`-lists or non-scope predicates.
571
+
572
+ **Auto-detection synonyms expanded.** When `firewall:` is omitted entirely, the compiler scans the schema for an isolation column. The org-scope list now accepts `organizationId`, `organisationId`, `orgId`, `organization`, `organisation`, `org` (American + British). User-scope still accepts `userId` only.
573
+
574
+ **`ownerId` is now a targeted error signal.** When a table carries `ownerId` but no isolation column AND no explicit `firewall:`, the compiler raises a specific error: `\`ownerId\` is business-logic ownership, not access control — Quickback won't auto-derive a firewall from it. Either rename to \`userId\` if this column controls access, add a separate \`userId\` / \`organizationId\` column, or specify \`firewall:\` explicitly.` This replaces the generic "missing isolation column" error in the `ownerId`-only case and preserves the documented distinction between RLS-style access control (`userId`) and business-logic ownership (`ownerId`).
575
+
576
+ Migration: nothing breaks. Projects on the predicate-array shape compile bit-identically. Projects on the named-scope shape — including any test fixtures or example projects that were left on the legacy form — now compile cleanly again.
577
+
578
+ ---
579
+
580
+ ## v0.10.0 — April 26, 2026
581
+
582
+ ### `q.scope()` column DSL + unified `masking.query` gate
583
+
584
+ Two related DSL consolidations land. The `q.scope()` half is purely additive; the `masking.query` half rejects three legacy per-capability flags at compile time (migration is mechanical — see below).
585
+
586
+ **`q.scope(kind)` — single-declaration tenant scoping.** Replaces the three-place pattern (column declaration + firewall predicate + implicit ownership-guard) with one column. `q.scope('organization')` compiles to `text(...).notNull()` and tells the compiler:
587
+
588
+ 1. Auto-derive the firewall predicate (`{ field: 'organizationId', equals: 'ctx.activeOrgId' }`) so the explicit `firewall:` block can be omitted entirely.
589
+ 2. Add the column to `GUARDS_CONFIG.systemManaged` so client input is rejected at the guard layer.
590
+ 3. Auto-populate from `ctx` on create / upsert.
591
+
592
+ The systemManaged extension generalises beyond `q.scope()`: any firewall predicate whose `equals` references `ctx.*` adds its `field` to the systemManaged set. So a hand-rolled `firewall: [{ field: 'tenantId', equals: 'ctx.activeOrgId' }]` gets the same treatment.
593
+
594
+ ```typescript
595
+ columns: {
596
+ organizationId: q.scope('organization'), // → ctx.activeOrgId
597
+ ownerId: q.scope('owner'), // → ctx.userId
598
+ teamId: q.scope('team'), // → ctx.activeTeamId
599
+ }
600
+ ```
601
+
602
+ The auto-derived firewall also includes the soft-delete predicate (`{ field: 'deletedAt', isNull: true }`) when audit-field injection is on (the default). See [`q.scope()` in the schema docs](/compiler/definitions/schema#qscope--tenant-scope-columns).
603
+
604
+ **`masking[col].query.roles` — unified role gate for filter / sort / search.** The three legacy per-capability flags (`filterable`, `searchable`, `sortable`) are replaced by a single allowlist that says "these roles can query the column."
605
+
606
+ ```typescript
607
+ masking: {
608
+ email: {
609
+ type: 'email',
610
+ show: { roles: ['admin'] },
611
+ query: { roles: ['admin'] }, // optional — defaults to show.roles
612
+ },
613
+ }
614
+ ```
615
+
616
+ When omitted, `query` inherits from `show.roles` ("if you can see it, you can query it") which is the right shape for almost all PII. A view's own `query.{filterable,searchable,sortable}` allowlist is the opt-in for higher-privileged roles; the existing intersection validator gates it at compile time. See [Masking query gate](/compiler/definitions/masking#query-gate-filter--sort--search).
617
+
618
+ **Breaking:** Setting `masking[col].filterable / .searchable / .sortable` is rejected at compile time with a migration hint. Replace with `query.roles` (or just delete the flags — `query` defaults to `show.roles`).
619
+
620
+ ---
621
+
622
+ ## v0.9.0 — April 25, 2026
623
+
624
+ ### DSL v2: unified `read:` pipeline, transactional batches, ID-probe defense
625
+
626
+ Step 8 of the DSL v2 refactor lands. The headline shift is that the read
627
+ side of every resource now has its own block — `read:` — that owns the
628
+ collection-level `GET /` endpoint, single-record `GET /:id`, and named view
629
+ projections. The legacy `crud.list` and `crud.get` shapes are rejected at
630
+ compile time. See the new [Read pipeline](/compiler/definitions/read) page
631
+ for the full reference and migration table.
632
+
633
+ **Breaking changes** (compile-time errors with migration hints):
634
+
635
+ - `crud.list` → [`read.access`](/compiler/definitions/read) (plus `read.pageSize` / `read.maxPageSize`)
636
+ - `crud.get` → `read.access` (single-record GET inherits automatically; use record-level conditions on `read.access` for differentiated single-record gates)
637
+ - Top-level `views: {...}` → [`read.views: {...}`](/compiler/definitions/read#views-under-read-views)
638
+ - `crud.list.fields` / `crud.get.fields` → declare a named view under `read.views` and call `?view={name}` (or `/views/{name}`)
639
+
640
+ **Pre-record access ordering on `/:id`**: handlers now run a role-only
641
+ access check **before** the firewall query, so a caller without a matching
642
+ role gets 403 before the database is touched. This closes the 404-vs-403
643
+ ID-probe channel — an unauthorized caller can no longer distinguish "row
644
+ exists in another tenant" from "row doesn't exist." See
645
+ [Access evaluation order](/compiler/definitions/access#evaluation-order).
646
+
647
+ **Transactional batch operations**: batch endpoints now expose a
648
+ `failFast` option (replacing the old `atomic` naming) and a
649
+ `meta.transactional` response field. On tx-supporting providers
650
+ (postgres, supabase, neon, libsql, better-sqlite3, bun-sqlite), `failFast: true`
651
+ wraps the per-record loop in `db.transaction(...)` so any failure rolls
652
+ back the entire batch. On Cloudflare D1 (no `db.transaction`), `failFast: true`
653
+ still stops on the first error but prior writes stay committed; inspect
654
+ `meta.transactional` to know which guarantee you got. Embedding queue
655
+ messages and realtime broadcasts are emitted **after** the transaction
656
+ commits, so a rolled-back batch produces no orphan jobs. See
657
+ [Batch Operations: Transactional semantics](/compiler/targets/hono-api/using-the-api/batch-operations#transactional-semantics).
658
+
659
+ **`firewallErrorMode` lifted off the firewall block**: the field that
660
+ controls 403-vs-404 on firewall misses now lives at the resource top level
661
+ (sibling to `firewall:`), since the firewall config is now a predicate
662
+ array and this is a presentation-layer choice. Existing `firewall.errorMode`
663
+ values should be lifted to `firewallErrorMode` at the resource level.
664
+
665
+ **Read-only resources**: an empty `crud: {}` block (or omitting `crud:`
666
+ entirely) is valid for read-only resources. `read:` alone is enough to
667
+ expose `GET /` and `GET /:id`.
668
+
669
+ **Strict-mode top-level keys**: the strict allow-list now includes `dev` so
670
+ `defineConfig({ dev: { ... } })` is accepted at the top level.
671
+
672
+ ---
673
+
674
+ ## v0.8.7 — April 17, 2026
675
+
676
+ ### Security: Hono CVE cluster fix
677
+
678
+ Hono is bumped to `^4.12.14` across the monorepo, the compiler Docker image's pre-installed deps, and every generator path that emits Hono into compiled projects. Older ranges (`^4.0.0` / `^4.5.0` / `^4.6.0` / `^4.7.11`) covered the vulnerable window. Recompile to pick up the fix in your generated project's `package.json`.
679
+
680
+ ### Cloudflare Email Sending is now in public beta
681
+
682
+ Quickback already defaults to the Workers `send_email` binding for Cloudflare deploys, and Cloudflare Email Sending has now graduated to public beta — production-ready with zero-config, no API keys, no third-party accounts. No action needed; recompiling any existing project continues to wire the default Cloudflare transport. AWS SES remains a fully supported opt-in (`email.provider: 'aws-ses'`) for non-Cloudflare runtimes or existing SES setups. See [Email Configuration](/compiler/config#email-configuration).
683
+
684
+ ### Minor/patch dep sweep
685
+
686
+ Aligned the whole dep surface — monorepo, compiler Docker image, and generator emissions into compiled projects — so new compiles and existing recompiles converge on the same versions:
687
+
688
+ - `wrangler@^4.83.0`
689
+ - `drizzle-orm@^0.45.2`, `drizzle-kit@^0.31.10`
690
+ - `zod@^4.3.6`
691
+ - `@cloudflare/workers-types@^4.20260417.1` (also deduped — was accidentally declared in both `dependencies` and `devDependencies` in some paths)
692
+ - `@tanstack/react-query@^5.99.0` (Account app)
693
+
694
+ ---
695
+
696
+ ## v0.8.5 — April 15, 2026
697
+
698
+ ### Fix: Better Auth 1.5 and `@cloudflare/workers-types` Compatibility
699
+
700
+ Generated API code failed to typecheck after Better Auth bumped to 1.5 and `@cloudflare/workers-types` tightened `BufferSource` to `ArrayBufferView<ArrayBuffer>`. Four unrelated surfaces broke:
701
+
702
+ - **`databaseHooks.member.update.after` was removed** in Better Auth 1.5. The compiler now emits the member role-change broadcast hook as `organizationHooks.afterUpdateMemberRole` inside the `organization()` plugin call, which is the current supported shape.
703
+ - **`REALTIME_URL` and `ACCESS_TOKEN`** are always emitted as optional `CloudflareBindings` fields when the organization plugin is active, so the broadcast hook typechecks even when `realtimeMode` is `"inline"` (or realtime isn't configured at all).
704
+ - **`auth.api.listOrganizations` / `getFullOrganization` / `session.session.activeOrganizationId`** — third-party Better Auth plugins narrow the inferred `auth.api` type and hide organization-plugin endpoints. The generated middleware and `/admin/v1/organizations` route now cast through `any` for these calls.
705
+ - **`crypto.subtle.sign` / `verify`** no longer accept `Uint8Array<ArrayBufferLike>` directly. Generated `jwt.ts` casts encoded payloads to `BufferSource`.
706
+
707
+ No config changes required — recompile to pick up the fixes.
708
+
709
+ ### CMS Admin Gate Now Enforced Server-Side
710
+
711
+ `cms: { access: "admin" }` previously only hid the CMS link in Account UI and rendered an "Access Denied" screen inside the SPA — the static assets, `/api/v1/schema`, and `/api/v1/custom_view` CRUD were reachable by any authenticated user. A non-admin with an API token or cookie could bypass the UI and read schema metadata or saved CMS views directly.
712
+
713
+ This release adds server-side enforcement at every CMS-facing surface:
714
+
715
+ - **CMS SPA shell** — the Worker checks `ctx.userRole === "admin"` before serving `index.html`. Unauthenticated requests redirect to login; authenticated non-admins get `403 Admin access required`. Static bundles (JS/CSS) remain reachable so browser caches aren't invalidated.
716
+ - **`/api/v1/schema`** — returns `403` to non-admins.
717
+ - **`custom_view` CRUD** — now gated on the new `userRole: ["admin"]` primitive rather than org membership.
718
+ - **In-SPA gate** — unchanged; defense in depth behind the server-side gates.
719
+
720
+ Your resource CRUD endpoints are unaffected — they keep their per-resource `crud.access.roles`.
721
+
722
+ ### New `userRole` Access Primitive
723
+
724
+ Added `userRole?: string[]` to the declarative `Access` config, evaluated against `ctx.userRole` (the Better Auth admin-plugin `user.role` column). This is distinct from `roles`, which matches `ctx.roles` (org membership).
725
+
726
+ ```typescript
727
+ // Old: in multi-tenant this meant org-admin, not platform-admin
728
+ access: { roles: ['admin'] }
729
+
730
+ // New: explicitly require user.role === 'admin' regardless of org membership
731
+ access: { userRole: ['admin'] }
732
+
733
+ // "Org owner OR platform admin"
734
+ access: { or: [{ roles: ['owner'] }, { userRole: ['admin'] }] }
735
+
736
+ // Platform admins see SSNs across every org
737
+ masking: { ssn: { type: 'ssn', show: { userRole: ['admin'] } } }
738
+ ```
739
+
740
+ `userRole` works everywhere `Access` is accepted — CRUD, actions, views, masking, and inside `or`/`and` combinators. See [Access - userRole vs roles](/compiler/definitions/access#userrole-vs-roles).
741
+
742
+ ### Fix: `ReferenceError: customAlphabet is not defined` in generated POST handlers
743
+
744
+ Projects with `providers.database.config.generateId: "short"` (or `"nanoid"` / `"cuid"`) compiled routes that called the ID helper but never imported it. Every generated `src/features/**/*.routes.ts` had `customAlphabet('0123...', 6)()` in its POST body but no matching `import { customAlphabet } from 'nanoid';` at the top of the file. Every `POST /api/v1/<resource>` and batch-create returned `500` with `ReferenceError: customAlphabet is not defined` on the first write.
745
+
746
+ The compiler now emits the correct import alongside the ID expression for all three modes: `nanoid`, `customAlphabet`, and `createId` from `@paralleldrive/cuid2`.
747
+
748
+ No config changes required — recompile to pick up the fix.
749
+
750
+ ### Fix: Dangling `export const` in generated `actions.ts` breaks `tsc`
751
+
752
+ When a feature authored actions as `export const xActions = defineActions(...)` (instead of `export default defineActions(...)`), the compiler's preamble extractor leaked the assignment's left-hand side into the generated `src/features/<feature>/actions.ts`. The output contained a dangling `export const xActions =` with no right-hand side, and `tsc --noEmit` failed with `TS1109: Expression expected`. Runtime happened to work because the unused placeholder was never evaluated, but typecheck was red.
753
+
754
+ The preamble extractor now anchors its boundary to the start of the top-level statement containing `defineActions(...)`, covering `export default`, `export const X =`, `const X =`, and bare call forms. Local Zod helper declarations above the call continue to be preserved.
755
+
756
+ ### Fix: Files worker `database_id` reverted to `"local-files"` on every compile
757
+
758
+ Projects using the two-worker R2 architecture had their files worker's `wrangler.toml` (`apps/backend/cloudflare-workers/files/wrangler.toml`) rewritten with `database_id = "local-files"` on every `quickback compile`, even when `providers.database.config.filesDatabaseId` was set to a real D1 UUID. The main worker's binding was correct — only the files worker fell through. Remote deploys of the files worker bound to a non-existent D1, so file serving and access-control reads failed with a binding error.
759
+
760
+ The files-worker wrangler generator now reads `filesDatabaseId` (and `filesDatabaseName`) from `providers.database.config` as a fallback when they aren't set on `providers.fileStorage.config`, matching the precedence chain already used by the main worker. Local dev is unaffected — `wrangler dev --local` uses `.wrangler/state/` regardless of the configured ID.
761
+
762
+ No config changes required — recompile and redeploy the files worker.
763
+
764
+ ---
765
+
766
+ ## v0.8.6 — April 16, 2026
767
+
768
+ ### Fix: Audit columns silently dropped from tables with a same-line index callback
769
+
770
+ Tables authored with the composite-index shape Drizzle / prettier produces —
771
+
772
+ ```ts
773
+ export const episodeTags = sqliteTable("episode_tags", {
774
+ id: text("id").primaryKey(),
775
+ episodeId: text("episode_id").notNull(),
776
+ tagId: text("tag_id").notNull(),
777
+ }, (t) => [ // <-- "}, (t) =>" on one line
778
+ uniqueIndex("episode_tag_unique").on(t.episodeId, t.tagId),
779
+ ]);
780
+ ```
781
+
782
+ never received audit field injection. A regex in `injectAuditFields` required a literal `\n` between the columns-object `},` and the `(t) =>` index callback, so same-line closers were silently skipped and the function returned the source unchanged. drizzle-kit then diffed the audit-less schema against the previous snapshot and emitted `ALTER TABLE ... DROP COLUMN created_at/modified_at/deleted_at/created_by/modified_by/deleted_by` for every affected table. Any project that applied those migrations had production CRUD return `500` because the generated firewall helper still referenced `deletedAt`.
783
+
784
+ The regex is now whitespace-flexible and the identifier class accepts any valid JS identifier (`t`, `table`, `_t`, `tbl2`). A defensive guard throws at compile time if all three terminator patterns fail on a recognizable Drizzle table — no more silent drops.
785
+
786
+ **Recovery path:**
787
+
788
+ - Most projects: recompile. drizzle-kit will detect the audit columns are missing from the DB snapshot and emit an `ADD COLUMN` migration to restore them. Apply it.
789
+ - Projects that already hand-patched their schema and ran a manual `ADD COLUMN` migration (like the `podcast-app` workaround in commit `98d8758`): the next compile will regenerate a matching `ADD COLUMN` migration that will fail with "duplicate column name" against a DB that already has the columns. Mark the new migration as applied without running it (e.g. `INSERT INTO __drizzle_migrations` in the features DB) or hand-edit the generated SQL to a no-op, then continue normally.
790
+
791
+ ### Fix: `firewall.exception` generated `isNull(<table>.deletedAt)` against a missing column
792
+
793
+ Resources with `firewall: { exception: true }` always emitted `return isNull(<table>.deletedAt);` inside `buildFirewallConditions()`, regardless of whether the table actually had a `deletedAt` column. Projects that disabled audit injection globally (`compiler.features.auditFields: false`) or authored a schema without `deletedAt` ended up with Drizzle resolving `<table>.deletedAt` to `undefined` at query time — every `GET /api/v1/<resource>` returned `500`.
794
+
795
+ The three concerns are now fully independent:
796
+
797
+ - **`firewall.exception: true`** — only disables tenant scoping (org/user/team `WHERE` clauses). It does not gate audit fields or soft-delete.
798
+ - **Audit fields** — always injected unless globally opted out. Unchanged.
799
+ - **Soft-delete filter** — emitted only when the schema actually has `deletedAt` *or* the user explicitly set `firewall.softDelete`.
800
+
801
+ In the default configuration (audit injection on), behavior is unchanged: exception resources still filter `deletedAt IS NULL`. Only the broken case changes — exception resources on a schema without `deletedAt` now return `undefined` (no firewall), matching the column reality.
802
+
803
+ No config changes required — recompile to pick up the fix.
804
+
805
+ ---
806
+
807
+ ## v0.8.4 — April 14, 2026
808
+
809
+ ### New `generateId: "short"` Strategy
810
+
811
+ Added a compact ID option for tables where short, shareable codes matter more than collision resistance at scale:
812
+
813
+ ```typescript
814
+ providers: {
815
+ database: defineDatabase("cloudflare-d1", {
816
+ generateId: "short",
817
+ }),
818
+ }
819
+ ```
820
+
821
+ Generates 6-character alphanumeric IDs (e.g. `a3F9xK`) using nanoid's `customAlphabet` with the full 62-char alphabet (`0-9A-Za-z`). Requires the `nanoid` package in your project (same as the existing `"nanoid"` strategy).
822
+
823
+ **When to use:** room codes, invite links, share URLs, ephemeral records — anywhere the ID appears in a URL or needs to be human-typeable.
824
+
825
+ **When not to use:** high-volume tables. 62^6 ≈ 56.8B combinations means ~238K rows before a 50% collision probability (birthday bound). For large tables stick with `"uuid"`, `"cuid"`, or `"prefixed"`.
826
+
827
+ See [Providers - ID Generation Options](/compiler/config/providers#id-generation-options) for the full list of strategies.
828
+
829
+ ---
830
+
831
+ ## v0.8.3 — April 14, 2026
832
+
833
+ ### Fix: `wrangler.toml` Route Placement and Binding IDs
834
+
835
+ Two bugs in the generated `wrangler.toml` that blocked production deployment without manual edits:
836
+
837
+ **Routes were nested under `[dev]`.** The `routes = [...]` array was emitted after the `[dev]` section header, so TOML parsed it as `dev.routes` and wrangler ignored the custom domain (warning: `Unexpected fields found in dev field: "routes"`). Routes now emit as a top-level key.
838
+
839
+ **D1 and KV bindings used placeholder IDs.** Despite `databaseId`, `filesDatabaseId`, and `kvId` being set in the quickback config, the generated `wrangler.toml` wrote `"local-features"`, `"local-files"`, and `"local"` instead of the real UUIDs. The compiler now resolves IDs from multiple config sources:
840
+
841
+ | Binding | Config sources checked (in order) |
842
+ |---------|-----------------------------------|
843
+ | `AUTH_DB` | `database.config.authDatabaseId` |
844
+ | `DB` | `database.config.featuresDatabaseId`, `database.config.databaseId` |
845
+ | `FILES_DB` | `fileStorage.config.filesDatabaseId`, `database.config.filesDatabaseId` |
846
+ | `KV` | `database.config.kvNamespaceId`, `storage.config.namespaceId`, `auth.config.kvId` |
847
+
848
+ See [Providers - Database Options](/compiler/config/providers#database-options) for the full list of supported ID properties.
849
+
850
+ ### Fix: Account SPA Post-Login Redirect on Unified Domain
851
+
852
+ When the Account SPA was served at `/account/` on the unified quickback domain (e.g. `secure.example.com/account/`), post-login redirects dropped the basepath and sent users to `/dashboard` instead of `/account/dashboard`. Sign-out redirects had the same issue.
853
+
854
+ The SPA now shares a basepath module across the router and all raw `window.location.href` assignments, so login, signup, email OTP, welcome, and sign-out flows all stay under the correct path prefix regardless of whether the SPA is on the unified domain or its own dedicated auth subdomain.
855
+
856
+ No config changes required — recompile to pick up the fix.
857
+
858
+ ---
859
+
860
+ ## v0.8.2 — April 11, 2026
861
+
862
+ ### Catch-All `VITE_QUICKBACK_URL` Environment Variable
863
+
864
+ Instead of setting four separate URL env vars, you can now point at a single Quickback origin:
865
+
866
+ ```bash
867
+ # One variable — done.
868
+ VITE_QUICKBACK_URL=https://secure.example.com
869
+ ```
870
+
871
+ When set, it's used as a fallback for the individual URLs:
872
+
873
+ | Individual var (explicit) | Fallback when unset |
874
+ |---|---|
875
+ | `VITE_QUICKBACK_API_URL` | `${VITE_QUICKBACK_URL}` |
876
+ | `VITE_QUICKBACK_ACCOUNT_URL` | `${VITE_QUICKBACK_URL}/account` |
877
+ | `VITE_QUICKBACK_CMS_URL` | `${VITE_QUICKBACK_URL}/cms` |
878
+
879
+ `VITE_QUICKBACK_APP_URL` stays independent — it points at the tenant's own frontend, not the Quickback server.
880
+
881
+ **Non-breaking.** Individual vars still take precedence when set, so existing configurations work unchanged. The compiler now also emits `VITE_QUICKBACK_URL` into the generated SPA `.env` files, and library users can set `__QUICKBACK_URL__` on `globalThis` for the same effect.
882
+
883
+ See [Environment Variables](/stack/account-ui/environment-variables) for the full reference.
884
+
885
+ ---
886
+
887
+ ## v0.8.1 — April 9, 2026
888
+
889
+ ### Role Hierarchy with `+` Suffix
890
+
891
+ You can now define a role hierarchy in your config and use the `+` suffix in access rules to mean "this role and above":
892
+
893
+ ```typescript
894
+ // quickback.config.ts
895
+ auth: {
896
+ roleHierarchy: ['member', 'admin', 'owner'],
897
+ }
898
+
899
+ // In resource definitions
900
+ crud: {
901
+ list: { access: { roles: ["member+"] } }, // member, admin, owner
902
+ create: { access: { roles: ["admin+"] } }, // admin, owner
903
+ delete: { access: { roles: ["owner"] } }, // owner only
904
+ }
905
+ ```
906
+
907
+ Roles are expanded at compile time. No `+` = exact match. See [Access - Role Hierarchy](/compiler/definitions/access#role-hierarchy) for details.
908
+
909
+ ---
910
+
911
+ ## v0.8.0 — April 9, 2026
912
+
913
+ ### Breaking: VITE URL Environment Variables Renamed
914
+
915
+ All Quickback-generated URL environment variables are now namespaced under `VITE_QUICKBACK_*` to avoid collisions with other Vite projects.
916
+
917
+ | Old | New |
918
+ |-----|-----|
919
+ | `VITE_API_URL` | `VITE_QUICKBACK_API_URL` |
920
+ | `VITE_ACCOUNT_URL` | `VITE_QUICKBACK_ACCOUNT_URL` |
921
+ | `VITE_APP_URL` | `VITE_QUICKBACK_APP_URL` |
922
+ | `VITE_CMS_URL` | `VITE_QUICKBACK_CMS_URL` |
923
+
924
+ **Non-URL variables are unchanged:** `VITE_ENABLE_*` feature flags, branding vars (`VITE_APP_NAME`, etc.), and `VITE_STRIPE_PUBLISHABLE_KEY` stay as-is.
925
+
926
+ **Action required:**
927
+ - **Compiled projects** — re-run `quickback compile`. The compiler generates the new names automatically.
928
+ - **Standalone deploys** — update `.env`, `.env.production`, and `wrangler.toml` files manually.
929
+ - **Library users** — the `__QUICKBACK_API_URL__` / `__QUICKBACK_APP_URL__` globalThis names are unchanged, but if you pipe Vite env vars into them, update the var names.
930
+
931
+ See [Environment Variables](/stack/account-ui/environment-variables) for the full reference.
932
+
933
+ ### CMS Access Control
934
+
935
+ The `cms.access` config option now enforces access at the CMS level, not just link visibility in Account UI.
936
+
937
+ ```typescript
938
+ cms: { access: "admin" }
939
+ ```
940
+
941
+ When set to `"admin"`, non-admin users (`user.role !== "admin"`) see an "Access Denied" screen with a sign-out button instead of the CMS. When set to `"user"` (the default), any authenticated user can access the CMS.
942
+
943
+ See [CMS Connecting](/stack/cms/connecting) and [Compiler Config](/compiler/config) for details.
944
+
945
+ ### SPA Sub-Route Fix
946
+
947
+ Fixed a bug where hard-refreshing or directly navigating to SPA sub-routes (e.g., `/account/profile`, `/cms/tables/users`) returned a blank white screen. The Worker now correctly serves `index.html` for all SPA paths, allowing the client-side router to handle routing.
948
+
949
+ ---
950
+
951
+ ## v0.5.11 — February 24, 2026
952
+
953
+ ### Email OTP & Auth Fixes
954
+
955
+ - Fixed email-OTP magic links not working correctly
956
+ - Removed deprecated `/internal/validate` endpoint — use standard Better Auth session validation instead
957
+ - Auth is now required for all API routes when running locally (previously some routes were unprotected in dev)
958
+
959
+ ### Multiple Table Exports Fix
960
+
961
+ - Fixed a compiler error when a single file exports multiple Drizzle tables alongside a `defineTable()` default export
962
+ - The CLI now properly detects and reports this with a clear error message pointing to the fix
963
+
964
+ ### Headless Drizzle Rename Hints
965
+
966
+ - Added `compiler.migrations.renames` configuration for CI/CD environments where Drizzle's interactive rename prompts would block compilation
967
+ - Compile errors now include explicit rename key paths and fail fast on malformed rename config keys
968
+ - See [Configuration](/compiler/config) for details
969
+
970
+ ### Security Contract Report Artifacts
971
+
972
+ - Added generated security contract artifacts to compiler output:
973
+ - `reports/security-contracts.report.json`
974
+ - `reports/security-contracts.report.sig.json`
975
+ - Added config-driven signing controls:
976
+ - `compiler.securityContracts.report.signature.enabled`
977
+ - `compiler.securityContracts.report.signature.required`
978
+ - `compiler.securityContracts.report.signature.key` / `keyEnv` / `keyId`
979
+ - Missing required signing keys now fail loudly with explicit remediation guidance
980
+ - Added strict config validation for report/signature paths and signing options
981
+
982
+ ### Mandatory Unsafe Action Audit Trail
983
+
984
+ - Added structured unsafe action config (`unsafe: { reason, adminOnly, crossTenant, targetScope }`)
985
+ - Cross-tenant unsafe actions now require Better Auth authentication plus platform admin role (`ctx.userRole === "admin"`)
986
+ - Added mandatory audit logging for unsafe cross-tenant actions (success, denial, and error paths)
987
+ - Cloudflare output now includes optional `AUDIT_DB` wiring, `drizzle.audit.config.ts`, and `db:migrate:audit:*` scripts when unsafe actions are present
988
+ - Added compile-time raw SQL guard for actions and handlers (`allowRawSql: true` required per action)
989
+
990
+ ---
991
+
992
+ ## v0.5.10 — February 19, 2026
993
+
994
+ ### Compiler Page Parsing & CLI Output
995
+
996
+ - Improved compiler page parsing for `definePage()` definitions
997
+ - Better CLI output formatting during compilation
998
+ - Added `apiPath` to schema registry for CMS integration
999
+
1000
+ ### Bug Fixes
1001
+
1002
+ - Fixed hyphenated action names not being properly quoted in generated code (e.g., `mark-complete` now generates valid JavaScript)
1003
+ - API key authentication (`x-api-key` header) is now handled separately from session tokens (`Bearer` header)
1004
+
1005
+ ---
1006
+
1007
+ ## v0.5.9 — February 16, 2026
1008
+
1009
+ ### CMS Pages & CLI Page Support
1010
+
1011
+ - Added `definePage()` support for CMS-managed pages
1012
+ - Auth middleware improvements for page routes
1013
+ - CLI now supports page definitions alongside table and action definitions
1014
+
1015
+ ---
1016
+
1017
+ ## v0.5.8 — February 14, 2026
1018
+
1019
+ ### CMS App
1020
+
1021
+ - Introduced the Quickback CMS — a schema-driven admin panel that connects to your generated API
1022
+ - CMS namespace added to actions for admin-specific operations
1023
+ - Fixed `guard` → `access` naming inconsistency in CMS action definitions
1024
+
1025
+ ### Schema Registry & Firewall Improvements
1026
+
1027
+ - Added schema registry generator — the compiler now outputs a JSON schema registry used by the CMS
1028
+ - Firewall error modes: choose between `reveal` (403 with details) and `hide` (opaque 404) for security-sensitive deployments
1029
+
1030
+ ### Bug Fixes
1031
+
1032
+ - Fixed anonymous user email format generation
1033
+ - Organization selector improvements in Account UI
1034
+ - Config validation now catches more errors at compile time
1035
+ - Better CRUD error handling with structured error responses
1036
+ - Fixed masking to use representative star counts instead of fixed formatting
1037
+
1038
+ ---
1039
+
1040
+ ## v0.5.7 — February 12, 2026
1041
+
1042
+ ### Scoped Database for Actions
1043
+
1044
+ Actions now receive a **security-scoped database** instead of a raw Drizzle instance. The compiler generates a proxy wrapper that automatically enforces org isolation, owner filtering, and soft-delete visibility — the same protections that CRUD routes have always had.
1045
+
1046
+ The scoped DB uses duck-typed column detection at runtime:
1047
+
1048
+ | Column Detected | SELECT / UPDATE / DELETE | INSERT |
1049
+ |---|---|---|
1050
+ | `organizationId` | Adds `WHERE organizationId = ?` | Auto-injects `organizationId` from context |
1051
+ | `ownerId` | Adds `WHERE ownerId = ?` | Auto-injects `ownerId` from context |
1052
+ | `deletedAt` | Adds `WHERE deletedAt IS NULL` | — |
1053
+
1054
+ This means **every action is secure by default** — no manual `WHERE` clauses needed.
1055
+
1056
+ ```typescript
1057
+ defineActions(todos, {
1058
+ complete: {
1059
+ type: "record",
1060
+ execute: async ({ db, ctx, record, input }) => {
1061
+ // db is scoped — only sees records in user's org, excludes soft-deleted
1062
+ const siblings = await db.select().from(todos);
1063
+ // ↑ automatically filtered to ctx.activeOrgId + deletedAt IS NULL
1064
+ },
1065
+ },
1066
+ });
1067
+ ```
1068
+
1069
+ #### Unsafe Mode
1070
+
1071
+ Actions that intentionally need to bypass security (admin reports, cross-org queries, migrations) can declare `unsafe: true` to receive a raw, unscoped database handle:
1072
+
1073
+ ```typescript
1074
+ defineActions(analytics, {
1075
+ globalReport: {
1076
+ unsafe: true,
1077
+ execute: async ({ db, rawDb, ctx, input }) => {
1078
+ // db → still scoped (safety net)
1079
+ // rawDb → bypasses all security filters
1080
+ const allOrgs = await rawDb.select().from(organizations);
1081
+ },
1082
+ },
1083
+ });
1084
+ ```
1085
+
1086
+ Without `unsafe: true`, `rawDb` is `undefined`.
1087
+
1088
+ **Related docs:** [Actions](/compiler/definitions/actions), [Actions API](/compiler/targets/hono-api/using-the-api/actions-api)
1089
+
1090
+ ---
1091
+
1092
+ ### Cascading Soft Delete
1093
+
1094
+ Soft-deleting a parent record now **automatically cascades** to child and junction tables within the same feature. The compiler detects foreign key references at build time and generates cascade UPDATE statements.
1095
+
1096
+ ```
1097
+ DELETE /api/v1/projects/:id
1098
+ ```
1099
+
1100
+ Generated behavior:
1101
+ ```typescript
1102
+ // 1. Soft delete the parent
1103
+ await db.update(projects)
1104
+ .set({ deletedAt: now, deletedBy: userId })
1105
+ .where(eq(projects.id, id));
1106
+
1107
+ // 2. Auto-cascade to children (compiler-generated)
1108
+ await db.update(projectMembers)
1109
+ .set({ deletedAt: now, deletedBy: userId })
1110
+ .where(eq(projectMembers.projectId, id));
1111
+
1112
+ await db.update(projectTasks)
1113
+ .set({ deletedAt: now, deletedBy: userId })
1114
+ .where(eq(projectTasks.projectId, id));
1115
+ ```
1116
+
1117
+ Rules:
1118
+ - Only applies to **soft delete** (the default). Hard delete relies on database-level `ON DELETE CASCADE`.
1119
+ - Only cascades within the **same feature** — cross-feature references are not affected.
1120
+ - Child tables must have `deletedAt` / `deletedBy` columns (auto-added by the compiler's audit fields).
1121
+
1122
+ **Related docs:** [Actions API — Cascading Soft Delete](/compiler/targets/hono-api/using-the-api/actions-api#cascading-soft-delete)
1123
+
1124
+ ---
1125
+
1126
+ ### Advanced Query Parameters
1127
+
1128
+ New query parameter capabilities for all list endpoints:
1129
+
1130
+ - **Field selection** — `?fields=id,name,status` returns only the columns you need
1131
+ - **Multi-sort** — `?sort=status:asc,createdAt:desc` sorts by multiple fields
1132
+ - **Total count** — `?count=true` returns total matching records in response headers (`X-Total-Count`)
1133
+ - **Full-text search** — `?search=keyword` searches across all text columns
1134
+
1135
+ ```bash
1136
+ # Get only names and statuses, sorted by status then date, with total count
1137
+ GET /api/v1/todos?fields=id,name,status&sort=status:asc,createdAt:desc&count=true
1138
+
1139
+ # Search across all text fields
1140
+ GET /api/v1/todos?search=urgent
1141
+ ```
1142
+
1143
+ **Related docs:** [Query Parameters](/compiler/targets/hono-api/using-the-api/query-params)
1144
+
1145
+ ---
1146
+
1147
+ ### Audit Field Improvements
1148
+
1149
+ - `deletedAt` and `deletedBy` fields are now **always injected** by the compiler for tables with soft delete enabled — no need to define them in your schema
1150
+ - All audit fields (`createdAt`, `createdBy`, `modifiedAt`, `modifiedBy`, `deletedAt`, `deletedBy`) are auto-managed
1151
+
1152
+ ---
1153
+
1154
+ ## v0.5.6 — February 8, 2026
1155
+
1156
+ ### Database Naming Conventions
1157
+
1158
+ - Default table and column naming changed to **snake_case** with `usePlurals: false`
1159
+ - Table names derived from generated Better Auth schema for consistency
1160
+ - Removed legacy single-database mode — split databases (auth + features) is now the standard
1161
+
1162
+ ### Auth Variable Shadowing Fix
1163
+
1164
+ - Fixed `member` variable in auth middleware that shadowed the Drizzle `member` table import
1165
+ - Renamed to `sessionMember` to avoid conflicts in generated routes
1166
+
1167
+ ---
1168
+
1169
+ ## v0.5.5 — February 5, 2026
1170
+
1171
+ ### Better Auth Plugins
1172
+
1173
+ - Published `@quickback-dev/better-auth-upgrade-anonymous` v1.1.0 — post-passkey email collection flow
1174
+ - Published `@quickback-dev/better-auth-combo-auth` — combined email + password + OTP authentication
1175
+ - Published `@quickback-dev/better-auth-aws-ses` — AWS SES email provider for Better Auth
1176
+
1177
+ ### OpenAPI Spec Generation
1178
+
1179
+ - Generated APIs now include a full OpenAPI specification at `/openapi.json`
1180
+ - Better Auth endpoints included in the spec
1181
+ - Runtime route: `GET /openapi.json`
1182
+
1183
+ ### Security Hardening
1184
+
1185
+ - Global error handler prevents leaking internal error details
1186
+ - Security headers middleware (CSP, HSTS, X-Frame-Options, X-Content-Type-Options)
1187
+ - `BETTER_AUTH_SECRET` properly passed to generated config
1188
+
1189
+ ---
1190
+
1191
+ ## v0.5.4 — January 30, 2026
1192
+
1193
+ ### Account UI
1194
+
1195
+ - Pre-built authentication UI deployed as Cloudflare Workers
1196
+ - Features: sessions, organizations, passkeys, passwordless, admin panel, API keys
1197
+ - Dual-mode: standalone (degit template) or embedded with Quickback projects
1198
+
1199
+ ### Webhook System
1200
+
1201
+ - Inbound webhook endpoints with signature verification
1202
+ - Outbound webhooks via Cloudflare Queues with automatic retries
1203
+ - Configurable per-feature webhook events
1204
+
1205
+ ### Realtime & Vector Search
1206
+
1207
+ - Durable Objects + WebSocket realtime subscriptions
1208
+ - Vector embeddings via Cloudflare Vectorize
1209
+ - KV and R2 storage integrations
1210
+
1211
+ ---
1212
+
1213
+ ## v0.5.0 — January 2026
1214
+
1215
+ ### Initial Release
1216
+
1217
+ - **Quickback Compiler** — TypeScript-first backend compiler
1218
+ - **Four Security Pillars** — Firewall, Access, Guards, Masking
1219
+ - **`defineTable()`** — Schema + security configuration in a single file
1220
+ - **Templates** — Cloudflare Workers, Bun standalone, B2B SaaS
1221
+ - **Cloud Compiler** — Remote compilation via `compiler.quickback.dev`
1222
+ - **CLI** — `quickback create`, `quickback compile`, `quickback init`
1223
+ - **Better Auth Integration** — Organizations, roles, sessions
1224
+ - **Drizzle ORM** — Schema-first with automatic migrations
1225
+ - **Cloudflare D1** — Split database support (auth + features)