@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.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +9 -0
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +7 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +13 -9
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +20 -5
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +4 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/references/build-plan.task-graph.config.md +12 -8
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +6 -2
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +13 -2
- package/dist/knowledge/references/example.inbound.email-to-todo.md +33 -2
- package/dist/knowledge/references/example.module.relationships.discriminator.md +7 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
- package/dist/knowledge/references/integration-plan.config.md +78 -8
- package/dist/knowledge/references/platform.config.environment.deployment.md +27 -4
- package/dist/knowledge/references/saas.backend.domain-module.md +15 -0
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-agent-card.md +43 -11
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +17 -11
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +11 -0
- package/dist/knowledge/references/saas.frontend.electronic-signatures.embedded-signing-frame.md +46 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +24 -33
- package/dist/knowledge/references/saas.models.flows-actors.mcp-server-declaration.md +63 -0
- package/dist/knowledge/references/saas.models.flows-actors.outbound-credential.md +61 -0
- package/dist/knowledge/references/saas.models.flows-actors.remote-agent-declaration.md +56 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +51 -0
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +7 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +11 -0
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +30 -0
- package/dist/knowledge/references/saas.rag.retrieval-scores.md +4 -2
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +45 -1
- package/dist/knowledge/registries/playbooks.json +2 -2
- package/dist/knowledge/registries/source-tags.json +1080 -1012
- package/dist/knowledge/skills/INDEX.md +2 -2
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +4 -1
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +15 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +3 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +4 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +7 -0
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +1 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +11 -0
- package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +12 -5
- package/dist/knowledge/skills/electronic-signature-deliverables/references/signing-inside-the-application.md +113 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +3 -2
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +8 -4
- package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +29 -7
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +66 -26
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +6 -2
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +13 -2
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +11 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +15 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-mcp-server-declaration-api.md +139 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-remote-a2a-agent-declaration-api.md +169 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +24 -33
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +33 -2
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +31 -9
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +27 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +26 -0
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +15 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +20 -1
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +13 -2
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +3 -0
- package/dist/knowledge/skills/resource-add-module/SKILL.md +8 -2
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +17 -0
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +51 -0
- package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +14 -5
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +30 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-client-registration-postures.md +5 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +4 -2
- package/dist/knowledge/topic-index.json +231 -84
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -20,7 +20,7 @@ export declare const playbookDefinition: {
|
|
|
20
20
|
readonly ref: "bottom_up.assemble-verify";
|
|
21
21
|
readonly version: "0.4.3";
|
|
22
22
|
readonly phase: "bottom_up";
|
|
23
|
-
readonly 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.";
|
|
23
|
+
readonly 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.";
|
|
24
24
|
readonly preconditions: readonly [{
|
|
25
25
|
readonly kind: "artifact_exists";
|
|
26
26
|
readonly selector: {
|
|
@@ -20,7 +20,7 @@ export const playbookDefinition = {
|
|
|
20
20
|
"ref": "bottom_up.assemble-verify",
|
|
21
21
|
"version": "0.4.3",
|
|
22
22
|
"phase": "bottom_up",
|
|
23
|
-
"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.",
|
|
23
|
+
"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.",
|
|
24
24
|
"preconditions": [
|
|
25
25
|
{ "kind": "artifact_exists", "selector": { "family": "build-plan" } }
|
|
26
26
|
],
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.assemble-verify/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,2BAA2B;IAClC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.assemble-verify/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,2BAA2B;IAClC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,8yGAA8yG;IACxzG,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,YAAY,EAAE,EAAE;KACtE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,YAAY,EAAE;KAC3B;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,iCAAiC;SAClC;KACF;IACD,UAAU,EAAE,mBAAmB;IAC/B,UAAU,EAAE,gBAAgB;IAC5B,uGAAuG;IACvG,QAAQ,EAAE;QACR,SAAS,EAAE,EAAE;KACd;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for topic 7 — the app-wide assemble/verify step.\n *\n * REBUILT rather than restored (issue #147). A playbook of this ref existed from\n * 2026-07-10 and was deleted on 2026-08-25 with the app-creation digest\n * demolition; the question it asked went with it, even though answering \"does\n * the built application assemble?\" needs no digests. Restoring it verbatim was\n * rejected: it declared the retired `COMPOSITE` executor, depended on two\n * families the demolition removed (`foundation-manifest`, `build-verification`),\n * and its method was explicit that NONE of its checks were actually run by the\n * runner — `// TODO CLI COMMAND:` placeholders and \"companion affordances that\n * do not exist yet\".\n *\n * What is different now is that the checks RUN. `DETERMINISTIC_CLI` is honoured\n * by the runtime as of #147, and the check refs below resolve through the same\n * closed `APPLICATION_CODING_TASK_VERIFICATION_CATALOG` a coding task uses, so\n * an unknown ref is refused rather than silently skipped.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.assemble-verify\",\n \"version\": \"0.4.3\",\n \"phase\": \"bottom_up\",\n \"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.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"build-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"build-plan\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"application-database-migrations\"\n ]\n },\n \"executor\": \"deterministic_cli\",\n \"approval\": \"approve_result\",\n // How many times the step may run (#1344). It makes no model call: it runs typechecks in a subprocess.\n \"budget\": {\n \"maxRuns\": 40\n },\n \"onFailure\": \"keep_and_flag\",\n} as const;\n"]}
|
|
@@ -51,7 +51,7 @@ export declare const playbookDefinition: {
|
|
|
51
51
|
readonly outputs: readonly [{
|
|
52
52
|
readonly family: "integration-plan";
|
|
53
53
|
readonly schemaRef: "saas-specifications:IntegrationPlan";
|
|
54
|
-
readonly description: "What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes),
|
|
54
|
+
readonly description: "What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), the providers it binds into each runtime owner's scope, and any need no engine provider or registry module fills, with why (the only door to authoring a new provider). Every collection may be empty, and saying so is an answer.";
|
|
55
55
|
}];
|
|
56
56
|
readonly method: {
|
|
57
57
|
readonly contextSources: readonly ["workspace_truth", "provider_registry"];
|
|
@@ -44,7 +44,7 @@ export const playbookDefinition = {
|
|
|
44
44
|
{
|
|
45
45
|
"family": "integration-plan",
|
|
46
46
|
"schemaRef": "saas-specifications:IntegrationPlan",
|
|
47
|
-
"description": "What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes),
|
|
47
|
+
"description": "What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), the providers it binds into each runtime owner's scope, and any need no engine provider or registry module fills, with why (the only door to authoring a new provider). Every collection may be empty, and saying so is an answer."
|
|
48
48
|
}
|
|
49
49
|
],
|
|
50
50
|
"method": {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.integration-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,+yBAA+yB;IACzzB,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,sJAAsJ,EAAE;QAC1L,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,+DAA+D,EAAE;QACrG,EAAE,QAAQ,EAAE,aAAa,EAAE,IAAI,EAAE,wFAAwF,EAAE;QAC3H,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wJAAwJ,EAAE;QACxM,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,oLAAoL,EAAE;KAC7N;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,kBAAkB;YAC5B,WAAW,EAAE,qCAAqC;YAClD,aAAa,EAAE,
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.integration-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,+yBAA+yB;IACzzB,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,sJAAsJ,EAAE;QAC1L,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,+DAA+D,EAAE;QACrG,EAAE,QAAQ,EAAE,aAAa,EAAE,IAAI,EAAE,wFAAwF,EAAE;QAC3H,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wJAAwJ,EAAE;QACxM,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,oLAAoL,EAAE;KAC7N;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,kBAAkB;YAC5B,WAAW,EAAE,qCAAqC;YAClD,aAAa,EAAE,wjBAAwjB;SACxkB;KACF;IACD,QAAQ,EAAE;QACR;;;;;;;;;;WAUG;QACH,gBAAgB,EAAE,CAAC,iBAAiB,EAAE,mBAAmB,CAAC;QAC1D;;;;;;WAMG;QACH,eAAe,EAAE,CAAC,kBAAkB,EAAE,kBAAkB,CAAC;QACzD,WAAW,EAAE;YACX,kBAAkB;YAClB,kBAAkB;YAClB,0BAA0B;YAC1B,+BAA+B;YAC/B,0BAA0B;YAC1B,wBAAwB;YACxB,mBAAmB;YACnB,kBAAkB;SACnB;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The background-execution and external-reach leaf (#1495). `add-minion`, `add-worker-node`,\n * `add-worker-rust`, `add-provider` and `add-file-picker-provider` all shipped as scenarios, and\n * the decomposer was told to plan \"workers / minions and other auxiliary execution surfaces\" and\n * \"providers, external connectors, billing wiring\" — with no product kind for any of them and,\n * measured 2026-09-22, ZERO worker and minion skills in the catalog. Nothing in the journey could\n * give an application a background worker, a cron minion or a provider binding.\n *\n * It produces the integration plan. Two consumers read it, and the split is the point:\n *\n * - `bottom_up.foundation` composes the PACKAGE — one `add-worker-node`, `add-worker-rust` or\n * `add-minion` per surface, fanned out exactly as modules and resources are fanned out of the\n * domain plan. That is why the capability composition reports those three scenarios as owned by\n * the foundation rather than as undecidable, which is what they read until this family existed.\n * - `bottom_up.build-decompose` emits the WORK — one task per worker, minion and provider binding,\n * each bound to its skill through the three total maps in `_core`, and one per inbound channel\n * producing its handler, which the dispatch routes to `inbound-channels` from the product (#1832).\n *\n * The build plan keeps ONE producer, which is what makes landing decidable (#895).\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.integration-plan\",\n \"version\": \"0.2.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.\",\n \"preconditions\": [\n /*\n * The DOMAIN PLAN is what a minion's containment is OVER: `readsResourceRefs` and\n * `writesResourceRefs` name decided resources, and a whitelist naming resources nobody decided\n * contains nothing. Its CONTENT is read, so `artifact_exists` is the honest strength (#1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"requirements\", \"//\": \"What somebody asked the application to do — including the work that cannot happen inside a request, which is the only honest reason a worker exists.\" },\n { \"family\": \"feature-drafts\", \"//\": \"The drafted features whose work a background surface carries.\" },\n { \"family\": \"domain-plan\", \"//\": \"The resources a minion's containment whitelist names, and the modules a worker serves.\" },\n { \"family\": \"roadmap\", \"render\": \"map\", \"//\": \"When each phase is owed, so a surface is planned against the phase that needs it. A MAP: the phases' own rationale is not this method's input (#1424).\" },\n { \"family\": \"integration-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its worker and minion refs, which build tasks name (#1430). Input, not precondition: a first run stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"integration-plan\",\n \"schemaRef\": \"saas-specifications:IntegrationPlan\",\n \"description\": \"What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), the providers it binds into each runtime owner's scope, and any need no engine provider or registry module fills, with why (the only door to authoring a new provider). Every collection may be empty, and saying so is an answer.\"\n }\n ],\n \"method\": {\n /*\n * WORKSPACE_TRUTH — this method plans against CODE as well as against decisions: which workers\n * and minions the application ALREADY carries (its `applicationWorkers` / `applicationMinions`\n * buckets), and which providers its scopes already name. A plan proposing a worker the tree\n * already has emits a task that composes a package twice.\n *\n * PROVIDER_REGISTRY (#2025) — the provider modules the registry OFFERS. Since the catalogue was\n * archived (#2019) a vendor reaches an application only by being installed from the registry, so\n * the workspace alone shows what is installed and nothing that could be added: an OCR or Teams need\n * was planned against nothing, or against a vendor recalled from training that no module provides.\n */\n \"contextSources\": [\"workspace_truth\", \"provider_registry\"],\n /*\n * TWO bodies reach this step (#1435), and they are the two the plan's central decisions depend\n * on: whether a surface is a worker or a minion, and what a minion's containment must name.\n * Both are impossible to decide from recollection — the difference is a runtime contract, and\n * the containment chain has three parts of which two are outside the minion's own package.\n * Every other skill is a contract the CODING AGENT opens when it builds the task.\n */\n \"skillBodyRefs\": [\"worker-authoring\", \"minion-authoring\"],\n \"skillRefs\": [\n \"worker-authoring\",\n \"minion-authoring\",\n \"provider-backend-package\",\n \"provider-frontend-file-picker\",\n \"provider-operation-calls\",\n \"resource-external-data\",\n \"configure-billing\",\n \"inbound-channels\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|