@wildo-ai/framework-knowledge 1.1.14 → 1.1.15

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 (94) 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/esm/framework-knowledge.definitions.d.ts +1 -1
  4. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  5. package/dist/esm/framework-knowledge.definitions.js +9 -0
  6. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  7. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  8. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  10. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +1 -1
  11. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +1 -1
  12. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  13. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  14. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  15. package/dist/knowledge/manifest.json +7 -7
  16. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +7 -0
  17. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +2 -2
  18. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
  19. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +1 -1
  20. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +13 -9
  21. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
  22. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +20 -5
  23. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -2
  24. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +4 -0
  25. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  26. package/dist/knowledge/references/build-plan.task-graph.config.md +12 -8
  27. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +6 -2
  28. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +13 -2
  29. package/dist/knowledge/references/example.inbound.email-to-todo.md +33 -2
  30. package/dist/knowledge/references/example.module.relationships.discriminator.md +7 -1
  31. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
  32. package/dist/knowledge/references/integration-plan.config.md +78 -8
  33. package/dist/knowledge/references/platform.config.environment.deployment.md +27 -4
  34. package/dist/knowledge/references/saas.backend.domain-module.md +15 -0
  35. package/dist/knowledge/references/saas.backend.flows-actors.a2a-agent-card.md +43 -11
  36. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +17 -11
  37. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +11 -0
  38. package/dist/knowledge/references/saas.frontend.electronic-signatures.embedded-signing-frame.md +46 -0
  39. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +24 -33
  40. package/dist/knowledge/references/saas.models.flows-actors.mcp-server-declaration.md +63 -0
  41. package/dist/knowledge/references/saas.models.flows-actors.outbound-credential.md +61 -0
  42. package/dist/knowledge/references/saas.models.flows-actors.remote-agent-declaration.md +56 -0
  43. package/dist/knowledge/references/saas.models.http-api-binding.md +51 -0
  44. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +7 -0
  45. package/dist/knowledge/references/saas.models.provider-capabilities.md +11 -0
  46. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +30 -0
  47. package/dist/knowledge/references/saas.rag.retrieval-scores.md +4 -2
  48. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  49. package/dist/knowledge/registries/framework-topics.json +45 -1
  50. package/dist/knowledge/registries/playbooks.json +2 -2
  51. package/dist/knowledge/registries/source-tags.json +1080 -1012
  52. package/dist/knowledge/skills/INDEX.md +2 -2
  53. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +4 -1
  54. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +15 -0
  55. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +3 -1
  56. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +4 -0
  57. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +7 -0
  58. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +1 -0
  59. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +11 -0
  60. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +12 -5
  61. package/dist/knowledge/skills/electronic-signature-deliverables/references/signing-inside-the-application.md +113 -0
  62. package/dist/knowledge/skills/email-add-template/SKILL.md +3 -2
  63. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +8 -4
  64. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -1
  65. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +29 -7
  66. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +66 -26
  67. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +6 -2
  68. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -3
  69. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +13 -2
  70. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +11 -0
  71. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +15 -0
  72. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-mcp-server-declaration-api.md +139 -0
  73. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-remote-a2a-agent-declaration-api.md +169 -0
  74. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +24 -33
  75. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +33 -2
  76. package/dist/knowledge/skills/infra-environment-config/SKILL.md +31 -9
  77. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +27 -4
  78. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +26 -0
  79. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +15 -0
  80. package/dist/knowledge/skills/module-relationships/SKILL.md +20 -1
  81. package/dist/knowledge/skills/provider-backend-package/SKILL.md +13 -2
  82. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
  83. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +3 -0
  84. package/dist/knowledge/skills/resource-add-module/SKILL.md +8 -2
  85. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +17 -0
  86. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +1 -1
  87. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +51 -0
  88. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +14 -5
  89. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +30 -0
  90. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-client-registration-postures.md +5 -0
  91. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +4 -2
  92. package/dist/knowledge/topic-index.json +231 -84
  93. package/dist/tsconfig.build.tsbuildinfo +1 -1
  94. package/package.json +4 -4
@@ -151,9 +151,9 @@ export enum BuildPlanTaskTargetKind {
151
151
  * task: the companion publishes into it, and the coding policy prohibits it by prefix.
152
152
  */
153
153
  TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',
154
- /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */
154
+ /** One worker package (`workers/<slug>/`, named by the integration plan's `worker-<slug>`), Node or Rust, plus its declaration in the SaaS config. */
155
155
  WORKER = 'WORKER',
156
- /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */
156
+ /** One cron minion package (`minions/<slug>/`, named by the integration plan's `minion-<slug>`) plus its declaration in the SaaS config. */
157
157
  MINION = 'MINION',
158
158
  /**
159
159
  * Declaring one provider in the application — the SaaS config's provider scopes, the backend
@@ -741,8 +741,8 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
741
741
  */
742
742
  serviceMethodDeliverableRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),
743
743
  }),
744
- z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
745
- z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
744
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: IntegrationWorkerRefSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
745
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: IntegrationMinionRefSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
746
746
  z.strictObject({
747
747
  kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),
748
748
  providerRef: SlugSchema,
@@ -1185,14 +1185,18 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
1185
1185
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),
1186
1186
  z.strictObject({
1187
1187
  kind: z.literal(BuildPlanTaskTargetKind.WORKER),
1188
- /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */
1189
- workerRef: SlugSchema,
1188
+ /**
1189
+ * The integration plan's `workerRef` (`worker-<slug>`), verbatim. The package directory is derived from it by
1190
+ * `integrationWorkerDirectoryName`, the same rule the foundation step composes the package with, so the plan never
1191
+ * has to guess where the package went.
1192
+ */
1193
+ workerRef: IntegrationWorkerRefSchema,
1190
1194
  runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),
1191
1195
  }),
1192
1196
  z.strictObject({
1193
1197
  kind: z.literal(BuildPlanTaskTargetKind.MINION),
1194
- /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */
1195
- minionRef: SlugSchema,
1198
+ /** The integration plan's `minionRef` (`minion-<slug>`), verbatim; the directory is `integrationMinionDirectoryName`'s. */
1199
+ minionRef: IntegrationMinionRefSchema,
1196
1200
  }),
1197
1201
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
1198
1202
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),
@@ -1715,4 +1719,4 @@ build plan is fully dispatched.
1715
1719
 
1716
1720
  Formerly 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):
1717
1721
 
1718
- Judge 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.)
1722
+ Judge 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. A provider package the run CREATED that no installed module and no `unprovidedNeeds` entry of the integration plan accounts for is RECORDED beside it as `unrecordedProviderDirectories` (#3995): a CONCERN (a provider authored with no recorded reason), never a GAP by itself. (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.)