@builtbyfriends/bwf 0.0.0-stage → 1.9.1

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 (448) hide show
  1. package/AGENTS_TEMPLATE.md +4 -0
  2. package/LICENSE +22 -0
  3. package/README.md +48 -2
  4. package/dist/account-cmd-Cj0I2_bJ.mjs +45 -0
  5. package/dist/agents-BLiMq9E1.mjs +113 -0
  6. package/dist/application-analysis-C9Ck2Yeg.mjs +1498 -0
  7. package/dist/application-routing-DbR-W5lG.mjs +25 -0
  8. package/dist/atomic-write-DA6eD1Kp.mjs +17 -0
  9. package/dist/auth-BKsUmWbT.d.mts +77 -0
  10. package/dist/auth-DkvoW5hB.mjs +33 -0
  11. package/dist/auth-aKyIWkdS.mjs +1 -0
  12. package/dist/auth-client-6-Ft9i9T.d.mts +5 -0
  13. package/dist/auth-client-DwCdwKbw.mjs +5 -0
  14. package/dist/auth-client-react-CJdeErvM.mjs +5 -0
  15. package/dist/auth-client-react-DvQLe5Zb.d.mts +5 -0
  16. package/dist/auth-link-D-DddkCQ.mjs +26 -0
  17. package/dist/auth-migrations-DDeifS3v.mjs +206 -0
  18. package/dist/auth-router-tWzIwf8f.mjs +66 -0
  19. package/dist/auth-xnkmpZUl.mjs +311 -0
  20. package/dist/base64-ikl9yBy3.mjs +15 -0
  21. package/dist/better-auth-shared-Br6TNaYJ.mjs +473 -0
  22. package/dist/better-auth-shared-CsBNvPOU.d.mts +56 -0
  23. package/dist/build-cmd-BnZezraT.mjs +153 -0
  24. package/dist/build-output-dir-Clj_unKN.mjs +402 -0
  25. package/dist/cancel-deploy-DKAj5U1Z.mjs +57 -0
  26. package/dist/cf-access-Bhz9wX6p.mjs +131 -0
  27. package/dist/cf-access-CUP5L08W.mjs +67 -0
  28. package/dist/cf-build-output-DA6uJomQ.mjs +1 -0
  29. package/dist/cf-build-output-DNQTwMNU.mjs +438 -0
  30. package/dist/cf-command-values-2kOtxMo1.mjs +26 -0
  31. package/dist/cf-config-migrate-COOCi4Ge.mjs +330 -0
  32. package/dist/cf-worker-settings-CIh4t_yG.mjs +41 -0
  33. package/dist/cli/cli.d.mts +1 -0
  34. package/dist/cli/cli.mjs +88 -0
  35. package/dist/cli/cloudflare-operation-process.d.mts +1 -0
  36. package/dist/cli/cloudflare-operation-process.mjs +1284 -0
  37. package/dist/cli/env-schema-probe.d.mts +43 -0
  38. package/dist/cli/env-schema-probe.mjs +165 -0
  39. package/dist/cli-main-HeXRQml6.mjs +1846 -0
  40. package/dist/client-D3D5RM5h.mjs +940 -0
  41. package/dist/client-VF2Nzc7Z.mjs +1 -0
  42. package/dist/cloudflare-auth-jb-1e43r.mjs +152 -0
  43. package/dist/cloudflare-cmd-B62t8Fm-.mjs +59 -0
  44. package/dist/cloudflare-config-i8yanry0.mjs +186 -0
  45. package/dist/cloudflare-connect-x7IsYghw.mjs +55 -0
  46. package/dist/cloudflare-operations-BeK7bhnP.mjs +627 -0
  47. package/dist/cloudflare-operations-C3Uu0Emj.mjs +1 -0
  48. package/dist/cloudflare-process-Cc6oiJqk.mjs +309 -0
  49. package/dist/cloudflare-user-output-CqONaAbP.mjs +19 -0
  50. package/dist/collect-8i0wU63d.mjs +1 -0
  51. package/dist/collect-C6Blu9yw.mjs +48 -0
  52. package/dist/config-CN_RFRkS.mjs +86 -0
  53. package/dist/config-D5G-Tx6o.mjs +1 -0
  54. package/dist/config-DOaFIK3w.mjs +88 -0
  55. package/dist/config-entry.d.mts +202 -0
  56. package/dist/config-entry.mjs +6 -0
  57. package/dist/config-tNx0HlFv.mjs +516 -0
  58. package/dist/connect-hLPNppu3.mjs +84 -0
  59. package/dist/create-project-B35ux-LA.mjs +126 -0
  60. package/dist/create-project-tJ1KwNss.mjs +1 -0
  61. package/dist/database-provider-DkZo4VwN.mjs +5 -0
  62. package/dist/database-provider.d.mts +25 -0
  63. package/dist/database-provider.mjs +1 -0
  64. package/dist/db-BH_md90k.mjs +1735 -0
  65. package/dist/delete-BSKI7V23.mjs +65 -0
  66. package/dist/deploy-C8KHBNsh.mjs +6512 -0
  67. package/dist/deploy-DCZBr7Ey.mjs +2 -0
  68. package/dist/deploy.d.mts +31 -0
  69. package/dist/deploy.mjs +118 -0
  70. package/dist/dev-inbox-I0nqTCdf.mjs +216 -0
  71. package/dist/discover-DJPmQcL5.mjs +36 -0
  72. package/dist/discover-EVuydEoM.mjs +1 -0
  73. package/dist/dist-B6eN80gc.mjs +1612 -0
  74. package/dist/dist-Cp4b1_T9.mjs +1 -0
  75. package/dist/dist-DMYe8CZJ.mjs +48 -0
  76. package/dist/dist-STQXl8ck.mjs +1878 -0
  77. package/dist/domain-C4ZhEiFG.mjs +149 -0
  78. package/dist/dotenv-4NdUCXbB.mjs +156 -0
  79. package/dist/drizzle-DqVFXtlc.mjs +306 -0
  80. package/dist/drizzle-Ds5P0n-S.mjs +1 -0
  81. package/dist/edge.d.mts +2 -0
  82. package/dist/edge.mjs +1 -0
  83. package/dist/email-B3TWga7x.mjs +742 -0
  84. package/dist/email-C_ATvNIG.mjs +2865 -0
  85. package/dist/email-cloudflare-DuAc9zny.mjs +854 -0
  86. package/dist/email-protocol-CZ0bAkI8.mjs +81 -0
  87. package/dist/env-CTAo8ifZ.mjs +73 -0
  88. package/dist/env-DUyTzroe.mjs +88 -0
  89. package/dist/env-Dl4Wggec.mjs +71 -0
  90. package/dist/env-helpers-BX0APszT.mjs +135 -0
  91. package/dist/env-helpers-U56xuFgL.d.mts +20 -0
  92. package/dist/env-mask-BsHxq3R8.mjs +46 -0
  93. package/dist/env-public-Cw_xPi1D.d.mts +119 -0
  94. package/dist/env-raw-Bo6TtrHU.mjs +41 -0
  95. package/dist/env-types-Bg-dTh8u.mjs +56 -0
  96. package/dist/env-validation-BufZConV.mjs +488 -0
  97. package/dist/env-validation-DPqDo4DU.mjs +1 -0
  98. package/dist/fetch-CBgyyhzm.d.mts +87 -0
  99. package/dist/fetch-error-DmlRM6e4.mjs +264 -0
  100. package/dist/fetch-stream-2GUN3YN1.mjs +102 -0
  101. package/dist/fetch-stream-bUXynOyZ.d.mts +32 -0
  102. package/dist/fetch-tpPiSK10.mjs +25 -0
  103. package/dist/gen-dc13IRXh.mjs +509 -0
  104. package/dist/gen-kQqhFyOP.mjs +1 -0
  105. package/dist/generate-BgtlYpKg.mjs +1 -0
  106. package/dist/generate-Da9mWKzU.mjs +80 -0
  107. package/dist/generated-wrangler-config-CoDaaFsA.mjs +17 -0
  108. package/dist/git-metadata-Cukp5kV5.mjs +82 -0
  109. package/dist/github-cmd-DT5Onu6E.mjs +690 -0
  110. package/dist/handler-CJ7DiiRF.mjs +161 -0
  111. package/dist/handler-CVsIfRv7.d.mts +279 -0
  112. package/dist/help-Bpv6Qeqn.mjs +1946 -0
  113. package/dist/help-CfZ4Bsw5.mjs +1 -0
  114. package/dist/inbound-CqubE-9T.d.mts +311 -0
  115. package/dist/inbound-lHugZPuK.mjs +509 -0
  116. package/dist/index.d.mts +64 -0
  117. package/dist/index.mjs +4163 -0
  118. package/dist/info-CLQoCenb.mjs +109 -0
  119. package/dist/init-DRUR0j8C.mjs +2486 -0
  120. package/dist/limits-CMmYT2l8.d.mts +16 -0
  121. package/dist/limits-D27Lp6FP.mjs +46 -0
  122. package/dist/link-DinwJnon.mjs +52 -0
  123. package/dist/list-B84t4BhW.mjs +130 -0
  124. package/dist/live-Dui0-aj_.d.mts +105 -0
  125. package/dist/live-saC8barp.mjs +410 -0
  126. package/dist/load-user-env-g0ahkZcj.mjs +34 -0
  127. package/dist/local-d1-C3EeOV7-.mjs +103 -0
  128. package/dist/log-JDnPc0cF.mjs +23 -0
  129. package/dist/login-Bl5lH8nH.mjs +87 -0
  130. package/dist/login-DoI7AsbY.mjs +1 -0
  131. package/dist/logs-CaT2N2f7.mjs +129 -0
  132. package/dist/migrate-CbGscX-V.mjs +125 -0
  133. package/dist/migrate-Ce3JKLVs.mjs +1 -0
  134. package/dist/migration-handler-22qiuWPq.mjs +469 -0
  135. package/dist/migration-handler-Bb2BJh6g.d.mts +38 -0
  136. package/dist/mime-BMUN_QKG.mjs +1004 -0
  137. package/dist/mysql-migration-sql-CNuBSqdx.mjs +239 -0
  138. package/dist/neon-CJzQSycr.mjs +52 -0
  139. package/dist/node-tfv-3v0V.mjs +64 -0
  140. package/dist/operator-ai-logging-Ay7M4KWw.mjs +121 -0
  141. package/dist/operator-args-BFg32YyY.mjs +722 -0
  142. package/dist/operator-auth-DdYZYEkO.mjs +47 -0
  143. package/dist/operator-client-DBujdELO.mjs +82 -0
  144. package/dist/operator-cmd-C73WWJBl.mjs +443 -0
  145. package/dist/operator-cmd-CdZytuAF.mjs +1 -0
  146. package/dist/output-Bb34lF0w.mjs +173 -0
  147. package/dist/output-CVolXKC1.mjs +1 -0
  148. package/dist/package-DO4d3Qz5.mjs +1444 -0
  149. package/dist/package-json-DvS6IFRv.mjs +43 -0
  150. package/dist/pg-DoyPxa_X.mjs +15 -0
  151. package/dist/picocolors-D1NxSLw-.mjs +71 -0
  152. package/dist/plan-BHNt1QhK.mjs +1 -0
  153. package/dist/plan-DX4_-OM5.mjs +58 -0
  154. package/dist/platform-args-NI_vfWvD.mjs +538 -0
  155. package/dist/platform-args-ZC1-A1N9.mjs +1 -0
  156. package/dist/platform-auth-config-d-lY5-aY.mjs +371 -0
  157. package/dist/platform-auth-protection-Dhw7lUCk.mjs +231 -0
  158. package/dist/platform-auth-recovery-DaCc0tlx.mjs +309 -0
  159. package/dist/platform-cmd-5Ry-C9im.mjs +193 -0
  160. package/dist/platform-cmd-5oZq91lI.mjs +1 -0
  161. package/dist/platform-discovery-Bxg9aZXU.mjs +40 -0
  162. package/dist/platform-domain-DLVdGvGG.mjs +256 -0
  163. package/dist/platform-lifecycle-CUgjipXO.mjs +1 -0
  164. package/dist/platform-lifecycle-fRt5VMls.mjs +8928 -0
  165. package/dist/platform-management-5hEsRfR2.mjs +1 -0
  166. package/dist/platform-management-Djh1hzLP.mjs +1607 -0
  167. package/dist/platform-plans-config-CkbUKFpm.mjs +447 -0
  168. package/dist/platform-recovery-Cghx7FCR.mjs +96 -0
  169. package/dist/platform-registry-x1m9HBxf.mjs +450 -0
  170. package/dist/platform-runtime-logs-kkoiYFpF.mjs +72 -0
  171. package/dist/platform-setup-SfwCwnZg.mjs +306 -0
  172. package/dist/prepare-B9mB47T5.mjs +84 -0
  173. package/dist/prepare-DNIq07so.mjs +13 -0
  174. package/dist/prepare-LHkyJqxi.mjs +1 -0
  175. package/dist/project-CC7eN00D.mjs +141 -0
  176. package/dist/project-DcSd4BeI.mjs +1 -0
  177. package/dist/project-cmd-DTF19-fC.mjs +109 -0
  178. package/dist/project-paths-iXHKRTTQ.mjs +159 -0
  179. package/dist/project-slug-BUy0lmyR.mjs +1 -0
  180. package/dist/project-slug-CO6ci9XG.mjs +7 -0
  181. package/dist/project-team-CvdLhDF2.mjs +129 -0
  182. package/dist/project-token-CwZdUEGu.mjs +70 -0
  183. package/dist/project-tsconfig-P9X952KG.mjs +98 -0
  184. package/dist/project-zero-trust-CKDoPdN1.mjs +64 -0
  185. package/dist/providers-Cd3c7wi0.mjs +64 -0
  186. package/dist/providers-Df69hb_X.d.mts +5 -0
  187. package/dist/provision-DGlFJ3T9.mjs +1 -0
  188. package/dist/provision-mYVLuQiy.mjs +1814 -0
  189. package/dist/queues-Bc3FsBQT.d.mts +5 -0
  190. package/dist/r2-conditions-DSLmkiR5.mjs +60 -0
  191. package/dist/requests-DNhfyF3l.mjs +52 -0
  192. package/dist/resolve-project-BCsAMDRA.mjs +47 -0
  193. package/dist/resolve-project-DhU9_lIo.mjs +1 -0
  194. package/dist/resource-name-DlJ9QXzg.mjs +10 -0
  195. package/dist/response-HmNjB30w.mjs +29 -0
  196. package/dist/rollback-BvCHol52.mjs +150 -0
  197. package/dist/rolldown-runtime-uD8oG6U2.mjs +24 -0
  198. package/dist/route-types-CRWhr93D.mjs +592 -0
  199. package/dist/route-url-BIDZT78M.mjs +58 -0
  200. package/dist/route-url-Bla3Upsy.d.mts +42 -0
  201. package/dist/routes-stub.d.mts +24 -0
  202. package/dist/routes-stub.mjs +1 -0
  203. package/dist/routing-assets-CSheDWWM.mjs +54 -0
  204. package/dist/rpc-DcByS_q0.d.mts +39 -0
  205. package/dist/rpc-DtxIN9Tv.mjs +19 -0
  206. package/dist/runner-CPerdjIl.mjs +163 -0
  207. package/dist/runner-CUNtS5x7.mjs +1 -0
  208. package/dist/runner-mysql-7aA5hGoM.mjs +145 -0
  209. package/dist/runner-mysql-DrMKw203.mjs +1 -0
  210. package/dist/runner-pg-2pjltt0t.mjs +1 -0
  211. package/dist/runner-pg-mYc75KfH.mjs +61 -0
  212. package/dist/runtime/ai.d.mts +50 -0
  213. package/dist/runtime/ai.mjs +455 -0
  214. package/dist/runtime/auth-client-react.d.mts +2 -0
  215. package/dist/runtime/auth-client-react.mjs +1 -0
  216. package/dist/runtime/auth-client.d.mts +2 -0
  217. package/dist/runtime/auth-client.mjs +1 -0
  218. package/dist/runtime/auth.d.mts +2 -0
  219. package/dist/runtime/auth.mjs +1 -0
  220. package/dist/runtime/better-auth-mysql.d.mts +5 -0
  221. package/dist/runtime/better-auth-mysql.mjs +21 -0
  222. package/dist/runtime/better-auth-pg.d.mts +5 -0
  223. package/dist/runtime/better-auth-pg.mjs +21 -0
  224. package/dist/runtime/better-auth.d.mts +6 -0
  225. package/dist/runtime/better-auth.mjs +22 -0
  226. package/dist/runtime/client-react.d.mts +5 -0
  227. package/dist/runtime/client-react.mjs +5 -0
  228. package/dist/runtime/client.d.mts +5 -0
  229. package/dist/runtime/client.mjs +5 -0
  230. package/dist/runtime/db-mysql.d.mts +2 -0
  231. package/dist/runtime/db-mysql.mjs +1 -0
  232. package/dist/runtime/db-pg.d.mts +2 -0
  233. package/dist/runtime/db-pg.mjs +1 -0
  234. package/dist/runtime/db.d.mts +17 -0
  235. package/dist/runtime/db.mjs +36 -0
  236. package/dist/runtime/drizzle-arktype.d.mts +1 -0
  237. package/dist/runtime/drizzle-arktype.mjs +2 -0
  238. package/dist/runtime/drizzle-valibot.d.mts +1 -0
  239. package/dist/runtime/drizzle-valibot.mjs +2 -0
  240. package/dist/runtime/drizzle-zod.d.mts +1 -0
  241. package/dist/runtime/drizzle-zod.mjs +2 -0
  242. package/dist/runtime/durable.d.mts +64 -0
  243. package/dist/runtime/durable.mjs +165 -0
  244. package/dist/runtime/email/testing.d.mts +108 -0
  245. package/dist/runtime/email/testing.mjs +268 -0
  246. package/dist/runtime/email-protocol.d.mts +25 -0
  247. package/dist/runtime/email-protocol.mjs +1 -0
  248. package/dist/runtime/email.d.mts +26 -0
  249. package/dist/runtime/email.mjs +524 -0
  250. package/dist/runtime/env-public-client.d.mts +19 -0
  251. package/dist/runtime/env-public-client.mjs +55 -0
  252. package/dist/runtime/env-public.d.mts +4 -0
  253. package/dist/runtime/env-public.mjs +277 -0
  254. package/dist/runtime/env.d.mts +12 -0
  255. package/dist/runtime/env.mjs +1 -0
  256. package/dist/runtime/fetch-server.d.mts +6 -0
  257. package/dist/runtime/fetch-server.mjs +29 -0
  258. package/dist/runtime/fetch-stream.d.mts +3 -0
  259. package/dist/runtime/fetch-stream.mjs +3 -0
  260. package/dist/runtime/fetch.d.mts +2 -0
  261. package/dist/runtime/fetch.mjs +3 -0
  262. package/dist/runtime/handler.d.mts +3 -0
  263. package/dist/runtime/handler.mjs +1 -0
  264. package/dist/runtime/kv.d.mts +45 -0
  265. package/dist/runtime/kv.mjs +103 -0
  266. package/dist/runtime/limits.d.mts +2 -0
  267. package/dist/runtime/limits.mjs +1 -0
  268. package/dist/runtime/live-client.d.mts +40 -0
  269. package/dist/runtime/live-client.mjs +282 -0
  270. package/dist/runtime/live-server.d.mts +11 -0
  271. package/dist/runtime/live-server.mjs +419 -0
  272. package/dist/runtime/live.d.mts +3 -0
  273. package/dist/runtime/live.mjs +1 -0
  274. package/dist/runtime/log.d.mts +24 -0
  275. package/dist/runtime/log.mjs +57 -0
  276. package/dist/runtime/migration-handler-mysql.d.mts +2 -0
  277. package/dist/runtime/migration-handler-mysql.mjs +111 -0
  278. package/dist/runtime/migration-handler-pg.d.mts +2 -0
  279. package/dist/runtime/migration-handler-pg.mjs +94 -0
  280. package/dist/runtime/migration-handler.d.mts +2 -0
  281. package/dist/runtime/migration-handler.mjs +1 -0
  282. package/dist/runtime/procedure.d.mts +27 -0
  283. package/dist/runtime/procedure.mjs +36 -0
  284. package/dist/runtime/procedures.d.mts +24 -0
  285. package/dist/runtime/procedures.mjs +56 -0
  286. package/dist/runtime/queues.d.mts +2 -0
  287. package/dist/runtime/queues.mjs +8 -0
  288. package/dist/runtime/remote/binding-handler.d.mts +11 -0
  289. package/dist/runtime/remote/binding-handler.mjs +227 -0
  290. package/dist/runtime/remote/index.d.mts +12 -0
  291. package/dist/runtime/remote/index.mjs +467 -0
  292. package/dist/runtime/response.d.mts +11 -0
  293. package/dist/runtime/response.mjs +1 -0
  294. package/dist/runtime/route-url.d.mts +2 -0
  295. package/dist/runtime/route-url.mjs +1 -0
  296. package/dist/runtime/routing.d.mts +53 -0
  297. package/dist/runtime/routing.mjs +425 -0
  298. package/dist/runtime/rpc-react.d.mts +16 -0
  299. package/dist/runtime/rpc-react.mjs +50 -0
  300. package/dist/runtime/rpc.d.mts +2 -0
  301. package/dist/runtime/rpc.mjs +1 -0
  302. package/dist/runtime/sandbox-container.d.mts +3 -0
  303. package/dist/runtime/sandbox-container.mjs +1 -0
  304. package/dist/runtime/sandbox.d.mts +5 -0
  305. package/dist/runtime/sandbox.mjs +196 -0
  306. package/dist/runtime/schema-d1.d.mts +1 -0
  307. package/dist/runtime/schema-d1.mjs +2 -0
  308. package/dist/runtime/schema-mysql.d.mts +1 -0
  309. package/dist/runtime/schema-mysql.mjs +2 -0
  310. package/dist/runtime/schema-pg.d.mts +1 -0
  311. package/dist/runtime/schema-pg.mjs +2 -0
  312. package/dist/runtime/seed.d.mts +34 -0
  313. package/dist/runtime/seed.mjs +5 -0
  314. package/dist/runtime/sse-client.d.mts +31 -0
  315. package/dist/runtime/sse-client.mjs +42 -0
  316. package/dist/runtime/sse.d.mts +32 -0
  317. package/dist/runtime/sse.mjs +1 -0
  318. package/dist/runtime/storage.d.mts +4 -0
  319. package/dist/runtime/storage.mjs +13 -0
  320. package/dist/runtime/validator.d.mts +2 -0
  321. package/dist/runtime/validator.mjs +1 -0
  322. package/dist/runtime/ws-server.d.mts +26 -0
  323. package/dist/runtime/ws-server.mjs +297 -0
  324. package/dist/runtime/ws.d.mts +2 -0
  325. package/dist/runtime/ws.mjs +108 -0
  326. package/dist/sandbox-CWDjoEG2.d.mts +50 -0
  327. package/dist/sandbox-container-BqamdFCx.d.mts +73 -0
  328. package/dist/sandbox-container-d1AHLpgn.mjs +291 -0
  329. package/dist/secret-DCF9RXTc.mjs +146 -0
  330. package/dist/skills-Dr3AjuBF.mjs +63 -0
  331. package/dist/sqlite-validation-CLJXXN93.mjs +24 -0
  332. package/dist/sse-CxR30yMF.mjs +174 -0
  333. package/dist/standard-schema-CuDawHOC.d.mts +40 -0
  334. package/dist/static-asset-marker-mWMX2dLa.mjs +38 -0
  335. package/dist/subcommand-prompt-B9yUo--u.mjs +370 -0
  336. package/dist/terminal-log-text-DNsWJREL.mjs +31 -0
  337. package/dist/types-D7-4tBu7.d.mts +1 -0
  338. package/dist/untrusted-env-lL7RkYiC.mjs +50 -0
  339. package/dist/validate-B-zsjhiz.mjs +162 -0
  340. package/dist/validate-DbqGdPPY.mjs +1 -0
  341. package/dist/validator-8-NZs2Xr.mjs +168 -0
  342. package/dist/version-metadata-DsSoNsKJ.mjs +23 -0
  343. package/dist/wrangler-DU784Dkf.mjs +1452 -0
  344. package/dist/wrangler-Rr9_76DQ.mjs +1 -0
  345. package/dist/ws-Q_osq9VK.d.mts +137 -0
  346. package/dist/yarn-pnp-DgWbE7z5.mjs +91 -0
  347. package/docs/guide/ai.md +273 -0
  348. package/docs/guide/app-types.md +101 -0
  349. package/docs/guide/auth.md +255 -0
  350. package/docs/guide/database/d1.md +86 -0
  351. package/docs/guide/database/mysql.md +72 -0
  352. package/docs/guide/database/postgresql.md +94 -0
  353. package/docs/guide/database.md +454 -0
  354. package/docs/guide/deployment.md +124 -0
  355. package/docs/guide/durable-state.md +192 -0
  356. package/docs/guide/edge/headers.md +47 -0
  357. package/docs/guide/edge/redirects.md +85 -0
  358. package/docs/guide/edge/rewrites.md +119 -0
  359. package/docs/guide/edge/static-assets.md +94 -0
  360. package/docs/guide/email/domains.md +119 -0
  361. package/docs/guide/email/receiving.md +142 -0
  362. package/docs/guide/email/sending.md +262 -0
  363. package/docs/guide/email.md +23 -0
  364. package/docs/guide/env-vars.md +115 -0
  365. package/docs/guide/index.md +37 -0
  366. package/docs/guide/jobs.md +80 -0
  367. package/docs/guide/kv.md +100 -0
  368. package/docs/guide/live.md +181 -0
  369. package/docs/guide/platform/administration/access.md +165 -0
  370. package/docs/guide/platform/administration/connected-apps.md +84 -0
  371. package/docs/guide/platform/administration/email.md +169 -0
  372. package/docs/guide/platform/administration/operations.md +100 -0
  373. package/docs/guide/platform/administration/plans.md +156 -0
  374. package/docs/guide/platform/administration/projects.md +74 -0
  375. package/docs/guide/platform/administration/zero-trust.md +205 -0
  376. package/docs/guide/platform/development/local.md +122 -0
  377. package/docs/guide/platform/development/runtime.md +115 -0
  378. package/docs/guide/platform/development/schema-ci.md +44 -0
  379. package/docs/guide/platform/installation/ci.md +62 -0
  380. package/docs/guide/platform/installation/credentials.md +140 -0
  381. package/docs/guide/platform/installation/domains.md +120 -0
  382. package/docs/guide/platform/installation/first-deployment.md +95 -0
  383. package/docs/guide/platform/installation/maintenance.md +250 -0
  384. package/docs/guide/platform/installation/prerequisites.md +176 -0
  385. package/docs/guide/platform/installation/setup.md +300 -0
  386. package/docs/guide/platform/installation/uninstall.md +110 -0
  387. package/docs/guide/platform-administration.md +19 -0
  388. package/docs/guide/platform-development.md +16 -0
  389. package/docs/guide/procedures.md +48 -0
  390. package/docs/guide/project-collaboration.md +99 -0
  391. package/docs/guide/queues.md +149 -0
  392. package/docs/guide/quickstart.md +129 -0
  393. package/docs/guide/remote-dev.md +67 -0
  394. package/docs/guide/sandboxes.md +134 -0
  395. package/docs/guide/self-hosted-platform.md +45 -0
  396. package/docs/guide/server-routing.md +283 -0
  397. package/docs/guide/sse.md +174 -0
  398. package/docs/guide/storage.md +82 -0
  399. package/docs/guide/testing.md +64 -0
  400. package/docs/guide/type-safety.md +270 -0
  401. package/docs/guide/typed-fetch.md +98 -0
  402. package/docs/guide/websockets.md +230 -0
  403. package/docs/index.md +102 -0
  404. package/docs/integrations/agents.md +38 -0
  405. package/docs/integrations/cloudflare.md +241 -0
  406. package/docs/integrations/hono.md +127 -0
  407. package/docs/reference/api/auth.md +195 -0
  408. package/docs/reference/api/client.md +90 -0
  409. package/docs/reference/api/database.md +118 -0
  410. package/docs/reference/api/deploy.md +63 -0
  411. package/docs/reference/api/durable.md +47 -0
  412. package/docs/reference/api/env.md +51 -0
  413. package/docs/reference/api/handlers.md +189 -0
  414. package/docs/reference/api/plugin.md +40 -0
  415. package/docs/reference/api/resources.md +116 -0
  416. package/docs/reference/api/rewrites.md +111 -0
  417. package/docs/reference/api/types.md +126 -0
  418. package/docs/reference/api.md +71 -0
  419. package/docs/reference/cli/auth.md +87 -0
  420. package/docs/reference/cli/database.md +159 -0
  421. package/docs/reference/cli/deploy.md +117 -0
  422. package/docs/reference/cli/domains.md +42 -0
  423. package/docs/reference/cli/email.md +145 -0
  424. package/docs/reference/cli/generate.md +113 -0
  425. package/docs/reference/cli/github.md +181 -0
  426. package/docs/reference/cli/platform-config.md +93 -0
  427. package/docs/reference/cli/platform-email.md +81 -0
  428. package/docs/reference/cli/platform-installation.md +166 -0
  429. package/docs/reference/cli/platform-operations.md +90 -0
  430. package/docs/reference/cli/platform-users.md +159 -0
  431. package/docs/reference/cli/platform-zero-trust.md +60 -0
  432. package/docs/reference/cli/platform.md +78 -0
  433. package/docs/reference/cli/project.md +208 -0
  434. package/docs/reference/cli/secrets.md +79 -0
  435. package/docs/reference/cli/setup.md +88 -0
  436. package/docs/reference/cli.md +115 -0
  437. package/docs/reference/config.md +478 -0
  438. package/docs/reference/resource-inference.md +72 -0
  439. package/docs/reference/structure.md +138 -0
  440. package/package.json +389 -3
  441. package/sandbox.Dockerfile +4 -0
  442. package/schema.json +353 -0
  443. package/skills/bwf/SKILL.md +100 -0
  444. package/skills/migrate-vite-cloudflare-to-bwf/SKILL.md +53 -0
  445. package/templates/assets/bwf.svg +5 -0
  446. package/templates/assets/icons.svg +49 -0
  447. package/templates/assets/react.svg +1 -0
  448. package/templates/assets/stack.svg +35 -0
