@wildo-ai/framework-knowledge 1.1.14 → 1.1.16

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 (120) 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/creation-state.md +4 -1
  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 +13 -0
  7. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  8. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  11. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +6 -4
  13. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +1 -1
  15. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +1 -1
  16. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  17. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  18. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  19. package/dist/knowledge/manifest.json +7 -7
  20. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +7 -0
  21. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +2 -2
  22. package/dist/knowledge/playbooks/bottom_up.build/method.md +10 -8
  23. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +1 -1
  24. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
  25. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +1 -1
  26. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +13 -9
  27. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
  28. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +20 -5
  29. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -2
  30. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +4 -0
  31. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  32. package/dist/knowledge/references/backend.inbound-handlers.definition.md +2 -1
  33. package/dist/knowledge/references/build-plan.task-graph.config.md +12 -8
  34. package/dist/knowledge/references/example.electronic-signature.engagement-letter-tool.md +54 -0
  35. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +6 -2
  36. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +13 -2
  37. package/dist/knowledge/references/example.inbound.email-to-todo.md +33 -2
  38. package/dist/knowledge/references/example.module.relationships.discriminator.md +14 -1
  39. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
  40. package/dist/knowledge/references/integration-plan.config.md +78 -8
  41. package/dist/knowledge/references/platform.config.environment.deployment.md +27 -4
  42. package/dist/knowledge/references/saas.backend.domain-module.md +15 -0
  43. package/dist/knowledge/references/saas.backend.flows-actors.a2a-agent-card.md +43 -11
  44. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +17 -11
  45. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +7 -0
  46. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +16 -0
  47. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +5 -2
  48. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +19 -0
  49. package/dist/knowledge/references/saas.frontend.electronic-signatures.embedded-signing-frame.md +46 -0
  50. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +21 -0
  51. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +24 -33
  52. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +9 -0
  53. package/dist/knowledge/references/saas.models.flows-actors.mcp-server-declaration.md +63 -0
  54. package/dist/knowledge/references/saas.models.flows-actors.outbound-credential.md +61 -0
  55. package/dist/knowledge/references/saas.models.flows-actors.remote-agent-declaration.md +56 -0
  56. package/dist/knowledge/references/saas.models.flows.run-state.md +9 -0
  57. package/dist/knowledge/references/saas.models.http-api-binding.md +51 -0
  58. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +7 -0
  59. package/dist/knowledge/references/saas.models.provider-capabilities.md +11 -0
  60. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +30 -0
  61. package/dist/knowledge/references/saas.rag.retrieval-scores.md +4 -2
  62. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  63. package/dist/knowledge/registries/framework-topics.json +55 -1
  64. package/dist/knowledge/registries/playbooks.json +2 -2
  65. package/dist/knowledge/registries/source-tags.json +1127 -1042
  66. package/dist/knowledge/skills/INDEX.md +2 -2
  67. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +20 -4
  68. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +4 -1
  69. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +15 -0
  70. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +3 -1
  71. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +4 -0
  72. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +7 -0
  73. package/dist/knowledge/skills/config-app-shell/SKILL.md +4 -0
  74. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +3 -0
  75. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +11 -0
  76. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +69 -19
  77. package/dist/knowledge/skills/electronic-signature-deliverables/references/signing-inside-the-application.md +113 -0
  78. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +32 -5
  79. package/dist/knowledge/skills/email-add-template/SKILL.md +3 -2
  80. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +8 -4
  81. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -1
  82. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +29 -7
  83. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +66 -26
  84. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +6 -2
  85. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +35 -3
  86. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +13 -2
  87. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +16 -0
  88. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -0
  89. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-mcp-server-declaration-api.md +139 -0
  90. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +5 -2
  91. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-remote-a2a-agent-declaration-api.md +207 -0
  92. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +9 -0
  93. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +24 -33
  94. package/dist/knowledge/skills/human-decision-notices/SKILL.md +5 -1
  95. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +9 -0
  96. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +7 -0
  97. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +2 -1
  98. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +33 -2
  99. package/dist/knowledge/skills/infra-environment-config/SKILL.md +31 -9
  100. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +27 -4
  101. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +26 -0
  102. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +15 -0
  103. package/dist/knowledge/skills/module-relationships/SKILL.md +27 -1
  104. package/dist/knowledge/skills/provider-backend-package/SKILL.md +32 -4
  105. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
  106. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +3 -0
  107. package/dist/knowledge/skills/resource-add-module/SKILL.md +8 -2
  108. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +17 -0
  109. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +1 -1
  110. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +51 -0
  111. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +14 -5
  112. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +30 -0
  113. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-client-registration-postures.md +5 -0
  114. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +4 -2
  115. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +21 -0
  116. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +5 -0
  117. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +19 -0
  118. package/dist/knowledge/topic-index.json +295 -114
  119. package/dist/tsconfig.build.tsbuildinfo +1 -1
  120. package/package.json +4 -4
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "artifactVersion": "3",
3
- "frameworkVersion": "1.1.14",
4
- "generatorVersion": "1.1.14",
5
- "generatedAt": "2026-11-16T14:58:04.129Z",
3
+ "frameworkVersion": "1.1.16",
4
+ "generatorVersion": "1.1.16",
5
+ "generatedAt": "2026-11-18T19:00:50.034Z",
6
6
  "packageName": "@wildo-ai/framework-knowledge",
