@wildo-ai/framework-knowledge 1.1.10 → 1.1.11

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 (1062) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +4 -2
  4. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  5. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  6. package/dist/esm/framework-knowledge.definitions.js +459 -76
  7. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  8. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  9. package/dist/esm/framework-knowledge.research-provenance.d.ts +88 -0
  10. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
  11. package/dist/esm/framework-knowledge.research-provenance.js +140 -0
  12. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
  13. package/dist/esm/index.d.ts +2 -0
  14. package/dist/esm/index.d.ts.map +1 -1
  15. package/dist/esm/index.js +2 -0
  16. package/dist/esm/index.js.map +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  18. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  19. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  20. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +5 -2
  23. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +11 -6
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  27. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +9 -5
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +11 -7
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +4 -1
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +3 -3
  41. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +3 -2
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -2
  45. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
  47. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +2 -2
  49. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +2 -2
  51. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +26 -7
  53. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -6
  55. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  56. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  59. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  60. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  61. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +9 -3
  62. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  63. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  65. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
  66. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  67. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +1 -1
  69. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  70. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
  72. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +6 -4
  74. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  77. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  83. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  86. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  87. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  88. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -1
  89. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +2 -1
  91. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  95. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +9 -3
  97. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +8 -2
  99. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +8 -2
  101. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
  104. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  108. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
  110. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  113. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  115. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  116. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  117. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +95 -0
  118. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
  119. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +111 -0
  120. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
  121. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  123. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +4 -3
  124. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  125. package/dist/esm/source-anchor-grammar.d.ts +70 -0
  126. package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
  127. package/dist/esm/source-anchor-grammar.js +114 -0
  128. package/dist/esm/source-anchor-grammar.js.map +1 -0
  129. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  130. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  131. package/dist/knowledge/manifest.json +8 -8
  132. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  133. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  134. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  135. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  136. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +350 -23
  137. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -3
  138. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +248 -9
  139. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  140. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
  141. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +2 -2
  142. package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
  143. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +3 -3
  144. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +12 -1
  145. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +5 -2
  146. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +13 -4
  147. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +4 -3
  148. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +5 -0
  149. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +1 -1
  150. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +12 -0
  151. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +4 -3
  152. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +33 -5
  153. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +3 -3
  154. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +176 -22
  155. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +20 -3
  156. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +3 -2
  157. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +6 -2
  158. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +97 -23
  159. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  160. package/dist/knowledge/playbooks/refinement.document-facts/method.md +30 -3
  161. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -2
  162. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  163. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
  164. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  165. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  166. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  167. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +9 -2
  168. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +2 -2
  169. package/dist/knowledge/playbooks/top_down.business-model/method.md +6 -0
  170. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +2 -2
  171. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  172. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +12 -2
  173. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +1 -1
  174. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -2
  175. package/dist/knowledge/playbooks/top_down.definition/playbook.json +5 -4
  176. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
  177. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +3 -3
  178. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  179. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -1
  180. package/dist/knowledge/playbooks/top_down.risk-register/method.md +1 -1
  181. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -1
  182. package/dist/knowledge/playbooks/top_down.service-method/method.md +198 -0
  183. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +96 -0
  184. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +4 -0
  185. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +5 -4
  186. package/dist/knowledge/references/acp.execution-profile.md +9 -1
  187. package/dist/knowledge/references/application-maturity.config.md +1 -1
  188. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +55 -0
  189. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +13 -2
  190. package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
  191. package/dist/knowledge/references/backend.inbound-handlers.definition.md +426 -5
  192. package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
  193. package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
  194. package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
  195. package/dist/knowledge/references/build-plan.task-graph.config.md +238 -8
  196. package/dist/knowledge/references/business-model.pricing-plan.config.md +7 -0
  197. package/dist/knowledge/references/business-model.snapshot.validation.md +18 -0
  198. package/dist/knowledge/references/capability-composition.config.md +4 -3
  199. package/dist/knowledge/references/cli.market.generate-command.md +2 -1
  200. package/dist/knowledge/references/companion.technical-doc.service.md +166 -32
  201. package/dist/knowledge/references/engine.client-bundle.allow-list.md +14 -0
  202. package/dist/knowledge/references/engine.saas-technical-doc.config.md +1 -1
  203. package/dist/knowledge/references/engine.saas-website.config.md +16 -44
  204. package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
  205. package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
  206. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +4 -3
  207. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +22 -0
  208. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +45 -0
  209. package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
  210. package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
  211. package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
  212. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
  213. package/dist/knowledge/references/example.config.design-system.full.md +40 -116
  214. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
  215. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +70 -14
  216. package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
  217. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
  218. package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
  219. package/dist/knowledge/references/example.infra.environment-config.local.md +24 -0
  220. package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
  221. package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
  222. package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
  223. package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
  224. package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
  225. package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
  226. package/dist/knowledge/references/example.provider.backend-module-shape.md +10 -0
  227. package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
  228. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
  229. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
  230. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -1
  231. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
  232. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +52 -22
  233. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +81 -0
  234. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +19 -20
  235. package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
  236. package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
  237. package/dist/knowledge/references/example.website.blocks.section.md +20 -0
  238. package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
  239. package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
  240. package/dist/knowledge/references/example.website.demo.append.md +57 -0
  241. package/dist/knowledge/references/example.website.demo.approval.md +47 -0
  242. package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
  243. package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
  244. package/dist/knowledge/references/example.website.demo.connect.md +45 -0
  245. package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
  246. package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
  247. package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
  248. package/dist/knowledge/references/example.website.demo.transform.md +43 -0
  249. package/dist/knowledge/references/example.website.page.manifest.md +2 -6
  250. package/dist/knowledge/references/example.website.section.bento.md +27 -0
  251. package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
  252. package/dist/knowledge/references/example.website.section.factories.md +82 -0
  253. package/dist/knowledge/references/example.website.section.faq.md +17 -0
  254. package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
  255. package/dist/knowledge/references/example.website.section.hero.md +16 -0
  256. package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
  257. package/dist/knowledge/references/example.website.section.marquee.md +26 -0
  258. package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
  259. package/dist/knowledge/references/example.website.section.site-block.md +43 -0
  260. package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
  261. package/dist/knowledge/references/example.website.section.stats.md +23 -0
  262. package/dist/knowledge/references/example.website.section.steps.md +15 -0
  263. package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
  264. package/dist/knowledge/references/example.website.theme.composed.md +69 -0
  265. package/dist/knowledge/references/experience-plan.config.md +16 -0
  266. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +6 -0
  267. package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
  268. package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
  269. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +6 -0
  270. package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
  271. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +64 -0
  272. package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
  273. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +61 -2
  274. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +70 -0
  275. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +253 -0
  276. package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
  277. package/dist/knowledge/references/integration-plan.config.md +21 -1
  278. package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
  279. package/dist/knowledge/references/minions.tick-contract.md +2 -2
  280. package/dist/knowledge/references/placement-plan.config.md +75 -13
  281. package/dist/knowledge/references/platform.config.environment.deployment.md +9 -1
  282. package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -0
  283. package/dist/knowledge/references/platform.config.platform-key-management.md +206 -0
  284. package/dist/knowledge/references/platform.config.saas.md +106 -14
  285. package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
  286. package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
  287. package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
  288. package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
  289. package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
  290. package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
  291. package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
  292. package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
  293. package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
  294. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
  295. package/dist/knowledge/references/presets.models.surface-variant.md +10 -0
  296. package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
  297. package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
  298. package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
  299. package/dist/knowledge/references/presets.themes.compose-theme.md +46 -0
  300. package/dist/knowledge/references/roadmap.phase.config.md +2 -16
  301. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +131 -0
  302. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +77 -11
  303. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +158 -0
  304. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
  305. package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
  306. package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
  307. package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
  308. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
  309. package/dist/knowledge/references/saas.backend.domain-module.md +76 -1
  310. package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
  311. package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
  312. package/dist/knowledge/references/saas.backend.email.send.md +7 -0
  313. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +9 -1
  314. package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
  315. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
  316. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
  317. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
  318. package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
  319. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +207 -0
  320. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
  321. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +300 -3
  322. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +13 -2
  323. package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
  324. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
  325. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
  326. package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
  327. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
  328. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +27 -0
  329. package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
  330. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
  331. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
  332. package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
  333. package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
  334. package/dist/knowledge/references/saas.backend.system-access-service.md +242 -107
  335. package/dist/knowledge/references/saas.config.content-security-policy.md +1 -2
  336. package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
  337. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
  338. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
  339. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
  340. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
  341. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
  342. package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
  343. package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
  344. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
  345. package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
  346. package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
  347. package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
  348. package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
  349. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +18 -16
  350. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
  351. package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
  352. package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
  353. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +17 -3
  354. package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
  355. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
  356. package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
  357. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +10 -2
  358. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +7 -4
  359. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +17 -16
  360. package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
  361. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
  362. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +149 -0
  363. package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
  364. package/dist/knowledge/references/saas.frontend.resource-label-params.md +3 -1
  365. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +17 -11
  366. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -51
  367. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +9 -6
  368. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +141 -32
  369. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +66 -4
  370. package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
  371. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
  372. package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
  373. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
  374. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
  375. package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
  376. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
  377. package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
  378. package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
  379. package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
  380. package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
  381. package/dist/knowledge/references/saas.models.audit.trail-config.md +18 -5
  382. package/dist/knowledge/references/{saas.models.auth.service-provider-client-authentication.md → saas.models.auth.relationship-grantor-authentication.md} +54 -48
  383. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
  384. package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
  385. package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
  386. package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
  387. package/dist/knowledge/references/saas.models.config.organization-types.md +42 -82
  388. package/dist/knowledge/references/saas.models.conversation-threads.md +4 -3
  389. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +22 -0
  390. package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
  391. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +27 -0
  392. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +403 -0
  393. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +84 -0
  394. package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -1
  395. package/dist/knowledge/references/saas.models.engine-capabilities.md +28 -0
  396. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
  397. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
  398. package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
  399. package/dist/knowledge/references/saas.models.external-data-pipeline.md +81 -18
  400. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
  401. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +317 -0
  402. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
  403. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
  404. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +147 -0
  405. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
  406. package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
  407. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
  408. package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
  409. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +62 -0
  410. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +314 -0
  411. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
  412. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +62 -0
  413. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
  414. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +1 -0
  415. package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
  416. package/dist/knowledge/references/saas.models.flows.runnable-model.md +255 -0
  417. package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
  418. package/dist/knowledge/references/saas.models.http-api-binding.md +157 -42
  419. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
  420. package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
  421. package/dist/knowledge/references/saas.models.inbound-channels.md +4 -1
  422. package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
  423. package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
  424. package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
  425. package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
  426. package/dist/knowledge/references/saas.models.notifications.targets.md +25 -2
  427. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +58 -6
  428. package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
  429. package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
  430. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +73 -0
  431. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +48 -0
  432. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
  433. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
  434. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +911 -0
  435. package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
  436. package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
  437. package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
  438. package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
  439. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +224 -0
  440. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +277 -0
  441. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +113 -0
  442. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +68 -5
  443. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +67 -2
  444. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
  445. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +278 -40
  446. package/dist/knowledge/references/saas.models.provider-capabilities.md +33 -0
  447. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
  448. package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
  449. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +8 -0
  450. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +37 -0
  451. package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
  452. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
  453. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
  454. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
  455. package/dist/knowledge/references/saas.models.representative-activity.md +65 -0
  456. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +58 -2
  457. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
  458. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +57 -11
  459. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
  460. package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
  461. package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
  462. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
  463. package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
  464. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +99 -2
  465. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
  466. package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
  467. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
  468. package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
  469. package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
  470. package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
  471. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +9 -0
  472. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
  473. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +25 -0
  474. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
  475. package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
  476. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
  477. package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
  478. package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
  479. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -6
  480. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -4
  481. package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
  482. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +121 -0
  483. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +3 -2
  484. package/dist/knowledge/references/saas.models.systems-of-record.md +36 -1
  485. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
  486. package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
  487. package/dist/knowledge/references/saas.public-runtime.contract.md +34 -2
  488. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
  489. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
  490. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +275 -13
  491. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
  492. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +9 -0
  493. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +16 -2
  494. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
  495. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
  496. package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
  497. package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
  498. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +24 -2
  499. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
  500. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +19 -5
  501. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
  502. package/dist/knowledge/references/saas.website.astro.bridge.md +51 -14
  503. package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
  504. package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
  505. package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
  506. package/dist/knowledge/references/saas.website.astro.label-loader.md +38 -9
  507. package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
  508. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +48 -17
  509. package/dist/knowledge/references/saas.website.astro.site-context.md +17 -8
  510. package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
  511. package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
  512. package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
  513. package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
  514. package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
  515. package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
  516. package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
  517. package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
  518. package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
  519. package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
  520. package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
  521. package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
  522. package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
  523. package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
  524. package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
  525. package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
  526. package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
  527. package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
  528. package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
  529. package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
  530. package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
  531. package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
  532. package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
  533. package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
  534. package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
  535. package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
  536. package/dist/knowledge/references/saas.website.blog.bridge.md +98 -53
  537. package/dist/knowledge/references/saas.website.blog.collection-config.md +76 -24
  538. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
  539. package/dist/knowledge/references/saas.website.blog.frontmatter.md +104 -7
  540. package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
  541. package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
  542. package/dist/knowledge/references/saas.website.blog.index.md +43 -0
  543. package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
  544. package/dist/knowledge/references/saas.website.blog.post-renderer.md +113 -85
  545. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +181 -0
  546. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
  547. package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
  548. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +2 -1
  549. package/dist/knowledge/references/saas.website.config.site-context-loader.md +21 -1
  550. package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
  551. package/dist/knowledge/references/saas.website.consent.context.md +1 -1
  552. package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
  553. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
  554. package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
  555. package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
  556. package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
  557. package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
  558. package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
  559. package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
  560. package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
  561. package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
  562. package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
  563. package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
  564. package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
  565. package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
  566. package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
  567. package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
  568. package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
  569. package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
  570. package/dist/knowledge/references/saas.website.label-keys.format.md +2 -2
  571. package/dist/knowledge/references/saas.website.label-pack.validator.md +7 -8
  572. package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
  573. package/dist/knowledge/references/saas.website.legal.public-document-links.md +19 -4
  574. package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
  575. package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
  576. package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
  577. package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
  578. package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
  579. package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
  580. package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
  581. package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
  582. package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
  583. package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
  584. package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
  585. package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
  586. package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
  587. package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
  588. package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
  589. package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
  590. package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
  591. package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
  592. package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
  593. package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
  594. package/dist/knowledge/references/saas.website.page.context.md +9 -2
  595. package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
  596. package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
  597. package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
  598. package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
  599. package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
  600. package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
  601. package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
  602. package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
  603. package/dist/knowledge/references/saas.website.product.figures.md +320 -0
  604. package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
  605. package/dist/knowledge/references/saas.website.product.panels.md +324 -0
  606. package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
  607. package/dist/knowledge/references/saas.website.refs.section.md +2 -2
  608. package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
  609. package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
  610. package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
  611. package/dist/knowledge/references/saas.website.runtime.context.md +44 -17
  612. package/dist/knowledge/references/saas.website.section.component.md +21 -19
  613. package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
  614. package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
  615. package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
  616. package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
  617. package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
  618. package/dist/knowledge/references/saas.website.stacking.md +86 -0
  619. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
  620. package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
  621. package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
  622. package/dist/knowledge/references/service-method.config.md +270 -0
  623. package/dist/knowledge/references/website-plan.config.md +544 -32
  624. package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
  625. package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
  626. package/dist/knowledge/references/website-plan.page-routes.md +39 -0
  627. package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
  628. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +73 -9
  629. package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
  630. package/dist/knowledge/references/zod.decorators.data-categories.md +101 -11
  631. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +75 -6
  632. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +23 -1
  633. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
  634. package/dist/knowledge/references/zod.decorators.file-schema.md +6 -5
  635. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
  636. package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
  637. package/dist/knowledge/references/zod.decorators.schema-metadata.md +4 -0
  638. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +32 -4
  639. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +44 -5
  640. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +130 -9
  641. package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -8
  642. package/dist/knowledge/references/zod.factories.code.md +18 -9
  643. package/dist/knowledge/references/zod.factories.duration.md +23 -14
  644. package/dist/knowledge/references/zod.factories.money.md +24 -15
  645. package/dist/knowledge/references/zod.factories.phone.md +23 -14
  646. package/dist/knowledge/references/zod.factories.range.md +5 -1
  647. package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
  648. package/dist/knowledge/registries/framework-topics.json +2411 -139
  649. package/dist/knowledge/registries/playbooks.json +51 -30
  650. package/dist/knowledge/registries/source-tags.json +8500 -4768
  651. package/dist/knowledge/rules/database-migration-obligation.md +11 -5
  652. package/dist/knowledge/skills/INDEX.md +60 -33
  653. package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
  654. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +203 -0
  655. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
  656. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
  657. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
  658. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
  659. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
  660. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +15 -3
  661. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
  662. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
  663. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
  664. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +341 -0
  665. package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
  666. package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
  667. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
  668. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
  669. package/dist/knowledge/skills/application-database-migrations/SKILL.md +27 -9
  670. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
  671. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +6 -6
  672. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +124 -3
  673. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +90 -0
  674. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +59 -0
  675. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
  676. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +79 -2
  677. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +35 -1
  678. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
  679. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +3 -0
  680. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
  681. package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
  682. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
  683. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +189 -0
  684. package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
  685. package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
  686. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +127 -2
  687. package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
  688. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
  689. package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
  690. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +163 -0
  691. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +295 -0
  692. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
  693. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
  694. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +134 -33
  695. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
  696. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
  697. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +34 -7
  698. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
  699. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +37 -0
  700. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +178 -4
  701. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
  702. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +485 -61
  703. package/dist/knowledge/skills/config-app-shell/SKILL.md +57 -28
  704. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
  705. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
  706. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
  707. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
  708. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +17 -6
  709. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +24 -22
  710. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
  711. package/dist/knowledge/skills/config-design-system/SKILL.md +245 -162
  712. package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
  713. package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
  714. package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
  715. package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
  716. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +37 -0
  717. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +235 -0
  718. package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
  719. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
  720. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
  721. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +7 -1
  722. package/dist/knowledge/skills/config-saas/SKILL.md +2 -0
  723. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +11 -3
  724. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +18 -5
  725. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +314 -0
  726. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
  727. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +8 -0
  728. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +1 -2
  729. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1182 -0
  730. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +61 -0
  731. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +56 -11
  732. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
  733. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +106 -14
  734. package/dist/knowledge/skills/config-saas-backend/SKILL.md +5 -3
  735. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
  736. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
  737. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +155 -92
  738. package/dist/knowledge/skills/configure-billing/SKILL.md +14 -0
  739. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +10 -0
  740. package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
  741. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
  742. package/dist/knowledge/skills/email-add-template/SKILL.md +46 -5
  743. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +7 -0
  744. package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
  745. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
  746. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +71 -14
  747. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +95 -13
  748. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +9 -1
  749. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
  750. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +44 -16
  751. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
  752. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
  753. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
  754. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +281 -20
  755. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +70 -14
  756. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +451 -0
  757. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +406 -0
  758. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +201 -0
  759. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +172 -0
  760. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
  761. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +7 -0
  762. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +63 -0
  763. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +324 -7
  764. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +95 -6
  765. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +255 -0
  766. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
  767. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
  768. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +112 -16
  769. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
  770. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +264 -0
  771. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +133 -0
  772. package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
  773. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +91 -5
  774. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +45 -0
  775. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +14 -3
  776. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
  777. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +5 -4
  778. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +27 -17
  779. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +136 -14
  780. package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
  781. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
  782. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
  783. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
  784. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
  785. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +4 -1
  786. package/dist/knowledge/skills/inbound-channels/SKILL.md +66 -8
  787. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +34 -1
  788. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +78 -6
  789. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
  790. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +434 -6
  791. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
  792. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +1 -1
  793. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +24 -13
  794. package/dist/knowledge/skills/infra-environment-config/SKILL.md +107 -2
  795. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +9 -1
  796. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -0
  797. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +294 -0
  798. package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
  799. package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
  800. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
  801. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
  802. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
  803. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
  804. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
  805. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
  806. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
  807. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
  808. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +4 -2
  809. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
  810. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +9 -0
  811. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +9 -0
  812. package/dist/knowledge/skills/market-generation-cli/SKILL.md +2 -1
  813. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +2 -1
  814. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
  815. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
  816. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +40 -10
  817. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +57 -2
  818. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
  819. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
  820. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +150 -4
  821. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +9 -0
  822. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +81 -1
  823. package/dist/knowledge/skills/module-relationships/SKILL.md +50 -27
  824. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
  825. package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
  826. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1233 -0
  827. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
  828. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
  829. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +521 -0
  830. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +162 -0
  831. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +145 -0
  832. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
  833. package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
  834. package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
  835. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +67 -0
  836. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
  837. package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
  838. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +1 -1
  839. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
  840. package/dist/knowledge/skills/provider-backend-package/SKILL.md +138 -4
  841. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +32 -28
  842. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
  843. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +6 -0
  844. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +634 -0
  845. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +70 -0
  846. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +61 -2
  847. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
  848. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +9 -5
  849. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +9 -2
  850. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +47 -5
  851. package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
  852. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
  853. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +26 -14
  854. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
  855. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
  856. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
  857. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
  858. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
  859. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +256 -1
  860. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +71 -35
  861. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
  862. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
  863. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +132 -55
  864. package/dist/knowledge/skills/resource-add-resource/SKILL.md +49 -4
  865. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +58 -2
  866. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +137 -0
  867. package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
  868. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +102 -4
  869. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
  870. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
  871. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +6 -0
  872. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +323 -0
  873. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +18 -0
  874. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +159 -0
  875. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +60 -3
  876. package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
  877. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
  878. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +1 -1
  879. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +3 -2
  880. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +195 -23
  881. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +108 -2
  882. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +242 -107
  883. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +176 -10
  884. package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
  885. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +88 -50
  886. package/dist/knowledge/skills/resource-external-data/SKILL.md +280 -64
  887. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
  888. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
  889. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +71 -12
  890. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
  891. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +81 -18
  892. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +238 -49
  893. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
  894. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +145 -0
  895. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
  896. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
  897. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +61 -14
  898. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
  899. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
  900. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +39 -13
  901. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
  902. package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
  903. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +1 -1
  904. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +17 -4
  905. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
  906. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
  907. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +6 -0
  908. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +31 -1
  909. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +3 -1
  910. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +68 -5
  911. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +25 -0
  912. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +26 -10
  913. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
  914. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +9 -7
  915. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  916. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +79 -6
  917. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
  918. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +127 -12
  919. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -4
  920. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +32 -4
  921. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +44 -5
  922. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +116 -66
  923. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
  924. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +203 -18
  925. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +6 -0
  926. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +155 -76
  927. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +19 -17
  928. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +120 -1
  929. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
  930. package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
  931. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +168 -58
  932. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
  933. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
  934. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +151 -1
  935. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +144 -57
  936. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +131 -0
  937. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +57 -31
  938. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +56 -0
  939. package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
  940. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
  941. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
  942. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +42 -11
  943. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +141 -32
  944. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +66 -4
  945. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
  946. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
  947. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +9 -0
  948. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +15 -7
  949. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +71 -14
  950. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +19 -5
  951. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +14 -5
  952. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -1
  953. package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
  954. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +5 -0
  955. package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
  956. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +11 -4
  957. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +11 -2
  958. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +17 -3
  959. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +61 -25
  960. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +251 -78
  961. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1064 -192
  962. package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
  963. package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
  964. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
  965. package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
  966. package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
  967. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +39 -18
  968. package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
  969. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +18 -5
  970. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +84 -28
  971. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +67 -64
  972. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +58 -23
  973. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
  974. package/dist/knowledge/skills/website-label-pack/SKILL.md +24 -17
  975. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +112 -77
  976. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +24 -13
  977. package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
  978. package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
  979. package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
  980. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +255 -397
  981. package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
  982. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +28 -6
  983. package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
  984. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -326
  985. package/dist/knowledge/skills/website-page-authoring/SKILL.md +160 -67
  986. package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
  987. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +24 -3
  988. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
  989. package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
  990. package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
  991. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +48 -28
  992. package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
  993. package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
  994. package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
  995. package/dist/knowledge/skills/website-section-contact/SKILL.md +408 -185
  996. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
  997. package/dist/knowledge/skills/website-section-cta/SKILL.md +398 -234
  998. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
  999. package/dist/knowledge/skills/website-section-faq/SKILL.md +561 -302
  1000. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
  1001. package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
  1002. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +647 -274
  1003. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
  1004. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +572 -264
  1005. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
  1006. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +532 -233
  1007. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
  1008. package/dist/knowledge/skills/website-section-hero/SKILL.md +603 -332
  1009. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
  1010. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
  1011. package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
  1012. package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
  1013. package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
  1014. package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
  1015. package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
  1016. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
  1017. package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
  1018. package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
  1019. package/dist/knowledge/skills/website-section-pricing/SKILL.md +549 -378
  1020. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +77 -0
  1021. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
  1022. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +2 -1
  1023. package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
  1024. package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
  1025. package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
  1026. package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
  1027. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
  1028. package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
  1029. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
  1030. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
  1031. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
  1032. package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
  1033. package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
  1034. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +739 -315
  1035. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
  1036. package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
  1037. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
  1038. package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
  1039. package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
  1040. package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
  1041. package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
  1042. package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
  1043. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +183 -67
  1044. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +575 -57
  1045. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +1 -1
  1046. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +6 -94
  1047. package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
  1048. package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
  1049. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
  1050. package/dist/knowledge/topic-index.json +16442 -8572
  1051. package/package.json +4 -4
  1052. package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
  1053. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
  1054. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
  1055. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
  1056. package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
  1057. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
  1058. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
  1059. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
  1060. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
  1061. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
  1062. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "bottom_up.build-dispatch",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Bottom-up build dispatch — the SECOND build-execution playbook, the pivot from DECOMPOSING the build (the build-plan task graph) to DISPATCHING it: turning one ordered task into an actually-run, verified coding-agent run under the D4 dispatch contract. Reads the approved TYPED build-plan (`BuildPlanTaskGraph` — each task carries a closed target kind, ONE MetaWorkflow_FunctionalTopic, its skill refs, and DECLARED prerequisite task refs) and the current journey state, selects the READY tasks (`selectReadyBuildPlanTasks`: every declared prerequisite has landed — resolved by the host, never inferred from prose) and dispatches them as a WAVE: up to the application's build parallelism at once (`wildo workbench parallelism`, 5 by default; 1 = one workspace-mutating run at a time), in ONE shared worktree, each slot refilled as its run settles. Each task in the wave runs the same typed contract: (1) the runner builds the context pack (task brief + the task's skill pointers + the relevant journey/definition artifacts + introspected app reality + repo paths); (2) it runs ONE prompt turn against the coding agent over the Agent Client Protocol, in a session rooted at the app workspace (cwd = app root, so CLAUDE.md / .claude skills load naturally), answering the agent's permission requests within the execution profile's declared ceiling and refusing anything above it or outside the task's mutation scope; (3) it captures the change-set around the run (git baseline/post-run worktree snapshots → per-file attribution → a structured GitChangeSetCapture recorded on the task row); (4) it runs the VERIFY gate OUTSIDE the coding agent (a deterministic typecheck the runner maps onto the dispatch verification hook — pnpm exec tsc --noEmit — the trust-but-verify floor); (5) it records the result + applies the onFailure disposition (keep_and_flag: a failed/timed-out run keeps its captured change-set flagged for human triage, never a silent half-applied state). When the wave's runs have settled, the runner commits what their own accepts left as one change naming every run it carries, and re-runs ALONE each task whose finished product a sibling overwrote; each run's record names what overlapped it (`concurrency`, `interferenceSuspected`). One run of this playbook is one bounded wave; run it again for the next. This playbook PRODUCES the per-task dispatch contract + execution semantics; it authors no schemas and generates no code (the coding agent does that at dispatch time). It does NOT decompose the plan (that is the build-decompose playbook, upstream — it owns the task graph) and does NOT choose the wave's width (the build parallelism is the person's setting). A revert_changeset failure path is a later phase (revert is a MUTATING git op outside the read-only change-set carve-out, deliberately deferred).",
6
6
  "preconditions": [
@@ -19,7 +19,7 @@
19
19
  "outputs": [],
20
20
  "stepOutputs": [],
21
21
  "method": {
22
- "guidance": "# Build Dispatch — Build-Plan Tasks → Verified Coding-Agent Runs, in Parallel Waves\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **The build runs in parallel by default.** One run of this playbook starts a\n> **wave**: up to N build-plan tasks at once, N being the application's **build\n> parallelism** (`wildo workbench parallelism`, 5 unless the person set it). Each\n> task in the wave follows the same per-task contract — its own coding run, its\n> change-set captured, verified outside the coding agent, recorded, the failure\n> disposition applied. With a build parallelism of `1` a run dispatches exactly\n> ONE task, which is the single-flight mode. A `revert_changeset` failure path is\n> still a **later phase** (see the boundary section).\n\n## Where you are in the journey\n\nThis is the **second build-execution playbook** — the pivot from **decomposing the\nbuild** (the build-plan: the ordered coding-agent task graph) to **dispatching it**\n(turning one ordered task into an actually-run, verified coding-agent run). It runs\nin the **bottom-up phase**, after the build plan exists (`artifact_exists\nbuild-plan`) and the foundation step has authored the app's config and skeleton.\nYou are not re-opening the decomposition\nhere — you are turning one *approved, ordered* task into a *dispatched, verified*\nchange to the application.\n\nUpstream, the **build-decompose** playbook produced the ordered task graph you\nconsume. The **scale** playbook describes the same wave from the scheduling side —\nthe ready-set, the width, the reconciliation — and runs through the same runtime\nbranch as this one; prefer this playbook to start a build. **You author the task\ngraph neither here nor there** — see the boundary section.\n\n## The typed task you dispatch\n\nThe build plan is a typed family (`BuildPlanTaskGraph`): dispatch selects ONE\nREADY task (all declared prerequisite task refs have landed) and hands the\ncoding host exactly that task's `objective`, `target`, `produces`,\n`functionalTopic` and `skillRefs`. The host derives the physical\nallowed/prohibited paths and the fixed verification from the target kind;\nnothing in the task — and nothing in this method prose — authors a path, a\ncommand, a prompt or a runtime control.\n\n`target` and `produces` answer two different questions, and a task needs both.\n`target` is the WRITE SCOPE — where this run may edit, and several tasks\nlegitimately share one. `produces` is what the run is ACCOUNTABLE for: the\nartifacts whose presence in the application proves the task done. A task has\nlanded when every artifact it declares is present and committed, so a run that\nsatisfies the objective's prose without delivering those artifacts is not\nfinished — the plan will offer the task again.\n\n## Import Origins\n\n- `@wildo-ai/saas-specifications`\n\n## Source Excerpts\n\n### Origin Package: `@wildo-ai/saas-specifications`\n\n```typescript\n *\n * Versioning for the build-plan task-graph payload format itself. `V1` —\n * initial shape (one ordered `tasks` collection with typed targets and\n * declared prerequisites). The shape grows additively across versions; the\n * `version` field is the explicit marker for consumers that branch on era.\n */\nexport enum BuildPlanTaskGraphVersion {\n V1 = 'v1',\n}\n\n/** Stable prefix every build-plan task ref carries; the trusted runtime stamps it, a provider supplies only the slug. */\nexport const BUILD_PLAN_TASK_REF_PREFIX = 'build-task-';\n\n/**\n * WHAT a build task builds — a closed vocabulary, because the host derives\n * the physical mutation scope and verification policy from the target kind\n * and the model must never author those powers through free text.\n */\nexport enum BuildPlanTaskTargetKind {\n /** A whole application module (its shared-lib registration, backend module and frontend module skeletons). */\n MODULE = 'MODULE',\n /** One build stage of one resource: schema → config → ui-behavior → spec. */\n RESOURCE_STAGE = 'RESOURCE_STAGE',\n /** One relationship between two resources. */\n RELATIONSHIP = 'RELATIONSHIP',\n /** A companion-owned deterministic generation step (labels, email templates, logo or database migrations) interleaved by the build loop, never a coding-agent run. */\n COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',\n /**\n * Authoring one SHELL SURFACE's placement configuration from the accepted\n * placement plan — the settings rail, the sidebar, the user menu or the\n * command palette.\n *\n * Its own kind rather than a reuse of the neighbours, because none of them is\n * true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide\n * and belongs to no resource), not a RELATIONSHIP, and emphatically not a\n * COMPANION_GENERATION_STEP — that kind is documented as \"never a coding-agent\n * run\" and writing `settings-hub.config.ts` is exactly a coding-agent run.\n * Borrowing one would hand the host the wrong mutation scope and the wrong\n * verification, which is what the closed vocabulary exists to prevent.\n */\n SHELL_PLACEMENT = 'SHELL_PLACEMENT',\n /*\n * THE NON-RESOURCE SURFACES (#1490). Until 2026-09-22 the five kinds above were the whole\n * vocabulary, and every one of them is about a resource or the shell placement of one. The\n * decompose method meanwhile told the planner to emit tasks for views, navigation, the design\n * system, custom components, PDF templates, workers, minions, providers, the website and the\n * documentation — surfaces the framework's own composition scenarios and 85 of its 111 skills\n * already build. A task for any of them had no kind to declare, so it either declared none\n * (landing as RAN-not-PROVEN forever) or borrowed `MODULE` with a product the module scope could\n * not prove. The members below are those surfaces, one per write scope the host can derive.\n */\n /**\n * The FRONTEND and SPECIFICATION layers of one module — its composite, custom and chart views,\n * its custom components and their specifications.\n *\n * Narrower than `MODULE` on purpose: a view task never touches `shared-lib` or `backend-api`, so\n * handing it the four-layer scope also hands it four typechecks and the FK sweep for a change\n * that can only break the frontend and the specifications package.\n */\n MODULE_FRONTEND = 'MODULE_FRONTEND',\n /**\n * The BACKEND layer of one module beside its shared-lib declarations — PDF templates and their\n * bindings, backend addons (services, controllers, flows-actors), email definitions.\n *\n * Shared-lib is in scope because a PDF template is bound to a resource FIELD the config declares\n * (`generatedSummaryPdf`), and a backend addon usually declares its contract there first.\n */\n MODULE_BACKEND = 'MODULE_BACKEND',\n /**\n * ONE application-wide frontend configuration surface — navigation, the design system, the app\n * shell's composition, the global views — named by {@link FrontendConfigSurface}.\n *\n * Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the\n * shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES\n * the surface itself (which sidebar sections exist, which transitions the primary zone uses,\n * which palette the product carries). Same file for `APP_SHELL`, different question.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /** The marketing website workspace (`website/`), composed by the `add-website` scenario. Pages and sections are its products. */\n WEBSITE = 'WEBSITE',\n /**\n * The technical-documentation workspace (`technical-doc/`) and the specification package's\n * `technical-documentation/` declarations that feed it. Its generated tree is never written by a\n * task: the companion publishes into it, and the coding policy prohibits it by prefix.\n */\n TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',\n /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */\n WORKER = 'WORKER',\n /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */\n MINION = 'MINION',\n /**\n * Declaring one provider in the application — the SaaS config's provider scopes, the backend\n * package dependency, the frontend provider module and its companion contribution.\n *\n * Application-wide by construction: a provider binding names no module, and the four files it\n * may touch are the same for every provider.\n */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * The application's BILLING CATALOGUE — the `ProductDefinition[]` in `shared-lib/src/engine/product.ts`\n * (and the product specifications that document it), which the backend syncs to the billing\n * provider and the public website reads for its pricing page (#1835).\n *\n * Its own kind because none of the others is true of it: the catalogue is application-wide (a plan\n * belongs to no module), it lives in the shared library's ENGINE module that no `MODULE_*` scope\n * reaches, and before it existed a journey-built application reached its website with an EMPTY\n * catalogue, so the website re-typed the business model's prices by hand.\n */\n BILLING_CATALOG = 'BILLING_CATALOG',\n /**\n * The application's own ROLES — `CUSTOM_ROLES_CONFIGURATION` in `shared-lib/src/engine/roles.ts`, the\n * organization types that offer them (`availableOrgRoles` in `wildo.saas.config.ts`), their\n * specifications, and the `roles` of the operations they unlock (#2490).\n *\n * Its own kind because none of the others reaches it: the role table is application-wide and lives in\n * the shared library's ENGINE module. Before it existed a requirement naming user groups (\"office and\n * field users see different things\") had no task able to declare a role, so app-creation-test-005\n * modelled roles as an access-role RESOURCE that nothing reads.\n */\n APPLICATION_ROLES = 'APPLICATION_ROLES',\n}\n\n/**\n * WHICH application-wide frontend configuration surface a task composes — one file each, in\n * `frontend/src/config/`, and the coding policy resolves the member to that file exactly as\n * `SHELL_PLACEMENT` resolves a `PlacementSurface`.\n *\n * Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a\n * subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of\n * those live in one file. A configuration surface is WHICH FILE a composition task authors, and\n * navigation and the design system are not places anything is placed.\n */\nexport enum FrontendConfigSurface {\n /** `frontend/src/config/navigation.config.ts` — zones, transitions, overlay appearance. */\n NAVIGATION = 'NAVIGATION',\n /** `frontend/src/config/design-system.config.ts` — palette, typography, shell appearance from the brand's visual tone. */\n DESIGN_SYSTEM = 'DESIGN_SYSTEM',\n /** `frontend/src/config/app-shell.config.ts` — top bar, sidebar sections, quick switcher: the shell's COMPOSITION, not a placement into it. */\n APP_SHELL = 'APP_SHELL',\n /** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */\n GLOBAL_VIEWS = 'GLOBAL_VIEWS',\n}\n\n/**\n * The two shapes of guidance an application gives a person, and the file each is declared in.\n *\n * They are distinct because they are found differently: an onboarding DOCUMENT is embedded in a\n * screen (`EmbedOnboarding`) and is there whenever that screen is, while a guidance FLOW is started\n * by an event and shows once. Both are listed on the owning frontend module — `onboardingViews` and\n * `guidanceFlows`. Each kind has a CONVENTIONAL definitions file, which the authoring skill teaches\n * and a landing probe reads for the declared ref (alongside the module's `index.ts`, where a small\n * module may declare inline). A convention for generated applications: a hand-authored application\n * may keep its declarations elsewhere, and then simply is not probed by a build plan.\n */\nexport enum ApplicationGuidanceKind {\n /** `frontend/src/modules/<m>/app-level-views/onboarding-views.definitions.ts` — an embedded onboarding document. */\n ONBOARDING_DOCUMENT = 'ONBOARDING_DOCUMENT',\n /** `frontend/src/modules/<m>/app-level-views/guidance-flows.definitions.ts` — a triggered guidance flow. */\n GUIDANCE_FLOW = 'GUIDANCE_FLOW',\n}\n\n/**\n * The two worker runtimes the framework composes (`add-worker-node`, `add-worker-rust`). The\n * runtime decides the entry file a landing probe reads and whether a typecheck exists to run: a\n * Node worker is verified by its package typecheck, a Rust worker has no TypeScript to check and\n * the policy says so rather than inventing a command.\n *\n * Not the SaaS config's `WorkerRuntime`, which is a free-form `{ type, language }` pair an\n * application authors for deployment; this is the closed set a creation run can COMPOSE.\n */\nexport enum BuildPlanWorkerRuntime {\n NODE = 'NODE',\n RUST = 'RUST',\n}\n\n/**\n * WHERE a provider is bound — which runtime owner's scope its declaration lands in. Each member\n * is a different file, so a probe and a write grant both derive from it.\n *\n * Named after the SaaS config's own scope keys (`providers.scopes.backend`, `.companion`,\n * `.frontendServices.app`, `.frontendServices.website`), which the `add-provider` and\n * `add-file-picker-provider` scenarios write. Minion and worker scopes are deliberately absent:\n * a provider reaching a minion is declared on that minion's own `providers` block and belongs to\n * the {@link BuildPlanTaskTargetKind.MINION} task that builds it.\n */\nexport enum ProviderBindingScope {\n BACKEND = 'BACKEND',\n COMPANION = 'COMPANION',\n FRONTEND_APP = 'FRONTEND_APP',\n WEBSITE = 'WEBSITE',\n}\n\n/** The per-resource build stages, in their fixed order. */\nexport enum BuildPlanResourceStage {\n SCHEMA = 'SCHEMA',\n CONFIG = 'CONFIG',\n UI_BEHAVIOR = 'UI_BEHAVIOR',\n SPEC = 'SPEC',\n}\n\nconst SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n\n/**\n * The key of the domain-plan MODULE a task targets or produces (`deals`, `tasks-manager`). Same\n * slug grammar as the other keys, declared as its own schema because it names one thing — a\n * module — where the other slugs name resources, relationships, steps, workers and products.\n */\nconst ModuleRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n\n/**\n * The governed document a task produces, named as a COMPLIANCE-DOCUMENT CANDIDATE names it:\n * `document:<namespace>.<id>`, e.g. `document:public.privacy-notice`.\n *\n * **This field was `SlugSchema`, and a slug cannot name a governed document — so until 2026-09-16 no\n * build plan in any application could declare a document the engine catalog defines.** A slug forbids\n * the colon and the dot, the catalog's definitions are `document-definition:public.privacy-notice`,\n * and `selectAssuranceDocumentBlueprintForDocumentRef` joins the two namespaces by exact suffix — so\n * every authored `documentRef` resolved to NO blueprint, and a blueprint is what says which sections,\n * facts and claim guards the document owes. The two vocabularies were disjoint by construction.\n *\n * The cost is measured rather than theoretical. Wonder CRM's plan declares two such products\n * (`gdpr-data-handling-governance`, `terminal-access-governance`), neither of which names anything;\n * the first was dispatched, and its agent spent a full turn establishing — with a positive control —\n * that the document does not exist and could only be invented, which the authoring skill forbids.\n *\n * The bare slug is STILL ACCEPTED, and that is deliberate rather than tidiness left undone: tightening\n * this to the namespaced form alone would make every already-accepted plan carrying one fail to parse,\n * and a build plan that cannot be READ stops the whole lane — the gate\n * `application-creation-directive.md` forbids, for a task nobody can fix by re-running anything. A slug\n * simply resolves to no blueprint, so the dispatcher skips that task with a message naming the ref,\n * and the rest of the plan proceeds.\n */\nconst DocumentProductRefSchema = z.union([\n z.string().regex(/^document:[a-z0-9]+(?:-[a-z0-9]+)*\\.[a-z0-9]+(?:-[a-z0-9]+)*$/),\n SlugSchema,\n]);\n/**\n * A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is\n * also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses\n * any skill name outside `[a-z0-9-]+`, so a ref that does not match this shape\n * can never resolve to an installed skill.\n */\nconst SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\nconst NonEmptyStringSchema = z.string().trim().min(1);\n\n/**\n * WHAT a build task PRODUCES — the artifact whose presence in the application\n * proves the task is done.\n *\n * **This is not `target`, and the difference is the whole reason it exists.**\n * `target` is a WRITE SCOPE: the host turns it into the path prefixes a run may\n * mutate, and several tasks legitimately share one. `produces` is a PRODUCT\n * IDENTITY: it says which artifact this task, and no other, is accountable for.\n *\n * Measured 2026-09-10 on Wonder CRM (issue #597): `build-task-pipeline-view`\n * and `build-task-deal-follow-through-operation` carry BYTE-IDENTICAL targets\n * (`{ kind: MODULE, moduleRef: 'deals' }`), and 7 of that plan's 42 tasks share\n * 3 targets. Landing had been answered by narrowing the target to a module\n * DIRECTORY — which `wildo compose` commits on day one, and which cannot tell\n * two tasks apart even in principle. The loop reported 40 of 42 tasks landed\n * while no coding task had ever run, so `dispatch-next` skipped every one of\n * them and the phase-advance gate read a build that was all but complete.\n *\n * Like `target`, this stays SEMANTIC: a product names a resource, a field, a\n * relationship or a view — never a path, and never a command. The host owns the\n * translation from a product to the physical question it asks of the working\n * tree, exactly as it owns the translation from a target kind to path prefixes.\n * A model that could author the path could author its own mutation scope.\n */\nexport enum BuildPlanTaskProductKind {\n /**\n * Named fields on one resource's schema.\n *\n * The shape an ENRICHMENT task needs, and the reason a product cannot always\n * be \"a file\": every resource file already exists, written by the scaffold\n * with its self-described STARTER shape, so file presence answers nothing.\n * The FIELDS are what the task adds.\n */\n RESOURCE_SCHEMA_FIELDS = 'RESOURCE_SCHEMA_FIELDS',\n /**\n * One resource's declared operations — its registry presence, named by the verbs it gains.\n *\n * The VERBS, not the config file: `<r>.resources-config.ts` is written by the scaffold, so its\n * existence is satisfied before any task runs. That is the exact shape of the defect this\n * vocabulary replaces, and a kind that reproduced it would be worse than no kind at all.\n */\n RESOURCE_REGISTRATION = 'RESOURCE_REGISTRATION',\n /** One resource's frontend ui-behavior. */\n RESOURCE_UI_BEHAVIOR = 'RESOURCE_UI_BEHAVIOR',\n /**\n * One resource's specification, named by the fields it documents.\n *\n * The FIELDS, for the same reason as {@link RESOURCE_REGISTRATION}: every resource is scaffolded\n * with a `*.resource.specification.ts` documenting only the starter shape, so file existence\n * proves nothing about the task that was meant to enrich it.\n */\n RESOURCE_SPECIFICATION = 'RESOURCE_SPECIFICATION',\n /** One relationship edge between two resources, named by the domain plan's `relationshipRef`. */\n RESOURCE_RELATIONSHIP = 'RESOURCE_RELATIONSHIP',\n /** One named custom operation on one resource. */\n RESOURCE_OPERATION = 'RESOURCE_OPERATION',\n /** One named application-level view. */\n APPLICATION_VIEW = 'APPLICATION_VIEW',\n /** One named governed application document (a compliance notice, a governance statement). */\n APPLICATION_DOCUMENT = 'APPLICATION_DOCUMENT',\n /** One application module, registered across the layer registries under one module identity. */\n APPLICATION_MODULE = 'APPLICATION_MODULE',\n /*\n * THE NON-RESOURCE PRODUCTS (#1490). Each names an artifact of a surface the five target kinds\n * above `MODULE_FRONTEND` could not express, and each is probed by the host from committed bytes —\n * a declaration in the one file that registers it, never a directory a scenario already wrote.\n */\n /**\n * Named declarations in ONE application-wide frontend configuration file — a sidebar section\n * ref the app shell gains, a zone the navigation config declares, a token the design system sets.\n *\n * The DECLARATIONS, never the file: every `frontend/src/config/*.config.ts` is written by\n * `wildo init`, so its presence is true before any task runs. Same reasoning as\n * {@link RESOURCE_SCHEMA_FIELDS}, one level up.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /**\n * One composite view of one resource — the cross-resource surface a resource's ui-behavior\n * declares under `compositeViews`. Distinct from {@link APPLICATION_VIEW}, which is\n * application-level and owned by a module rather than a resource.\n */\n RESOURCE_COMPOSITE_VIEW = 'RESOURCE_COMPOSITE_VIEW',\n /** One custom operation or execution view of one resource, bound in its ui-behavior. */\n RESOURCE_CUSTOM_VIEW = 'RESOURCE_CUSTOM_VIEW',\n /** One chart view of one resource, declared under its ui-behavior's `chartViews`. */\n RESOURCE_CHART_VIEW = 'RESOURCE_CHART_VIEW',\n /** One custom frontend component, registered by `componentRef` in the module's or the engine's registrations. */\n CUSTOM_COMPONENT = 'CUSTOM_COMPONENT',\n /**\n * One milestone a module declares — the moment the application recognises and celebrates.\n *\n * Named by its identifier, which is what the module's `milestones.ts` declares\n * (`first-project-created` is spelled `FIRST_PROJECT_CREATED` there). The module FILE is not the\n * product: a module may carry milestones before this task runs, and only the identifier says this\n * one landed.\n */\n APPLICATION_MILESTONE = 'APPLICATION_MILESTONE',\n /** One onboarding document or guidance flow a module declares, named by its ref. */\n APPLICATION_GUIDANCE = 'APPLICATION_GUIDANCE',\n /** One PDF template bound to one resource's generated-file field. */\n PDF_TEMPLATE = 'PDF_TEMPLATE',\n /**\n * One worker's JOBS — the named handlers its entry file declares.\n *\n * The jobs, not the package: `add-worker-node` writes the package, so its directory proves\n * nothing. What a coding task adds is behaviour, and behaviour is a symbol in the entry file.\n */\n APPLICATION_WORKER = 'APPLICATION_WORKER',\n /** One minion's BEHAVIOURS — the named tick handlers its entry file declares. Same reasoning as the worker. */\n APPLICATION_MINION = 'APPLICATION_MINION',\n /** One provider declared in one runtime owner's scope. */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * One product of the application's billing catalogue — a plan, add-on or purchase the application\n * sells — named by its catalogue `key`, which the catalogue file declares (`key: 'team'`).\n *\n * The KEY, not the file: `wildo init` writes `product.ts` with an empty catalogue, so the file proves\n * nothing. Written from the accepted business model's pricing plans, with the plan's price as typed\n * money and the pricing-surface facts (recommended, price disclosure, availability) the plan implies.\n */\n APPLICATION_BILLING_PRODUCT = 'APPLICATION_BILLING_PRODUCT',\n /**\n * One data seed a module declares — rows the application creates for itself, named by the seed's\n * `seedKey` (`crm:demo-customers`).\n *\n * The seed is its own file, `backend-api/src/modules/<module>/seeds/<seedKey with ':' as '.'>.seed.ts`,\n * and it lands only once the module registers it — a seed file nothing imports never runs. Its\n * {@link BuildPlanDataSeedContent} says whether it is REFERENCE data the application needs everywhere\n * or DEMONSTRATION data that must never reach production.\n */\n APPLICATION_DATA_SEED = 'APPLICATION_DATA_SEED',\n /** One website page, registered in the website root config by its manifest. */\n WEBSITE_PAGE = 'WEBSITE_PAGE',\n /** One section of one website page, declared in that page's sections file. */\n WEBSITE_SECTION = 'WEBSITE_SECTION',\n /**\n * One authored documentation chapter — a consumer guide the specifications package declares\n * for the documentation portal to publish (#874's publication input).\n */\n DOCUMENTATION_CHAPTER = 'DOCUMENTATION_CHAPTER',\n /**\n * One inbound CHANNEL handler — the code that decides what a message arriving on a channel causes\n * (#1832). Named by the handler's `ref` (`matters.mail-intake`), which the handler file spells and whose\n * file NAME is derived from it, so the module index's import of that file is what proves the handler is\n * registered. Produced once per channel the integration plan declares (`inboundChannels`).\n */\n INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',\n /**\n * One role the application declares, named by its role name (`FIELD_TECHNICIAN`), which is its key in\n * `CUSTOM_ROLES_CONFIGURATION`. The NAME, not the file: `wildo init` writes `roles.ts` with an empty\n * table, so the file proves nothing (#2490).\n */\n APPLICATION_ROLE = 'APPLICATION_ROLE',\n}\n\n\n/**\n * What a data seed's rows ARE, which decides where they may exist.\n *\n * - `REFERENCE` — rows the application needs to work wherever it runs: a closed list, a default\n * record, a system template. Every environment, production included.\n * - `DEMONSTRATION` — sample rows that make a freshly created application look lived-in (customers,\n * projects, a few records per list). They must never sit beside real rows, so the seed declares\n * `allowedApplicationEnvironments` without `production`, and the task lands only once it does.\n */\nexport enum BuildPlanDataSeedContent {\n REFERENCE = 'REFERENCE',\n DEMONSTRATION = 'DEMONSTRATION',\n}\n\n/**\n * A data seed's key: kebab-case segments joined by `:` (`crm:demo-customers`), the convention a\n * `DataSeedDefinition` documents. Constrained here because the seed's FILE is derived from it.\n */\n/**\n * An application role's name, as `CUSTOM_ROLES_CONFIGURATION` keys it: upper snake case (`FIELD_TECHNICIAN`).\n * A core role (`ORG_MEMBER`, `APP_ADMIN_SUPER_ADMIN`) is not something an application declares, so the\n * product refuses one: a plan naming it would claim to create a role the engine already owns.\n */\nexport const APPLICATION_ROLE_NAME_PATTERN: RegExp = /^[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*$/;\nconst CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);\n\nexport const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;\n\n/**\n * One artifact a task is accountable for. Closed by construction: a product the\n * host cannot ask a question about is a product that can never be shown to have\n * landed, so the vocabulary only grows alongside the resolver that answers it.\n */\nexport const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /**\n * At least one field, because a task that enriches a schema with nothing is\n * the vacuity this whole field exists to stop: it would land the moment the\n * scaffold existed, which is the defect being fixed.\n */\n fieldRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_REGISTRATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SPECIFICATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, fieldRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP).systemEnum('BuildPlanTaskProductKind'),\n relationshipRef: SlugSchema,\n /*\n * The two resources the edge relates, NAMED rather than parsed out of the ref.\n *\n * A ref is `<source>-<target>` by convention and that convention is not invertible:\n * `next-step-deal` splits as (`next`, `step-deal`) or (`next-step`, `deal`) and only the domain\n * plan knows which. The domain plan already carries both, so the plan passes them on instead of\n * making the host guess — a host that guesses wrong probes for a resource that does not exist\n * and reports the task permanently unlanded.\n */\n sourceResourceRef: SlugSchema,\n targetResourceRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_OPERATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_VIEW).systemEnum('BuildPlanTaskProductKind'), viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DOCUMENT).systemEnum('BuildPlanTaskProductKind'), documentRef: DocumentProductRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MODULE).systemEnum('BuildPlanTaskProductKind'), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG).systemEnum('BuildPlanTaskProductKind'),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n /** At least one, for the same vacuity reason as a schema's `fieldRefs`: the file exists on day one. */\n declarationRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CHART_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, chartRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.CUSTOM_COMPONENT).systemEnum('BuildPlanTaskProductKind'), componentRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MILESTONE).systemEnum('BuildPlanTaskProductKind'), milestoneRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_GUIDANCE).systemEnum('BuildPlanTaskProductKind'),\n /** Which definitions file carries it — a document and a flow live in different ones. */\n guidanceKind: z.enum(ApplicationGuidanceKind).systemEnum('ApplicationGuidanceKind'),\n guidanceRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PDF_TEMPLATE).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */\n templateRef: NonEmptyStringSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),\n providerRef: SlugSchema,\n scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_ROLE).systemEnum('BuildPlanTaskProductKind'),\n roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).refine((roleRef) => !CORE_ROLE_NAMES.has(roleRef), {\n message: 'A core role is the engine\\'s; an application role needs a name of its own.',\n }),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DATA_SEED).systemEnum('BuildPlanTaskProductKind'),\n seedKey: z.string().regex(DATA_SEED_KEY_PATTERN),\n /** The resource whose rows the seed writes — the `resourceType` it declares. */\n resourceRef: SlugSchema,\n content: z.enum(BuildPlanDataSeedContent).systemEnum('BuildPlanDataSeedContent'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER).systemEnum('BuildPlanTaskProductKind'),\n /** The channel the handler serves — one the integration plan declared. Email is the only declarable channel. */\n channel: z.literal(InboundChannelKind.EMAIL).systemEnum('InboundChannelKind'),\n /** The handler's `ref`, exactly as `inboundHandlerRef()` will accept it. */\n handlerRef: z.string().regex(INBOUND_HANDLER_REF_PATTERN),\n }),\n]);\nexport type BuildPlanTaskProduct = z.infer<typeof BuildPlanTaskProductSchema>;\n\n/**\n * Every artifact identity a product claims — one string per artifact, not one\n * per product, because a product may claim several.\n *\n * `RESOURCE_SCHEMA_FIELDS` is why this returns a list. Two tasks may both enrich\n * one resource's schema (a domain shape and a billing concern, say), and that is\n * legitimate; what must never overlap is the FIELDS. Comparing whole products\n * would refuse the legitimate pair, and comparing only the resource would let two\n * tasks claim one field and make landing ambiguous again.\n *\n * Derived from the product's own members rather than stored, and total over the\n * vocabulary, so a kind added tomorrow must state its identity here or fail to\n * compile — it cannot be silently treated as equal to its siblings.\n */\nexport function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): readonly string[] {\n switch (product.kind) {\n case BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_REGISTRATION:\n return product.operationRefs.map((operationRef) => `${product.kind}:${product.resourceRef}:${operationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_SPECIFICATION:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR:\n return [`${product.kind}:${product.resourceRef}`];\n case BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP:\n return [`${product.kind}:${product.relationshipRef}`];\n case BuildPlanTaskProductKind.RESOURCE_OPERATION:\n return [`${product.kind}:${product.resourceRef}:${product.operationRef}`];\n case BuildPlanTaskProductKind.APPLICATION_VIEW:\n return [`${product.kind}:${product.viewRef}`];\n case BuildPlanTaskProductKind.APPLICATION_DOCUMENT:\n /*\n * The ref AS AUTHORED, so a slug and a namespaced ref are different artifact identities even\n * where they mean the same document — the duplicate-artifact refusal cannot see two tasks\n * claiming one document if they spell it differently. Not normalisable: a slug carries no\n * namespace, so nothing can recover `public.` from `privacy-notice`. It costs nothing today\n * because a slug names no catalogued document at all, and the dispatcher skips such a task.\n */\n return [`${product.kind}:${product.documentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MODULE:\n return [`${product.kind}:${product.moduleRef}`];\n // One identity per DECLARATION, like schema fields: two tasks may compose one config file as\n // long as they declare different things in it.\n case BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG:\n return product.declarationRefs.map((declarationRef) => `${product.kind}:${product.configSurface}:${declarationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW:\n case BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.viewRef}`];\n case BuildPlanTaskProductKind.RESOURCE_CHART_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.chartRef}`];\n case BuildPlanTaskProductKind.CUSTOM_COMPONENT:\n return [`${product.kind}:${product.componentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MILESTONE:\n return [`${product.kind}:${product.milestoneRef}`];\n // The ref alone: a document and a flow sharing one ref is still one guidance identity, and the\n // runtime keys a person's saved state by it — two artifacts claiming it would collide there too.\n case BuildPlanTaskProductKind.APPLICATION_GUIDANCE:\n return [`${product.kind}:${product.guidanceRef}`];\n case BuildPlanTaskProductKind.PDF_TEMPLATE:\n return [`${product.kind}:${product.resourceRef}:${product.templateRef}`];\n case BuildPlanTaskProductKind.APPLICATION_WORKER:\n return product.jobRefs.map((jobRef) => `${product.kind}:${product.workerRef}:${jobRef}`);\n case BuildPlanTaskProductKind.APPLICATION_MINION:\n return product.behaviorRefs.map((behaviorRef) => `${product.kind}:${product.minionRef}:${behaviorRef}`);\n // The SCOPE is part of the identity: one provider bound on the backend and on the website is two artifacts.\n case BuildPlanTaskProductKind.PROVIDER_BINDING:\n return [`${product.kind}:${product.scope}:${product.providerRef}`];\n case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:\n return [`${product.kind}:${product.productKey}`];\n case BuildPlanTaskProductKind.APPLICATION_ROLE:\n return [`${product.kind}:${product.roleRef}`];\n // The key alone: two seeds may write one resource, and the key is what the seed run ledger tracks.\n case BuildPlanTaskProductKind.APPLICATION_DATA_SEED:\n return [`${product.kind}:${product.seedKey}`];\n case BuildPlanTaskProductKind.WEBSITE_PAGE:\n return [`${product.kind}:${product.pageRef}`];\n case BuildPlanTaskProductKind.WEBSITE_SECTION:\n return [`${product.kind}:${product.pageRef}:${product.sectionRef}`];\n case BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER:\n return [`${product.kind}:${product.chapterRef}`];\n case BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER:\n return [`${product.kind}:${product.handlerRef}`];\n default: {\n const unhandled: never = product;\n throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);\n }\n }\n}\n\n/**\n * The skill every billing-catalogue task is authored with (#1835): the product-catalogue contract, the\n * money encoding (minor units), and the pricing-surface facts. The dispatch derives it from an\n * `APPLICATION_BILLING_PRODUCT` product whatever the decomposer wrote, so an agent writing the catalogue\n * the backend sells from is never without it.\n */\nexport const BILLING_CATALOG_SKILL_REF = 'configure-billing';\n\n/**\n * The skill every application-roles task is authored with (#2490): the role table, the organization\n * types that offer a role, and the operation roles that make it matter. The dispatch derives it from an\n * `APPLICATION_ROLE` product whatever the decomposer wrote.\n */\nexport const APPLICATION_ROLES_SKILL_REF = 'application-roles-authoring';\n\n/**\n * The skill every data-seed task is authored with (#2234): levels, modes, business keys, and the\n * environment restriction that keeps demonstration rows out of production. The dispatch derives it from\n * an `APPLICATION_DATA_SEED` product whatever the decomposer wrote.\n */\nexport const DATA_SEED_SKILL_REF = 'seeding-authoring';\n\n/**\n * The skill every PDF-template task is authored with (#2495): the template contract, the file field it fills, and\n * where the generated file is stored. The dispatch derives it from a `PDF_TEMPLATE` product whatever the decomposer\n * wrote.\n */\nexport const PDF_TEMPLATE_SKILL_REF = 'pdf-template-authoring';\n\n/**\n * The skill a resource CONFIG task carries when the resource DECLARES personal data (#2495): its retention binding\n * lives in that configuration file, and storage limitation is a duty about personal data. The dispatch reads the\n * declaration from the resource's schema (the engine's personal-data markers), whatever the decomposer wrote.\n */\nexport const RESOURCE_RETENTION_SKILL_REF = 'resource-retention-binding';\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: ModuleRefSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: ModuleRefSchema,\n relationshipRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),\n /** The companion generation step this task runs (e.g. i18n-labels, email-templates); resolved by the companion, never by a coding agent. */\n generationStepRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),\n /**\n * Which shell surface this task authors — the placement family's OWN\n * `PlacementSurface`, deliberately not a build-plan copy of it.\n *\n * A copy was written first and was a defect, caught by probing the landing\n * renderer rather than by any test: `PlacementAddress` discriminates on\n * `surface` with `z.literal(...)` per option, so only the VALUES survive into\n * the schema, and the renderer resolves a discriminator by matching that value\n * SET against the exported enums. Two enums with identical values made the\n * match ambiguous, the renderer correctly refused to guess an owner, and the\n * address discriminator became unnameable — a landed placement plan would have\n * emitted `surface: \"SETTINGS_HUB\"` as a bare string instead of\n * `PlacementSurface.SETTINGS_HUB`. One concept, one named source.\n */\n surface: z.enum(PlacementSurface).systemEnum('PlacementSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_FRONTEND), moduleRef: ModuleRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_BACKEND), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_FRONTEND_CONFIG),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.WEBSITE) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.WORKER),\n /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */\n workerRef: SlugSchema,\n runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.MINION),\n /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */\n minionRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),\n]);\nexport type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;\n\n/**\n * One ordered build task. It names WHAT to build and WHY; it never carries\n * HOW (no paths, commands, prompts, cwd, model, profile). The host resolves\n * the physical allowed/prohibited paths and the fixed verification from the\n * target kind, and the installed skills from `skillRefs` against the app\n * knowledge catalog.\n *\n * Dependency readiness is DECLARED as prerequisite task refs and RESOLVED by\n * the host (a prerequisite is satisfied when its task has landed), never a\n * solved DAG the model must get right.\n */\nexport const BuildPlanTaskSchema = z.strictObject({\n /** `build-task-<slug>`, stamped by the trusted runtime. */\n taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),\n /**\n * One sentence of intent: what this task delivers.\n *\n * Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also\n * hold. A display decorator mutates the instance it is applied to, and the workbench gives those\n * refs a receding identifier look, which the objective sentence then took too.\n */\n objective: z.string().trim().min(1),\n target: BuildPlanTaskTargetSchema,\n /**\n * The artifacts this task is accountable for — what proves it done.\n *\n * Coding tasks should declare at least one product that composition did not already\n * write. A target is a shared mutation scope; its scaffolded file is not evidence\n * that this task's intended work exists. Products identify the output to probe.\n *\n * Empty declarations remain representable and produce the advisory\n * `TASK_DECLARES_NO_PRODUCT`. The host may advance after a COMPLETED durable run,\n * while naming the task in `unverifiableLandedTaskRefs`: it ran, but its output\n * cannot be proven from a product declaration. An unexecuted task is not landed.\n * This distinction avoids repeatedly dispatching the same unprovable task without\n * presenting execution history as evidence that the intended product is correct.\n *\n * The ONE hard exception is a `COMPANION_GENERATION_STEP`, which must declare NONE.\n * That kind already carries its own typed landed condition, owned by the\n * generation-step service — a set computed asynchronously (planner units x\n * enabled locales), and for the migration step a STATE rather than files. A\n * product declared beside it would be read by nothing, which is the inert\n * declaration this field exists to avoid. Enforced on the graph below, in both\n * directions.\n */\n produces: z.array(BuildPlanTaskProductSchema).default([]),\n /**\n * Exactly ONE functional topic this task belongs to.\n *\n * **It does NOT drive ordering** — this said \"drives cross-app ordering\" until 2026-08-30 and\n * nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it\n * is the only thing that decides what may run next.\n *\n * What it DOES: the dispatch host stamps it into the coding-agent's task payload beside\n * `skillRefs`, so the agent is told which phase of building the application this task belongs to.\n * That is context an LLM reads, not a value the runtime branches on — the distinction matters,\n * because a reader who believes it orders will look here for a scheduling bug that lives in the\n * prerequisite graph. See issue #124.\n */\n functionalTopic: z.enum(MetaWorkflow_FunctionalTopic).systemEnum('MetaWorkflow_FunctionalTopic'),\n /** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */\n skillRefs: z.array(SkillRefSchema).min(1),\n /** Task refs that must have landed first; resolved by the host, not solved by the model. */\n prerequisiteTaskRefs: z.array(z.string()).default([]),\n /**\n * What this task is accountable to — traceability only, NEVER scope authority.\n *\n * The vocabulary is the target aspects `BUILD_PLAN_FAMILY_ASPECTS` declares for this edge:\n * functional and non-functional requirements, roadmap phases, the vision's success criteria and\n * constraints, drafted features, pricing plans, and the brand's name, logo direction and visual\n * tone. Each target after the first three was added because a producer had already been writing\n * it (#629, #1433, #1835, #2221). A companion generation step serves what it consumes: the `logo`\n * step serves the brand's logo direction and name.\n *\n * This schema accepts any non-empty string. Generation does not: the edge is DECLARED, so a key\n * that resolves to no element of a target family (when that family has landed) is a dangling\n * reference. The model is told so on retry, and the landing refuses it. That is why widening the\n * vocabulary to what producers genuinely mean matters: a true link the vocabulary does not name\n * fails generation. The workbench renders a key outside the vocabulary as visibly unresolved.\n */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n /**\n * Who asked for this task DIRECTLY (#1608), rather than it being derived from the specifications: the\n * signed-in person who added it in conversation. STAMPED by the append, never authored: a value in\n * generated output is discarded. Absent on every task the decomposition derived.\n *\n * It is what keeps a requested task alive. Build decomposition refines the plan from the domain plan, and\n * a task nothing in the specifications justifies would read as unjustified and be dropped; a requested\n * task it leaves out is carried forward instead, keeping only the prerequisites the new plan still holds.\n */\n requestedBy: NonEmptyStringSchema.optional(),\n});\nexport type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;\n\n/**\n * THE build-plan payload — a **single aggregate per product**: the ORDERED\n * task graph that turns the accepted domain plan into buildable units.\n *\n * **Artifact-family id: `build-plan`.** This schema is the shape of the\n * journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===\n * 'build-plan'` (the `family` vocabulary stays an open string owned by the\n * selector surface; this note is the single place tying the SHAPE to the\n * NAME). Produced by the build-decompose playbook, consumed by\n * build-dispatch (and build-scale, which runs the same branch): ready tasks\n * are dispatched in parallel waves of up to the application's build\n * parallelism (`wildo workbench parallelism`, 5 by default; 1 = one at a\n * time).\n *\n * Invariants enforced here: unique task refs; every prerequisite names a task\n * in this graph; no self-prerequisite. Cycle detection and ordering\n * soundness are the deterministic validator's job (`validateBuildPlanTaskGraph`).\n */\nexport const BuildPlanTaskGraphSchema = z.object({\n version: z.enum(BuildPlanTaskGraphVersion).default(BuildPlanTaskGraphVersion.V1),\n /**\n * At least one task, at the SCHEMA — not merely as a validator warning. The first live playbook-loop\n * run (2026-08-24) proved why: build-decompose answered `tasks: []`, which was schema-valid, passed\n * `_core` validation as a mere warning, and LANDED — overwriting a completed 3-task plan with a\n * vacuous artifact. Decomposing to zero tasks is a refusal (\"nothing to decompose\"), never an\n * artifact: an empty plan carries no information a reader could act on, and the file it replaces\n * does. Same vacuity class already closed on the requirements family (`functional: min(1)`).\n */\n tasks: z.array(BuildPlanTaskSchema).min(1),\n}).superRefine((graph, context) => {\n const refs = new Set<string>();\n graph.tasks.forEach((task, index) => {\n if (refs.has(task.taskRef)) {\n context.addIssue({ code: 'custom', message: `duplicate build task ref \"${task.taskRef}\"`, path: ['tasks', index, 'taskRef'] });\n }\n refs.add(task.taskRef);\n });\n /*\n * No two tasks claim the same artifact.\n *\n * This is what makes landing DECIDABLE, not a tidiness rule. If two tasks name\n * one product, the host cannot tell which of them a present artifact proves —\n * exactly the ambiguity that shared `target`s created, arriving through the\n * field that replaced them. Enforced here rather than left to the validator\n * because a graph that cannot answer \"has this task landed?\" is not a graph\n * the loop may run at all.\n */\n graph.tasks.forEach((task, index) => {\n const isGenerationStep = task.target.kind === BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP;\n if (isGenerationStep && task.produces.length > 0) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" is a companion generation step and must declare no products; its landing is the generation step's own condition`,\n path: ['tasks', index, 'produces'],\n });\n }\n });\n const productOwners = new Map<string, string>();\n graph.tasks.forEach((task, index) => {\n task.produces.forEach((product, productIndex) => {\n buildPlanTaskProductIdentities(product).forEach((identity) => {\n const owner = productOwners.get(identity);\n if (owner !== undefined) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" claims the same artifact as \"${owner}\" (${identity}); an artifact is produced by exactly one task`,\n path: ['tasks', index, 'produces', productIndex],\n });\n return;\n }\n productOwners.set(identity, task.taskRef);\n });\n });\n });\n graph.tasks.forEach((task, index) => {\n task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {\n if (prerequisite === task.taskRef) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" cannot be its own prerequisite`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n } else if (!refs.has(prerequisite)) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" names an unknown prerequisite \"${prerequisite}\"`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n }\n });\n });\n});\nexport type BuildPlanTaskGraph = z.infer<typeof BuildPlanTaskGraphSchema>;\n```\n\n## What this playbook does\n\nYou are the **dispatch orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, for *one* task at a time: *\"dispatch this\ntask safely, verify it, and record what happened.\"* You do **not** produce a new\njourney artifact — the dispatch's observable result (the change-set + the task\nstatus) is materialized by the runner on the task row, not authored here (see \"What\nyou emit\"). You do **not** decompose the plan, author any schema, or write any code\n— the coding agent writes the code at dispatch time; the plan is the\nbuild-decompose playbook's; scale is the scale playbook's.\n\n## The dispatch contract — the runner owns the mechanism, you sequence it\n\nMost of the D4 dispatch contract is **runner mechanism**, not prose you re-implement:\nthe runner composes the context pack, opens a coding session with the agent over the\nAgent Client Protocol and sends one prompt turn, answers the agent's permission\nrequests within the declared ceiling, captures the change-set, runs the verify hook,\nkeeps each task from being built twice at once, fills the wave to the configured width,\nand applies its configured execution limits. Your method here is the **declarative recipe** the runner interprets —\n*which* task to dispatch next, *when* it is authorized, and *how* its outcome is\njudged. Do not hand-compose a dispatch prompt or drive git yourself; let the runner\nown composition and change-set capture.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the build by one wave*\n(by one task when the build parallelism is `1`).\nBefore dispatching anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the **build plan** is present\n and approved, and confirm the **foundation** ran. For each build-plan task,\n determine its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify), or\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run or a\n failed verify). This tri-state matters: under `keep_and_flag` a **failed** task\n *also* has a captured change-set, so \"has a change-set\" alone does NOT mean the\n task is done — read the task's terminal status + verify outcome, not just the\n presence of a change-set.\n2. Read the approved **build plan** (`build-plan` — the ordered task graph). It is your\n work list.\n\n Evidence that the foundation ran is `./wildo.saas.config.ts` itself, committed: the\n app either has a config and a skeleton or it does not, and git answers that without a\n journey artifact standing in for it. (A `foundation-manifest` family was that stand-in\n until 2026-08-25; it was retired with the app-creation verification/digest aspect, and\n this playbook no longer gates on it.) The honest limitation inherited from the\n foundation step still applies: at scaffold depth the on-disk skeleton *materialization*\n depends on greenfield bring-up tooling (deferred). The dispatch contract is real and\n runs against an **existing** app skeleton — the dogfood app already has one.\n\n// Operator status: `wildo context journey` (eligibility board + runs in flight). Which tasks already\n// landed is read from GIT by the runner itself — a task is landed when every file it produces is\n// committed clean.\n\nYou **read** `build-plan`; you **write** no journey artifact\n— the runner records the change-set + task status on the dispatched task's row.\n\n## Precondition — the application must establish the agent's role, or dispatch stalls\n\nCheck this before the first dispatch of an application's life. It costs one look and it is the\ndifference between a working lane and one that burns model time producing nothing.\n\n**The application needs a root `CLAUDE.md` stating that a task dispatched by its dev companion is\nlegitimate work.** Without it the agent is right to refuse, and refusing is what it does.\n\nThe reason is structural rather than a matter of tone. A dispatched task reaches the agent as an\nordinary prompt — a user turn carrying an objective, a mutation scope and skill refs. Nothing in\nthat turn proves where it came from. So the agent is being handed conversational content that\ntells it to write files into a repository, which is indistinguishable from the thing every\ncareful agent is supposed to decline, and the more trustworthy the agent the more reliably it\ndeclines. Measured on a real application with no such file: two dispatched runs stalled, one\nanswering *\"content that arrives as conversational input doesn't get to reassign what I am\"*.\n\nThe failure does not look like a missing file. It looks like an agent that deliberates well,\nidentifies exactly which files it would author, explains its reasoning, asks a human to confirm,\nand ends its turn — `end_turn`, no error, no denial, an empty change set, and a bill for the\ntokens. Read as \"the agent chose not to work\", which invites prompt-tuning that cannot fix it.\n\n`wildo init` scaffolds this file. An application created before that, or one whose `CLAUDE.md`\ncovers only its own conventions, needs the section added. What it must establish:\n\n- the task is **selected by the host** from the accepted build plan, not composed by a caller;\n- its **file edits** are **confined before they arrive** — the host answers every permission request\n against the declared mutation scope and refuses paths outside it;\n- its **shell commands are NOT**, and the section must say so. A command declares no `locations`, so\n the scope predicate never runs for one; telling an agent it \"need not police itself\" is true of its\n edits and false of its commands, and that is the half a stray write comes through. Name the\n compensations with it: the post-run change set and the companion's warning DETECT such a write,\n they do not prevent it;\n- it is **reversible** — every write is an uncommitted working edit until something commits it. Do\n not state WHO commits as a property of the lane: that is the host's autonomy posture, it changes,\n and an agent that reads \"a human commits\" from a scaffold written under a different posture is\n working from a stale contract.\n\nTwo smaller things belong in the same section, because both were observed costing a run:\n\n- **Say what `allowedPathPrefixes` are relative to.** The agent receives bare prefixes such as\n `shared-lib/src/modules/<module>/` with no root, and cannot verify its own confinement against\n them. One sentence naming the application root removes the ambiguity.\n- **Do not name a task so it reads as a fixture.** An agent that concludes it is looking at a\n smoke test will say so and stop. Name the task after the product change it makes.\n\n## Step 1 — Select the ready tasks (the wave)\n\nWalk the build plan in its authored order. A task is **ready** when it is not yet\ndispatched (or a previously-**failed** task cleared for retry — see Step 5), it is\nnot already running, and its declared prerequisites have all **succeeded**. The\nrunner selects ready tasks in that order and keeps up to the build parallelism of\nthem running; when a run settles, its slot is refilled with whatever is ready THEN,\nso a task that just landed unlocks its dependents within the same wave. If **no**\ntask is ready — every task has already succeeded, or the only undispatched tasks\nare blocked behind a still-unresolved failure — there is nothing to dispatch:\nreport the build as done (or blocked on the failed task) and stop. An empty build\nplan is the same.\n\n- **How many run at once is the build parallelism, and it is the person's call.**\n `wildo workbench parallelism` shows it (5 by default) and sets it; `1` means one\n workspace-mutating run at a time. The runner reads it at the start of every wave,\n so a change needs no restart. Do not try to widen a wave beyond it.\n- **The runs share ONE worktree, by design.** Concurrent runs may edit the same\n files. The runner does not prevent that; it prevents only a task being built\n twice at once, and it REPAIRS the rest when the wave's runs have settled: it\n commits what the runs' own accepts left as one change naming every run whose\n writes it carries, then re-runs ALONE each task whose finished product a sibling\n overwrote. Each run's record says which runs overlapped it (`concurrency`), and\n whether a failure is suspected to come from a sibling (`interferenceSuspected`).\n- **One wave is bounded.** A call takes at most four tasks per slot, and runs each\n generation step at most once; it then stops taking tasks, waits for its runs and\n returns. The next run of this playbook continues from where the build stands.\n- **One wave at a time.** A second wave is refused while one runs, including during\n its end-of-wave commit and repair: start the next only once the running one has\n ended.\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task is ready\n only when every task it depends on is dispatched-and-succeeded (verify passed).\n A prerequisite that is dispatched-and-**failed** (its change-set is flagged for\n triage under `keep_and_flag`) does **not** satisfy the dependency — its dependents\n stay **blocked** until the failure is triaged and the prerequisite re-dispatched\n successfully. Do not build a config on a schema whose run failed. Never dispatch a\n task before the stage it depends on (a config before its schema, a spec before its\n ui-behavior — the build-decompose playbook ordered these).\n- **Companion-generation steps are not coding-agent dispatches.** A build-plan task\n marked as a companion-owned generation step (labels / i18n, email templates,\n seeds) runs through its deterministic companion endpoint, not the coding-agent\n dispatch lane. Route it there; do not dispatch a coding agent for it. In a wave\n the runner runs a ready generation step in its turn while the coding runs already\n started keep going.\n\n## Step 2 — Check the actual host authorization boundary\n\nA coding dispatch writes the application workspace. Read its selected task, readiness,\nmutation scope and the configured coding host's authorization policy before invoking it.\nEvery run of a wave writes the same shared workspace; each is confined to its own task's\nmutation scope, and nothing confines it from its siblings (Step 1).\n\nThe playbook's `approval` declaration and the journey autonomy presets express policy\nintent. The current playbook runner does not interpret them as pre-dispatch gates,\nautomatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does\nnot create a pending Authority Request, and no authority workflow exists to create one —\nnever invent one from an enum.\n\nLikewise, do not infer enforced per-playbook or per-journey run ceilings from declared\nbudget fields. Respect the limits actually reported by the execution host. Inspect the\nrecorded changes and verification result after each task; no preset commits or accepts them.\n\n## Step 3 — Dispatch the task through the coding-agent contract\n\nThe companion triggers the run (from a console, `wildo build run` or `/wildo:build`). The runner then performs the D4\ndispatch contract for you (you do not hand-assemble any of it):\n\n1. **Context pack** — the runner composes the prompt: the task brief, the task's\n skill pointers (`Read .claude/skills/<skillRef>/SKILL.md first` — the per-task\n HOW-skills the build plan named on this task), the relevant journey / definition\n artifacts, an introspected app-reality block, and the repo paths.\n2. **Session and one prompt turn** — the runner starts the agent over the Agent\n Client Protocol and opens a session rooted at the app workspace (cwd = the\n application root, so `./CLAUDE.md`, the sub-`CLAUDE.md`s, and the `.claude/` rules\n and skills load naturally), then sends the task as a single prompt turn. It is a\n session rather than a one-shot process, which is what makes the next three things\n possible at all:\n - **Permissions are answered, not assumed.** The agent asks before each action it\n considers privileged; the runner answers within the execution profile's declared\n ceiling and refuses anything above it, or anything touching a path outside the\n task's mutation scope. Refusals are counted on the task row, so a run that was\n held back is distinguishable from a run that had nothing to do.\n - **The turn can be cancelled.** Cancellation asks the agent to stop and waits, so\n the run terminalises with its change-set intact instead of being killed — an\n operator who stops a run still needs to know what it had already written.\n - **Usage is reported.** Tokens and cost come back from the run itself rather than\n being unavailable, which lets the host report a terminal timeout instead of leaving the run ambiguous.\n3. **Change-set capture** — the runner captures a git worktree snapshot before and\n after the run and attributes each touched file (the run's own edit vs. an\n already-dirty parallel-session file vs. a file that appeared during the run),\n recording a structured change-set on the task row. On the dogfood tree,\n dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture\n *attributes* rather than assuming the run had the tree to itself.\n\n// The trigger is `wildo creation run <playbookRef>` or `wildo build run` (from a Claude Code session,\n// `/wildo:run` or `/wildo:build`), or the workbench; each reaches the companion with its local token.\n// The runner composes the typed context pack, runs one ACP prompt turn, and captures the change-set.\n\n## Step 4 — Verify OUTSIDE the coding agent\n\nTrust, but verify. The verify gate runs **outside** the coding agent, after the run,\nso the agent cannot mark its own homework:\n\n- **`dispatch-typecheck` (deterministic — the auto-run trust floor).** The runner\n maps this `deterministic_validator` gate (`validatorRef: typecheck`) onto the\n dispatch verification hook and runs a typecheck (`pnpm exec tsc --noEmit`) over the\n application workspace after the run, **outside** the coding agent. This is a\n **real, wired** gate — it actually executes and its result is recorded on the task\n row. A run whose typecheck fails is a failed run (apply the failure disposition in\n Step 5). At scaffold depth the gate is a **workspace-wide** typecheck (one static\n gate for every dispatch of this playbook); narrowing it to the specific package a\n given task touched — a per-task `typecheck:<pkgDir>` or a `vitest:<path>` targeted\n at the task's tests — is a later refinement, since a static playbook gate cannot\n vary per task.\n- **`dispatch-outcome-sound` (declarative reviewer checklist).** The six-invariant\n reviewer checklist (task accomplished, change-set scoped to the task, verify ran +\n passed, attribution clean, failure disposition correct, boundary discipline)\n is the *trust-but-verify reviewer* pass. It is **declarative** — the creator's\n review checklist; the compiled build-dispatch Evaluation Treatment is what the\n runtime judges with, and the deterministic typecheck above is what runs\n automatically. **In a wave the runtime does not compose this judge per run**: each\n run's record carries its outcome, its checks, and what it overlapped, and the\n wave's end-of-run repair is on the wave's result. Read those; with a build\n parallelism of `1` the judge runs on the single dispatch as before.\n\n## Step 5 — Record the result and apply the failure disposition\n\nThe runner records the change-set + the task's terminal status on the task row. On a\n**failed or timed-out** run, the current coding host retains its captured changes for inspection (the declaration describes this as **`keep_and_flag`**): the\ncaptured change-set is **kept and flagged for human triage** — never silently\nreverted, and never left as an un-recorded half-applied state. The change-set capture\n*is* the flag: it attributes exactly which files the run touched, so a human can\nreview, keep, or unwind them.\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a failed\n> run's edits is a *mutating* git operation, deliberately **outside** the read-only\n> change-set carve-out the dispatch lane observes (the runner *observes* git —\n> baseline/post-run snapshots — but stage/commit/revert stay a human/CLI concern).\n> So `keep_and_flag` is both the correct F-5 workspace-safety posture (no silent\n> half-applied state) and the behavior the runner actually enforces today. Wiring a\n> `revert_changeset` path is a deliberate later boundary decision, not a gap this\n> playbook papers over.\n\nOn a **succeeded** run (change-set captured + verify passed), the task is done and\nits dependents become eligible. On a **failed** run, the task is **not** done — it is\nflagged for human triage, and its dependents stay blocked (Step 1) until it is\ntriaged and cleared for re-dispatch. Triage is a human decision: keep + fix forward,\nunwind the flagged change-set by hand, or re-dispatch the task once its blocker is\nresolved. This playbook does not auto-retry a failed task — automated retry / backoff\nis a deferred build-loop-resilience concern, and human triage is the v1 disposition;\nhere the loop simply surfaces the failure and stops advancing that dependency chain.\n\nThen **loop**: on the next run of this playbook, the build plan's task records reflect the\noutcomes of the wave that just ran (`wildo build tasks`), and the next wave selects from\nwhat is ready now (Step 1). Close a significant stretch of dispatches with a progress summary — what was\nproduced, which change-sets landed, what verify said, and any failed task left\nflagged for triage.\n\n## Refine, don't re-dispatch\n\n- **Never re-dispatch a SUCCEEDED task.** A task that is dispatched-and-succeeded\n (change-set captured + verify passed) is done — advance to the next ready task, do\n not re-run it because the plan was re-opened elsewhere. A dispatched-and-**failed**\n task is a different case: it is re-dispatchable once triaged (Step 5) — a captured\n change-set alone does not make a task \"finished\".\n- **Follow the plan's order.** If the build plan was refined upstream (a task added,\n an ordering corrected), respect the new order on the next selection — do not cache\n a stale work list across runs.\n- **A host execution refusal is a real stop.** When an actual execution limit is reported, stop dispatching\n and report what remains; do not do the coding work out-of-band to \"finish the\n build\" — that makes the journey's task history a lie.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **dispatch depth**: which tasks run, under what contract, and\nwhat each run's outcome was. Explicitly **out of scope here**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order the\n graph, or add tasks — the **build-decompose** playbook owns the task graph. You\n read it and dispatch from it.\n- **The width and the isolation model.** How many tasks run at once is the\n application's build parallelism, set by the person; the runs share one worktree and\n are repaired, not isolated. You do NOT choose a width, partition the worktree, or\n design a different schedule.\n- **A `revert_changeset` failure path.** Undoing a failed run's edits is a mutating\n git op outside the read-only change-set carve-out — deferred. `keep_and_flag` (keep\n + flag the captured change-set for triage) is the v1 disposition.\n- **Auto-executed reviewer checklist.** The checklist ships **declarative** —\n the deterministic typecheck gate runs automatically and the compiled Evaluation\n Treatment is the judged protocol; nothing executes the checklist prose. Do not\n assume it auto-ran.\n- **Schema / field authoring + code generation.** You dispatch a task; the **coding\n agent** authors the fields, schemas, ui-behavior, and code at dispatch time. If you\n catch yourself writing application code or a resource schema here, stop — that is\n the dispatched agent's job, not the orchestrator's.\n\nIf you find yourself designing how MANY agents run concurrently, stop: the width is\nthe build parallelism and the schedule is the runner's.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable result\nof a dispatch — the **change-set** (files touched, attributed, summarized) and the\n**task status** — is materialized by the runner on the dispatched task's row, not\nauthored by this playbook. That is deliberately not duplicated into a separate\njourney artifact family: the task row already *is* the dispatch record, and a second\nhome for the same record would drift.\n\nDispatch uses the configured host's actual authorization boundary. The creator reviews\nthe recorded change-sets and verification outcomes afterwards, wave by wave, until the\nbuild plan is fully dispatched.\n\n## References\n\n- A playbook's declared `approval` and failure policy gate nothing on a leaf run; they are read only\n at a composite lane's boundary, where they frame a decision for the person and revert nothing.\n\n## Reviewer checklist — `dispatch-outcome-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim (minus the retired runner's closing sentence, and with repository-specific wording made application-neutral):\n\nJudge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag). Files attributed BASELINE_DIRTY_AMBIGUOUS were already dirty and changed again during the run; this establishes uncertainty, not ownership by a parallel editor. Every changed path outside the declared scope — ambiguous or not, and including a parallel session's edits, which the capture cannot tell apart from the run's own — is RECORDED on the result as `outOfScopePaths`; nothing refuses the run for it. Treat each as a CONCERN and resolve its authorship during review, never as a GAP by itself. Committed-window entries and recognized concurrent host-lane paths are classified separately and left off that list. (3) VERIFY RAN + PASSED — the deterministic verify gate (typecheck) ran OUTSIDE the coding agent after the run and passed; a run recorded as succeeded whose typecheck the reviewer cannot confirm passed is a CONCERN, and a run whose typecheck FAILED but was recorded succeeded is a GAP. (4) ATTRIBUTION READ AGAINST THE WAVE — the run's edits are cleanly attributable to it in the captured change-set (files classed RUN_EXCLUSIVE or APPEARED_DURING_RUN). In a wave the runs share one worktree, so overlap is expected and RECORDED rather than prevented: the run's `concurrency` entry names the runs that overlapped it and the paths they both touched. A change-set dominated by BASELINE_DIRTY_AMBIGUOUS overlap, or captured across a HEAD that moved mid-run, is a CONCERN the reviewer resolves using that record before accepting the run; a run marked `interferenceSuspected`, or whose product a sibling overwrote, is a CONCERN until its re-run alone has landed. Overlap alone is not a GAP. (5) FAILURE DISPOSITION CORRECT — a failed/timed-out run's captured change-set is KEPT + FLAGGED for human triage (keep_and_flag), never silently reverted nor silently left as an un-recorded half-applied state; a failed run with no recorded change-set flag is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the dispatch stays at dispatch depth: it runs the ready tasks up to the build parallelism, captures + verifies + records each, and applies onFailure. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT choose its own width or a different isolation model (the build parallelism is the person's setting, and the runs share one worktree by design), and does NOT itself author schemas / fields / code (the coding agent does that at dispatch time). Evidence of re-decomposition, a width other than the configured one, or the dispatcher authoring code itself is a CONCERN (scope creep out of the dispatch lane). (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)\n",
22
+ "guidance": "# Build Dispatch — Build-Plan Tasks → Verified Coding-Agent Runs, in Parallel Waves\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **The build runs in parallel by default.** One run of this playbook starts a\n> **wave**: up to N build-plan tasks at once, N being the application's **build\n> parallelism** (`wildo workbench parallelism`, 5 unless the person set it). Each\n> task in the wave follows the same per-task contract — its own coding run, its\n> change-set captured, verified outside the coding agent, recorded, the failure\n> disposition applied. With a build parallelism of `1` a run dispatches exactly\n> ONE task, which is the single-flight mode. A `revert_changeset` failure path is\n> still a **later phase** (see the boundary section).\n\n## Where you are in the journey\n\nThis is the **second build-execution playbook** — the pivot from **decomposing the\nbuild** (the build-plan: the ordered coding-agent task graph) to **dispatching it**\n(turning one ordered task into an actually-run, verified coding-agent run). It runs\nin the **bottom-up phase**, after the build plan exists (`artifact_exists\nbuild-plan`) and the foundation step has authored the app's config and skeleton.\nYou are not re-opening the decomposition\nhere — you are turning one *approved, ordered* task into a *dispatched, verified*\nchange to the application.\n\nUpstream, the **build-decompose** playbook produced the ordered task graph you\nconsume. The **scale** playbook describes the same wave from the scheduling side —\nthe ready-set, the width, the reconciliation — and runs through the same runtime\nbranch as this one; prefer this playbook to start a build. **You author the task\ngraph neither here nor there** — see the boundary section.\n\n## The typed task you dispatch\n\nThe build plan is a typed family (`BuildPlanTaskGraph`): dispatch selects ONE\nREADY task (all declared prerequisite task refs have landed) and hands the\ncoding host exactly that task's `objective`, `target`, `produces`,\n`functionalTopic` and `skillRefs`. The host derives the physical\nallowed/prohibited paths and the fixed verification from the target kind;\nnothing in the task — and nothing in this method prose — authors a path, a\ncommand, a prompt or a runtime control.\n\n`target` and `produces` answer two different questions, and a task needs both.\n`target` is the WRITE SCOPE — where this run may edit, and several tasks\nlegitimately share one. `produces` is what the run is ACCOUNTABLE for: the\nartifacts whose presence in the application proves the task done. A task has\nlanded when every artifact it declares is present and committed, so a run that\nsatisfies the objective's prose without delivering those artifacts is not\nfinished — the plan will offer the task again.\n\n## Import Origins\n\n- `@wildo-ai/saas-specifications`\n\n## Source Excerpts\n\n### Origin Package: `@wildo-ai/saas-specifications`\n\n```typescript\n *\n * Versioning for the build-plan task-graph payload format itself. `V1` —\n * initial shape (one ordered `tasks` collection with typed targets and\n * declared prerequisites). The shape grows additively across versions; the\n * `version` field is the explicit marker for consumers that branch on era.\n */\nexport enum BuildPlanTaskGraphVersion {\n V1 = 'v1',\n}\n\n/** Stable prefix every build-plan task ref carries; the trusted runtime stamps it, a provider supplies only the slug. */\nexport const BUILD_PLAN_TASK_REF_PREFIX = 'build-task-';\n\n/**\n * WHAT a build task builds — a closed vocabulary, because the host derives\n * the physical mutation scope and verification policy from the target kind\n * and the model must never author those powers through free text.\n */\nexport enum BuildPlanTaskTargetKind {\n /** A whole application module (its shared-lib registration, backend module and frontend module skeletons). */\n MODULE = 'MODULE',\n /** One build stage of one resource: schema → config → ui-behavior → spec. */\n RESOURCE_STAGE = 'RESOURCE_STAGE',\n /** One relationship between two resources. */\n RELATIONSHIP = 'RELATIONSHIP',\n /** A companion-owned deterministic generation step (labels, email templates, logo or database migrations) interleaved by the build loop, never a coding-agent run. */\n COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',\n /**\n * Authoring one SHELL SURFACE's placement configuration from the accepted\n * placement plan — the settings rail, the sidebar, the user menu or the\n * command palette.\n *\n * Its own kind rather than a reuse of the neighbours, because none of them is\n * true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide\n * and belongs to no resource), not a RELATIONSHIP, and emphatically not a\n * COMPANION_GENERATION_STEP — that kind is documented as \"never a coding-agent\n * run\" and writing `settings-hub.config.ts` is exactly a coding-agent run.\n * Borrowing one would hand the host the wrong mutation scope and the wrong\n * verification, which is what the closed vocabulary exists to prevent.\n */\n SHELL_PLACEMENT = 'SHELL_PLACEMENT',\n /*\n * THE NON-RESOURCE SURFACES (#1490). Until 2026-09-22 the five kinds above were the whole\n * vocabulary, and every one of them is about a resource or the shell placement of one. The\n * decompose method meanwhile told the planner to emit tasks for views, navigation, the design\n * system, custom components, PDF templates, workers, minions, providers, the website and the\n * documentation — surfaces the framework's own composition scenarios and 85 of its 111 skills\n * already build. A task for any of them had no kind to declare, so it either declared none\n * (landing as RAN-not-PROVEN forever) or borrowed `MODULE` with a product the module scope could\n * not prove. The members below are those surfaces, one per write scope the host can derive.\n */\n /**\n * The FRONTEND and SPECIFICATION layers of one module — its composite, custom and chart views,\n * its custom components and their specifications.\n *\n * Narrower than `MODULE` on purpose: a view task never touches `shared-lib` or `backend-api`, so\n * handing it the four-layer scope also hands it four typechecks and the FK sweep for a change\n * that can only break the frontend and the specifications package.\n */\n MODULE_FRONTEND = 'MODULE_FRONTEND',\n /**\n * The BACKEND layer of one module beside its shared-lib declarations — PDF templates and their\n * bindings, backend addons (services, controllers, flows-actors), email definitions.\n *\n * Shared-lib is in scope because a PDF template is bound to a resource FIELD the config declares\n * (`generatedSummaryPdf`), and a backend addon usually declares its contract there first.\n */\n MODULE_BACKEND = 'MODULE_BACKEND',\n /**\n * ONE application-wide frontend configuration surface — navigation, the design system, the app\n * shell's composition, the global views, the shell layout — named by {@link FrontendConfigSurface}.\n *\n * Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the\n * shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES\n * the surface itself (which sidebar sections exist, which transitions the primary zone uses,\n * which palette the product carries). Same file for `APP_SHELL`, different question.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /** The marketing website workspace (`website/`), composed by the `add-website` scenario. Pages and sections are its products. */\n WEBSITE = 'WEBSITE',\n /**\n * The technical-documentation workspace (`technical-doc/`) and the specification package's\n * `technical-documentation/` declarations that feed it. Its generated tree is never written by a\n * task: the companion publishes into it, and the coding policy prohibits it by prefix.\n */\n TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',\n /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */\n WORKER = 'WORKER',\n /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */\n MINION = 'MINION',\n /**\n * Declaring one provider in the application — the SaaS config's provider scopes, the backend\n * package dependency, the frontend provider module and its companion contribution.\n *\n * Application-wide by construction: a provider binding names no module, and the four files it\n * may touch are the same for every provider.\n */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * The application's BILLING CATALOGUE — the `ProductDefinition[]` in `shared-lib/src/engine/product.ts`\n * (and the product specifications that document it), which the backend syncs to the billing\n * provider and the public website reads for its pricing page (#1835).\n *\n * Its own kind because none of the others is true of it: the catalogue is application-wide (a plan\n * belongs to no module), it lives in the shared library's ENGINE module that no `MODULE_*` scope\n * reaches, and before it existed a journey-built application reached its website with an EMPTY\n * catalogue, so the website re-typed the business model's prices by hand.\n */\n BILLING_CATALOG = 'BILLING_CATALOG',\n /**\n * The application's own ROLES — `CUSTOM_ROLES_CONFIGURATION` in `shared-lib/src/engine/roles.ts`, the\n * organization types that offer them (`availableOrgRoles` in `wildo.saas.config.ts`), their\n * specifications, and the `roles` of the operations they unlock (#2490).\n *\n * Its own kind because none of the others reaches it: the role table is application-wide and lives in\n * the shared library's ENGINE module. Before it existed a requirement naming user groups (\"office and\n * field users see different things\") had no task able to declare a role, so app-creation-test-005\n * modelled roles as an access-role RESOURCE that nothing reads.\n */\n APPLICATION_ROLES = 'APPLICATION_ROLES',\n}\n\n/**\n * WHICH application-wide frontend configuration surface a task composes — one file each (in\n * `frontend/src/config/`, except the shell layout, whose one line lives in the engine registrations\n * file), and the coding policy resolves the member to that file exactly as `SHELL_PLACEMENT` resolves\n * a `PlacementSurface`.\n *\n * Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a\n * subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of\n * those live in one file. A configuration surface is WHICH FILE a composition task authors, and\n * navigation and the design system are not places anything is placed.\n */\nexport enum FrontendConfigSurface {\n /** `frontend/src/config/navigation.config.ts` — zones, transitions, overlay appearance. */\n NAVIGATION = 'NAVIGATION',\n /** `frontend/src/config/design-system.config.ts` — palette, typography, shell appearance from the brand's visual tone. */\n DESIGN_SYSTEM = 'DESIGN_SYSTEM',\n /** `frontend/src/config/app-shell.config.ts` — top bar, sidebar sections, quick switcher: the shell's COMPOSITION, not a placement into it. */\n APP_SHELL = 'APP_SHELL',\n /** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */\n GLOBAL_VIEWS = 'GLOBAL_VIEWS',\n /**\n * `frontend/src/engine/component-registrations.frontend.ts` — the ONE animated 2D shell layout the application moves\n * in (`register2DLayout(MORPH_LAYOUT_2D, { speed })`), decided beside the design system because both are the\n * brand's: the design system its palette and pace, the layout how the shell moves at that pace. Its single\n * declaration names the layout constant, written out. A 3D layout is never decided here: it is the operator's\n * opt-in, through the `add-3d-layout` composition scenario.\n */\n SHELL_LAYOUT = 'SHELL_LAYOUT',\n}\n\n/**\n * The two shapes of guidance an application gives a person, and the file each is declared in.\n *\n * They are distinct because they are found differently: an onboarding DOCUMENT is embedded in a\n * screen (`EmbedOnboarding`) and is there whenever that screen is, while a guidance FLOW is started\n * by an event and shows once. Both are listed on the owning frontend module — `onboardingViews` and\n * `guidanceFlows`. Each kind has a CONVENTIONAL definitions file, which the authoring skill teaches\n * and a landing probe reads for the declared ref (alongside the module's `index.ts`, where a small\n * module may declare inline). A convention for generated applications: a hand-authored application\n * may keep its declarations elsewhere, and then simply is not probed by a build plan.\n */\nexport enum ApplicationGuidanceKind {\n /** `frontend/src/modules/<m>/app-level-views/onboarding-views.definitions.ts` — an embedded onboarding document. */\n ONBOARDING_DOCUMENT = 'ONBOARDING_DOCUMENT',\n /** `frontend/src/modules/<m>/app-level-views/guidance-flows.definitions.ts` — a triggered guidance flow. */\n GUIDANCE_FLOW = 'GUIDANCE_FLOW',\n}\n\n/**\n * The two worker runtimes the framework composes (`add-worker-node`, `add-worker-rust`). The\n * runtime decides the entry file a landing probe reads and whether a typecheck exists to run: a\n * Node worker is verified by its package typecheck, a Rust worker has no TypeScript to check and\n * the policy says so rather than inventing a command.\n *\n * Not the SaaS config's `WorkerRuntime`, which is a free-form `{ type, language }` pair an\n * application authors for deployment; this is the closed set a creation run can COMPOSE.\n */\nexport enum BuildPlanWorkerRuntime {\n NODE = 'NODE',\n RUST = 'RUST',\n}\n\n/**\n * WHERE a provider is bound — which runtime owner's scope its declaration lands in. Each member\n * is a different file, so a probe and a write grant both derive from it.\n *\n * Named after the SaaS config's own scope keys (`providers.scopes.backend`, `.companion`,\n * `.frontendServices.app`, `.frontendServices.website`), which the `add-provider` and\n * `add-file-picker-provider` scenarios write. Minion and worker scopes are deliberately absent:\n * a provider reaching a minion is declared on that minion's own `providers` block and belongs to\n * the {@link BuildPlanTaskTargetKind.MINION} task that builds it.\n */\nexport enum ProviderBindingScope {\n BACKEND = 'BACKEND',\n COMPANION = 'COMPANION',\n FRONTEND_APP = 'FRONTEND_APP',\n WEBSITE = 'WEBSITE',\n}\n\n/** The per-resource build stages, in their fixed order. */\nexport enum BuildPlanResourceStage {\n SCHEMA = 'SCHEMA',\n CONFIG = 'CONFIG',\n UI_BEHAVIOR = 'UI_BEHAVIOR',\n SPEC = 'SPEC',\n}\n\nconst SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n\n/**\n * The key of the domain-plan MODULE a task targets or produces (`deals`, `tasks-manager`). Same\n * slug grammar as the other keys, declared as its own schema because it names one thing — a\n * module — where the other slugs name resources, relationships, steps, workers and products.\n */\nconst ModuleRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n\n/**\n * The governed document a task produces, named as a COMPLIANCE-DOCUMENT CANDIDATE names it:\n * `document:<namespace>.<id>`, e.g. `document:public.privacy-notice`.\n *\n * **This field was `SlugSchema`, and a slug cannot name a governed document — so until 2026-09-16 no\n * build plan in any application could declare a document the engine catalog defines.** A slug forbids\n * the colon and the dot, the catalog's definitions are `document-definition:public.privacy-notice`,\n * and `selectAssuranceDocumentBlueprintForDocumentRef` joins the two namespaces by exact suffix — so\n * every authored `documentRef` resolved to NO blueprint, and a blueprint is what says which sections,\n * facts and claim guards the document owes. The two vocabularies were disjoint by construction.\n *\n * The cost is measured rather than theoretical. Wonder CRM's plan declares two such products\n * (`gdpr-data-handling-governance`, `terminal-access-governance`), neither of which names anything;\n * the first was dispatched, and its agent spent a full turn establishing — with a positive control —\n * that the document does not exist and could only be invented, which the authoring skill forbids.\n *\n * The bare slug is STILL ACCEPTED, and that is deliberate rather than tidiness left undone: tightening\n * this to the namespaced form alone would make every already-accepted plan carrying one fail to parse,\n * and a build plan that cannot be READ stops the whole lane — the gate\n * `application-creation-directive.md` forbids, for a task nobody can fix by re-running anything. A slug\n * simply resolves to no blueprint, so the dispatcher skips that task with a message naming the ref,\n * and the rest of the plan proceeds.\n */\nconst DocumentProductRefSchema = z.union([\n z.string().regex(/^document:[a-z0-9]+(?:-[a-z0-9]+)*\\.[a-z0-9]+(?:-[a-z0-9]+)*$/),\n SlugSchema,\n]);\n/**\n * A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is\n * also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses\n * any skill name outside `[a-z0-9-]+`, so a ref that does not match this shape\n * can never resolve to an installed skill.\n */\nconst SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\nconst NonEmptyStringSchema = z.string().trim().min(1);\n\n/**\n * WHAT a build task PRODUCES — the artifact whose presence in the application\n * proves the task is done.\n *\n * **This is not `target`, and the difference is the whole reason it exists.**\n * `target` is a WRITE SCOPE: the host turns it into the path prefixes a run may\n * mutate, and several tasks legitimately share one. `produces` is a PRODUCT\n * IDENTITY: it says which artifact this task, and no other, is accountable for.\n *\n * Measured 2026-09-10 on Wonder CRM (issue #597): `build-task-pipeline-view`\n * and `build-task-deal-follow-through-operation` carry BYTE-IDENTICAL targets\n * (`{ kind: MODULE, moduleRef: 'deals' }`), and 7 of that plan's 42 tasks share\n * 3 targets. Landing had been answered by narrowing the target to a module\n * DIRECTORY — which `wildo compose` commits on day one, and which cannot tell\n * two tasks apart even in principle. The loop reported 40 of 42 tasks landed\n * while no coding task had ever run, so `dispatch-next` skipped every one of\n * them and the phase-advance gate read a build that was all but complete.\n *\n * Like `target`, this stays SEMANTIC: a product names a resource, a field, a\n * relationship or a view — never a path, and never a command. The host owns the\n * translation from a product to the physical question it asks of the working\n * tree, exactly as it owns the translation from a target kind to path prefixes.\n * A model that could author the path could author its own mutation scope.\n */\nexport enum BuildPlanTaskProductKind {\n /**\n * Named fields on one resource's schema.\n *\n * The shape an ENRICHMENT task needs, and the reason a product cannot always\n * be \"a file\": every resource file already exists, written by the scaffold\n * with its self-described STARTER shape, so file presence answers nothing.\n * The FIELDS are what the task adds.\n */\n RESOURCE_SCHEMA_FIELDS = 'RESOURCE_SCHEMA_FIELDS',\n /**\n * One resource's declared operations — its registry presence, named by the verbs it gains.\n *\n * The VERBS, not the config file: `<r>.resources-config.ts` is written by the scaffold, so its\n * existence is satisfied before any task runs. That is the exact shape of the defect this\n * vocabulary replaces, and a kind that reproduced it would be worse than no kind at all.\n */\n RESOURCE_REGISTRATION = 'RESOURCE_REGISTRATION',\n /** One resource's frontend ui-behavior. */\n RESOURCE_UI_BEHAVIOR = 'RESOURCE_UI_BEHAVIOR',\n /**\n * One resource's specification, named by the fields it documents.\n *\n * The FIELDS, for the same reason as {@link RESOURCE_REGISTRATION}: every resource is scaffolded\n * with a `*.resource.specification.ts` documenting only the starter shape, so file existence\n * proves nothing about the task that was meant to enrich it.\n */\n RESOURCE_SPECIFICATION = 'RESOURCE_SPECIFICATION',\n /** One relationship edge between two resources, named by the domain plan's `relationshipRef`. */\n RESOURCE_RELATIONSHIP = 'RESOURCE_RELATIONSHIP',\n /** One named custom operation on one resource. */\n RESOURCE_OPERATION = 'RESOURCE_OPERATION',\n /** One named application-level view. */\n APPLICATION_VIEW = 'APPLICATION_VIEW',\n /** One named governed application document (a compliance notice, a governance statement). */\n APPLICATION_DOCUMENT = 'APPLICATION_DOCUMENT',\n /** One application module, registered across the layer registries under one module identity. */\n APPLICATION_MODULE = 'APPLICATION_MODULE',\n /*\n * THE NON-RESOURCE PRODUCTS (#1490). Each names an artifact of a surface the five target kinds\n * above `MODULE_FRONTEND` could not express, and each is probed by the host from committed bytes —\n * a declaration in the one file that registers it, never a directory a scenario already wrote.\n */\n /**\n * Named declarations in ONE application-wide frontend configuration file — a sidebar section\n * ref the app shell gains, a zone the navigation config declares, a token the design system sets.\n *\n * The DECLARATIONS, never the file: every `frontend/src/config/*.config.ts` is written by\n * `wildo init`, so its presence is true before any task runs. Same reasoning as\n * {@link RESOURCE_SCHEMA_FIELDS}, one level up.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /**\n * One composite view of one resource — the cross-resource surface a resource's ui-behavior\n * declares under `compositeViews`. Distinct from {@link APPLICATION_VIEW}, which is\n * application-level and owned by a module rather than a resource.\n */\n RESOURCE_COMPOSITE_VIEW = 'RESOURCE_COMPOSITE_VIEW',\n /** One custom operation or execution view of one resource, bound in its ui-behavior. */\n RESOURCE_CUSTOM_VIEW = 'RESOURCE_CUSTOM_VIEW',\n /** One chart view of one resource, declared under its ui-behavior's `chartViews`. */\n RESOURCE_CHART_VIEW = 'RESOURCE_CHART_VIEW',\n /** One custom frontend component, registered by `componentRef` in the module's or the engine's registrations. */\n CUSTOM_COMPONENT = 'CUSTOM_COMPONENT',\n /**\n * One milestone a module declares — the moment the application recognises and celebrates.\n *\n * Named by its identifier, which is what the module's `milestones.ts` declares\n * (`first-project-created` is spelled `FIRST_PROJECT_CREATED` there). The module FILE is not the\n * product: a module may carry milestones before this task runs, and only the identifier says this\n * one landed.\n */\n APPLICATION_MILESTONE = 'APPLICATION_MILESTONE',\n /** One onboarding document or guidance flow a module declares, named by its ref. */\n APPLICATION_GUIDANCE = 'APPLICATION_GUIDANCE',\n /** One PDF template bound to one resource's generated-file field. */\n PDF_TEMPLATE = 'PDF_TEMPLATE',\n /**\n * One worker's JOBS — the named handlers its entry file declares.\n *\n * The jobs, not the package: `add-worker-node` writes the package, so its directory proves\n * nothing. What a coding task adds is behaviour, and behaviour is a symbol in the entry file.\n */\n APPLICATION_WORKER = 'APPLICATION_WORKER',\n /** One minion's BEHAVIOURS — the named tick handlers its entry file declares. Same reasoning as the worker. */\n APPLICATION_MINION = 'APPLICATION_MINION',\n /** One provider declared in one runtime owner's scope. */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * One product of the application's billing catalogue — a plan, add-on or purchase the application\n * sells — named by its catalogue `key`, which the catalogue file declares (`key: 'team'`).\n *\n * The KEY, not the file: `wildo init` writes `product.ts` with an empty catalogue, so the file proves\n * nothing. Written from the accepted business model's pricing plans, with the plan's price as typed\n * money and the pricing-surface facts (recommended, price disclosure, availability) the plan implies.\n */\n APPLICATION_BILLING_PRODUCT = 'APPLICATION_BILLING_PRODUCT',\n /**\n * One data seed a module declares — rows the application creates for itself, named by the seed's\n * `seedKey` (`crm:demo-customers`).\n *\n * The seed is its own file, `backend-api/src/modules/<module>/seeds/<seedKey with ':' as '.'>.seed.ts`,\n * and it lands only once the module registers it — a seed file nothing imports never runs. Its\n * {@link BuildPlanDataSeedContent} says whether it is REFERENCE data the application needs everywhere\n * or DEMONSTRATION data that must never reach production.\n */\n APPLICATION_DATA_SEED = 'APPLICATION_DATA_SEED',\n /** One website page, registered in the website root config by its manifest. */\n WEBSITE_PAGE = 'WEBSITE_PAGE',\n /** One section of one website page, declared in that page's sections file. */\n WEBSITE_SECTION = 'WEBSITE_SECTION',\n /**\n * One authored documentation chapter — a consumer guide the specifications package declares\n * for the documentation portal to publish (#874's publication input).\n */\n DOCUMENTATION_CHAPTER = 'DOCUMENTATION_CHAPTER',\n /**\n * One inbound CHANNEL handler — the code that decides what a message arriving on a channel causes\n * (#1832). Named by the handler's `ref` (`matters.mail-intake`), which the handler file spells and whose\n * file NAME is derived from it, so the module index's import of that file is what proves the handler is\n * registered. Produced once per channel the integration plan declares (`inboundChannels`).\n */\n INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',\n /**\n * One role the application declares, named by its role name (`FIELD_TECHNICIAN`), which is its key in\n * `CUSTOM_ROLES_CONFIGURATION`. The NAME, not the file: `wildo init` writes `roles.ts` with an empty\n * table, so the file proves nothing (#2490).\n */\n APPLICATION_ROLE = 'APPLICATION_ROLE',\n /*\n * AGENT WORK (#2966). An agent, the approval gate on one of its tools, and the resource whose rows are the cases its\n * work is costed to. None of them is a name the tree spells in one file: an agent's ref and a gate's role are written\n * through constants in other files, and a gate is a property of a tool object. So each is proven from the REGISTRY the\n * application's backend registers at startup, read through introspection, never from text.\n */\n /**\n * One AI agent the application registers, named by its `ref` — a chat agent's (`agents`) or an autonomous agent's\n * (`autonomousAgents`), as its {@link BuildPlanAgentShape} says. Its shape also decides the skill it is built with.\n */\n APPLICATION_AGENT = 'APPLICATION_AGENT',\n /**\n * The approval gate on one function tool (`humanApproval`): its calls wait for the person the ROUTE names, holding the\n * role the gate requires. Proven when the registered tool's gate has that route and that role, so a gate routed to the\n * wrong role, or a tool left ungated, does not land.\n */\n AGENT_APPROVAL_GATE = 'AGENT_APPROVAL_GATE',\n /**\n * One resource declared as the application's unit of work (`workUnit: true`): its rows are the cases model spend is\n * attributed to, and cost per case is read by them.\n */\n WORK_UNIT_RESOURCE = 'WORK_UNIT_RESOURCE',\n /**\n * One operation of one resource that records usage of one METERED billing product when it succeeds (`recordsUsage`,\n * #2305 S5). How a price per case is billed: the operation that closes a case records one unit, once per case. Proven\n * from the registry like the agent work: the declaration is a property of one operation object in the resource's\n * configuration, which no text in the tree ties to that operation.\n */\n METERED_USAGE_RECORDING = 'METERED_USAGE_RECORDING',\n /**\n * One resource's rows bound to one of the application's retention classes (`retentionBinding`, #2305 S6): how long the\n * firm's case evidence is kept. Proven from the registry: the binding is a property of the resource's configuration.\n */\n RESOURCE_RETENTION_BINDING = 'RESOURCE_RETENTION_BINDING',\n /**\n * One role CONFERRED through one organization relationship kind (#2305 S6): the relationship's `confers.roles` holds it\n * and every organization type the relationship grants offers it (`availableOrgRoles`). How the firm's people come to\n * hold, for a client, the role a decision of its method requires. Proven from the application's configuration\n * (`wildo.saas.config.ts`), read fresh at landing: the role is spelled through constants, so no text can prove it.\n * \"Conferred\" is the kind's CEILING: each client still grants the role, or not, on its own relationship. And the fresh\n * read re-evaluates the configuration and the files it imports by relative path; a value imported from a package is\n * read from that package's build.\n */\n RELATIONSHIP_CONFERRED_ROLE = 'RELATIONSHIP_CONFERRED_ROLE',\n}\n\n/**\n * How an agent is started and talked to (#2966), which decides the skill it is built with\n * ({@link BUILD_PLAN_AGENT_SHAPE_SKILL_REF}) and where its ref is registered.\n */\nexport enum BuildPlanAgentShape {\n /** A person converses with it in the application. Registered under the module's `agents`. */\n CHAT_ASSISTANT = 'CHAT_ASSISTANT',\n /** It runs with nobody signed in: on a schedule, or when a message arrives. Registered under `autonomousAgents`. */\n AUTONOMOUS = 'AUTONOMOUS',\n /** The application's own code calls it once and uses its answer. Registered under `agents`. */\n INVOKED = 'INVOKED',\n /** One step of a declared flow. Registered under `agents`. */\n FLOW_STEP = 'FLOW_STEP',\n}\n\n\n/**\n * What a data seed's rows ARE, which decides where they may exist.\n *\n * - `REFERENCE` — rows the application needs to work wherever it runs: a closed list, a default\n * record, a system template. Every environment, production included.\n * - `DEMONSTRATION` — sample rows that make a freshly created application look lived-in (customers,\n * projects, a few records per list). They must never sit beside real rows, so the seed declares\n * `allowedApplicationEnvironments` without `production`, and the task lands only once it does.\n */\nexport enum BuildPlanDataSeedContent {\n REFERENCE = 'REFERENCE',\n DEMONSTRATION = 'DEMONSTRATION',\n}\n\n/**\n * A data seed's key: kebab-case segments joined by `:` (`crm:demo-customers`), the convention a\n * `DataSeedDefinition` documents. Constrained here because the seed's FILE is derived from it.\n */\n/**\n * An application role's name, as `CUSTOM_ROLES_CONFIGURATION` keys it: upper snake case (`FIELD_TECHNICIAN`).\n * A core role (`ORG_MEMBER`, `APP_ADMIN_SUPER_ADMIN`) is not something an application declares, so the\n * product refuses one: a plan naming it would claim to create a role the engine already owns.\n */\nexport const APPLICATION_ROLE_NAME_PATTERN: RegExp = /^[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*$/;\n/** Every role the ENGINE defines: an application role may not take one of these names, and a qualification may name one without declaring it. */\nexport const CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);\n\n/**\n * An agent's or a function tool's ref: segments of letters and digits joined by `.`, `-` or `_`\n * (`close-assistant.chat.agent`, `todos.overdue-triage`, `resource.adjustmentProposals.post`). Case is kept, because a\n * tool ref follows the framework's `resource.<resourceType>.<operation>` convention and a multi-word resource type is\n * camelCase. Constrained because the probe compares it EXACTLY with the registered ref: no space, no slash, no empty\n * segment.\n */\nexport const AGENT_WORK_REF_PATTERN: RegExp = /^[A-Za-z0-9]+(?:[._-][A-Za-z0-9]+)*$/;\n\n/**\n * A step or a decision point of the firm's method (#2305), addressed as `<serviceRef>/<elementRef>`\n * (`month-end-close/approve-posting`). A step's and a decision's ref are unique only within their service, so the\n * service qualifies them; the `service-method` family declares both halves as kebab-case slugs.\n */\nexport const SERVICE_METHOD_ELEMENT_REF_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*\\/[a-z0-9]+(?:-[a-z0-9]+)*$/;\n\n/** The ref a build-plan product carries for one step or decision point of the method (#2305). */\nexport function serviceMethodElementRef(serviceRef: string, elementRef: string): string {\n return `${serviceRef}/${elementRef}`;\n}\n\nexport const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;\n\n/**\n * One artifact a task is accountable for. Closed by construction: a product the\n * host cannot ask a question about is a product that can never be shown to have\n * landed, so the vocabulary only grows alongside the resolver that answers it.\n */\nexport const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /**\n * At least one field, because a task that enriches a schema with nothing is\n * the vacuity this whole field exists to stop: it would land the moment the\n * scaffold existed, which is the defect being fixed.\n */\n fieldRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_REGISTRATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SPECIFICATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, fieldRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP).systemEnum('BuildPlanTaskProductKind'),\n relationshipRef: SlugSchema,\n /*\n * The two resources the edge relates, NAMED rather than parsed out of the ref.\n *\n * A ref is `<source>-<target>` by convention and that convention is not invertible:\n * `next-step-deal` splits as (`next`, `step-deal`) or (`next-step`, `deal`) and only the domain\n * plan knows which. The domain plan already carries both, so the plan passes them on instead of\n * making the host guess — a host that guesses wrong probes for a resource that does not exist\n * and reports the task permanently unlanded.\n */\n sourceResourceRef: SlugSchema,\n targetResourceRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_OPERATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_VIEW).systemEnum('BuildPlanTaskProductKind'), viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DOCUMENT).systemEnum('BuildPlanTaskProductKind'), documentRef: DocumentProductRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MODULE).systemEnum('BuildPlanTaskProductKind'), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG).systemEnum('BuildPlanTaskProductKind'),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n /** At least one, for the same vacuity reason as a schema's `fieldRefs`: the file exists on day one. */\n declarationRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CHART_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, chartRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.CUSTOM_COMPONENT).systemEnum('BuildPlanTaskProductKind'), componentRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MILESTONE).systemEnum('BuildPlanTaskProductKind'), milestoneRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_GUIDANCE).systemEnum('BuildPlanTaskProductKind'),\n /** Which definitions file carries it — a document and a flow live in different ones. */\n guidanceKind: z.enum(ApplicationGuidanceKind).systemEnum('ApplicationGuidanceKind'),\n guidanceRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PDF_TEMPLATE).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */\n templateRef: NonEmptyStringSchema,\n /**\n * #2305 S6: the deliverable of the firm's method this document is, as `<serviceRef>/<deliverableRef>`. Its resource\n * must be the one the deliverable is produced from; the derivation check compares them.\n */\n serviceMethodDeliverableRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),\n providerRef: SlugSchema,\n scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),\n /**\n * The provider this module adds operations to, copied from the integration plan's binding (#2025). Present, it\n * changes what landing means: the application's opt-in under `providers.augmentations.<augments>` lists the module's\n * package, rather than a scope naming `providerRef` (an augmentation writes no scope entry).\n */\n augments: SlugSchema.optional(),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_ROLE).systemEnum('BuildPlanTaskProductKind'),\n roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).refine((roleRef) => !CORE_ROLE_NAMES.has(roleRef), {\n message: 'A core role is the engine\\'s; an application role needs a name of its own.',\n }),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DATA_SEED).systemEnum('BuildPlanTaskProductKind'),\n seedKey: z.string().regex(DATA_SEED_KEY_PATTERN),\n /** The resource whose rows the seed writes — the `resourceType` it declares. */\n resourceRef: SlugSchema,\n content: z.enum(BuildPlanDataSeedContent).systemEnum('BuildPlanDataSeedContent'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_AGENT).systemEnum('BuildPlanTaskProductKind'),\n /** The agent's `ref` exactly as it is registered (`close-assistant.chat.agent`, `todos.overdue-triage`). */\n agentRef: z.string().regex(AGENT_WORK_REF_PATTERN),\n shape: z.enum(BuildPlanAgentShape).systemEnum('BuildPlanAgentShape'),\n /**\n * The firm's method steps this agent carries (#2305), as `<serviceRef>/<stepRef>`: set when the application has a\n * service method, so the derivation can be checked as total (every agent step has its agent). One agent may carry\n * several steps; each must be an AGENT step of the same `shape`.\n */\n serviceMethodStepRefs: z.array(z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN)).min(1).optional(),\n /**\n * The decision points of the firm's method this agent ASKS as a review question (an actor-system question routed\n * to people when its run suspends), as `<serviceRef>/<decisionRef>` (#2305). A decision is realized either so or by\n * a tool's approval gate (`serviceMethodDecisionRef`), never both: a review question IS the review, and its tool\n * carries no gate. Its route is built by the agent's code when it suspends, so only the realization is checked here.\n */\n serviceMethodAskedDecisionRefs: z.array(z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN)).min(1).optional(),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.AGENT_APPROVAL_GATE).systemEnum('BuildPlanTaskProductKind'),\n /** The gated tool's `functionRef` exactly as it is registered (`resource.<resourceType>.<operation>` for a resource tool). */\n functionRef: z.string().regex(AGENT_WORK_REF_PATTERN),\n route: z.enum(HumanDecision_RouteKind).systemEnum('HumanDecision_RouteKind'),\n /**\n * The role every answerer must hold, as the role table keys it: required for a ROLE or ASSIGNEE route, refused for\n * an OWNER route (answered by the person whose turn it is) — the engine's own rule for a gate, so a plan cannot name a\n * gate the engine would refuse at startup.\n */\n eligibleRole: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).optional(),\n /**\n * The professional qualifications the answerer must ALSO hold (#2967), as the application's\n * `professionalQualificationKinds` keys them: a ROLE or ASSIGNEE gate only, the engine's own rule. Landing compares\n * them with the gate's, so a gate built without the qualification the plan required does not land.\n */\n requiredQualificationKinds: z.array(z.string().regex(LABEL_KEY_SEGMENT_PATTERN)).min(1).optional(),\n /**\n * The decision point of the firm's method this gate realizes (#2305), as `<serviceRef>/<decisionRef>`: set when the\n * application has a service method. Its route must be the decision's, its role the decision's qualification's\n * role, and its qualifications that qualification's kind; the derivation check compares them.\n */\n serviceMethodDecisionRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),\n }).refine((gate) => (gate.route === HumanDecision_RouteKind.OWNER) === (gate.eligibleRole === undefined), {\n message: 'An OWNER gate names no role; a ROLE or ASSIGNEE gate names the role its answerer must hold.',\n path: ['eligibleRole'],\n }).refine((gate) => gate.route !== HumanDecision_RouteKind.OWNER || gate.requiredQualificationKinds === undefined, {\n message: 'An OWNER gate requires no qualification: its answerer is the person whose turn it is, whom nothing vets.',\n path: ['requiredQualificationKinds'],\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WORK_UNIT_RESOURCE).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.METERED_USAGE_RECORDING).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /** The operation that records, as the resource's configuration keys it (`record-sign-off` for `record_sign_off`). */\n operationRef: SlugSchema,\n /** The METERED product it records against: an `APPLICATION_BILLING_PRODUCT` of this plan, by its catalogue key. */\n productKey: SlugSchema,\n /** Whether it records at most once per row (`oncePerRecord`). A price per case counts each case once, however often it closes. */\n oncePerRecord: z.boolean(),\n /**\n * #2305 S5: the service of the firm's method whose price PER CASE this records, by its `serviceRef`. Its resource must\n * be that service's case and it must count once per row; the derivation check compares them.\n */\n serviceMethodServiceRef: SlugSchema.optional(),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RETENTION_BINDING).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n retentionClass: z.enum(DataRetentionClass).systemEnum('DataRetentionClass'),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RELATIONSHIP_CONFERRED_ROLE).systemEnum('BuildPlanTaskProductKind'),\n /** The relationship kind, by its key in `organizationRelationships` (`service`). */\n relationshipRef: SlugSchema,\n /** The role conferred, by its key in the role table (`ORG_QUALIFIED_ACCOUNTANT`), a core role or the application's. */\n roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER).systemEnum('BuildPlanTaskProductKind'),\n /** The channel the handler serves — one the integration plan declared. Email is the only declarable channel. */\n channel: z.literal(InboundChannelKind.EMAIL).systemEnum('InboundChannelKind'),\n /** The handler's `ref`, exactly as `inboundHandlerRef()` will accept it. */\n handlerRef: z.string().regex(INBOUND_HANDLER_REF_PATTERN),\n }),\n]);\nexport type BuildPlanTaskProduct = z.infer<typeof BuildPlanTaskProductSchema>;\n\n/**\n * Every artifact identity a product claims — one string per artifact, not one\n * per product, because a product may claim several.\n *\n * `RESOURCE_SCHEMA_FIELDS` is why this returns a list. Two tasks may both enrich\n * one resource's schema (a domain shape and a billing concern, say), and that is\n * legitimate; what must never overlap is the FIELDS. Comparing whole products\n * would refuse the legitimate pair, and comparing only the resource would let two\n * tasks claim one field and make landing ambiguous again.\n *\n * Derived from the product's own members rather than stored, and total over the\n * vocabulary, so a kind added tomorrow must state its identity here or fail to\n * compile — it cannot be silently treated as equal to its siblings.\n */\nexport function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): readonly string[] {\n switch (product.kind) {\n case BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_REGISTRATION:\n return product.operationRefs.map((operationRef) => `${product.kind}:${product.resourceRef}:${operationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_SPECIFICATION:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR:\n return [`${product.kind}:${product.resourceRef}`];\n case BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP:\n return [`${product.kind}:${product.relationshipRef}`];\n case BuildPlanTaskProductKind.RESOURCE_OPERATION:\n return [`${product.kind}:${product.resourceRef}:${product.operationRef}`];\n case BuildPlanTaskProductKind.APPLICATION_VIEW:\n return [`${product.kind}:${product.viewRef}`];\n case BuildPlanTaskProductKind.APPLICATION_DOCUMENT:\n /*\n * The ref AS AUTHORED, so a slug and a namespaced ref are different artifact identities even\n * where they mean the same document — the duplicate-artifact refusal cannot see two tasks\n * claiming one document if they spell it differently. Not normalisable: a slug carries no\n * namespace, so nothing can recover `public.` from `privacy-notice`. It costs nothing today\n * because a slug names no catalogued document at all, and the dispatcher skips such a task.\n */\n return [`${product.kind}:${product.documentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MODULE:\n return [`${product.kind}:${product.moduleRef}`];\n // One identity per DECLARATION, like schema fields: two tasks may compose one config file as\n // long as they declare different things in it.\n case BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG:\n return product.declarationRefs.map((declarationRef) => `${product.kind}:${product.configSurface}:${declarationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW:\n case BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.viewRef}`];\n case BuildPlanTaskProductKind.RESOURCE_CHART_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.chartRef}`];\n case BuildPlanTaskProductKind.CUSTOM_COMPONENT:\n return [`${product.kind}:${product.componentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MILESTONE:\n return [`${product.kind}:${product.milestoneRef}`];\n // The ref alone: a document and a flow sharing one ref is still one guidance identity, and the\n // runtime keys a person's saved state by it — two artifacts claiming it would collide there too.\n case BuildPlanTaskProductKind.APPLICATION_GUIDANCE:\n return [`${product.kind}:${product.guidanceRef}`];\n case BuildPlanTaskProductKind.PDF_TEMPLATE:\n return [`${product.kind}:${product.resourceRef}:${product.templateRef}`];\n case BuildPlanTaskProductKind.APPLICATION_WORKER:\n return product.jobRefs.map((jobRef) => `${product.kind}:${product.workerRef}:${jobRef}`);\n case BuildPlanTaskProductKind.APPLICATION_MINION:\n return product.behaviorRefs.map((behaviorRef) => `${product.kind}:${product.minionRef}:${behaviorRef}`);\n // The SCOPE is part of the identity: one provider bound on the backend and on the website is two artifacts.\n case BuildPlanTaskProductKind.PROVIDER_BINDING:\n return [`${product.kind}:${product.scope}:${product.providerRef}`];\n case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:\n return [`${product.kind}:${product.productKey}`];\n case BuildPlanTaskProductKind.APPLICATION_ROLE:\n return [`${product.kind}:${product.roleRef}`];\n // The key alone: two seeds may write one resource, and the key is what the seed run ledger tracks.\n case BuildPlanTaskProductKind.APPLICATION_DATA_SEED:\n return [`${product.kind}:${product.seedKey}`];\n case BuildPlanTaskProductKind.WEBSITE_PAGE:\n return [`${product.kind}:${product.pageRef}`];\n case BuildPlanTaskProductKind.WEBSITE_SECTION:\n return [`${product.kind}:${product.pageRef}:${product.sectionRef}`];\n case BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER:\n return [`${product.kind}:${product.chapterRef}`];\n case BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER:\n return [`${product.kind}:${product.handlerRef}`];\n case BuildPlanTaskProductKind.APPLICATION_AGENT:\n return [`${product.kind}:${product.agentRef}`];\n // The TOOL alone: one tool has one gate, so two tasks gating it differently would make landing ambiguous.\n case BuildPlanTaskProductKind.AGENT_APPROVAL_GATE:\n return [`${product.kind}:${product.functionRef}`];\n case BuildPlanTaskProductKind.WORK_UNIT_RESOURCE:\n return [`${product.kind}:${product.resourceRef}`];\n // The operation and the product: one operation may record several products, and two tasks recording one product on\n // one operation would make landing ambiguous.\n case BuildPlanTaskProductKind.METERED_USAGE_RECORDING:\n return [`${product.kind}:${product.resourceRef}:${product.operationRef}:${product.productKey}`];\n // One resource has one binding, so two tasks binding it would make landing ambiguous.\n case BuildPlanTaskProductKind.RESOURCE_RETENTION_BINDING:\n return [`${product.kind}:${product.resourceRef}`];\n case BuildPlanTaskProductKind.RELATIONSHIP_CONFERRED_ROLE:\n return [`${product.kind}:${product.relationshipRef}:${product.roleRef}`];\n default: {\n const unhandled: never = product;\n throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);\n }\n }\n}\n\n/**\n * The skill every billing-catalogue task is authored with (#1835): the product-catalogue contract, the\n * money encoding (minor units), and the pricing-surface facts. The dispatch derives it from an\n * `APPLICATION_BILLING_PRODUCT` product whatever the decomposer wrote, so an agent writing the catalogue\n * the backend sells from is never without it. A `METERED_USAGE_RECORDING` task carries it too (#2305 S5): the skill\n * says how an operation records usage of a metered product, and how a price per case counts each case once.\n */\nexport const BILLING_CATALOG_SKILL_REF = 'configure-billing';\n\n/**\n * The skill every application-roles task is authored with (#2490): the role table, the organization\n * types that offer a role, and the operation roles that make it matter. The dispatch derives it from an\n * `APPLICATION_ROLE` product whatever the decomposer wrote.\n */\nexport const APPLICATION_ROLES_SKILL_REF = 'application-roles-authoring';\n\n/**\n * The skill every data-seed task is authored with (#2234): levels, modes, business keys, and the\n * environment restriction that keeps demonstration rows out of production. The dispatch derives it from\n * an `APPLICATION_DATA_SEED` product whatever the decomposer wrote.\n */\nexport const DATA_SEED_SKILL_REF = 'seeding-authoring';\n\n/**\n * The skill every PDF-template task is authored with (#2495): the template contract, the file field it fills, and\n * where the generated file is stored. The dispatch derives it from a `PDF_TEMPLATE` product whatever the decomposer\n * wrote.\n */\nexport const PDF_TEMPLATE_SKILL_REF = 'pdf-template-authoring';\n\n/**\n * The skill a resource CONFIG task carries when the resource DECLARES personal data (#2495): its retention binding\n * lives in that configuration file, and storage limitation is a duty about personal data. The dispatch reads the\n * declaration from the resource's schema (the engine's personal-data markers), whatever the decomposer wrote.\n */\nexport const RESOURCE_RETENTION_SKILL_REF = 'resource-retention-binding';\n\n/**\n * The skill a task conferring a role through an organization relationship is authored with (#2305 S6): the relationship\n * kind's `confers`, the granting types that must offer the role, and the startup checks that refuse a mismatch. The\n * dispatch derives it from a `RELATIONSHIP_CONFERRED_ROLE` product whatever the decomposer wrote.\n */\nexport const ORGANIZATION_RELATIONSHIPS_SKILL_REF = 'organization-relationships';\n\n/**\n * The skill each agent shape is built with (#2966). The dispatch derives it from an `APPLICATION_AGENT` product whatever\n * the decomposer wrote. Total over {@link BuildPlanAgentShape}, so a shape added tomorrow must name its skill.\n */\nexport const BUILD_PLAN_AGENT_SHAPE_SKILL_REF: Readonly<Record<BuildPlanAgentShape, string>> = {\n [BuildPlanAgentShape.CHAT_ASSISTANT]: 'flows-actors-chat-assistant',\n [BuildPlanAgentShape.AUTONOMOUS]: 'flows-actors-autonomous-agents',\n [BuildPlanAgentShape.INVOKED]: 'flows-actors-llm-agent-invocation',\n [BuildPlanAgentShape.FLOW_STEP]: 'flows-actors-declared-flow',\n};\n\n/**\n * The skill every agent and every approval gate is ALSO built with (#2966): what the agent's use is for, whether it\n * decides anything about a person, and its gated writes. An agent built from its shape skill alone is the undeclared,\n * unguarded shape.\n */\nexport const AI_USE_DECLARATION_SKILL_REF = 'ai-use-declaration';\n\n/**\n * The skill an approval gate is built with (#2966): `flows-actors-chat-assistant` is where the `humanApproval` contract\n * is taught whole — the three routes, the eligible role, an assignee, escalation, deadlines and the review calendar —\n * whichever kind of agent calls the tool.\n */\nexport const AGENT_APPROVAL_GATE_SKILL_REF = 'flows-actors-chat-assistant';\n\n/** The skill a work-unit task is built with (#2966): the `workUnit` declaration, model prices and the case passed to agent turns. */\nexport const WORK_UNIT_SKILL_REF = 'model-cost-attribution';\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: ModuleRefSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: ModuleRefSchema,\n relationshipRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),\n /** The companion generation step this task runs (e.g. i18n-labels, email-templates); resolved by the companion, never by a coding agent. */\n generationStepRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),\n /**\n * Which shell surface this task authors — the placement family's OWN\n * `PlacementSurface`, deliberately not a build-plan copy of it.\n *\n * A copy was written first and was a defect, caught by probing the landing\n * renderer rather than by any test: `PlacementAddress` discriminates on\n * `surface` with `z.literal(...)` per option, so only the VALUES survive into\n * the schema, and the renderer resolves a discriminator by matching that value\n * SET against the exported enums. Two enums with identical values made the\n * match ambiguous, the renderer correctly refused to guess an owner, and the\n * address discriminator became unnameable — a landed placement plan would have\n * emitted `surface: \"SETTINGS_HUB\"` as a bare string instead of\n * `PlacementSurface.SETTINGS_HUB`. One concept, one named source.\n */\n surface: z.enum(PlacementSurface).systemEnum('PlacementSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_FRONTEND), moduleRef: ModuleRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_BACKEND), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_FRONTEND_CONFIG),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.WEBSITE) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.WORKER),\n /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */\n workerRef: SlugSchema,\n runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.MINION),\n /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */\n minionRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),\n]);\nexport type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;\n\n/**\n * One ordered build task. It names WHAT to build and WHY; it never carries\n * HOW (no paths, commands, prompts, cwd, model, profile). The host resolves\n * the physical allowed/prohibited paths and the fixed verification from the\n * target kind, and the installed skills from `skillRefs` against the app\n * knowledge catalog.\n *\n * Dependency readiness is DECLARED as prerequisite task refs and RESOLVED by\n * the host (a prerequisite is satisfied when its task has landed), never a\n * solved DAG the model must get right.\n */\nexport const BuildPlanTaskSchema = z.strictObject({\n /** `build-task-<slug>`, stamped by the trusted runtime. */\n taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),\n /**\n * One sentence of intent: what this task delivers.\n *\n * Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also\n * hold. The workbench's reading decorations are keyed by INSTANCE, and it gives those refs a receding\n * identifier look, which the objective sentence took too while it shared their leaf.\n */\n objective: z.string().trim().min(1),\n target: BuildPlanTaskTargetSchema,\n /**\n * The artifacts this task is accountable for — what proves it done.\n *\n * Coding tasks should declare at least one product that composition did not already\n * write. A target is a shared mutation scope; its scaffolded file is not evidence\n * that this task's intended work exists. Products identify the output to probe.\n *\n * Empty declarations remain representable and produce the advisory\n * `TASK_DECLARES_NO_PRODUCT`. The host may advance after a COMPLETED durable run,\n * while naming the task in `unverifiableLandedTaskRefs`: it ran, but its output\n * cannot be proven from a product declaration. An unexecuted task is not landed.\n * This distinction avoids repeatedly dispatching the same unprovable task without\n * presenting execution history as evidence that the intended product is correct.\n *\n * The ONE hard exception is a `COMPANION_GENERATION_STEP`, which must declare NONE.\n * That kind already carries its own typed landed condition, owned by the\n * generation-step service — a set computed asynchronously (planner units x\n * enabled locales), and for the migration step a STATE rather than files. A\n * product declared beside it would be read by nothing, which is the inert\n * declaration this field exists to avoid. Enforced on the graph below, in both\n * directions.\n */\n produces: z.array(BuildPlanTaskProductSchema).default([]),\n /**\n * Exactly ONE functional topic this task belongs to.\n *\n * **It does NOT drive ordering** — this said \"drives cross-app ordering\" until 2026-08-30 and\n * nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it\n * is the only thing that decides what may run next.\n *\n * What it DOES: the dispatch host stamps it into the coding-agent's task payload beside\n * `skillRefs`, so the agent is told which phase of building the application this task belongs to.\n * That is context an LLM reads, not a value the runtime branches on — the distinction matters,\n * because a reader who believes it orders will look here for a scheduling bug that lives in the\n * prerequisite graph. See issue #124.\n */\n functionalTopic: z.enum(MetaWorkflow_FunctionalTopic).systemEnum('MetaWorkflow_FunctionalTopic'),\n /** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */\n skillRefs: z.array(SkillRefSchema).min(1),\n /** Task refs that must have landed first; resolved by the host, not solved by the model. */\n prerequisiteTaskRefs: z.array(z.string()).default([]),\n /**\n * What this task is accountable to — traceability only, NEVER scope authority.\n *\n * The vocabulary is the target aspects `BUILD_PLAN_FAMILY_ASPECTS` declares for this edge:\n * functional and non-functional requirements, roadmap phases, the vision's success criteria and\n * constraints, drafted features, pricing plans, and the brand's name, logo direction and visual\n * tone. Each target after the first three was added because a producer had already been writing\n * it (#629, #1433, #1835, #2221). A companion generation step serves what it consumes: the `logo`\n * step serves the brand's logo direction and name.\n *\n * This schema accepts any non-empty string. Generation does not: the edge is DECLARED, so a key\n * that resolves to no element of a target family (when that family has landed) is a dangling\n * reference. The model is told so on retry, and the landing refuses it. That is why widening the\n * vocabulary to what producers genuinely mean matters: a true link the vocabulary does not name\n * fails generation. The workbench renders a key outside the vocabulary as visibly unresolved.\n */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n /**\n * Who asked for this task DIRECTLY (#1608), rather than it being derived from the specifications: the\n * signed-in person who added it in conversation. STAMPED by the append, never authored: a value in\n * generated output is discarded. Absent on every task the decomposition derived.\n *\n * It is what keeps a requested task alive. Build decomposition refines the plan from the domain plan, and\n * a task nothing in the specifications justifies would read as unjustified and be dropped; a requested\n * task it leaves out is carried forward instead, keeping only the prerequisites the new plan still holds.\n */\n requestedBy: NonEmptyStringSchema.optional(),\n});\nexport type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;\n\n/**\n * THE build-plan payload — a **single aggregate per product**: the ORDERED\n * task graph that turns the accepted domain plan into buildable units.\n *\n * **Artifact-family id: `build-plan`.** This schema is the shape of the\n * journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===\n * 'build-plan'` (the `family` vocabulary stays an open string owned by the\n * selector surface; this note is the single place tying the SHAPE to the\n * NAME). Produced by the build-decompose playbook, consumed by\n * build-dispatch (and build-scale, which runs the same branch): ready tasks\n * are dispatched in parallel waves of up to the application's build\n * parallelism (`wildo workbench parallelism`, 5 by default; 1 = one at a\n * time).\n *\n * Invariants enforced here: unique task refs; every prerequisite names a task\n * in this graph; no self-prerequisite. Cycle detection and ordering\n * soundness are the deterministic validator's job (`validateBuildPlanTaskGraph`).\n */\nexport const BuildPlanTaskGraphSchema = z.object({\n version: z.enum(BuildPlanTaskGraphVersion).default(BuildPlanTaskGraphVersion.V1),\n /**\n * At least one task, at the SCHEMA — not merely as a validator warning. The first live playbook-loop\n * run (2026-08-24) proved why: build-decompose answered `tasks: []`, which was schema-valid, passed\n * `_core` validation as a mere warning, and LANDED — overwriting a completed 3-task plan with a\n * vacuous artifact. Decomposing to zero tasks is a refusal (\"nothing to decompose\"), never an\n * artifact: an empty plan carries no information a reader could act on, and the file it replaces\n * does. Same vacuity class already closed on the requirements family (`functional: min(1)`).\n */\n tasks: z.array(BuildPlanTaskSchema).min(1),\n}).superRefine((graph, context) => {\n const refs = new Set<string>();\n graph.tasks.forEach((task, index) => {\n if (refs.has(task.taskRef)) {\n context.addIssue({ code: 'custom', message: `duplicate build task ref \"${task.taskRef}\"`, path: ['tasks', index, 'taskRef'] });\n }\n refs.add(task.taskRef);\n });\n /*\n * No two tasks claim the same artifact.\n *\n * This is what makes landing DECIDABLE, not a tidiness rule. If two tasks name\n * one product, the host cannot tell which of them a present artifact proves —\n * exactly the ambiguity that shared `target`s created, arriving through the\n * field that replaced them. Enforced here rather than left to the validator\n * because a graph that cannot answer \"has this task landed?\" is not a graph\n * the loop may run at all.\n */\n graph.tasks.forEach((task, index) => {\n const isGenerationStep = task.target.kind === BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP;\n if (isGenerationStep && task.produces.length > 0) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" is a companion generation step and must declare no products; its landing is the generation step's own condition`,\n path: ['tasks', index, 'produces'],\n });\n }\n });\n const productOwners = new Map<string, string>();\n graph.tasks.forEach((task, index) => {\n task.produces.forEach((product, productIndex) => {\n buildPlanTaskProductIdentities(product).forEach((identity) => {\n const owner = productOwners.get(identity);\n if (owner !== undefined) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" claims the same artifact as \"${owner}\" (${identity}); an artifact is produced by exactly one task`,\n path: ['tasks', index, 'produces', productIndex],\n });\n return;\n }\n productOwners.set(identity, task.taskRef);\n });\n });\n });\n graph.tasks.forEach((task, index) => {\n task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {\n if (prerequisite === task.taskRef) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" cannot be its own prerequisite`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n } else if (!refs.has(prerequisite)) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" names an unknown prerequisite \"${prerequisite}\"`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n }\n });\n });\n});\nexport type BuildPlanTaskGraph = z.infer<typeof BuildPlanTaskGraphSchema>;\n```\n\n## What this playbook does\n\nYou are the **dispatch orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, for *one* task at a time: *\"dispatch this\ntask safely, verify it, and record what happened.\"* You do **not** produce a new\njourney artifact — the dispatch's observable result (the change-set + the task\nstatus) is materialized by the runner on the task row, not authored here (see \"What\nyou emit\"). You do **not** decompose the plan, author any schema, or write any code\n— the coding agent writes the code at dispatch time; the plan is the\nbuild-decompose playbook's; scale is the scale playbook's.\n\n## The dispatch contract — the runner owns the mechanism, you sequence it\n\nMost of the D4 dispatch contract is **runner mechanism**, not prose you re-implement:\nthe runner composes the context pack, opens a coding session with the agent over the\nAgent Client Protocol and sends one prompt turn, answers the agent's permission\nrequests within the declared ceiling, captures the change-set, runs the verify hook,\nkeeps each task from being built twice at once, fills the wave to the configured width,\nand applies its configured execution limits. Your method here is the **declarative recipe** the runner interprets —\n*which* task to dispatch next, *when* it is authorized, and *how* its outcome is\njudged. Do not hand-compose a dispatch prompt or drive git yourself; let the runner\nown composition and change-set capture.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the build by one wave*\n(by one task when the build parallelism is `1`).\nBefore dispatching anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the **build plan** is present\n and approved, and confirm the **foundation** ran. For each build-plan task,\n determine its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify), or\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run or a\n failed verify). This tri-state matters: under `keep_and_flag` a **failed** task\n *also* has a captured change-set, so \"has a change-set\" alone does NOT mean the\n task is done — read the task's terminal status + verify outcome, not just the\n presence of a change-set.\n2. Read the approved **build plan** (`build-plan` — the ordered task graph). It is your\n work list.\n\n Evidence that the foundation ran is `./wildo.saas.config.ts` itself, committed: the\n app either has a config and a skeleton or it does not, and git answers that without a\n journey artifact standing in for it. (A `foundation-manifest` family was that stand-in\n until 2026-08-25; it was retired with the app-creation verification/digest aspect, and\n this playbook no longer gates on it.) The honest limitation inherited from the\n foundation step still applies: at scaffold depth the on-disk skeleton *materialization*\n depends on greenfield bring-up tooling (deferred). The dispatch contract is real and\n runs against an **existing** app skeleton — the dogfood app already has one.\n\n// Operator status: `wildo context journey` (eligibility board + runs in flight). Which tasks already\n// landed is read from GIT by the runner itself — a task is landed when every file it produces is\n// committed clean.\n\nYou **read** `build-plan`; you **write** no journey artifact\n— the runner records the change-set + task status on the dispatched task's row.\n\n## Precondition — the application must establish the agent's role, or dispatch stalls\n\nCheck this before the first dispatch of an application's life. It costs one look and it is the\ndifference between a working lane and one that burns model time producing nothing.\n\n**The application needs a root `CLAUDE.md` stating that a task dispatched by its dev companion is\nlegitimate work.** Without it the agent is right to refuse, and refusing is what it does.\n\nThe reason is structural rather than a matter of tone. A dispatched task reaches the agent as an\nordinary prompt — a user turn carrying an objective, a mutation scope and skill refs. Nothing in\nthat turn proves where it came from. So the agent is being handed conversational content that\ntells it to write files into a repository, which is indistinguishable from the thing every\ncareful agent is supposed to decline, and the more trustworthy the agent the more reliably it\ndeclines. Measured on a real application with no such file: two dispatched runs stalled, one\nanswering *\"content that arrives as conversational input doesn't get to reassign what I am\"*.\n\nThe failure does not look like a missing file. It looks like an agent that deliberates well,\nidentifies exactly which files it would author, explains its reasoning, asks a human to confirm,\nand ends its turn — `end_turn`, no error, no denial, an empty change set, and a bill for the\ntokens. Read as \"the agent chose not to work\", which invites prompt-tuning that cannot fix it.\n\n`wildo init` scaffolds this file. An application created before that, or one whose `CLAUDE.md`\ncovers only its own conventions, needs the section added. What it must establish:\n\n- the task is **selected by the host** from the accepted build plan, not composed by a caller;\n- its **file edits** are **confined before they arrive** — the host answers every permission request\n against the declared mutation scope and refuses paths outside it;\n- its **shell commands are NOT**, and the section must say so. A command declares no `locations`, so\n the scope predicate never runs for one; telling an agent it \"need not police itself\" is true of its\n edits and false of its commands, and that is the half a stray write comes through. Name the\n compensations with it: the post-run change set and the companion's warning DETECT such a write,\n they do not prevent it;\n- it is **reversible** — every write is an uncommitted working edit until something commits it. Do\n not state WHO commits as a property of the lane: that is the host's autonomy posture, it changes,\n and an agent that reads \"a human commits\" from a scaffold written under a different posture is\n working from a stale contract.\n\nTwo smaller things belong in the same section, because both were observed costing a run:\n\n- **Say what `allowedPathPrefixes` are relative to.** The agent receives bare prefixes such as\n `shared-lib/src/modules/<module>/` with no root, and cannot verify its own confinement against\n them. One sentence naming the application root removes the ambiguity.\n- **Do not name a task so it reads as a fixture.** An agent that concludes it is looking at a\n smoke test will say so and stop. Name the task after the product change it makes.\n\n## Step 1 — Select the ready tasks (the wave)\n\nWalk the build plan in its authored order. A task is **ready** when it is not yet\ndispatched (or a previously-**failed** task cleared for retry — see Step 5), it is\nnot already running, and its declared prerequisites have all **succeeded**. The\nrunner selects ready tasks in that order and keeps up to the build parallelism of\nthem running; when a run settles, its slot is refilled with whatever is ready THEN,\nso a task that just landed unlocks its dependents within the same wave. If **no**\ntask is ready — every task has already succeeded, or the only undispatched tasks\nare blocked behind a still-unresolved failure — there is nothing to dispatch:\nreport the build as done (or blocked on the failed task) and stop. An empty build\nplan is the same.\n\n- **How many run at once is the build parallelism, and it is the person's call.**\n `wildo workbench parallelism` shows it (5 by default) and sets it; `1` means one\n workspace-mutating run at a time. The runner reads it at the start of every wave,\n so a change needs no restart. Do not try to widen a wave beyond it.\n- **The runs share ONE worktree, by design.** Concurrent runs may edit the same\n files. The runner does not prevent that; it prevents only a task being built\n twice at once, and it REPAIRS the rest when the wave's runs have settled: it\n commits what the runs' own accepts left as one change naming every run whose\n writes it carries, then re-runs ALONE each task whose finished product a sibling\n overwrote. Each run's record says which runs overlapped it (`concurrency`), and\n whether a failure is suspected to come from a sibling (`interferenceSuspected`).\n- **One wave is bounded.** A call takes at most four tasks per slot, and runs each\n generation step at most once; it then stops taking tasks, waits for its runs and\n returns. The next run of this playbook continues from where the build stands.\n- **One wave at a time.** A second wave is refused while one runs, including during\n its end-of-wave commit and repair: start the next only once the running one has\n ended.\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task is ready\n only when every task it depends on is dispatched-and-succeeded (verify passed).\n A prerequisite that is dispatched-and-**failed** (its change-set is flagged for\n triage under `keep_and_flag`) does **not** satisfy the dependency — its dependents\n stay **blocked** until the failure is triaged and the prerequisite re-dispatched\n successfully. Do not build a config on a schema whose run failed. Never dispatch a\n task before the stage it depends on (a config before its schema, a spec before its\n ui-behavior — the build-decompose playbook ordered these).\n- **Companion-generation steps are not coding-agent dispatches.** A build-plan task\n marked as a companion-owned generation step (labels / i18n, email templates,\n seeds) runs through its deterministic companion endpoint, not the coding-agent\n dispatch lane. Route it there; do not dispatch a coding agent for it. In a wave\n the runner runs a ready generation step in its turn while the coding runs already\n started keep going.\n\n## Step 2 — Check the actual host authorization boundary\n\nA coding dispatch writes the application workspace. Read its selected task, readiness,\nmutation scope and the configured coding host's authorization policy before invoking it.\nEvery run of a wave writes the same shared workspace; each is confined to its own task's\nmutation scope, and nothing confines it from its siblings (Step 1).\n\nThe playbook's `approval` declaration and the journey autonomy presets express policy\nintent. The current playbook runner does not interpret them as pre-dispatch gates,\nautomatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does\nnot create a pending Authority Request, and no authority workflow exists to create one —\nnever invent one from an enum.\n\nLikewise, do not infer enforced per-playbook or per-journey run ceilings from declared\nbudget fields. Respect the limits actually reported by the execution host. Inspect the\nrecorded changes and verification result after each task; no preset commits or accepts them.\n\n## Step 3 — Dispatch the task through the coding-agent contract\n\nThe companion triggers the run (from a console, `wildo build run` or `/wildo:build`). The runner then performs the D4\ndispatch contract for you (you do not hand-assemble any of it):\n\n1. **Context pack** — the runner composes the prompt: the task brief, the task's\n skill pointers (`Read .claude/skills/<skillRef>/SKILL.md first` — the per-task\n HOW-skills the build plan named on this task), the relevant journey / definition\n artifacts, an introspected app-reality block, and the repo paths.\n2. **Session and one prompt turn** — the runner starts the agent over the Agent\n Client Protocol and opens a session rooted at the app workspace (cwd = the\n application root, so `./CLAUDE.md`, the sub-`CLAUDE.md`s, and the `.claude/` rules\n and skills load naturally), then sends the task as a single prompt turn. It is a\n session rather than a one-shot process, which is what makes the next three things\n possible at all:\n - **Permissions are answered, not assumed.** The agent asks before each action it\n considers privileged; the runner answers within the execution profile's declared\n ceiling and refuses anything above it, or anything touching a path outside the\n task's mutation scope. Refusals are counted on the task row, so a run that was\n held back is distinguishable from a run that had nothing to do.\n - **The turn can be cancelled.** Cancellation asks the agent to stop and waits, so\n the run terminalises with its change-set intact instead of being killed — an\n operator who stops a run still needs to know what it had already written.\n - **Usage is reported.** Tokens and cost come back from the run itself rather than\n being unavailable, which lets the host report a terminal timeout instead of leaving the run ambiguous.\n3. **Change-set capture** — the runner captures a git worktree snapshot before and\n after the run and attributes each touched file (the run's own edit vs. an\n already-dirty parallel-session file vs. a file that appeared during the run),\n recording a structured change-set on the task row. On the dogfood tree,\n dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture\n *attributes* rather than assuming the run had the tree to itself.\n\n// The trigger is `wildo creation run <playbookRef>` or `wildo build run` (from a Claude Code session,\n// `/wildo:run` or `/wildo:build`), or the workbench; each reaches the companion with its local token.\n// The runner composes the typed context pack, runs one ACP prompt turn, and captures the change-set.\n\n## Step 4 — Verify OUTSIDE the coding agent\n\nTrust, but verify. The verify gate runs **outside** the coding agent, after the run,\nso the agent cannot mark its own homework:\n\n- **`dispatch-typecheck` (deterministic — the auto-run trust floor).** The runner\n maps this `deterministic_validator` gate (`validatorRef: typecheck`) onto the\n dispatch verification hook and runs a typecheck (`pnpm exec tsc --noEmit`) over the\n application workspace after the run, **outside** the coding agent. This is a\n **real, wired** gate — it actually executes and its result is recorded on the task\n row. A run whose typecheck fails is a failed run (apply the failure disposition in\n Step 5). At scaffold depth the gate is a **workspace-wide** typecheck (one static\n gate for every dispatch of this playbook); narrowing it to the specific package a\n given task touched — a per-task `typecheck:<pkgDir>` or a `vitest:<path>` targeted\n at the task's tests — is a later refinement, since a static playbook gate cannot\n vary per task.\n- **`dispatch-outcome-sound` (declarative reviewer checklist).** The six-invariant\n reviewer checklist (task accomplished, change-set scoped to the task, verify ran +\n passed, attribution clean, failure disposition correct, boundary discipline)\n is the *trust-but-verify reviewer* pass. It is **declarative** — the creator's\n review checklist; the compiled build-dispatch Evaluation Treatment is what the\n runtime judges with, and the deterministic typecheck above is what runs\n automatically. **In a wave the runtime does not compose this judge per run**: each\n run's record carries its outcome, its checks, and what it overlapped, and the\n wave's end-of-run repair is on the wave's result. Read those; with a build\n parallelism of `1` the judge runs on the single dispatch as before.\n\n- **The look (a task that changes how a surface renders — advisory).** A task whose skills include\n `resource-ui-behavior` changes what a person SEES, which no typecheck can confirm. The coding\n agent is asked, by that skill's verification, to photograph the surface with `wildo frontend look`\n (the listing, the first record, its form; light and dark), compare the screenshots with the skill's\n `references/visual-quality-rubric.md`, and fix what fails before finishing. Its summary says that it\n looked and what it changed after looking — or, when the camera could not run (exit code 2: no\n Playwright or Chromium, the frontend or its sign-in not answering), that it could not. This check\n never blocks the run: a look that could not run is MARKED in the result, not a precondition.\n\n## Step 5 — Record the result and apply the failure disposition\n\nThe runner records the change-set + the task's terminal status on the task row. On a\n**failed or timed-out** run, the current coding host retains its captured changes for inspection (the declaration describes this as **`keep_and_flag`**): the\ncaptured change-set is **kept and flagged for human triage** — never silently\nreverted, and never left as an un-recorded half-applied state. The change-set capture\n*is* the flag: it attributes exactly which files the run touched, so a human can\nreview, keep, or unwind them.\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a failed\n> run's edits is a *mutating* git operation, deliberately **outside** the read-only\n> change-set carve-out the dispatch lane observes (the runner *observes* git —\n> baseline/post-run snapshots — but stage/commit/revert stay a human/CLI concern).\n> So `keep_and_flag` is both the correct F-5 workspace-safety posture (no silent\n> half-applied state) and the behavior the runner actually enforces today. Wiring a\n> `revert_changeset` path is a deliberate later boundary decision, not a gap this\n> playbook papers over.\n\nOn a **succeeded** run (change-set captured + verify passed), the task is done and\nits dependents become eligible. On a **failed** run, the task is **not** done — it is\nflagged for human triage, and its dependents stay blocked (Step 1) until it is\ntriaged and cleared for re-dispatch. Triage is a human decision: keep + fix forward,\nunwind the flagged change-set by hand, or re-dispatch the task once its blocker is\nresolved. This playbook does not auto-retry a failed task — automated retry / backoff\nis a deferred build-loop-resilience concern, and human triage is the v1 disposition;\nhere the loop simply surfaces the failure and stops advancing that dependency chain.\n\nThen **loop**: on the next run of this playbook, the build plan's task records reflect the\noutcomes of the wave that just ran (`wildo build tasks`), and the next wave selects from\nwhat is ready now (Step 1). Close a significant stretch of dispatches with a progress summary — what was\nproduced, which change-sets landed, what verify said, and any failed task left\nflagged for triage.\n\n## Refine, don't re-dispatch\n\n- **Never re-dispatch a SUCCEEDED task.** A task that is dispatched-and-succeeded\n (change-set captured + verify passed) is done — advance to the next ready task, do\n not re-run it because the plan was re-opened elsewhere. A dispatched-and-**failed**\n task is a different case: it is re-dispatchable once triaged (Step 5) — a captured\n change-set alone does not make a task \"finished\".\n- **Follow the plan's order.** If the build plan was refined upstream (a task added,\n an ordering corrected), respect the new order on the next selection — do not cache\n a stale work list across runs.\n- **A host execution refusal is a real stop.** When an actual execution limit is reported, stop dispatching\n and report what remains; do not do the coding work out-of-band to \"finish the\n build\" — that makes the journey's task history a lie.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **dispatch depth**: which tasks run, under what contract, and\nwhat each run's outcome was. Explicitly **out of scope here**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order the\n graph, or add tasks — the **build-decompose** playbook owns the task graph. You\n read it and dispatch from it.\n- **The width and the isolation model.** How many tasks run at once is the\n application's build parallelism, set by the person; the runs share one worktree and\n are repaired, not isolated. You do NOT choose a width, partition the worktree, or\n design a different schedule.\n- **A `revert_changeset` failure path.** Undoing a failed run's edits is a mutating\n git op outside the read-only change-set carve-out — deferred. `keep_and_flag` (keep\n + flag the captured change-set for triage) is the v1 disposition.\n- **Auto-executed reviewer checklist.** The checklist ships **declarative** —\n the deterministic typecheck gate runs automatically and the compiled Evaluation\n Treatment is the judged protocol; nothing executes the checklist prose. Do not\n assume it auto-ran.\n- **Schema / field authoring + code generation.** You dispatch a task; the **coding\n agent** authors the fields, schemas, ui-behavior, and code at dispatch time. If you\n catch yourself writing application code or a resource schema here, stop — that is\n the dispatched agent's job, not the orchestrator's.\n\nIf you find yourself designing how MANY agents run concurrently, stop: the width is\nthe build parallelism and the schedule is the runner's.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable result\nof a dispatch — the **change-set** (files touched, attributed, summarized) and the\n**task status** — is materialized by the runner on the dispatched task's row, not\nauthored by this playbook. That is deliberately not duplicated into a separate\njourney artifact family: the task row already *is* the dispatch record, and a second\nhome for the same record would drift.\n\nDispatch uses the configured host's actual authorization boundary. The creator reviews\nthe recorded change-sets and verification outcomes afterwards, wave by wave, until the\nbuild plan is fully dispatched.\n\n## References\n\n- A playbook's declared `approval` and failure policy gate nothing on a leaf run; they are read only\n at a composite lane's boundary, where they frame a decision for the person and revert nothing.\n\n## Reviewer checklist — `dispatch-outcome-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim (minus the retired runner's closing sentence, and with repository-specific wording made application-neutral):\n\nJudge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants (and, for a surface-rendering task, the seventh below) and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag). Files attributed BASELINE_DIRTY_AMBIGUOUS were already dirty and changed again during the run; this establishes uncertainty, not ownership by a parallel editor. Every changed path outside the declared scope — ambiguous or not, and including a parallel session's edits, which the capture cannot tell apart from the run's own — is RECORDED on the result as `outOfScopePaths`; nothing refuses the run for it. Treat each as a CONCERN and resolve its authorship during review, never as a GAP by itself. Committed-window entries and recognized concurrent host-lane paths are classified separately and left off that list. (3) VERIFY RAN + PASSED — the deterministic verify gate (typecheck) ran OUTSIDE the coding agent after the run and passed; a run recorded as succeeded whose typecheck the reviewer cannot confirm passed is a CONCERN, and a run whose typecheck FAILED but was recorded succeeded is a GAP. (4) ATTRIBUTION READ AGAINST THE WAVE — the run's edits are cleanly attributable to it in the captured change-set (files classed RUN_EXCLUSIVE or APPEARED_DURING_RUN). In a wave the runs share one worktree, so overlap is expected and RECORDED rather than prevented: the run's `concurrency` entry names the runs that overlapped it and the paths they both touched. A change-set dominated by BASELINE_DIRTY_AMBIGUOUS overlap, or captured across a HEAD that moved mid-run, is a CONCERN the reviewer resolves using that record before accepting the run; a run marked `interferenceSuspected`, or whose product a sibling overwrote, is a CONCERN until its re-run alone has landed. Overlap alone is not a GAP. (5) FAILURE DISPOSITION CORRECT — a failed/timed-out run's captured change-set is KEPT + FLAGGED for human triage (keep_and_flag), never silently reverted nor silently left as an un-recorded half-applied state; a failed run with no recorded change-set flag is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the dispatch stays at dispatch depth: it runs the ready tasks up to the build parallelism, captures + verifies + records each, and applies onFailure. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT choose its own width or a different isolation model (the build parallelism is the person's setting, and the runs share one worktree by design), and does NOT itself author schemas / fields / code (the coding agent does that at dispatch time). Evidence of re-decomposition, a width other than the configured one, or the dispatcher authoring code itself is a CONCERN (scope creep out of the dispatch lane). (7) LOOKED AT — only for a task whose skills include `resource-ui-behavior`: the run's summary reports that the surface was photographed with `wildo frontend look` and checked against the rubric, or says why the camera could not run. A summary that says neither is a CONCERN, never a GAP, and the reviewer can take the look themselves with the same command. (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)\n",
23
23
  "skillRefs": [],
24
24
  "skillBodyRefs": [],
25
25
  "contextSources": [],
@@ -14,8 +14,8 @@ Read and apply these patterns from the application-developer point of view:
14
14
 
15
15
  ## What this step does
16
16
 
17
- The framework ships one composition scenario per folder under `templates/saas/scenarios/`. Two of
18
- them — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The
17
+ The framework ships a closed set of composition scenarios, each one applied by `wildo compose <ref>`
18
+ with the scenario ref named in the table below. Two of them — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The
19
19
  others give an application a marketing website, a documentation portal, a cron minion, a worker, a
20
20
  provider, a file-picker provider, a second website locale, another deployment environment or the
21
21
  optional 3D layout, and until this step existed nothing in the journey decided whether an
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "bottom_up.capability-composition",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Capability composition — decide WHICH of the framework's composition scenarios this application needs (a marketing website, a technical-documentation portal, workers, minions, a second locale, a provider, an environment) and record that decision as the `capability-composition` family, one decision per scenario the framework ships, each naming the declaration it was derived from. DERIVED, never asked: a website follows from an inbound web channel in the market snapshot, a landed brand brief or declared pricing plans; a documentation portal from targeted organisation ICPs or a portability requirement; where no typed declaration can decide a scenario yet (a worker, a minion, a locale) the record says DECLINED and names the declaration that would decide it. Scenarios another step applies (modules and resources by the domain composition, sections and pages by build tasks, providers by the provider decision, environments by deployment) are recorded as owned by that step, so the record stays total. Runs after the domain plan and before the foundation, which applies the NEEDED scenarios and names every scenario applied and declined with its basis.",
6
6
  "preconditions": [
@@ -42,7 +42,7 @@
42
42
  ],
43
43
  "stepOutputs": [],
44
44
  "method": {
45
- "guidance": "# Capability Composition — Which Scenarios This Application Needs\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe framework ships one composition scenario per folder under `templates/saas/scenarios/`. Two of\nthem — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The\nothers give an application a marketing website, a documentation portal, a cron minion, a worker, a\nprovider, a file-picker provider, a second website locale, another deployment environment or the\noptional 3D layout, and until this step existed nothing in the journey decided whether an\napplication needed any of them: they were reachable only by a person running `wildo compose`.\n\nThis step records that decision as the `capability-composition` family: **one decision per\nscenario the framework ships**, each with a disposition, the closed basis it was derived from,\nand a one-sentence detail naming the declaring entries.\n\n## It is derived, never asked\n\nNothing here is an interview. Every decision is read off what the application's own families\nDECLARE:\n\n| scenario | NEEDED when | read from |\n|---|---|---|\n| `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |\n| `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |\n| `add-locale` | a website is composed and either the market targets a country whose languages the configuration does not serve (one locale for each such country's first listed language) or the configuration serves more than one language (one locale per language beyond the primary) — the decision names its `locales` | `market-snapshot.icps` geographies (CORE and EXPANSION), and `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |\n\nWhere no typed declaration can decide a scenario, the record says **DECLINED with the basis\n`NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for\nsomebody to add, never a question for somebody to answer. Today the only such case is `add-locale`\nwhen a website is composed but the host could not read the configuration's languages.\n\nEach basis justifies exactly ONE disposition (`COMPOSITION_BASIS_DISPOSITION`): a declaration that\nwas read and implies nothing is `NO_DECLARATION_IMPLIES_IT`, never a NEED basis with a DECLINED\nverdict. A market whose countries the configuration cannot address is never declined in silence:\nwith a website it makes `add-locale` NEEDED on `MARKET_TARGETS_UNSERVED_LANGUAGES`, naming each\nlanguage, and with or without one the coherence report names the gap as a contradiction, so the\nconfiguration's own `enabledLanguages` can follow.\n\nScenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so\nthe record stays total without claiming the application lacks them:\n\n| scenario | owner |\n|---|---|\n| `add-module`, `add-resource` | `bottom_up.foundation` — the domain composition |\n| `add-minion`, `add-worker-node`, `add-worker-rust` | `bottom_up.foundation` — one per surface the integration plan declares |\n| `add-custom-operation`, `add-website-section`, `add-marketing-page`, `add-file-picker-provider` | the build tasks that produce those artifacts (`bottom_up.build-decompose`) |\n| `add-provider` | the foundation's provider decision |\n| `add-environment` | the operator, at deployment (`wildo compose add-environment`) |\n| `add-3d-layout` | the operator's opt-in (`wildo compose add-3d-layout`): nothing a product declares decides a rendering style, so the journey never adopts the optional 3D layout |\n\n## Where it lands, and who reads it\n\nThe family lands at `specifications/src/capability-composition/index.ts` and is wired onto the\n`capabilityComposition` companion-exports slot. `bottom_up.foundation` reads it there: the NEEDED\nscenarios are applied after the domain scenarios, with the application's own host facts (slug,\ndisplay name, public domain from its infrastructure environments, its port block), and the\nfoundation record names **every scenario applied and every scenario declined with the declaration\neach came from**. A package that already exists (`website/`, `technical-doc/`) is left alone and\nreported as already composed.\n\n## Read state first\n\nA composition landed before the market, the brand or the business model exists declines what\nnothing yet implies, and says so in each decision's detail. That is the honest first record, not a\nmistake: derived staleness marks the composition stale when any input family lands or changes, and\nre-running this step refines it. Nothing is re-asked because nothing was asked.\n\n## What you emit\n\n- The **capability-composition** at `specifications/src/capability-composition/index.ts` —\n one decision per scenario, total over the scenarios the framework ships.\n\n## Verification\n\n- The record is total: `validateCapabilityComposition` reports `SCENARIO_NOT_DECIDED` for any\n scenario the framework ships that the record never decided about, and\n `DISPOSITION_BASIS_MISMATCH` for a disposition whose basis contradicts it.\n- `rg -n \"disposition: CompositionDisposition.NEEDED\" specifications/src/capability-composition/index.ts`\n lists what the foundation will apply.\n\n## References — named by REF, because nothing here opens a file\n\nThis step is RUNNER-OWNED: the composition is derived by a function, and no model reads this method\nat all. The two skills are named by ref rather than by path for the same reason the tool-less\nplaybooks are (#1435) — a path is an instruction nothing can follow:\n\n- `config-saas` — the SaaS-config surface the applied scenarios append to\n (`applicationExtraServices`, the workspace members), which is what the foundation executor writes.\n",
45
+ "guidance": "# Capability Composition — Which Scenarios This Application Needs\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe framework ships a closed set of composition scenarios, each one applied by `wildo compose <ref>`\nwith the scenario ref named in the table below. Two of them — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The\nothers give an application a marketing website, a documentation portal, a cron minion, a worker, a\nprovider, a file-picker provider, a second website locale, another deployment environment or the\noptional 3D layout, and until this step existed nothing in the journey decided whether an\napplication needed any of them: they were reachable only by a person running `wildo compose`.\n\nThis step records that decision as the `capability-composition` family: **one decision per\nscenario the framework ships**, each with a disposition, the closed basis it was derived from,\nand a one-sentence detail naming the declaring entries.\n\n## It is derived, never asked\n\nNothing here is an interview. Every decision is read off what the application's own families\nDECLARE:\n\n| scenario | NEEDED when | read from |\n|---|---|---|\n| `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |\n| `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |\n| `add-locale` | a website is composed and either the market targets a country whose languages the configuration does not serve (one locale for each such country's first listed language) or the configuration serves more than one language (one locale per language beyond the primary) — the decision names its `locales` | `market-snapshot.icps` geographies (CORE and EXPANSION), and `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |\n\nWhere no typed declaration can decide a scenario, the record says **DECLINED with the basis\n`NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for\nsomebody to add, never a question for somebody to answer. Today the only such case is `add-locale`\nwhen a website is composed but the host could not read the configuration's languages.\n\nEach basis justifies exactly ONE disposition (`COMPOSITION_BASIS_DISPOSITION`): a declaration that\nwas read and implies nothing is `NO_DECLARATION_IMPLIES_IT`, never a NEED basis with a DECLINED\nverdict. A market whose countries the configuration cannot address is never declined in silence:\nwith a website it makes `add-locale` NEEDED on `MARKET_TARGETS_UNSERVED_LANGUAGES`, naming each\nlanguage, and with or without one the coherence report names the gap as a contradiction, so the\nconfiguration's own `enabledLanguages` can follow.\n\nScenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so\nthe record stays total without claiming the application lacks them:\n\n| scenario | owner |\n|---|---|\n| `add-module`, `add-resource` | `bottom_up.foundation` — the domain composition |\n| `add-minion`, `add-worker-node`, `add-worker-rust` | `bottom_up.foundation` — one per surface the integration plan declares |\n| `add-custom-operation`, `add-website-section`, `add-marketing-page`, `add-file-picker-provider` | the build tasks that produce those artifacts (`bottom_up.build-decompose`) |\n| `add-provider` | the foundation's provider decision |\n| `add-environment` | the operator, at deployment (`wildo compose add-environment`) |\n| `add-3d-layout` | the operator's opt-in (`wildo compose add-3d-layout`): nothing a product declares decides a rendering style, so the journey never adopts the optional 3D layout |\n\n## Where it lands, and who reads it\n\nThe family lands at `specifications/src/capability-composition/index.ts` and is wired onto the\n`capabilityComposition` companion-exports slot. `bottom_up.foundation` reads it there: the NEEDED\nscenarios are applied after the domain scenarios, with the application's own host facts (slug,\ndisplay name, public domain from its infrastructure environments, its port block), and the\nfoundation record names **every scenario applied and every scenario declined with the declaration\neach came from**. A package that already exists (`website/`, `technical-doc/`) is left alone and\nreported as already composed.\n\n## Read state first\n\nA composition landed before the market, the brand or the business model exists declines what\nnothing yet implies, and says so in each decision's detail. That is the honest first record, not a\nmistake: derived staleness marks the composition stale when any input family lands or changes, and\nre-running this step refines it. Nothing is re-asked because nothing was asked.\n\n## What you emit\n\n- The **capability-composition** at `specifications/src/capability-composition/index.ts` —\n one decision per scenario, total over the scenarios the framework ships.\n\n## Verification\n\n- The record is total: `validateCapabilityComposition` reports `SCENARIO_NOT_DECIDED` for any\n scenario the framework ships that the record never decided about, and\n `DISPOSITION_BASIS_MISMATCH` for a disposition whose basis contradicts it.\n- `rg -n \"disposition: CompositionDisposition.NEEDED\" specifications/src/capability-composition/index.ts`\n lists what the foundation will apply.\n\n## References — named by REF, because nothing here opens a file\n\nThis step is RUNNER-OWNED: the composition is derived by a function, and no model reads this method\nat all. The two skills are named by ref rather than by path for the same reason the tool-less\nplaybooks are (#1435) — a path is an instruction nothing can follow:\n\n- `config-saas` — the SaaS-config surface the applied scenarios append to\n (`applicationExtraServices`, the workspace members), which is what the foundation executor writes.\n",
46
46
  "skillRefs": [
47
47
  "config-saas"
48
48
  ],
@@ -22,8 +22,9 @@ placement plan — and it ends on the placement plan, which is the lane's closin
22
22
  requirements and the market. Asks the creator one question (tenancy) and may suspend
23
23
  mid-run on a clarification.
24
24
  - **`top_down.expert-personas`** — derives and accepts the expert charters the panels
25
- convene. Runner-owned, lands no family, never re-derives a committed charter, reports
26
- a role whose inputs have not landed as waiting.
25
+ convene. Runner-owned; lands the charters (`expert-personas`), never re-derives a
26
+ committed charter, reports a role whose inputs have not landed as waiting, and is
27
+ offered again once such a role can be staffed.
27
28
  - **`bottom_up.capability-composition`** — which composition scenarios the
28
29
  application needs (a website, a technical-doc portal, workers, minions). Its record
29
30
  is what the foundation applies.
@@ -51,11 +52,15 @@ already offers the three that follow it.
51
52
  - **Missing beats present.** A plan or a placement already on record whose inputs
52
53
  have not changed since it landed is not offered at all. Every option is marked
53
54
  FIRST RUN, or REFRESH with the input that moved.
54
- - **The runner-owned steps run once.** The foundation and the personas land nothing
55
- the runtime marks delivered, so they stay eligible; the round history is the record
56
- that they ran. Do not spend a round on either a second time.
57
- - **Independent children share a round.** The personas and the foundation both need
58
- only the plan and can run beside each other.
55
+ - **The foundation runs once.** It lands nothing the runtime marks delivered, so it
56
+ stays eligible; the round history is the record that it ran. Do not spend a round on
57
+ it a second time.
58
+ - **The personas run when they are offered.** They are offered (FIRST RUN or REFRESH)
59
+ only while a role can be staffed now, and marked current otherwise. A second run is
60
+ how a role that waited on the brand or the business model gets its charter once that
61
+ family has landed.
62
+ - **Independent children share a round.** The personas and the foundation do not wait on
63
+ each other and can run beside each other.
59
64
  - **A child waiting on the creator is not offered** — an unanswered interview, or a
60
65
  suspended clarification. Run everything else, and stop when nothing eligible advances
61
66
  the conception.