@@ -0,0 +1,166 @@
1
+ ---
2
+ description: 'Install a bwf platform from the CLI, set its domain, and run its lifecycle commands.'
3
+ outline: deep
4
+ ---
5
+
6
+ # Platform Installation {#nosam-platform-install}
7
+
8
+ ```sh
9
+ bwf platform install [options] [--yes]
10
+ ```
11
+
12
+ | Option | Purpose |
13
+ | ----------------------------------------- | ------------------------------------------------------------------------------------ |
14
+ | `--name <slug>` | Installation name used in `void-<name>-<role>` resource names; choose an unused name |
15
+ | `--display-name <name>` | Human-readable platform name |
16
+ | `--account <id>` | Cloudflare account id |
17
+ | `--auth-config <path>` | Login methods, signup policy, and environment references for provider secrets |
18
+ | `--login-methods <methods>` | Comma-separated `github`, `google`, `oidc`, or `cloudflare-access` login methods |
19
+ | `--access-protection` | Protect the platform UI and APIs with Cloudflare Access |
20
+ | `--no-access-protection` | Skip Cloudflare Access protection |
21
+ | `--app-access <public\|platform\|custom>` | Public apps, the platform's Access policy, or separately selected app policies |
22
+ | `--hyperdrive <create\|id>` | Create Hyperdrive or use the specified existing configuration |
23
+ | `--application-domain <domain>` | Base domain for deployed apps |
24
+ | `--workers-dev` | Explicit testing mode; add an application domain later |
25
+ | `--zone <domain>` | Cloudflare zone containing the application domain |
26
+ | `--dedicated-zone` | Add zone-wide catch-all routes; valid only when the app domain is the whole zone |
27
+ | `--no-dedicated-zone` | Skip zone-wide application catch-all routes |
28
+ | `--custom-domains` | Let projects add their own domains; needs a dedicated zone |
29
+ | `--runtime-logs <full\|minimal>` | `minimal` keeps request URLs and log and exception messages out of runtime logs |
30
+ | `--storage-location <hint\|automatic>` | Default location hint for new project R2 buckets; `automatic` clears it |
31
+ | `--control-plane-domain <domain>` | Optional API custom hostname; defaults to `workers.dev` |
32
+ | `--no-control-plane-domain` | Use the default `workers.dev` API hostname |
33
+ | `--dashboard-url <origin>` | HTTPS origin of an optional dashboard deployed separately |
34
+ | `--plan` | Preview Cloudflare changes and save installation choices locally |
35
+ | `--resume` | Continue the matching checkpointed installation |
36
+ | `--runtime <path>` | Deploy a locally built, integrity-checked runtime directory |
37
+ | `--yes` | Acknowledge Cloudflare changes in non-interactive use |
38
+
39
+ For a first installation, follow [Install a bwf Platform](../../guide/self-hosted-platform.md). The interactive installer recommends using a domain and offers **Use workers.dev for testing** as a visible alternative. bwf creates the platform infrastructure and tables. External PostgreSQL and a configured login method are required in either mode. Select all login methods you want to enable; none are selected initially. Non-interactive installation defaults to GitHub when no login configuration is supplied. `--workers-dev` skips zone/DNS/certificate operations and cannot be combined with `--application-domain`, `--zone`, or `--dedicated-zone`.
40
+
41
+ Read-only plans, workers.dev installations with the default API hostname, and supported lifecycle operations can use Cloudflare browser login and the system keychain. Installation that writes DNS or creates a zone needs a management API token. The interactive installer guides you to create one and paste it into a masked prompt; scripts use `CLOUDFLARE_API_TOKEN` or `CF_API_TOKEN`.
42
+
43
+ The installed platform needs a separate runtime token to provision resources for apps. The interactive installer prompts for it and the other setup values. For non-interactive installs, inject the variables listed in [Install from CI](../../guide/platform/installation/ci.md).
44
+
45
+ To enable email during install or upgrade, set both `NOSAM_EMAIL_SENDER_DOMAIN` and `NOSAM_EMAIL_SHARED_ZONE_ID`. bwf records the pair for later upgrades; supplying only one is an error.
46
+
47
+ Use `--dashboard-url https://dash.example.com` when deploying the optional user
48
+ dashboard separately. The URL must be an HTTPS origin without credentials, a
49
+ path, query, or fragment. bwf permits that origin's login callbacks and saves
50
+ it for later maintenance; it does not deploy a dashboard Worker. Omission keeps
51
+ an existing installation's saved dashboard origin.
52
+
53
+ `--plan` previews resource names, login methods, default app access, the login callback URL, database configuration, and credential requirements. An existing Hyperdrive shows its database and configuration name. Setup links are shown during guided credential setup. Completed previews save nonsecret installation choices locally. Rerun `bwf platform install` to choose a saved plan and review a fresh check of Cloudflare state, or run the install or resume command printed at the end. Started installations use their saved checkpoints; completed installations are excluded from the chooser. For login configuration, use either `--auth-config` or `--login-methods` with the Access protection flags.
54
+
55
+ App access is configured before traffic opens. With platform protection enabled,
56
+ the installer recommends reusing its company policy; otherwise it defaults to
57
+ public apps. Use `--app-access custom` to select separate hosting-account policies.
58
+ Public apps in a Default-Deny account receive scoped public Access rules. The
59
+ installer explains and collects the encrypted management credential when needed;
60
+ scripts supply `NOSAM_PLATFORM_APP_ACCESS_TOKEN` or `appAccess.tokenEnv` in the
61
+ authentication file. Upgrades preserve administrator settings.
62
+
63
+ New resources use `void-<name>-<role>` names; choose an unused installation name. The installer opens setup pages for missing credentials and reuses values already supplied.
64
+
65
+ During Access setup, choose existing company policies or **Create in Cloudflare**
66
+ for manual setup instructions and an account dashboard link. After you save the
67
+ policy and confirm completion, bwf reloads the list so you can select it and
68
+ continue in the same run. When bwf creates the Access applications, **Allow my
69
+ company’s email domain** creates an Allow policy for the domains you enter and
70
+ selects it. **Refresh list** reloads policies created in another window. Your
71
+ identity-provider choice and still-available policy selections are retained. If a
72
+ selected policy does not restrict sign-in to company identities, bwf explains why
73
+ and asks again.
74
+
75
+ Installation progress and partial credentials are saved encrypted locally. Rerun the installer to continue unfinished setup, or pass `--resume --name <id>`. Use lifecycle commands for completed installations.
76
+
77
+ Use an empty PostgreSQL database dedicated to the installation. You can correct a failed initial connection, but after the database is claimed or Hyperdrive is provisioned, commands reject a different URL.
78
+
79
+ Choose whether bwf creates Hyperdrive or uses an existing configuration. An existing Hyperdrive must point to the platform database with SQL result caching disabled. Supply a database owner URL for migrations. See [Use an existing Hyperdrive](../../guide/platform/installation/prerequisites.md#use-an-existing-hyperdrive) for setup and [Install from CI](../../guide/platform/installation/ci.md) for unattended inputs.
80
+
81
+ Recovery secrets are encrypted using your system keychain. Without one, supply a base64-encoded 32-byte `NOSAM_PLATFORM_RECOVERY_KEY`. Keep the original credentials in protected CI secrets for recovery.
82
+
83
+ If a newly created zone is waiting for registrar delegation, resume after it becomes active:
84
+
85
+ ```sh
86
+ bwf platform install --resume --name <installation-id>
87
+ ```
88
+
89
+ See [Self-host a bwf platform](../../guide/self-hosted-platform.md) for prerequisites, token scope, exact footprint, domain behavior, and an end-to-end walkthrough.
90
+
91
+ ## `bwf platform domain set` {#nosam-platform-domain-set}
92
+
93
+ ```sh
94
+ bwf platform domain set <domain> [--installation <id>] [--zone <domain>] [--dedicated-zone] [--plan] [--yes]
95
+ ```
96
+
97
+ Add an application domain to a workers.dev test platform. Domain-based installations remain the recommended default. The command detects the zone when possible, creates missing DNS and routes after confirmation, and checks HTTPS and project Zero Trust protection before making the domain canonical. If DNS, certificates, or protection are pending, rerun the same command to resume. `--plan` is read-only; non-interactive mutations require `--yes`.
98
+
99
+ Existing workers.dev URLs remain available, and the platform API origin, OAuth callback, projects, and deployments stay unchanged. The command verifies the running runtime token's Cache Purge permission for the new zone. A disabled platform stays disabled. Use the database URL from the original installation when administering from another machine. Replacing an already configured application domain is not supported. See [Adding a Domain](../../guide/platform/installation/domains.md#adding-a-domain).
100
+
101
+ ## Lifecycle commands {#lifecycle-commands}
102
+
103
+ Use these commands to recover, update, pause, or remove an installation:
104
+
105
+ ```sh
106
+ bwf platform discover [--account <id>] [--installation <id-or-name>]
107
+ bwf platform upgrade [id] [--runtime <path>] [--dashboard-url <origin>] [--custom-domains] [--runtime-logs <full|minimal>] [--storage-location <hint|automatic>] [--plan] [--yes]
108
+ bwf platform rollback [id] --runtime <earlier-path> [--from-runtime <current-path>] [--plan] [--yes]
109
+ bwf platform repair [id] [--runtime <path>] [--dashboard-url <origin>] [--custom-domains] [--auth-config <path>] [--plan] [--yes]
110
+ bwf platform disable [id] [--plan] [--yes]
111
+ bwf platform enable [id] [--runtime <path>] [--plan] [--yes]
112
+ bwf platform uninstall [id] [--plan] [--purge-data | --purge-resources] [--yes]
113
+ ```
114
+
115
+ `discover --installation` limits recovery and endpoint verification to one installation in a shared Cloudflare account.
116
+
117
+ Use the installation slug shown beside its name in `bwf platform list`. Installation IDs and saved connection IDs also work. Lifecycle commands require local installation records; use `discover` to restore them on another machine. Omit `id` when only one installation is configured, or choose from the interactive picker. Non-interactive commands need a slug or ID when several installations exist. Commands that make changes also require `--yes`; `--plan` only previews changes.
118
+
119
+ `upgrade --runtime-logs <full|minimal>` changes what runtime logs record; without it, upgrades keep the current setting. See [Choose what runtime logs record](../../guide/platform/installation/setup.md#runtime-logs).
120
+
121
+ `upgrade --storage-location <hint|automatic>` changes the default location hint for new project R2 buckets. Omission keeps the current setting; `automatic` clears it. Existing buckets stay in place. See [Choose a default storage location](../../guide/platform/installation/setup.md#choose-a-default-storage-location).
122
+
123
+ To add or explicitly change a separately deployed dashboard after installation,
124
+ use `repair --dashboard-url <origin>` or `upgrade --dashboard-url <origin>`.
125
+ Preview with `--plan` first. Existing Access protection must cover the configured
126
+ dashboard origin before maintenance can proceed. See [Optional Dashboard](../../guide/platform/installation/domains.md#optional-dashboard).
127
+
128
+ While first administrator setup is pending, `repair --auth-config <path>` replaces
129
+ the login settings from a file in the install format and prints a new setup code.
130
+ Interactive repair offers the same change with the saved values filled in. Login
131
+ methods and Access protection stay as installed. Run it on the computer that
132
+ installed the platform. See [First administrator sign-in fails](../../guide/platform/installation/maintenance.md#first-administrator-sign-in-fails).
133
+
134
+ After discovery on another machine, set `NOSAM_PLATFORM_DATABASE_URL`. See [Manage an installation from another machine](../../guide/platform/installation/maintenance.md#manage-an-installation-from-another-machine) for the secrets needed to recreate a missing Worker.
135
+
136
+ | Command | Behavior |
137
+ | ----------- | ----------------------------------------------------------------------------------------------------------- |
138
+ | `discover` | Verifies remote ownership and restores local installation records without downloading secrets |
139
+ | `repair` | Recreates missing resources owned by the installer |
140
+ | `upgrade` | Deploys the selected runtime and supported pending migrations |
141
+ | `rollback` | Restores a declared-compatible earlier runtime without reversing PostgreSQL migrations |
142
+ | `disable` | Blocks app traffic and the platform API without removing data; only admin status and sign-in stay available |
143
+ | `enable` | Redeploys and verifies the platform Workers, then restores traffic |
144
+ | `uninstall` | Blocks traffic and removes eligible resources, retaining data by default |
145
+
146
+ Repair and upgrade preserve disabled state. New, resumed, and previously disabled installations block user traffic until all target Workers pass verification; the installer's health probes can still run. Routes and custom domains remain attached.
147
+
148
+ Replacing platform Worker configuration changed outside bwf requires interactive approval. Follow [Platform Workers changed outside bwf](../../guide/platform/installation/maintenance.md#workers-changed-outside-nosam) if maintenance asks for it.
149
+
150
+ `--runtime` selects a custom platform build. Relative paths resolve from your current directory. bwf verifies the build before making changes; see [Platform Development](../../guide/platform/development/runtime.md#deploying-your-runtime) for creating one.
151
+
152
+ Without `--runtime`, the CLI uses its packaged platform version.
153
+
154
+ Platform migrations only move forward. bwf checks compatibility before updating the database and tells you if an intermediate release is needed.
155
+
156
+ An upgrade completes after the new Workers pass health checks. If rollout fails, bwf attempts to restore the previous Workers. Retrying does not repeat completed migrations.
157
+
158
+ `platform rollback` restores a compatible earlier runtime without reversing database migrations. Pass its files with `--runtime`; if the installed version is custom, also supply that version with `--from-runtime`. bwf refuses incompatible targets.
159
+
160
+ If project Zero Trust is on and no platform user exists yet, uninstall turns it off and deletes its Access applications first. Run it on the computer that installed the platform.
161
+
162
+ Uninstall verifies remote ownership before removing anything. Data resources are retained unless you pass `--purge-data`. Workers, the Queues they use, R2, AI Gateway, DNS records, routes, custom domains, adopted resources, external PostgreSQL, and zones are retained for manual review. `--keep-zone` is deprecated and has no effect; uninstall always keeps zones.
163
+
164
+ `--purge-resources` includes `--purge-data` and also deletes every other resource the installation created, including Workers, Queues, R2, AI Gateway, the platform DNS record, routes, custom domains, and installer-created Access resources. It removes only the Email Routing rules that send mail to the platform email gateway, and keeps zones, adopted resources, external PostgreSQL, other Email Routing settings, and API tokens. A route, custom domain, DNS record, or Access resource that no longer matches the installation's record is kept and listed. It refuses before any change while projects remain or resource reads are denied. Use the Edit permissions listed by `--plan`; read checks cannot verify them, so a denied deletion can stop uninstall after changes have begun. Rerun the same command to continue after an interruption, or after a plain or `--purge-data` uninstall stopped.
165
+
166
+ See [Disable and Uninstall](../../guide/platform/installation/uninstall.md#remove-retained-resources) for the full removal policy and the cleanup order.
@@ -0,0 +1,90 @@
1
+ ---
2
+ description: 'Inspect deployments, logs, and platform health, and preview changes before applying them.'
3
+ outline: deep
4
+ ---
5
+
6
+ # Platform Operations {#operator-deployments}
7
+
8
+ Use your administrator session for these commands. See [Platform Management](./platform.md#operator-commands) for platform selection, previews, and confirmation.
9
+
10
+ Find a deployment, inspect its manifest, or request cancellation:
11
+
12
+ ```sh
13
+ bwf platform deployment list [--project <id-or-slug>] [--status <status>] [--search <text>] [--page <n>] [--limit <n>]
14
+ bwf platform deployment show <id>
15
+ bwf platform deployment cancel <id>
16
+ bwf platform deployment migrate-assets <id> [--cursor <cursor>] [--plan|--yes]
17
+ ```
18
+
19
+ Cancellation applies while a deployment is pending, uploading, or migrating, and can be requested again while it is canceling. A deployment that has begun switching traffic, is compensating for a failure, or has finished cannot be canceled through this command.
20
+
21
+ `migrate-assets` copies a deployment's legacy assets to scoped R2 storage without changing application traffic. Use `--plan` to preview and `--cursor` to resume from a successful batch. Original assets remain in place.
22
+
23
+ Read its runtime logs with:
24
+
25
+ ```sh
26
+ bwf platform deployment logs <id> [--since <time>] [--cursor <cursor>] [--limit <n>] [--follow]
27
+ ```
28
+
29
+ The default is the last hour, oldest first, with up to 100 records. `--since` accepts a duration such as `10m`, `2h`, or `1d`, an ISO date, or epoch milliseconds. Set `--limit` from 1 to 500 and pass the response's `nextCursor` as `--cursor` to read another page.
30
+
31
+ `--follow` reads the remaining pages and checks for new logs every two seconds until you press Ctrl+C. It checks a five-minute overlap for delayed records and suppresses replayed rows. Records that arrive later may need a subsequent historical query. Following stops with an error if a window exceeds 10,000 records; use a narrower historical query in that case.
32
+
33
+ ## Builds {#operator-builds}
34
+
35
+ Inspect a build or read its output:
36
+
37
+ ```sh
38
+ bwf platform build show <id>
39
+ bwf platform build logs <id> [--since <sequence>] [--limit <n>] [--follow]
40
+ ```
41
+
42
+ Build logs start at sequence `0` and return up to 500 lines. Use the returned `lastSeq` as `--since` to continue; `--limit` accepts 1 to 500. Container log retrieval requires managed builds to be enabled. GitHub Actions builds return an external log URL.
43
+
44
+ Following waits for the final logs after the build becomes terminal. If completion cannot be confirmed within two minutes, the command exits with an error.
45
+
46
+ ## System {#operator-system}
47
+
48
+ Inspect activity, check service health, or review administrative changes:
49
+
50
+ ```sh
51
+ bwf platform system overview
52
+ bwf platform system health
53
+ bwf platform system cli-versions
54
+ bwf platform system asset-migrations [--page <n>] [--limit <n>]
55
+ bwf platform system events [--page <n>] [--limit <n>]
56
+ bwf platform system backfill-queue-tokens
57
+ bwf platform system sandbox-drain [--cursor <opaque-cursor>]
58
+ bwf platform system rotate-proxy-tokens [--project <id> | --all]
59
+ ```
60
+
61
+ `overview` shows platform totals and recent activity. `health` checks the configured services and database, and exits with a nonzero status if a check fails. `cli-versions` reports the CLI versions used by deployments.
62
+
63
+ `asset-migrations` inventories stored deployment assets and reports `needsMigration` and `invalid` counts. Use the response's pagination fields to read all entries.
64
+
65
+ `events` shows the administrator, target, and outcome of changes. A pending event means the outcome has not been recorded. Previews and session login/logout do not create these events. `backfill-queue-tokens` repairs older queue entries that are missing authentication tokens and supports `--plan` before applying the repair.
66
+
67
+ `sandbox-drain` removes legacy tenant-owned Sandbox resources. Use `--plan` to preview and `--yes` to apply, then pass `nextCursor` as `--cursor` to continue. Application traffic stays paused during cleanup.
68
+
69
+ `rotate-proxy-tokens` gives projects new platform credentials on their live Worker and the Workers kept for rollback, without a redeploy. Workers kept for rollback whose author can no longer deploy keep the old credentials. Use `--project <id>` for one project or `--all` for every project, with `--plan` to preview and `--yes` to apply. `--plan` alone shows every rotation that is still running. Each run does a bounded batch and the platform finishes the rest in the background; a rotation takes about 6 minutes per project, longer while a deploy is running. Use `--plan` to check progress until nothing is pending or failed. Running `--yes` again with `--project` or `--all` while a rotation is still running starts one more rotation for that project. When a rotation is finished, the previous credentials no longer work. Each rotation starts a new version of the project's live Worker, so WebSocket connections reconnect once.
70
+
71
+ Use the [platform lifecycle commands](./platform-installation.md#lifecycle-commands) to maintain your installation's Workers.
72
+
73
+ ## Hosted Workers {#operator-workers}
74
+
75
+ The following commands manage the Workers of the hosted bwf Cloud platform.
76
+ They are unavailable on a self-hosted installation; use the
77
+ [lifecycle commands](./platform-installation.md#lifecycle-commands) there instead.
78
+
79
+ ```sh
80
+ bwf platform worker list [--environment <production|staging>]
81
+ bwf platform worker show <worker-name> [--environment <production|staging>]
82
+ bwf platform worker rollback <worker-name> <version-id> [--environment <production|staging>]
83
+ bwf platform worker rollback-all [--environment <production|staging>]
84
+ bwf platform worker events [batch-id] [--environment <production|staging>]
85
+ ```
86
+
87
+ Use a name from `worker list`, such as `api` or `proxy`. `show` lists its
88
+ versions and current deployment. Preview either rollback with `--plan`, then
89
+ apply it interactively or with `--yes` in a script. `events` lists worker
90
+ operation events or inspects one batch by ID.
@@ -0,0 +1,159 @@
1
+ ---
2
+ description: 'Manage platform users, their projects, and the plans assigned to their accounts.'
3
+ outline: deep
4
+ ---
5
+
6
+ # Platform Users and Projects {#operator-users}
7
+
8
+ Use your administrator session for these commands. See [Platform Management](./platform.md#operator-commands) for platform selection, previews, and confirmation.
9
+
10
+ Find a user by login, email, or ID, then inspect their projects and usage:
11
+
12
+ ```sh
13
+ bwf platform user list [--search <text>] [--page <n>] [--limit <n>]
14
+ bwf platform user show <id>
15
+ ```
16
+
17
+ Use the same ID to change a plan, suspend or restore the account, or delete it:
18
+
19
+ ```sh
20
+ bwf platform user plan <id> <plan-id>
21
+ bwf platform user suspend <id> [--reason <text>]
22
+ bwf platform user restore <id>
23
+ bwf platform user delete <id>
24
+ ```
25
+
26
+ Suspending a user blocks their applications, including scheduled jobs and queue consumers. While the account is suspended, each queue message is retried about once an hour, and each retry uses one of its queue's retries. Messages that run out of retries are dropped: after about 3 hours with the default of 3 retries, and at once for a queue with `maxRetries: 0`. Restore an account suspended by mistake promptly; queue delivery resumes within about an hour. Deleting a user also deletes their project resources. A plan change updates resource limits while preserving any administrator suspension. It also applies the new plan's [AI Gateway logging](#ai-gateway-logging) default to the account's projects, up to 100 projects per run. If the account has more, or if that step fails, the command says so; run the same plan change again until it completes. Each run continues where the last one stopped.
27
+
28
+ The last active administrator cannot be deleted or suspended. Both previews and
29
+ actual mutations enforce this rule, including in the browser admin UI. Allowed
30
+ administrator removals revoke administrator access before resource cleanup; if
31
+ cleanup fails, access stays revoked and the partial result reports it.
32
+
33
+ ## Projects {#operator-projects}
34
+
35
+ List projects across the platform, filter them by owner, or inspect one project's resources:
36
+
37
+ ```sh
38
+ bwf platform project list [--user <user-id>] [--search <text>] [--page <n>] [--limit <n>]
39
+ bwf platform project show <id>
40
+ bwf platform project normalize <id> [--plan | --yes]
41
+ bwf platform project delete <id>
42
+ bwf platform project owner <project-id> <user-id>
43
+ bwf platform project ai-logging <project-id> <inherit|off|metadata|full> [--plan | --yes]
44
+ ```
45
+
46
+ Search matches a project's slug, ID, or owner's login. `show` includes resources, domains, the latest 10 deployments, and the latest 20 builds. `delete` removes the project and its resources.
47
+
48
+ If deployment reports that a project requires normalization, an operator can preview `normalize <id> --plan`, then apply it with `--yes`. It verifies the serving deployment and any recorded queue names before updating project records. It leaves traffic and Cloudflare resources in place and refuses changes while deployment or recovery is active. If a verified queue name differs from the expected delivery routing name, normalization refuses the change; reconcile that queue routing before retrying. If the serving deployment cannot be verified, investigate the reported route before retrying. Finish interrupted deployment recovery on the previous compatible platform runtime before upgrading a project whose active deployment is missing.
49
+
50
+ `owner` transfers a project to another registered user. Preview it with `--plan`; apply it interactively or with `--yes`. The preview reports active-work blockers and the account plan that will apply. The former owner becomes a project administrator, existing project-scoped CI deploy credentials are revoked, and usage already incurred remains with the former owner.
51
+
52
+ ### AI Gateway Logging
53
+
54
+ Administrators choose how AI Gateway logs a project's AI requests. Apps cannot change this setting.
55
+
56
+ | Mode | AI Gateway stores |
57
+ | ---------- | ------------------------------------------------------------------------------------- |
58
+ | `inherit` | Whatever the gateway is set to. This is the default. |
59
+ | `off` | No log entry. |
60
+ | `metadata` | Model, provider, status, token counts, cost, and duration, but no prompt or response. |
61
+ | `full` | A log entry with the prompt and response. |
62
+
63
+ `inherit` follows the installation gateway's own logging setting, which the platform does not read. A new installation creates its gateway with logging turned on, so `inherit` stores prompts and responses until you change the gateway in Cloudflare.
64
+
65
+ Each project uses the first setting that applies:
66
+
67
+ 1. The project's own setting, from `bwf platform project ai-logging`.
68
+ 2. The default of the owner's plan. See [Plans and Limits](../../guide/platform/administration/plans.md#ai-gateway-logging). An account whose plan is not in the catalog uses the default plan's setting.
69
+ 3. `inherit`.
70
+
71
+ Preview a change, then apply it:
72
+
73
+ ```sh
74
+ bwf platform project ai-logging <project-id> metadata --plan
75
+ bwf platform project ai-logging <project-id> metadata --yes
76
+ ```
77
+
78
+ The preview shows the current and new setting. The result names the setting, where it comes from, and when new requests are expected to follow it:
79
+
80
+ ```txt
81
+ AI logging for <project-id>: metadata (set on project; plan "pro" default: inherit)
82
+ New AI requests are expected to follow it by 14:03:20 UTC (normally within 2 minutes).
83
+ ```
84
+
85
+ Set the project back to `inherit` to remove its own setting and use the plan default again. Changes apply to new requests without redeploying.
86
+
87
+ `bwf platform project show <project-id>` reports the setting and whether it is applied:
88
+
89
+ ```txt
90
+ AI Gateway logging: metadata (from plan "pro") — applied
91
+ ```
92
+
93
+ | `state` | Meaning |
94
+ | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
95
+ | `applied` | New AI requests follow the setting. |
96
+ | `pending` | The setting is published. New requests are expected to follow it by the time shown. |
97
+ | `pending_plan_publish` | The plan default is still being published. Run `bwf platform config plans sync --yes`, or repeat the account's `user plan` change, to continue. |
98
+ | `drift` | The published setting differs from the saved one. An hourly check repairs it; to fix a project setting now, run `project ai-logging` again. |
99
+ | `unknown` | The published setting could not be read. Check again shortly. |
100
+
101
+ `show` prints the state in words, such as `pending (expected by 14:03:20 UTC)`. With `--json`, `aiLogging` holds `mode` (the project's own setting, or `inherit`), `planId`, `planKnown`, `defaultPlanId`, `planMode`, `effective`, `source` (`project`, `plan`, or `gateway`), `published`, `publishedAt`, and `state`.
102
+
103
+ #### What the Setting Covers
104
+
105
+ When an administrator sets a project's AI logging to `off` or `metadata`, the command prints the time by which new requests are expected to follow it (normally within 2 minutes). `bwf platform project show <project-id>` reports `applied` once that time has passed and the setting is published. From then on, for every new AI request the platform runs for that project (Workers AI calls, Markdown conversion and provider calls, from deployed Workers and from `bwf dev`), AI Gateway stores:
106
+
107
+ - `off`: no log entry.
108
+ - `metadata`: model, provider, status, token counts, cost and duration, but no prompt or response.
109
+
110
+ A plan default applies to a project once the plan change reports "AI logging published", then normally within 2 minutes.
111
+
112
+ If the platform cannot read the published setting, it refuses the AI request with status 503. `ai_logging_policy_unavailable` is temporary; the app can retry. `ai_logging_policy_invalid` means the published value is not valid; set the project's AI logging again. Until a change is published, the project keeps its previous behavior. `show` reports this as `pending_plan_publish` (a plan default not yet published to the project) or `drift` (a published setting that differs from the saved one). `pending` means the change is already published and is still reaching every location. On a new installation the previous behavior is full logging.
113
+
114
+ Not covered: requests already running, logs stored earlier, separately configured Logpush exports, billing details that Cloudflare always keeps for Unified Billing requests, and log retention, which Cloudflare sets per gateway. AI usage limits still apply in every mode. See [Cloudflare logging controls](https://developers.cloudflare.com/ai-gateway/observability/logging/).
115
+
116
+ If the command fails with `ai_logging_publish_failed`, this change was not saved; the message names the project setting that is still saved. With `ai_logging_publish_pending`, the setting was saved but not published, and the project keeps its previous behavior until it is. In both cases, run the same command again. A saved setting that is not published yet goes live at the next hourly repair even if you do not retry, so to cancel a pending change, set the previous value again.
117
+
118
+ Project settings need platform 1.8.0 or later. On an older platform, the CLI stops with "This platform does not support AI logging policies. Run `bwf platform upgrade`."
119
+
120
+ ## Signup Access {#operator-signup}
121
+
122
+ Inspect signup restrictions, open signup to everyone, or require an allowlist match:
123
+
124
+ ```sh
125
+ bwf platform signup show
126
+ bwf platform signup open
127
+ bwf platform signup restrict
128
+ ```
129
+
130
+ Add and remove GitHub or email entries by their type and pattern:
131
+
132
+ ```sh
133
+ bwf platform signup allow <github|email> <pattern> [--note <text>]
134
+ bwf platform signup disallow <github|email> <pattern>
135
+ bwf platform signup remove <github|email> <pattern>
136
+ ```
137
+
138
+ `remove` remains available as an alias for existing scripts. GitHub entries match a login. Email entries match an address or a domain pattern such as `*@example.com`, across sign-in providers. Quote wildcard patterns in your shell.
139
+
140
+ For an OIDC identity that has no verified email, grant access using its configured connection ID and stable provider subject:
141
+
142
+ ```sh
143
+ bwf platform signup allow identity <connection-id> <subject> [--note <text>]
144
+ bwf platform signup disallow identity <connection-id> <subject>
145
+ ```
146
+
147
+ Connection IDs are shown by `bwf platform config auth list`. Identity subjects match exactly and case-sensitively; wildcards, email inference, and account linking are not applied. The login method's domain or group restrictions must still pass, and a newly admitted account has the ordinary user role. Under invited/allowlisted signup, an empty allowlist blocks new accounts. Under company-approved signup, explicit grants admit people in addition to the company rules.
148
+
149
+ ## Invitations {#operator-invitations}
150
+
151
+ Invite people by email and track whether they have joined:
152
+
153
+ ```sh
154
+ bwf platform invitation list [--page <n>] [--limit <n>]
155
+ bwf platform invitation send <email[,email...]>
156
+ bwf platform invitation revoke <id>
157
+ ```
158
+
159
+ Send accepts up to 100 comma-separated addresses. Invitations grant signup access even if email delivery is unavailable or fails; delivery is reported separately. Share the platform's `/invite` page or `bwf connect '<platform URL>'` command yourself when no email is sent. Revoking a pending invitation removes its exact email grant. A broader domain entry can still allow that person to sign up.
@@ -0,0 +1,60 @@
1
+ ---
2
+ description: 'Turn Cloudflare Access on or off for project hostnames from an administrator session.'
3
+ outline: deep
4
+ ---
5
+
6
+ # Project Zero Trust {#operator-zero-trust}
7
+
8
+ Use your administrator session for these commands. See [Platform Management](./platform.md#operator-commands) for platform selection, previews, and confirmation.
9
+
10
+ Configure the installation-wide Cloudflare Access policy and project overrides:
11
+
12
+ ```sh
13
+ bwf platform zero-trust status [--check]
14
+ printf '%s' "$ACCESS_API_TOKEN" | bwf platform zero-trust configure \
15
+ --identity-providers <id[,id...]> \
16
+ --policies <id[,id...]> \
17
+ [--existing-projects <protected|public>] \
18
+ [--protect-new-projects] \
19
+ --token-stdin \
20
+ --yes
21
+ bwf platform zero-trust reconcile
22
+ bwf platform zero-trust disable
23
+
24
+ bwf platform zero-trust project-status <project-id>
25
+ bwf platform zero-trust project-protect <project-id>
26
+ bwf platform zero-trust project-public <project-id>
27
+ bwf platform zero-trust project-reconcile <project-id>
28
+ ```
29
+
30
+ New installations configure app access in `bwf platform install`. Use these
31
+ commands to inspect or change it later. To configure or renew public-only rules
32
+ for a Default-Deny account, omit identity policies and use `--public-apps`:
33
+
34
+ ```sh
35
+ printf '%s' "$ACCESS_API_TOKEN" | bwf platform zero-trust configure \
36
+ --public-apps --token-stdin --yes
37
+ ```
38
+
39
+ Add `--existing-projects public` when enabling from a disabled configuration.
40
+ Public-only rules cannot be combined with protected project choices. To switch an
41
+ already protected configuration to public-only rules, first disable it; Access may
42
+ block traffic during that transition in a Default-Deny account.
43
+
44
+ Mutations support `--plan`, `--yes`, and `--timeout`; use `--plan` instead of
45
+ `--yes` to inspect this change without applying it. The Access management token
46
+ is accepted only on standard input. Zero Trust uses the Cloudflare account that
47
+ hosts the platform. Omit `--protect-new-projects` to make new projects public
48
+ by default. `--existing-projects` is required when you enable Zero Trust and
49
+ rejected once it is enabled; later configuration changes keep each project's
50
+ protection. `status` reports saved state; `--check` also compares it with
51
+ Cloudflare Access. If status remains `configuring` or `disabling`, run
52
+ `bwf platform zero-trust reconcile` to resume the saved operation. Protected
53
+ projects support up to 100 custom domains.
54
+
55
+ The token needs **Access: Apps and Policies Write** plus **Access:
56
+ Organizations, Identity Providers, and Groups Read**, scoped to the platform's
57
+ Cloudflare account. Select at least one Allow policy that matches people by
58
+ identity; bwf rejects Bypass and Service Auth policies and rules that allow
59
+ Everyone or any service token. See [Project Zero Trust](../../guide/platform/administration/zero-trust.md)
60
+ for requirements and recovery.
@@ -0,0 +1,78 @@
1
+ ---
2
+ description: 'Select a platform, confirm changes, and run operator commands against that installation.'
3
+ outline: deep
4
+ ---
5
+
6
+ # Platform Management {#platform-management}
7
+
8
+ Nosam-managed projects deploy to an explicitly selected platform. Join one with [`bwf connect`](./auth.md#connect). Connections are stored per API origin, and credentials are scoped to that origin.
9
+
10
+ ## Connection commands {#connection-commands}
11
+
12
+ ```sh
13
+ bwf platform list
14
+ bwf platform use [id]
15
+ bwf platform status [id]
16
+ ```
17
+
18
+ `list` shows the currently selected platform first, followed by other saved platforms. For a platform with local installation records, its installation slug appears beside its name, such as `Cloudflare bwf (cloudflare)`. Select it with `bwf platform use cloudflare`. For a connected platform without a local installation slug, use its printed API URL.
19
+
20
+ `use` and `status` accept an installation slug, display name, saved ID, or API URL. If a slug or name matches several platforms, use the API URL to choose one. They auto-select the only configured platform; with multiple platforms they show a picker interactively and require an explicit selector in non-interactive use. A project with a recorded platform URL keeps using that platform when the global default changes.
21
+
22
+ For a self-hosted installation, `status <installation-id>` prints locally saved
23
+ lifecycle progress before checking the live API. The saved checkpoint may be out
24
+ of date. If live discovery fails during maintenance, the command still shows that
25
+ checkpoint and exits with an error; it does not confirm current availability.
26
+
27
+ ## Operator commands {#operator-commands}
28
+
29
+ Use `bwf platform` to administer the users and apps on your selected platform. Start with the [Platform Administration guide](../../guide/platform-administration.md) for signing in, giving people access, and investigating deployments.
30
+
31
+ Every command below accepts `--connection <slug-or-url>` to select a registered platform and `--json` for structured output. Display names and saved IDs also work. Without `--connection`, bwf uses `BWF_API_URL` if set, then the active platform connection. Application project files do not change this selection.
32
+
33
+ ### Making Changes {#making-changes}
34
+
35
+ Commands that change users, projects, signup access, invitations, or Workers show a preview before asking for confirmation:
36
+
37
+ ```sh
38
+ bwf platform user plan <user-id> pro --plan
39
+ bwf platform user plan <user-id> pro --yes
40
+ ```
41
+
42
+ `--plan` validates the change and prints its effect without applying it. `--yes` applies the change without prompting, which is required in scripts. Use one or the other; they cannot be combined. These flags also apply to deployment cancellation and maintenance commands, but not to authentication commands.
43
+
44
+ Each preview and apply request allows five minutes. Set `--timeout <seconds>` to an integer from 1 to 3600 to change that limit. Read requests and individual log polls allow 30 seconds.
45
+
46
+ bwf does not automatically retry changes. If a request loses its connection or times out, inspect the affected objects and `bwf platform system events` before repeating it. Partial results describe the work that completed and exit with a nonzero status.
47
+
48
+ ### Authentication {#operator-authentication}
49
+
50
+ Sign in, inspect your session, or sign out:
51
+
52
+ ```sh
53
+ bwf platform auth login [--provider <connection-id>] [--token-stdin]
54
+ bwf platform auth status
55
+ bwf platform auth logout
56
+ bwf platform auth token [--token-stdin]
57
+ ```
58
+
59
+ Browser login offers the platform's enabled methods; `--provider <connection-id>` selects one. Login saves a one-hour administrator session in your system keychain. Logout revokes that session and removes its local credential.
60
+
61
+ `auth token` prints your current operator token. With `--token-stdin`, it exchanges a full administrator API login session from standard input for a new operator token. `auth login --token-stdin` saves the exchanged token to the keychain instead of printing it.
62
+
63
+ For automation, supply `NOSAM_OPERATOR_TOKEN` with an explicit `BWF_API_URL` or `--connection`. Operator tokens are stored separately from application deployment credentials. The API checks your current administrator access on every request. See [Using Scripts](../../guide/platform/administration/operations.md#using-scripts) for an example.
64
+
65
+ ## Pagination and JSON {#pagination-and-json}
66
+
67
+ User, project, deployment, invitation, and event lists default to page `1` with 20 items. `--limit` accepts 1 to 100 for these lists. Their JSON responses include the page, limit, and total count.
68
+
69
+ With `--json`, results go to standard output and command errors go to standard error as JSON. Errors and partial failures exit with a nonzero status. An unhealthy `system health` result stays on standard output and also exits nonzero. Log following writes one JSON object per response, including each page and empty responses.
70
+
71
+ ## Platform Command Groups
72
+
73
+ - [Installation and maintenance](./platform-installation.md)
74
+ - [Plans and authentication configuration](./platform-config.md)
75
+ - [Users, projects, and signup access](./platform-users.md)
76
+ - [Project Zero Trust](./platform-zero-trust.md)
77
+ - [Deployments, builds, and system operations](./platform-operations.md)
78
+ - [Email administration](./platform-email.md)