7
- "topicCount": 1070,
8
- "referenceFileCount": 927,
7
+ "topicCount": 1075,
8
+ "referenceFileCount": 932,
9
9
  "payload": {
10
10
  "topicIndexPath": "topic-index.json",
11
11
  "registriesDirectory": "registries",
@@ -21,13 +21,13 @@
21
21
  "registryName": "source-tags",
22
22
  "filePath": "registries/source-tags.json",
23
23
  "description": "Source-derived tag registry for extracted framework references.",
24
- "entryCount": 927
24
+ "entryCount": 932
25
25
  },
26
26
  {
27
27
  "registryName": "framework-topics",
28
28
  "filePath": "registries/framework-topics.json",
29
29
  "description": "Topic registry derived from extracted framework-knowledge tags.",
30
- "entryCount": 1070
30
+ "entryCount": 1075
31
31
  },
32
32
  {
33
33
  "registryName": "playbooks",
@@ -20,6 +20,13 @@ is evaluated exactly as the companion evaluates it, and a specification its fact
20
20
  message. Such a specification typechecks; it is dropped from what the companion serves, so it is a gap in the
21
21
  application nothing else reports.
22
22
 
23
+ **It verifies that every module's files are where the framework reads them** (`check:module-layout`): a module's
24
+ email definitions under `emails/`, its custom operations under `resources/`, a resource's schema, configuration, UI
25
+ behaviour and specification in their `resources/` folders. A file elsewhere compiles and is then silently not read (a
26
+ generated email lands where nothing registers it, an operation is never registered). Each finding is the `mv` and
27
+ the imports that correct it; a task's own check carried any misplacement that predates it, so this is where it is asked
28
+ again.
29
+
23
30
  **It verifies that the website's drawn demos are true of the application** (`check:website-demo-facts`): every
24
31
  demo scenario the site defines that binds a resource names a resource the application has, and shows only values
25
32
  its schema and operations allow. Each website task was checked when it landed; this asks again because a later task
@@ -2,7 +2,7 @@
2
2
  "ref": "bottom_up.assemble-verify",
3
3
  "version": "0.4.3",
4
4
  "phase": "bottom_up",
5
- "intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'); and it asks the RUNNING backend's readiness and renders the frontend in a browser, each reported unrun rather than passed when the stack is not up. Since #2404 it also builds the resources registry offline, as the backend's startup does (`check:resources-registry-init`), so a resource configuration the engine refuses at start is named before the running backend is asked. Since #2784 it also holds the website's drawn demos to the application (`check:website-demo-facts`), because a later resource change can make a landed drawing untrue. Since #3211 it also evaluates the specifications package as the companion does (`check:specification-exports`), so a specification its factory refuses — valid TypeScript, dropped from what the companion serves — is named. The whole test suite and OpenAPI/docs regeneration are NOT in this set.",
5
+ "intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'); and it asks the RUNNING backend's readiness and renders the frontend in a browser, each reported unrun rather than passed when the stack is not up. Since #2404 it also builds the resources registry offline, as the backend's startup does (`check:resources-registry-init`), so a resource configuration the engine refuses at start is named before the running backend is asked. Since #2784 it also holds the website's drawn demos to the application (`check:website-demo-facts`), because a later resource change can make a landed drawing untrue. Since #3211 it also evaluates the specifications package as the companion does (`check:specification-exports`), so a specification its factory refuses — valid TypeScript, dropped from what the companion serves — is named. Since #3904 it also holds every module's conventional files to the folders the framework reads them from (`check:module-layout`), so a misplacement a task's own check carried is asked once more. The whole test suite and OpenAPI/docs regeneration are NOT in this set.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -19,7 +19,7 @@
19
19
  "outputs": [],
20
20
  "stepOutputs": [],
21
21
  "method": {
22
- "guidance": "# Assemble & verify — does the built application hold together?\n\nThis is the last bottom-up step. Everything before it AUTHORED the application; this one asks\nwhether what was authored is one working program.\n\n## What this playbook does\n\nIt runs a fixed set of deterministic checks against the application's workspace packages, outside\nany coding agent, and reports one outcome per check. It changes nothing.\n\nThe check set is host-owned, not authored here. A playbook names semantic check references; turning\none into an executable command is reviewed host work, which is why a new check cannot be introduced\nby editing this file.\n\n## What it verifies today, and what it does not\n\n**It verifies that every specification is admitted** (`check:specification-exports`): the specifications package\nis evaluated exactly as the companion evaluates it, and a specification its factory refuses (a chart without its\n`description` text slot, an `errorCode` that belongs in `customMessageReference`) is named with the validator's\nmessage. Such a specification typechecks; it is dropped from what the companion serves, so it is a gap in the\napplication nothing else reports.\n\n**It verifies that the website's drawn demos are true of the application** (`check:website-demo-facts`): every\ndemo scenario the site defines that binds a resource names a resource the application has, and shows only values\nits schema and operations allow. Each website task was checked when it landed; this asks again because a later task\nthat changes a resource (a status member removed, a field excluded from update) can make a landed drawing untrue,\nand no website task runs again to notice. An application with no website answers \"no demo to check\".\n\n**It verifies** that the application typechecks as a whole — every workspace package it has:\n`specifications`, `shared-lib`, `backend-api` and `frontend`, and the `website`, the technical\ndocumentation site and each worker and minion package where the application composed one. The set is\nderived from the application's packages, so a package added to it is checked without anyone listing\nit; one the application does not have answers \"nothing to typecheck\". That is the question no earlier step answers: the dispatch lane\ntypechecks the one package a task mutated, so a build can consist entirely of green tasks and still\nnot compile as a program. Cross-package breakage is the characteristic failure of a build assembled\nfrom independent tasks, and this is where it surfaces.\n\n**It also verifies that the database schema plan is in sync** — that every resource the application\nmodels has a migration behind it. This is a different question from compilation, and no typecheck\ncan answer it: on a PostgreSQL-backed application a table is built by a MIGRATION and by nothing\nelse, so a resource whose migration was never generated compiles perfectly in every package and\nthen refuses to boot with `postgresql_table_schema_mismatch`. There is no type in the program that\nknows whether a table exists.\n\nThe check is safe on every application because it resolves three outcomes rather than two:\n\n- **no committed schema-plan lockfile** — read against the application's DECLARED store, because the\n absence means opposite things (#1144). A MongoDB application is permanently in this state and the\n check passes saying it verified nothing: a collection exists on first write. A PostgreSQL one has\n had no migration create its tables and cannot boot, so the check FAILS and names the initial\n `wildo db generate`. A store the check cannot read is \"we could not ask\", like the case below.\n- **no compiled `backend-api/dist`** — the plan is computed by importing the compiled registry, and\n a build that only ran `tsc --noEmit` never emitted one. Reported as an INFRASTRUCTURE error, never\n as drift: \"we could not ask\" is not \"the application has drifted\".\n- **both present** — `wildo db diff --check` decides, and its own message names the drifted tables\n and the command that fixes them.\n\nA failure here means a migration is owed. Generate it with `wildo db generate --name <what-changed>`,\nwhich writes the migration **and** advances the lockfile in one invocation; the\n`application-database-migrations` skill carries the full procedure and every refusal.\n\n**It also verifies that the sites BUILD and that the configuration VALIDATES** (#2228) — questions\na typecheck cannot answer. The `website` runs its own `astro build`, which refuses a page with no\nsections and renders every route; the documentation portal runs `docusaurus build`, which refuses\nuntil the documentation is published and resolves every link. An application without one of them\nanswers \"nothing to build\". `wildo config validate` runs the checks the backend runs at startup:\nan error fails the check, because a backend with configuration errors does not boot; a warning\ndoes not. A missing `wildo` CLI is \"we could not ask\", never a failing configuration. These run\nhere and at the end of the build plan, never per task: a site build takes minutes, and every task\nalready owes its package's typecheck.\n\n**It does not** boot the application, run its test suite, or regenerate OpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist\nyet. They are absent rather than declared-and-skipped on purpose: the previous version of this\nplaybook declared all of them, ran none, and carried a long disclaimer saying so — a check that is\nannounced and not executed is worse than one that is missing, because a reader counts it.\n\n## Reading the result\n\nThree outcomes, and they mean different things:\n\n- **every check passed** — the application assembles. This is the signal the phase gate wants.\n- **a check failed** — the application does not assemble. The failure names the package. Repairing it\n is not this playbook's job: the build's next dispatch answers with a repair run for the first failing\n check, scoped and verified from that check. A check gets at most two repairs per round, and none when\n the last one was given the same failure. Once those are spent, the build's refusal names the check, and\n it needs a person or a new build task.\n- **an infrastructure error** — the check could not be RUN. This is reported separately and must not\n be read as a failure: \"the application does not typecheck\" and \"we could not run the typecheck\"\n lead you to entirely different places, and only the first is the application's fault.\n\nA dry run resolves the check set and executes nothing, so it tells you what would be verified\nwithout paying for it.\n\n## Quality gate\n\nThe gate is the check set itself, run by the host. There is no declared gate restating it — a second\ndescription of a live check is exactly what the retired `qualityGates` field was.\n\n## Acceptance\n\nThe creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing:\nacceptance is a later commit, and who makes it is the host's autonomy posture.\n",
22
+ "guidance": "# Assemble & verify — does the built application hold together?\n\nThis is the last bottom-up step. Everything before it AUTHORED the application; this one asks\nwhether what was authored is one working program.\n\n## What this playbook does\n\nIt runs a fixed set of deterministic checks against the application's workspace packages, outside\nany coding agent, and reports one outcome per check. It changes nothing.\n\nThe check set is host-owned, not authored here. A playbook names semantic check references; turning\none into an executable command is reviewed host work, which is why a new check cannot be introduced\nby editing this file.\n\n## What it verifies today, and what it does not\n\n**It verifies that every specification is admitted** (`check:specification-exports`): the specifications package\nis evaluated exactly as the companion evaluates it, and a specification its factory refuses (a chart without its\n`description` text slot, an `errorCode` that belongs in `customMessageReference`) is named with the validator's\nmessage. Such a specification typechecks; it is dropped from what the companion serves, so it is a gap in the\napplication nothing else reports.\n\n**It verifies that every module's files are where the framework reads them** (`check:module-layout`): a module's\nemail definitions under `emails/`, its custom operations under `resources/`, a resource's schema, configuration, UI\nbehaviour and specification in their `resources/` folders. A file elsewhere compiles and is then silently not read (a\ngenerated email lands where nothing registers it, an operation is never registered). Each finding is the `mv` and\nthe imports that correct it; a task's own check carried any misplacement that predates it, so this is where it is asked\nagain.\n\n**It verifies that the website's drawn demos are true of the application** (`check:website-demo-facts`): every\ndemo scenario the site defines that binds a resource names a resource the application has, and shows only values\nits schema and operations allow. Each website task was checked when it landed; this asks again because a later task\nthat changes a resource (a status member removed, a field excluded from update) can make a landed drawing untrue,\nand no website task runs again to notice. An application with no website answers \"no demo to check\".\n\n**It verifies** that the application typechecks as a whole — every workspace package it has:\n`specifications`, `shared-lib`, `backend-api` and `frontend`, and the `website`, the technical\ndocumentation site and each worker and minion package where the application composed one. The set is\nderived from the application's packages, so a package added to it is checked without anyone listing\nit; one the application does not have answers \"nothing to typecheck\". That is the question no earlier step answers: the dispatch lane\ntypechecks the one package a task mutated, so a build can consist entirely of green tasks and still\nnot compile as a program. Cross-package breakage is the characteristic failure of a build assembled\nfrom independent tasks, and this is where it surfaces.\n\n**It also verifies that the database schema plan is in sync** — that every resource the application\nmodels has a migration behind it. This is a different question from compilation, and no typecheck\ncan answer it: on a PostgreSQL-backed application a table is built by a MIGRATION and by nothing\nelse, so a resource whose migration was never generated compiles perfectly in every package and\nthen refuses to boot with `postgresql_table_schema_mismatch`. There is no type in the program that\nknows whether a table exists.\n\nThe check is safe on every application because it resolves three outcomes rather than two:\n\n- **no committed schema-plan lockfile** — read against the application's DECLARED store, because the\n absence means opposite things (#1144). A MongoDB application is permanently in this state and the\n check passes saying it verified nothing: a collection exists on first write. A PostgreSQL one has\n had no migration create its tables and cannot boot, so the check FAILS and names the initial\n `wildo db generate`. A store the check cannot read is \"we could not ask\", like the case below.\n- **no compiled `backend-api/dist`** — the plan is computed by importing the compiled registry, and\n a build that only ran `tsc --noEmit` never emitted one. Reported as an INFRASTRUCTURE error, never\n as drift: \"we could not ask\" is not \"the application has drifted\".\n- **both present** — `wildo db diff --check` decides, and its own message names the drifted tables\n and the command that fixes them.\n\nA failure here means a migration is owed. Generate it with `wildo db generate --name <what-changed>`,\nwhich writes the migration **and** advances the lockfile in one invocation; the\n`application-database-migrations` skill carries the full procedure and every refusal.\n\n**It also verifies that the sites BUILD and that the configuration VALIDATES** (#2228) — questions\na typecheck cannot answer. The `website` runs its own `astro build`, which refuses a page with no\nsections and renders every route; the documentation portal runs `docusaurus build`, which refuses\nuntil the documentation is published and resolves every link. An application without one of them\nanswers \"nothing to build\". `wildo config validate` runs the checks the backend runs at startup:\nan error fails the check, because a backend with configuration errors does not boot; a warning\ndoes not. A missing `wildo` CLI is \"we could not ask\", never a failing configuration. These run\nhere and at the end of the build plan, never per task: a site build takes minutes, and every task\nalready owes its package's typecheck.\n\n**It does not** boot the application, run its test suite, or regenerate OpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist\nyet. They are absent rather than declared-and-skipped on purpose: the previous version of this\nplaybook declared all of them, ran none, and carried a long disclaimer saying so — a check that is\nannounced and not executed is worse than one that is missing, because a reader counts it.\n\n## Reading the result\n\nThree outcomes, and they mean different things:\n\n- **every check passed** — the application assembles. This is the signal the phase gate wants.\n- **a check failed** — the application does not assemble. The failure names the package. Repairing it\n is not this playbook's job: the build's next dispatch answers with a repair run for the first failing\n check, scoped and verified from that check. A check gets at most two repairs per round, and none when\n the last one was given the same failure. Once those are spent, the build's refusal names the check, and\n it needs a person or a new build task.\n- **an infrastructure error** — the check could not be RUN. This is reported separately and must not\n be read as a failure: \"the application does not typecheck\" and \"we could not run the typecheck\"\n lead you to entirely different places, and only the first is the application's fault.\n\nA dry run resolves the check set and executes nothing, so it tells you what would be verified\nwithout paying for it.\n\n## Quality gate\n\nThe gate is the check set itself, run by the host. There is no declared gate restating it — a second\ndescription of a live check is exactly what the retired `qualityGates` field was.\n\n## Acceptance\n\nThe creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing:\nacceptance is a later commit, and who makes it is the host's autonomy posture.\n",
23
23
  "skillRefs": [
24
24
  "application-database-migrations"
25
25
  ],
@@ -36,11 +36,12 @@ never a "done".
36
36
  - **`bottom_up.assemble-verify`** — does the built application assemble? The
37
37
  deterministic verification set over the application's packages and the migration
38
38
  drift probe.
39
- - **`top_down.expert-personas`** — the staffing step, here only to repair: a build task
40
- can change an input an expert's charter reads (the design system, for the art director
41
- and the design-system guardian), and a panel then refuses to seat the stale charter.
42
- The dispatch child runs it ITSELF after its wave (`staffingRepair` in its result) and the
43
- held steps run in the next wave, so you rarely select it.
39
+ - **`top_down.expert-personas`** — the staffing step, here only to repair: an input an
40
+ expert's charter reads can move during the build (the brand, the vision), and a panel then
41
+ refuses to seat the stale charter. The build's own changes to the design system and the
42
+ accepted mark do not make a charter stale while the build is unfinished. The dispatch child
43
+ starts the staffing step ITSELF the moment a step is held, beside its wave (`staffingRepair`
44
+ in its result), and the held steps run once it lands, so you rarely select it.
44
45
  - **`bottom_up.maturity-reading`** — what the built application is WORTH against the
45
46
  requirements it was asked to satisfy: which are addressed, by what evidence, and the
46
47
  stage that puts it at. This is what the lane ends on. Assembly says the code compiles;
@@ -65,9 +66,10 @@ between rounds unblocks its dependents without re-planning.
65
66
  runs as many tasks at once as the build parallelism allows. A second child in the same
66
67
  round would start a second wave beside it and double the width the person chose.
67
68
  - **Stale charters never end the lane.** A step whose panel refused them is held, every
68
- other task keeps running, and the dispatch child runs the staffing step after its wave.
69
- Keep dispatching. Select `top_down.expert-personas` yourself only when the dispatch
70
- result's `staffingRepair` says it failed and the staffing step is on offer.
69
+ other task keeps running, and the dispatch child starts the staffing step beside its wave.
70
+ Keep dispatching. `staffingRepair` with `inFlight` is not a failure: the staffing step is
71
+ still running, so never select it then. Select `top_down.expert-personas` yourself only
72
+ when `staffingRepair` says the staffing step failed and it is on offer.
71
73
  - **A parked question waits for the creator.** A coding run that parked on a question
72
74
  is answered on the creation surface; the task is re-dispatched when it is.
73
75
 
@@ -39,7 +39,7 @@
39
39
  }
40
40
  ],
41
41
  "method": {
42
- "guidance": "# The Build Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** — one WAVE per run: up to the application's build\n parallelism of ready tasks at once (`wildo workbench parallelism`, 5 by default), each\n routed by its target — a coding run in the workspace, or a companion-owned generation\n step (labels, logo, emails, seeds). The runs share the worktree; the wave repairs what\n they overwrote in each other when they have settled, then reports every run's outcome.\n With a build parallelism of `1` it is one task per run. Lands no family, so it is\n offered again every round — that is the loop.\n- **`bottom_up.build-scale`** — the same act as dispatch: it declares the same executor\n and starts the same wave. Prefer `bottom_up.build-dispatch`; selecting scale instead\n gains nothing, and selecting both in one round would start two waves side by side.\n- **`bottom_up.assemble-verify`** — does the built application assemble? The\n deterministic verification set over the application's packages and the migration\n drift probe.\n- **`top_down.expert-personas`** — the staffing step, here only to repair: a build task\n can change an input an expert's charter reads (the design system, for the art director\n and the design-system guardian), and a panel then refuses to seat the stale charter.\n The dispatch child runs it ITSELF after its wave (`staffingRepair` in its result) and the\n held steps run in the next wave, so you rarely select it.\n- **`bottom_up.maturity-reading`** — what the built application is WORTH against the\n requirements it was asked to satisfy: which are addressed, by what evidence, and the\n stage that puts it at. This is what the lane ends on. Assembly says the code compiles;\n the reading says what the application has become.\n\nNothing above is a sequence. The plan needs the conception; dispatch needs the plan;\nassembly needs the plan. Readiness is re-derived from git each round, so a task accepted\nbetween rounds unblocks its dependents without re-planning.\n\n## Selecting the next child\n\n- **Decompose once.** Re-decompose only when the decomposer's gate says an input has\n moved since the plan landed, when dispatch reports a task that cannot land, or when the\n decomposer is offered again after its own judge found the plan does not cover the domain\n plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of\n what has landed, and aimed at the criterion that faulted.\n- **Dispatch while tasks remain.** Each round's objective names the tasks the previous\n round's wave dispatched and how each came out — the dispatch child returns those\n outcomes, so read them rather than assuming. Once every task has landed, dispatch is no longer\n offered at all and the remaining child is assemble-verify.\n- **One child per round.** The parallelism is INSIDE the dispatch child: its wave already\n runs as many tasks at once as the build parallelism allows. A second child in the same\n round would start a second wave beside it and double the width the person chose.\n- **Stale charters never end the lane.** A step whose panel refused them is held, every\n other task keeps running, and the dispatch child runs the staffing step after its wave.\n Keep dispatching. Select `top_down.expert-personas` yourself only when the dispatch\n result's `staffingRepair` says it failed and the staffing step is on offer.\n- **A parked question waits for the creator.** A coding run that parked on a question\n is answered on the creation surface; the task is re-dispatched when it is.\n\n## Composing an objective for a child\n\nFor dispatch: the tasks the previous round's wave dispatched, their outcomes, and what\nthe tasks ready now are expected to produce. For a refine decomposition: the task that could\nnot land and why. For assembly: nothing to compose — it runs the declared checks.\n\n## When to stop\n\nStop on the maturity reading. It is the decision this lane ends on, and it names a\nSTAGE rather than a completion — there is no \"done\" for an application, only a\nmeasurement against its requirements that moves every time a later run lands something. Stop when dispatch has reported a task\nthat cannot land twice, or a parked question waits on the creator, and say which. A\nfull build takes several runs of this lane; each resumes where readiness now stands.\n\n## What the creator reviews\n\nEach dispatched task's work in the application workspace, through `git status`, and\nthe assembly verdict. A task lands when its product is in the working tree and its run's\nchecks passed; the companion's build checkpoints commit it under the automatic posture, and\nunder a reviewing posture acceptance is the person's commit.\n",
42
+ "guidance": "# The Build Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** — one WAVE per run: up to the application's build\n parallelism of ready tasks at once (`wildo workbench parallelism`, 5 by default), each\n routed by its target — a coding run in the workspace, or a companion-owned generation\n step (labels, logo, emails, seeds). The runs share the worktree; the wave repairs what\n they overwrote in each other when they have settled, then reports every run's outcome.\n With a build parallelism of `1` it is one task per run. Lands no family, so it is\n offered again every round — that is the loop.\n- **`bottom_up.build-scale`** — the same act as dispatch: it declares the same executor\n and starts the same wave. Prefer `bottom_up.build-dispatch`; selecting scale instead\n gains nothing, and selecting both in one round would start two waves side by side.\n- **`bottom_up.assemble-verify`** — does the built application assemble? The\n deterministic verification set over the application's packages and the migration\n drift probe.\n- **`top_down.expert-personas`** — the staffing step, here only to repair: an input an\n expert's charter reads can move during the build (the brand, the vision), and a panel then\n refuses to seat the stale charter. The build's own changes to the design system and the\n accepted mark do not make a charter stale while the build is unfinished. The dispatch child\n starts the staffing step ITSELF the moment a step is held, beside its wave (`staffingRepair`\n in its result), and the held steps run once it lands, so you rarely select it.\n- **`bottom_up.maturity-reading`** — what the built application is WORTH against the\n requirements it was asked to satisfy: which are addressed, by what evidence, and the\n stage that puts it at. This is what the lane ends on. Assembly says the code compiles;\n the reading says what the application has become.\n\nNothing above is a sequence. The plan needs the conception; dispatch needs the plan;\nassembly needs the plan. Readiness is re-derived from git each round, so a task accepted\nbetween rounds unblocks its dependents without re-planning.\n\n## Selecting the next child\n\n- **Decompose once.** Re-decompose only when the decomposer's gate says an input has\n moved since the plan landed, when dispatch reports a task that cannot land, or when the\n decomposer is offered again after its own judge found the plan does not cover the domain\n plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of\n what has landed, and aimed at the criterion that faulted.\n- **Dispatch while tasks remain.** Each round's objective names the tasks the previous\n round's wave dispatched and how each came out — the dispatch child returns those\n outcomes, so read them rather than assuming. Once every task has landed, dispatch is no longer\n offered at all and the remaining child is assemble-verify.\n- **One child per round.** The parallelism is INSIDE the dispatch child: its wave already\n runs as many tasks at once as the build parallelism allows. A second child in the same\n round would start a second wave beside it and double the width the person chose.\n- **Stale charters never end the lane.** A step whose panel refused them is held, every\n other task keeps running, and the dispatch child starts the staffing step beside its wave.\n Keep dispatching. `staffingRepair` with `inFlight` is not a failure: the staffing step is\n still running, so never select it then. Select `top_down.expert-personas` yourself only\n when `staffingRepair` says the staffing step failed and it is on offer.\n- **A parked question waits for the creator.** A coding run that parked on a question\n is answered on the creation surface; the task is re-dispatched when it is.\n\n## Composing an objective for a child\n\nFor dispatch: the tasks the previous round's wave dispatched, their outcomes, and what\nthe tasks ready now are expected to produce. For a refine decomposition: the task that could\nnot land and why. For assembly: nothing to compose — it runs the declared checks.\n\n## When to stop\n\nStop on the maturity reading. It is the decision this lane ends on, and it names a\nSTAGE rather than a completion — there is no \"done\" for an application, only a\nmeasurement against its requirements that moves every time a later run lands something. Stop when dispatch has reported a task\nthat cannot land twice, or a parked question waits on the creator, and say which. A\nfull build takes several runs of this lane; each resumes where readiness now stands.\n\n## What the creator reviews\n\nEach dispatched task's work in the application workspace, through `git status`, and\nthe assembly verdict. A task lands when its product is in the working tree and its run's\nchecks passed; the companion's build checkpoints commit it under the automatic posture, and\nunder a reviewing posture acceptance is the person's commit.\n",
43
43
  "skillRefs": [],
44
44
  "skillBodyRefs": [],
45
45
  "derivedFromAnswers": [],
@@ -140,8 +140,8 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
140
140
  | `APPLICATION_MILESTONE` | `milestoneRef` | a milestone the module declares — the experience plan's identifier, as a slug |
141
141
  | `APPLICATION_GUIDANCE` | `guidanceKind` + `guidanceRef` | an onboarding document or guidance flow the module declares — the experience plan's `kind` and ref |
142
142
  | `PDF_TEMPLATE` | `resourceRef` + `templateRef` | a PDF template BOUND to a resource's generated-file field (`generatedSummaryPdf`) |
143
- | `APPLICATION_WORKER` | `workerRef` + the `jobRefs` its entry file declares | a worker's behaviour. The JOBS, not the package: `add-worker-node` / `add-worker-rust` write the package |
144
- | `APPLICATION_MINION` | `minionRef` + the `behaviorRefs` its entry file declares | a minion's tick behaviour. Same rule: `add-minion` writes the package |
143
+ | `APPLICATION_WORKER` | `workerRef` (the integration plan's `worker-<slug>`, verbatim) + the `jobRefs` its entry file declares | a worker's behaviour. The JOBS, not the package: `add-worker-node` / `add-worker-rust` write the package |
144
+ | `APPLICATION_MINION` | `minionRef` (the integration plan's `minion-<slug>`, verbatim) + the `behaviorRefs` its entry file declares | a minion's tick behaviour. Same rule: `add-minion` writes the package |
145
145
  | `PROVIDER_BINDING` | `providerRef` + `scope` (`BACKEND`, `COMPANION`, `FRONTEND_APP`, `WEBSITE`), + `augments` when the binding has it | one provider declared in one runtime owner's scope — the SaaS config block, or the service's `provider-contributions.ts`. With `augments`, the module's opt-in under `providers.augmentations.<augments>` instead |
146
146
  | `WEBSITE_PAGE` | `pageRef` | a marketing page, registered in `website-root.config.ts` by its manifest |
147
147
  | `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |
@@ -309,9 +309,9 @@ export enum BuildPlanTaskTargetKind {
309
309
  * task: the companion publishes into it, and the coding policy prohibits it by prefix.
310
310
  */
311
311
  TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',
312
- /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */
312
+ /** One worker package (`workers/<slug>/`, named by the integration plan's `worker-<slug>`), Node or Rust, plus its declaration in the SaaS config. */
313
313
  WORKER = 'WORKER',
314
- /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */
314
+ /** One cron minion package (`minions/<slug>/`, named by the integration plan's `minion-<slug>`) plus its declaration in the SaaS config. */
315
315
  MINION = 'MINION',
316
316
  /**
317
317
  * Declaring one provider in the application — the SaaS config's provider scopes, the backend
@@ -899,8 +899,8 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
899
899
  */
900
900
  serviceMethodDeliverableRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),
901
901
  }),
902
- z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
903
- z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
902
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: IntegrationWorkerRefSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
903
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: IntegrationMinionRefSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
904
904
  z.strictObject({
905
905
  kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),
906
906
  providerRef: SlugSchema,
@@ -1343,14 +1343,18 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
1343
1343
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),
1344
1344
  z.strictObject({
1345
1345
  kind: z.literal(BuildPlanTaskTargetKind.WORKER),
1346
- /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */
1347
- workerRef: SlugSchema,
1346
+ /**
1347
+ * The integration plan's `workerRef` (`worker-<slug>`), verbatim. The package directory is derived from it by
1348
+ * `integrationWorkerDirectoryName`, the same rule the foundation step composes the package with, so the plan never
1349
+ * has to guess where the package went.
1350
+ */
1351
+ workerRef: IntegrationWorkerRefSchema,
1348
1352
  runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),
1349
1353
  }),
1350
1354
  z.strictObject({
1351
1355
  kind: z.literal(BuildPlanTaskTargetKind.MINION),
1352
- /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */
1353
- minionRef: SlugSchema,
1356
+ /** The integration plan's `minionRef` (`minion-<slug>`), verbatim; the directory is `integrationMinionDirectoryName`'s. */
1357
+ minionRef: IntegrationMinionRefSchema,
1354
1358
  }),
1355
1359
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
1356
1360
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),
@@ -2074,6 +2078,19 @@ replaced — the judge reports it as a gap.
2074
2078
  `provider-operation-calls` and `configure-billing` as the task's further reading when the
2075
2079
  binding is one an application then CALLS. Environment and infra config are the
2076
2080
  foundation's, not a build task's.
2081
+ Such a task WIRES a provider that exists: an engine provider, or a registry module it
2082
+ installs with `wildo registry add`. The app-side module, contribution and scope entry a
2083
+ frontend binding writes are that wiring. It never writes a NEW vendor implementation (a
2084
+ provider package or module neither the engine nor the registry supplies), with ONE
2085
+ exception: a binding whose `providerRef` the integration plan records in `unprovidedNeeds`
2086
+ (#3992). That task writes the new provider; its objective carries the entry's `need` and
2087
+ `whyNoExistingProvider`, and it reaches for `provider-backend-package` (for a frontend scope, the
2088
+ skill the scope maps to, which authors the browser module). An `unprovidedNeeds` entry that
2089
+ names a worker or minion in `wiredByRef` has no binding: the WORKER or MINION task of that
2090
+ surface writes the new provider, declares it in the surface's own scope
2091
+ (`providers.scopes.workers.<key>` / `providers.scopes.minions.<key>`), carries the entry's
2092
+ `need` and `whyNoExistingProvider` in its objective, and adds `provider-backend-package` to
2093
+ its skills. Emit no task that writes a new vendor implementation for any other reason.
2077
2094
  - **What the domain plan left to the engine** — its `engineRealizedRequirements` name the
2078
2095
  requirements met by configuration rather than a module. Each still owes configuration work:
2079
2096
  `APPLICATION_ROLES` → the roles task below; `NOTIFICATIONS` → the triggering operation's task