@wildo-ai/framework-knowledge 1.1.5 → 1.1.7
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 +14 -0
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
- package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
- package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
- package/dist/{knowledge/skills/journey-run/references/framework-playbook-approval-policy.md → claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md} +10 -8
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
- package/dist/{knowledge/skills/journey-run → claude-marketplace/plugins/wildo}/references/expert-personas-and-deliberations.md +8 -8
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
- package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
- 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 +321 -11
- 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.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +0 -3
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +12 -2
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +33 -2
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +8 -5
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +55 -10
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -6
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -4
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +10 -3
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +7 -3
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +8 -3
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +7 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +9 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +4 -3
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +1 -3
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +10 -3
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +8 -3
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +12 -5
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +33 -5
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +36 -17
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +67 -17
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -3
- package/dist/esm/playbooks/top_down.vision-elicitation/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 +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +4 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +31 -7
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +134 -26
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +7 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +84 -29
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -7
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +12 -23
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -7
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +12 -14
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +20 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +15 -7
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +8 -6
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +11 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +2 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +18 -2
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +2 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -5
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +16 -2
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +8 -7
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +11 -4
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +27 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +1 -4
- package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +112 -21
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +7 -2
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -4
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +6 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +0 -4
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +5 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +0 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.definition/method.md +7 -4
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +52 -7
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +17 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +2 -5
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +15 -7
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +12 -5
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
- package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +71 -6
- package/dist/knowledge/references/capability-composition.config.md +20 -1
- package/dist/knowledge/references/cli.market.generate-command.md +18 -2
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +7 -22
- package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
- package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
- package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +11 -0
- package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
- package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
- package/dist/knowledge/references/example.config.backend.required-floors.md +7 -0
- package/dist/knowledge/references/example.config.navigation.full.md +45 -2
- package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
- package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
- package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +26 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +1 -1
- package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
- package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
- package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +14 -30
- package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
- package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +8 -13
- package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
- package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
- package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +3 -0
- package/dist/knowledge/references/example.provider.frontend-app.module.md +9 -0
- package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +14 -13
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +18 -0
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +11 -11
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +5 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +2 -0
- package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +24 -6
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +36 -25
- package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
- package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
- package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
- package/dist/knowledge/references/example.website.page.manifest.md +30 -0
- package/dist/knowledge/references/experience-plan.config.md +11 -4
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +20 -0
- package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
- package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +21 -0
- package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
- package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
- package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
- package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/integration-plan.config.md +34 -2
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.buying-journey.config.md +1 -1
- package/dist/knowledge/references/market.category.config.md +1 -1
- package/dist/knowledge/references/market.channel.config.md +1 -1
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +1 -1
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +1 -1
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +1 -1
- package/dist/knowledge/references/market.positioning.config.md +1 -1
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/placement-plan.config.md +7 -1
- package/dist/knowledge/references/platform.config.backing-services.md +15 -15
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +57 -57
- package/dist/knowledge/references/presets.3d.focal-plane-settings.md +45 -0
- package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
- package/dist/knowledge/references/presets.3d.layout-contract.md +235 -0
- package/dist/knowledge/references/presets.3d.register-layout.md +100 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +5 -0
- package/dist/knowledge/references/presets.models.shell-region.md +47 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
- package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +7 -6
- package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +7 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +93 -15
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +200 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +2 -0
- package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +33 -9
- package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +98 -0
- package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
- package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
- package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
- package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +2 -2
- package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +253 -0
- package/dist/knowledge/references/saas.frontend.billing-context.md +25 -2
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
- package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
- package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +7 -5
- package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +17 -2
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +9 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +100 -5
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +61 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +0 -1
- package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
- package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
- package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
- package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +15 -9
- package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +8 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +54 -1
- package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +74 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +31 -14
- package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +4 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +12 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +5 -1
- package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
- package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +667 -6
- package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
- package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +812 -29
- package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
- package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
- package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
- package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
- package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +11 -7
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +32 -23
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +8 -4
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +22 -20
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +14 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +20 -12
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +61 -34
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +9 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
- package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +34 -0
- package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
- package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +61 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +98 -13
- package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -28
- package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +6 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +8 -0
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
- package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +242 -7
- package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
- package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +75 -7
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +106 -13
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +6 -4
- package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +14 -2
- package/dist/knowledge/references/saas.specifications.processor-register.md +77 -0
- package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
- package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +112 -45
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +13 -1
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
- package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +32 -9
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +1 -1
- package/dist/knowledge/references/saas.website.astro.label-loader.md +7 -4
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +15 -15
- package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
- package/dist/knowledge/references/saas.website.blog.bridge.md +17 -4
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
- package/dist/knowledge/references/saas.website.consent.banner.md +10 -10
- package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
- package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
- package/dist/knowledge/references/saas.website.page-layout.component.md +5 -2
- package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
- package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
- package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
- package/dist/knowledge/references/saas.website.runtime.context.md +23 -4
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
- package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
- package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
- package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
- package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
- package/dist/knowledge/references/website-plan.config.md +39 -6
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +2 -1
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +21 -0
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +1 -2
- package/dist/knowledge/references/zod.decorators.file-schema.md +11 -10
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +7 -4
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +8 -2
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +5 -1
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +5 -1
- package/dist/knowledge/references/zod.factories.address.md +7 -7
- package/dist/knowledge/references/zod.factories.code.md +2 -2
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +3 -3
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +1248 -54
- package/dist/knowledge/registries/playbooks.json +81 -109
- package/dist/knowledge/registries/source-tags.json +3201 -1118
- package/dist/knowledge/rules/live-context-door.md +29 -0
- package/dist/knowledge/skills/INDEX.md +27 -24
- package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +31 -0
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +1 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +9 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +94 -16
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +21 -8
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +7 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +13 -5
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +30 -6
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +160 -32
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +20 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +14 -2
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +88 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +112 -14
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +21 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +2 -2
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +279 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +114 -16
- package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +11 -7
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +29 -5
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +40 -27
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +22 -20
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +112 -5
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +10 -10
- package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
- package/dist/knowledge/skills/config-saas/SKILL.md +3 -1
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +7 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +21 -11
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +5 -1
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +59 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +46 -0
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +251 -12
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +8 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +81 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +37 -15
- package/dist/knowledge/skills/configure-billing/SKILL.md +64 -24
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +35 -2
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +14 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +3 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +25 -2
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +73 -1
- package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +27 -12
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +11 -2
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +26 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +61 -24
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +5 -2
- package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
- package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +1 -0
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +6 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +27 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +31 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +26 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +202 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +93 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +96 -11
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +2 -1
- package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -2
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +14 -9
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +1 -0
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +5 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +5 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +8 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +5 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +150 -44
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +83 -74
- package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +180 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +53 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +245 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +108 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +259 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +43 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +32 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +36 -4
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +2 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +3 -2
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
- package/dist/knowledge/skills/market-category/SKILL.md +2 -1
- package/dist/knowledge/skills/market-channels/SKILL.md +2 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +7 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +6 -4
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +28 -13
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +18 -3
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -1
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +4 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -1
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +3 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +2 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +3 -2
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +1 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +5 -1
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +17 -16
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +6 -4
- package/dist/knowledge/skills/module-registration/SKILL.md +2 -1
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +93 -15
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +86 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +3 -2
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
- package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -33
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +132 -23
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +29 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
- package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +75 -24
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +3 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +61 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +17 -2
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +15 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +25 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +105 -6
- package/dist/knowledge/skills/resource-add-module/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +2 -1
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +3 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +124 -30
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +8 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +9 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +17 -1
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +124 -30
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +7 -6
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +142 -34
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +98 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +86 -52
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +100 -5
- package/dist/knowledge/skills/resource-external-data/SKILL.md +1026 -28
- package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
- package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +686 -11
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +904 -31
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +166 -6
- package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
- package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
- package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
- package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
- package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +12 -0
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +28 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +5 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +34 -30
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +5 -1
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +101 -42
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +21 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +1 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +125 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +8 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +61 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +110 -9
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +1 -0
- package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +61 -0
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +14 -16
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +6 -4
- package/dist/knowledge/skills/spec-component-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
- package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +13 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +158 -46
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +5 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +2 -1
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +43 -1
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +5 -1
- package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +29 -6
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +17 -4
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +23 -28
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +7 -22
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +167 -20
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +63 -6
- package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
- package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -2
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -2
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +117 -33
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +65 -36
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-cta/SKILL.md +32 -22
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-faq/SKILL.md +99 -63
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +27 -18
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +33 -22
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +31 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-hero/SKILL.md +65 -44
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +217 -200
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +45 -34
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +30 -25
- package/dist/knowledge/skills/worker-authoring/SKILL.md +1 -0
- package/dist/knowledge/topic-index.json +5957 -1729
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/skills/journey-approve/SKILL.md +0 -63
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -77
- package/dist/knowledge/skills/journey-next/SKILL.md +0 -82
- package/dist/knowledge/skills/journey-report/SKILL.md +0 -56
- package/dist/knowledge/skills/journey-run/SKILL.md +0 -140
- package/dist/knowledge/skills/journey-status/SKILL.md +0 -60
- /package/dist/{knowledge/skills/journey-approve → claude-marketplace/plugins/wildo}/references/specification-family-map.md +0 -0
|
@@ -5,7 +5,8 @@ Read this when:
|
|
|
5
5
|
- you are authoring a pipeline's field mapping and do not want to wait for `scheduleCron`;
|
|
6
6
|
- a pipeline appears not to have run, and you need to know whether it is DECLARED but has never run
|
|
7
7
|
(no state at all) versus mid-pass (a non-null cursor);
|
|
8
|
-
- a sync reported success but a row did not change, and you need the load's own verdict
|
|
8
|
+
- a sync reported success but a row did not change, and you need the load's own verdict;
|
|
9
|
+
- a pipeline keeps failing, or refuses some source rows, and you need its run history and the refused rows.
|
|
9
10
|
|
|
10
11
|
The listing is declaration-first: a pipeline that has never run still appears, with a null state.
|
|
11
12
|
That is deliberate — a pipeline missing from a state-first listing is exactly the one you are
|
|
@@ -18,13 +19,118 @@ Three fields answer different questions:
|
|
|
18
19
|
nor reconciliation: a new or retried first batch also starts there.
|
|
19
20
|
- **`loadStatus`** is the seed engine's write verdict. For a partial or failed load, inspect the
|
|
20
21
|
ledger named by `seedRunId` for entry details.
|
|
21
|
-
- **`reconciliationStatus`** distinguishes `pending`, `completed`, `load-failed
|
|
22
|
-
`skipped-unidentified-rows`.
|
|
23
|
-
inference was made, even under REPORT
|
|
22
|
+
- **`reconciliationStatus`** distinguishes `pending`, `completed`, `load-failed`,
|
|
23
|
+
`skipped-unidentified-rows` and `deferred-to-full-pass`. `skipped-unidentified-rows` means a source
|
|
24
|
+
row could not be identified, so no orphan inference was made, even under REPORT; identifiable
|
|
25
|
+
rejected rows still count as present. `deferred-to-full-pass` is every successful INCREMENTAL run:
|
|
26
|
+
it never looks for deletions, which only a full pass can find.
|
|
27
|
+
|
|
28
|
+
A pipeline declaring `incremental` has a second track (see `incremental-extraction.md`). Its listing
|
|
29
|
+
entry carries `incremental` (the declaration) and `incrementalTrack` (`watermark`, and `cursor` when an
|
|
30
|
+
incremental pass is part-way through), independent of the full pass's `cursor`. Every summary and run
|
|
31
|
+
report carries `passMode` — `full` or `incremental` — and `incrementalTrackReset` when that run started
|
|
32
|
+
the incremental track over. `POST …/run` accepts `"passMode": "full"` to run a deletion-detecting pass
|
|
33
|
+
now; without it the run is the kind `scheduleCron` runs. An OUTBOUND pipeline runs `send` passes only — `full` or
|
|
34
|
+
`incremental` is refused for it — and its report carries an `outbound` summary of what was sent, kept, dropped and
|
|
35
|
+
left for an operator (`outbound-pipelines.md`).
|
|
36
|
+
|
|
37
|
+
Three summary fields name rows the source HOLDS that the run deliberately did not load. All are
|
|
38
|
+
still counted as present, so none can reach the orphan policy:
|
|
39
|
+
|
|
40
|
+
- **`unassignedPartitions`** lists, per remote partition key, the rows of a partitioned source whose
|
|
41
|
+
partition no operator has assigned to an organization unit. Assign the partition to load them.
|
|
42
|
+
- **`excludedArchivedRows`** counts archived Odoo records left out because the pipeline declares
|
|
43
|
+
`archivedRecords: exclude-from-load`.
|
|
44
|
+
- **`suppressedRows`** counts records a subject erasure removed locally and the pipeline therefore
|
|
45
|
+
declines to copy back (see `erasure-suppression.md`). Beside it, **`liveSuppressedRows`** counts
|
|
46
|
+
suppressed records that nonetheless have a LIVE destination row — an erasure that committed while
|
|
47
|
+
an earlier pass was loading. Above zero means an erasure did not hold: erase those rows again.
|
|
48
|
+
|
|
49
|
+
The run report also carries **`releasedSuppressions`**: suppressions a completed full pass over the
|
|
50
|
+
whole entity released because their records are gone at the source.
|
|
51
|
+
|
|
52
|
+
A summary written before a field existed omits it; absent means "not recorded", not "none".
|
|
53
|
+
|
|
54
|
+
Every run report and summary also carries **`pacing`** — `pacedMs`, `budgetWaits`,
|
|
55
|
+
`vendorThrottleWaits` and `stoppedAtDeadline` — what waiting on the source's rate budget cost the run
|
|
56
|
+
(see `rate-budgets-and-pacing.md`). A run that stopped at its `maxRunDurationMs` is a `partial-pass`
|
|
57
|
+
whose cursor continues on the next run, never a failure.
|
|
58
|
+
|
|
59
|
+
While a pipeline's system of record cannot be REACHED — a timeout, a network failure, a `429`/`502`/`503`/`504`
|
|
60
|
+
the transport retried to exhaustion, an unreachable token endpoint — its listing entry carries
|
|
61
|
+
**`sourceUnreachable`**: `since` (the first failed attempt), `failedAttempts`, `skippedScheduledRuns`,
|
|
62
|
+
`lastCause` (and `lastStatus`) and `nextScheduledAttemptAt`. Scheduled runs back off: after the n-th
|
|
63
|
+
failed attempt the next one is the 2ⁿ-th `scheduleCron` occurrence (never more than a day apart, never
|
|
64
|
+
sooner than a `Retry-After` the source named), and the ticks in between are skipped without a log line.
|
|
65
|
+
The first failure logs one WARN, each later attempt one summary line, ERROR from the third. A refusal
|
|
66
|
+
(`401`, a JSON-RPC error) or a malformed answer is not unreachability: it never starts a streak, and
|
|
67
|
+
because it proves the source answered, it ends one. `POST …/run` ignores the backoff and runs at once;
|
|
68
|
+
the first run the source answers clears the streak and logs the recovery. It stays null while the
|
|
69
|
+
source answers.
|
|
24
70
|
|
|
25
71
|
An accepted multi-run pass retains earlier source keys across process restarts. Missing or corrupt
|
|
26
72
|
accepted journal records cause a refusal before loading; they are not interpreted as absence.
|
|
27
73
|
|
|
74
|
+
A summary carries **`fullPassRestart: extraction-basis-changed`** when that full run abandoned a pass
|
|
75
|
+
because the declaration changed under it (see `incremental-extraction.md`).
|
|
76
|
+
|
|
77
|
+
**`POST …/reset`** is the way past those refusals — a checkpoint with no version, a malformed
|
|
78
|
+
checkpoint, a membership journal that is cyclic, does not match its pass, or was recorded in the format
|
|
79
|
+
used before its keys were stored one row each — which otherwise repeat on
|
|
80
|
+
every scheduled tick. Body: `{ "resourceType": "…", "mode": "restart-pass" | "full-resync", "reason":
|
|
81
|
+
"…", "operator": "…" }`. `restart-pass` discards the full pass in flight (cursor, checkpoint, membership
|
|
82
|
+
journal) and the next full run starts over; `full-resync` also discards the incremental watermark, so
|
|
83
|
+
the next incremental pass re-reads the whole source. `reason` is required. The answer names what was
|
|
84
|
+
discarded, and so does the audit trail (`external_data_pipeline_reset`: pipeline, mode, reason, the
|
|
85
|
+
operator as stated, the discarded pass id, cursor and watermark). Destination rows, erasure
|
|
86
|
+
suppressions and pending references are never touched. The door answers `409` while the pipeline is
|
|
87
|
+
running; retry when the run has finished. You do NOT need it after a declaration change — the run
|
|
88
|
+
restarts the pass itself.
|
|
89
|
+
|
|
90
|
+
## The run history — what happened across runs, and which rows were refused
|
|
91
|
+
|
|
92
|
+
The listing shows each pipeline's CURRENT state; the history shows what its runs did. Every run leaves one row —
|
|
93
|
+
a run that produced a report, and a run that threw, including one refused before it started (no owner
|
|
94
|
+
organization) and one that could not reach its source. A trigger answered `already-running` was not a run and
|
|
95
|
+
leaves none. Rows are kept for the application's `OPERATIONAL_LOGS` retention period.
|
|
96
|
+
|
|
97
|
+
Each listing entry carries **`health`**, read from that history:
|
|
98
|
+
|
|
99
|
+
- `lastRunAt` and `lastOutcome` — `completed-pass`, `partial-pass` or `failed`;
|
|
100
|
+
- `consecutiveFailures` — how many of the latest runs failed in a row, counted over the 50 most recent (a partial
|
|
101
|
+
pass ends the streak: it is progress);
|
|
102
|
+
- `lastCompletedPassAt` — when the last run that completed its pass started, either track: how fresh the copy
|
|
103
|
+
is at best;
|
|
104
|
+
- `lastCompletedFullPassAt` — the same for a FULL pass: how fresh deletion detection is.
|
|
105
|
+
|
|
106
|
+
The instants are null when the pipeline has never done that, and `health` itself is null when the history could
|
|
107
|
+
not be read (the rest of the entry still answers). A pipeline that has failed for a hundred runs still names its
|
|
108
|
+
last completed pass.
|
|
109
|
+
|
|
110
|
+
Locally, `wildo context pipelines` prints the listing with each pipeline's last completed pass and how long
|
|
111
|
+
ago it was, and `wildo context pipelines --runs <resourceType> [--limit N]` prints the history below — the CLI
|
|
112
|
+
reads the door with the application's stored admin secret, so you need not call it by hand.
|
|
113
|
+
|
|
114
|
+
**`GET …/runs?resourceType=…&limit=…`** answers one pipeline's runs, most recently STARTED first (20 by default, at
|
|
115
|
+
most 100).
|
|
116
|
+
Each run names its trigger, `passMode`, `passId`, `outcome`, counts (`extractedRows`, `rejectedRows`,
|
|
117
|
+
`submittedEntries`, `suppressedRows`, `pendingReferences`), `durationMs`, `seedRunId`, `fullPassRestart` and
|
|
118
|
+
`incrementalTrackReset`. A failed run also names its **`failureKind`**:
|
|
119
|
+
|
|
120
|
+
| `failureKind` | What to do |
|
|
121
|
+
|---|---|
|
|
122
|
+
| `source-unreachable` (with `unreachableCause`) | Wait, or fix the instance address; the scheduled runs back off (see above). |
|
|
123
|
+
| `owner-organization-absent` | Seed or promote the application's owner organization; nothing loads until it exists. |
|
|
124
|
+
| `ownership-lost` | Nothing: the run lost its lease and a later run continues from the accepted checkpoint. |
|
|
125
|
+
| `other` | Read `failureMessage` — the failure's log line, URL query strings removed. A refused stored state is cleared with `POST …/reset`. |
|
|
126
|
+
|
|
127
|
+
**`rejections`** lists the source rows the transform refused — up to 100 per run, `rejectionsTruncated` true
|
|
128
|
+
when there were more (`rejectedRows` stays exact). Each carries the row's `remoteKey` (null when the row could
|
|
129
|
+
not even be identified), its `rowIndex` among the rows the run extracted, and a `reason` that names the remote field
|
|
130
|
+
and the problem. A reason never quotes a value the row carried — not a mapped field, not a reference to another
|
|
131
|
+
record; only the row's own malformed KEY may be quoted, since it is the row's identity. This is the list to fix the
|
|
132
|
+
data at the source from.
|
|
133
|
+
|
|
28
134
|
The endpoints are mounted only when the admin secret is configured, and answer `503` otherwise.
|
|
29
135
|
|
|
30
136
|
## Import Origins
|
|
@@ -57,10 +163,21 @@ export const ExternalDataAdminEndpointMountBasePath = '/internal/admin/external-
|
|
|
57
163
|
|
|
58
164
|
/** Sub-paths, relative to {@link ExternalDataAdminEndpointMountBasePath}. */
|
|
59
165
|
export const ExternalDataAdminEndpointPath = {
|
|
60
|
-
/**
|
|
166
|
+
/**
|
|
167
|
+
* GET — every declared pipeline with its persisted cursor, its incremental track when it declares
|
|
168
|
+
* `incremental` (#1682), its last-run summary, and — while its system of record cannot be reached — the
|
|
169
|
+
* unreachable streak (`sourceUnreachable`, #1475): since when, how many failed attempts, how many scheduled
|
|
170
|
+
* runs were skipped, and when the next scheduled attempt is. Each entry carries `health` (#1740), read from the run
|
|
171
|
+
* history: the last run and its outcome, the failures in a row, and when it last completed a pass.
|
|
172
|
+
*/
|
|
61
173
|
PIPELINES: '/pipelines',
|
|
62
174
|
/**
|
|
63
|
-
* POST — run ONE pipeline now. `{ "resourceType": "externalCustomers" }
|
|
175
|
+
* POST — run ONE pipeline now. `{ "resourceType": "externalCustomers" }`, optionally with
|
|
176
|
+
* `"passMode": "full" | "incremental"` (#1682). Absent runs the pass the pipeline's `scheduleCron`
|
|
177
|
+
* runs; `"full"` forces a deletion-detecting full pass on a pipeline that reads incrementally.
|
|
178
|
+
*
|
|
179
|
+
* It runs AT ONCE even while scheduled runs are backing off from an unreachable source (#1475): a person
|
|
180
|
+
* asking now is the best evidence there is. A run that reaches the source clears the streak.
|
|
64
181
|
*
|
|
65
182
|
* This exists because a scheduled-only capability is undevelopable: authoring a mapping against
|
|
66
183
|
* SAP or Dynamics means change → sync → look, dozens of times, and an hourly cron makes that loop
|
|
@@ -68,6 +185,49 @@ export const ExternalDataAdminEndpointPath = {
|
|
|
68
185
|
* config, which is what proved the door was missing.
|
|
69
186
|
*/
|
|
70
187
|
RUN: '/run',
|
|
188
|
+
/**
|
|
189
|
+
* GET — one pipeline's run history, newest first (#1740): `?resourceType=externalCustomers&limit=20`. Each row names
|
|
190
|
+
* the trigger, track, pass, outcome, counts and duration; a failed run its failure kind (source unreachable, no owner
|
|
191
|
+
* organization, lost lease, other) and message; and every run up to 100 of its REJECTED rows with their remote key and
|
|
192
|
+
* reason — what an operator needs to fix the data at the source. Kept for the application's OPERATIONAL_LOGS period.
|
|
193
|
+
*/
|
|
194
|
+
RUNS: '/runs',
|
|
195
|
+
/**
|
|
196
|
+
* POST — reset ONE pipeline (#1734): `{ "resourceType": "externalCustomers", "mode": "restart-pass" | "full-resync",
|
|
197
|
+
* "reason": "…", "operator"?: "…" }`. `restart-pass` discards the full pass in flight (cursor, checkpoint, membership
|
|
198
|
+
* journal) so the next full run starts over; `full-resync` also discards the incremental watermark, so the next
|
|
199
|
+
* incremental pass re-reads the whole source. Destination rows are never touched. The reason is required and
|
|
200
|
+
* recorded on the audit trail with what was discarded.
|
|
201
|
+
*
|
|
202
|
+
* This is the way past the run's deliberate refusals on state it cannot trust — a checkpoint with no version, a
|
|
203
|
+
* malformed checkpoint, a membership journal that is cyclic or does not match its pass. Answers 409 while the
|
|
204
|
+
* pipeline is running.
|
|
205
|
+
*/
|
|
206
|
+
RESET: '/reset',
|
|
207
|
+
/**
|
|
208
|
+
* GET — one OUTBOUND pipeline's changes of UNKNOWN outcome (#2039): `?resourceType=leads&limit=50`. A write the pass
|
|
209
|
+
* sent and got no clear answer for — a timeout after sending — is never sent again on its own, because a create sent
|
|
210
|
+
* twice is a duplicate record. Each entry names the local row, the write that was sent (`dispatchedVerb`), the last
|
|
211
|
+
* outcome code, who made the change and when. What to look up in the system of record before answering.
|
|
212
|
+
*/
|
|
213
|
+
OUTBOUND_CHANGES: '/outbound-changes',
|
|
214
|
+
/**
|
|
215
|
+
* POST — answer ONE of them (#2039): `{ "resourceType": "leads", "localResourceId": "…", "answer": "applied" |
|
|
216
|
+
* "not-applied", "remoteKey"?: "…", "reason": "…", "operator"?: "…" }`.
|
|
217
|
+
*
|
|
218
|
+
* - `applied` for a create REQUIRES `remoteKey` — the key of the record you found. It is checked against the binding's
|
|
219
|
+
* key fields and written onto the row, so the row's later edits update that record instead of creating another. It
|
|
220
|
+
* is refused (409) when the row already holds a different key, another row already holds that key, the row is gone,
|
|
221
|
+
* or it is not the owner organization's.
|
|
222
|
+
* - `applied` for an update, or `not-applied` for either, takes no key; `not-applied` makes the pass send it again. A
|
|
223
|
+
* create answered `not-applied` is refused (409) when its row already holds a key: that says the create landed.
|
|
224
|
+
*
|
|
225
|
+
* A refusal carries a stable `code` (`ExternalDataOutboundResolutionRefusal`, `@wildo-ai/saas-models`) to branch on.
|
|
226
|
+
*
|
|
227
|
+
* The reason is required and recorded on the audit trail with what the answer changed. 409 when the change is not of
|
|
228
|
+
* unknown outcome any more (answered, or settled by a pass) — list again.
|
|
229
|
+
*/
|
|
230
|
+
OUTBOUND_CHANGES_RESOLVE: '/outbound-changes/resolve',
|
|
71
231
|
} as const;
|
|
72
232
|
|
|
73
233
|
export type ExternalDataAdminEndpointPathValue =
|
|
@@ -0,0 +1,152 @@
|
|
|
1
|
+
# Incremental extraction — read only what changed, and still find deletions
|
|
2
|
+
|
|
3
|
+
Read this when:
|
|
4
|
+
|
|
5
|
+
- a pipeline's source is large enough that re-reading all of it every run is too slow or too costly
|
|
6
|
+
(an Odoo model with hundreds of thousands of rows, synced hourly);
|
|
7
|
+
- you are choosing `lookbackSeconds` or `fullPassCron`;
|
|
8
|
+
- an incremental pipeline kept a row that was deleted in the source, or re-read the whole source after
|
|
9
|
+
a deploy, and you want to know why.
|
|
10
|
+
|
|
11
|
+
## What `incremental` changes
|
|
12
|
+
|
|
13
|
+
Without it, every run belongs to a FULL pass: the pipeline reads the whole source in key order, over as
|
|
14
|
+
many runs as `maxRowsPerRun` requires, and when the pass completes it compares what it read against the
|
|
15
|
+
destination and applies your `orphanPolicy` to rows the source no longer holds.
|
|
16
|
+
|
|
17
|
+
With it, the pipeline has TWO independent tracks:
|
|
18
|
+
|
|
19
|
+
| track | runs on | reads | may delete |
|
|
20
|
+
|---|---|---|---|
|
|
21
|
+
| incremental | `scheduleCron` | rows changed since the watermark | only the keys the source REPORTS deleted (the OData delta-link mode) |
|
|
22
|
+
| full | `incremental.fullPassCron` (and continues on `scheduleCron` ticks until it completes) | the whole source | yes — the only one that can |
|
|
23
|
+
|
|
24
|
+
A deleted row does not "change", so a read of what changed cannot see it — except under the OData
|
|
25
|
+
delta-link mode, where the service itself reports deleted entities. That is why `fullPassCron` is
|
|
26
|
+
required: an incremental-only pipeline would otherwise keep deleted rows forever, and even the
|
|
27
|
+
delta-link mode needs full passes after a lost position (below). Pick a cadence that bounds how
|
|
28
|
+
long a deleted row may linger (nightly is common), not how fresh changes are — the incremental track
|
|
29
|
+
already handles freshness.
|
|
30
|
+
|
|
31
|
+
The tracks never share a field. A full pass that needs two hundred runs does not hold up incremental
|
|
32
|
+
passes, and an incremental pass never moves the full pass's cursor. While a full pass is in flight,
|
|
33
|
+
every key an incremental pass reads is added to that full pass's record of what the source holds, so a
|
|
34
|
+
row that entered the source behind the full pass's cursor (a filter field changed, a record was
|
|
35
|
+
un-archived) is not treated as deleted when the full pass completes.
|
|
36
|
+
|
|
37
|
+
## Declaring it (Odoo)
|
|
38
|
+
|
|
39
|
+
```ts
|
|
40
|
+
externalDataPipeline: {
|
|
41
|
+
// …binding, remoteKeyLocalField, mapping…
|
|
42
|
+
scheduleCron: '*/15 * * * *', // incremental passes
|
|
43
|
+
incremental: {
|
|
44
|
+
mode: ExternalDataIncrementalExtractionMode.ODOO_WRITE_DATE,
|
|
45
|
+
fullPassCron: '0 3 * * *', // the deletion detector
|
|
46
|
+
lookbackSeconds: 300, // default
|
|
47
|
+
},
|
|
48
|
+
}
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
<!-- TIER C WAIVER: a declaration fragment, not an API excerpt — the full contract is inlined from the anchored source in framework-external-data-pipeline-api.md. -->
|
|
52
|
+
|
|
53
|
+
Refused at startup, with the reason named:
|
|
54
|
+
|
|
55
|
+
- `incremental` on a source whose dialect does not speak the mode (the Odoo mode on an OData source);
|
|
56
|
+
- `incremental` without `scheduleCron` — nothing would run incremental passes;
|
|
57
|
+
- a mode the source's VENDOR does not declare (the vendor facet lists the modes it supports);
|
|
58
|
+
- the delta-link mode with a `sourceFilter` or with a composite key (see below).
|
|
59
|
+
|
|
60
|
+
OData v2 and REST_JSON sources have no incremental mode; they run full passes.
|
|
61
|
+
|
|
62
|
+
## Declaring it (OData v4)
|
|
63
|
+
|
|
64
|
+
Two modes, and the vendor facet says which it supports (Dataverse: both; Business Central, SAP S/4HANA
|
|
65
|
+
v4: modified-at; the generic `odata` facet: both):
|
|
66
|
+
|
|
67
|
+
| mode | reads | sees deletions | declare |
|
|
68
|
+
|---|---|---|---|
|
|
69
|
+
| `ODATA_MODIFIED_AT` | rows whose timestamp property is at or after the watermark (less `lookbackSeconds`) | no | `modifiedAtRemoteField` — the entity's `Edm.DateTimeOffset` "modified" property, per entity (`modifiedon` on Dataverse, `lastModifiedDateTime` on Business Central) |
|
|
70
|
+
| `ODATA_DELTA_LINK` | the service's own change feed: `Prefer: odata.track-changes`, then its `@odata.deltaLink` | yes — each deleted entity's key gets your `orphanPolicy` | nothing more; the vendor must track changes for the entity set (Dataverse: enable change tracking on the table) |
|
|
71
|
+
|
|
72
|
+
- **Modified-at reads in KEY order**, like a full pass, so the watermark moves only when a pass
|
|
73
|
+
COMPLETES — to the largest timestamp the pass read, but never past the moment the pass started when it
|
|
74
|
+
took several pages: a row already read can change while later pages are still being read, and its new
|
|
75
|
+
timestamp is below theirs. So the next pass re-reads everything changed since the pass began. It
|
|
76
|
+
filters with `ge`, so rows sharing the watermark's instant are re-read, never skipped. The start is the
|
|
77
|
+
engine's clock and the timestamps are the source's; `lookbackSeconds` absorbs the difference, so set
|
|
78
|
+
it above any clock skew between the two. Changing `modifiedAtRemoteField` makes the stored watermark and
|
|
79
|
+
any half-read pass unrecognised, so the next pass reads everything once; a full pass in flight is not
|
|
80
|
+
disturbed, because the property changes where the incremental track reads from, not what a row holds.
|
|
81
|
+
- **Delta link** keeps the link the service puts on a pass's last page; the next pass follows it and
|
|
82
|
+
receives what changed and what was deleted. The link replaces the watermark only when that pass's
|
|
83
|
+
last page names the next one. Refused at startup: a `sourceFilter` (change tracking refuses `$filter`)
|
|
84
|
+
and a composite key (a deleted entity names one id). A service that answers the first pass without a
|
|
85
|
+
delta link does not track changes — that pass fails, naming the cause.
|
|
86
|
+
- **A delta link that has EXPIRED** resets the track, and the same run falls back to a FULL pass — the
|
|
87
|
+
read that finds the deletions the expired link would have reported. Expired means `410 Gone` or
|
|
88
|
+
`404 Not Found` (what the protocol lets a service answer), or the vendor's own error code where its
|
|
89
|
+
system-of-record facet declares one: Dataverse keeps change tracking for `ExpireChangeTrackingInDays`
|
|
90
|
+
(seven by default) and answers an older token with `0x80044352`, "Please perform a full sync". The run reports
|
|
91
|
+
`incrementalTrackReset: position-rejected` with `passMode: full`, and the next incremental run starts a
|
|
92
|
+
new delta link.
|
|
93
|
+
|
|
94
|
+
## How the Odoo mode reads what changed
|
|
95
|
+
|
|
96
|
+
Odoo keeps `write_date` ("Last Updated on") on every model that logs access. It STORES the value with
|
|
97
|
+
microseconds but SERVES it cut to the second, and a domain compares the stored value. So neither
|
|
98
|
+
obvious design works: reading `write_date > watermark` skips rows that share the last row's second
|
|
99
|
+
but did not fit on the page, and resuming after the served `(write_date, id)` re-reads its own last
|
|
100
|
+
row, because a row served as `10:00:00` is stored after `10:00:00`. The pipeline therefore reads by
|
|
101
|
+
(SECOND, id): it finishes one second in id order, then looks for the rows after it. Every row is read
|
|
102
|
+
once per pass, however many rows share a second and however a page boundary falls.
|
|
103
|
+
|
|
104
|
+
- **The watermark is the furthest position whose rows were all LOADED** — a position in Odoo's own
|
|
105
|
+
`write_date` order, never your server's clock, and it only moves after the rows that reached it were
|
|
106
|
+
written. A crash re-reads; it never skips.
|
|
107
|
+
- **`lookbackSeconds` re-reads the last few minutes at the start of every incremental pass.** Odoo
|
|
108
|
+
stamps `write_date` when a transaction RUNS, not when it commits, so a long transaction can commit a
|
|
109
|
+
row whose `write_date` is already older than the watermark, or inside the watermark's own second.
|
|
110
|
+
Re-reading is cheap: the load compares content and writes nothing for an unchanged row. Raise it for
|
|
111
|
+
a deployment with long batch jobs. `0` disables it and is not harmless: a row written later inside a
|
|
112
|
+
second a pass already finished is then read only when it changes again, or by a full pass.
|
|
113
|
+
- **`write_date` is read but not loaded.** Map it like any other field if the destination should show
|
|
114
|
+
it.
|
|
115
|
+
- **A model without access logging has no `write_date`.** The first incremental page refuses, naming
|
|
116
|
+
the field; read such a model with full passes only (remove `incremental`).
|
|
117
|
+
- **A record with an EMPTY `write_date`** (inserted beneath Odoo's ORM, by SQL or an import) has no
|
|
118
|
+
position in the order: incremental passes never read it, and full passes load it like any other row.
|
|
119
|
+
- Archived records are read by both tracks, exactly as without `incremental`.
|
|
120
|
+
|
|
121
|
+
## When the whole source is read again
|
|
122
|
+
|
|
123
|
+
An incremental pass never re-reads a row that did not change in the source. So a change on YOUR side
|
|
124
|
+
would otherwise reach only rows that happen to change remotely afterwards. The pipeline fingerprints
|
|
125
|
+
everything that decides what is extracted and how a row is loaded — binding, key fields, the whole
|
|
126
|
+
mapping, `sourceFilter`, `archivedRecords`, the partition fields, the operator's partition
|
|
127
|
+
ASSIGNMENTS, and the owner organization. When the fingerprint changes, the watermark is dropped and
|
|
128
|
+
the next incremental pass reads the whole source once. The run reports
|
|
129
|
+
`incrementalTrackReset: extraction-basis-changed` (or `no-track` on the first ever pass).
|
|
130
|
+
|
|
131
|
+
Schedule, `maxRowsPerRun`, `lookbackSeconds`, the orphan policy and the population are NOT in the
|
|
132
|
+
fingerprint: they change how often or how carefully rows are read, not what a row holds.
|
|
133
|
+
|
|
134
|
+
The FULL pass keys on the same fingerprint. A full pass that spans several runs records the
|
|
135
|
+
fingerprint it started under, and a run under a different one ABANDONS it and starts a new full pass
|
|
136
|
+
from the beginning, reporting `fullPassRestart: extraction-basis-changed`. Resuming would make one pass
|
|
137
|
+
mix two declarations: a changed key would orphan everything read before it, and a narrower
|
|
138
|
+
`sourceFilter` would leave the rows it now excludes in place. So a declaration change costs one
|
|
139
|
+
re-read on each track, and nothing else — the load compares content and skips unchanged rows.
|
|
140
|
+
|
|
141
|
+
## Reading a run
|
|
142
|
+
|
|
143
|
+
- `passMode` on the run report, on the stored `lastRunSummary`, and on the run's audit row says which
|
|
144
|
+
track the run advanced; the run's history row also records `incrementalMode` (write-date, modified-at or
|
|
145
|
+
delta link) and `removedRows` — the deletions the source reported, handed to the orphan policy (a count of
|
|
146
|
+
reports: a key you never held still counts; the load's own ledger row says what the policy did).
|
|
147
|
+
- An incremental run's `reconciliationStatus` is `deferred-to-full-pass` (or `load-failed`) — it never
|
|
148
|
+
INFERS a deletion from what it did not read; only the deletions a delta link reports are applied.
|
|
149
|
+
- `cursor` on the report is the continuation of THAT run's track. The admin listing shows the full
|
|
150
|
+
pass's `cursor` and, separately, the `incrementalTrack` (`watermark`, `cursor`).
|
|
151
|
+
- The admin `POST …/run` takes `"passMode": "full"` to force a deletion-detecting pass between cadence
|
|
152
|
+
ticks; without it, the run is the kind `scheduleCron` runs.
|
|
@@ -0,0 +1,60 @@
|
|
|
1
|
+
# Reading an OData v2 service (`ODATA_V2`)
|
|
2
|
+
|
|
3
|
+
Read this when the system you are reading serves OData **v2** — SAP's classic Gateway services
|
|
4
|
+
(`https://<host>/sap/opu/odata/sap/<SERVICE>`, `API_BUSINESS_PARTNER` first among them) — whether as a
|
|
5
|
+
read-through virtual resource or as a pipeline source.
|
|
6
|
+
|
|
7
|
+
## Declare it on the instance AND the binding
|
|
8
|
+
|
|
9
|
+
v2 is its own dialect, not v4 with a header. The system-of-record instance and every binding that reads
|
|
10
|
+
it declare `dialect: ODATA_V2`; the binding otherwise has the same shape as an `ODATA` one (`entityRef` is
|
|
11
|
+
the entity set, `keyFields`, `fieldMappings`). The instance's `baseUrl` is the v2 **service root**.
|
|
12
|
+
|
|
13
|
+
- Each key field's `codec` must match its Edm type in `$metadata`: `STRING` for an `Edm.String` key (SAP's
|
|
14
|
+
`BusinessPartner` is text, even though it looks numeric), `INTEGER` for an `Edm.Int32`/`Edm.Int64` key,
|
|
15
|
+
`GUID` for an `Edm.Guid` key. A key literal the type cannot hold is refused at the first read. An
|
|
16
|
+
`Edm.DateTime` key component cannot be read yet: its value arrives as an instant, which a row id cannot
|
|
17
|
+
be built from.
|
|
18
|
+
- One instance per service root. A system you read over both v2 and v4 is two instances — each with its
|
|
19
|
+
own credential and `maxRequestsPerMinute`, and their sum must stay under the vendor's allowance.
|
|
20
|
+
- A v2 root declared as `ODATA` is refused at the first read with a message naming `odata-v2`.
|
|
21
|
+
|
|
22
|
+
## What the engine does for you
|
|
23
|
+
|
|
24
|
+
- **It reads the service's `$metadata`** once per client (per resource for read-through, per run for a
|
|
25
|
+
pipeline), with the instance's credentials. Every property's Edm type comes from it, because v2 JSON
|
|
26
|
+
does not say what a value is and a filter literal must be spelled for its type. If `$metadata` cannot be
|
|
27
|
+
read, the read fails — it never guesses.
|
|
28
|
+
- **It decodes values before you see them:** `"/Date(1767571200000)/"` becomes a `Date`; a string
|
|
29
|
+
`Edm.Decimal`, `Edm.Int64`, `Edm.Double` becomes a `number`; `__metadata` and deferred navigation
|
|
30
|
+
properties are removed. Map these fields onto `z.date()` / `z.number()` directly — no coercion needed.
|
|
31
|
+
- **It refuses what a number cannot hold exactly,** naming the property: an `Edm.Int64` beyond
|
|
32
|
+
2^53 − 1, and an `Edm.Decimal` with more than 15 significant digits. It only fetches what you read, so
|
|
33
|
+
this fails only a read that asks for the property: a read-through `$select`s the fields of the
|
|
34
|
+
resource's schema (plus its keys), and a pipeline the fields its mapping reads. Leave such a property
|
|
35
|
+
out of the resource's schema or the mapping, or read it from a service that serves it as `Edm.String`.
|
|
36
|
+
- **It spells each filter for the property's type:** `datetime'2026-01-05T00:00:00.000'`, `42L`,
|
|
37
|
+
`2.5M`, `guid'…'`, and search as `substringof('needle', tolower(Prop)) eq true`. Every request asks for
|
|
38
|
+
JSON (`$format=json`); totals use `$inlinecount=allpages`. When the service serves fewer rows than a
|
|
39
|
+
read-through page asked for and hands back a `__next`, the page is read to its end, so the next page
|
|
40
|
+
starts where this one really ended.
|
|
41
|
+
- **A pipeline walks the entity's KEY,** not `__next`: each page asks for the next N keys after the last
|
|
42
|
+
one read (`Key gt 'last'`, lexicographic for a composite key). v2 does not promise a partial listing is
|
|
43
|
+
stable, and a complete pass that skipped a row would delete its local copy. A page served out of key
|
|
44
|
+
order is refused rather than trusted.
|
|
45
|
+
|
|
46
|
+
## What it cannot do
|
|
47
|
+
|
|
48
|
+
- **Write.** A binding opening `create` / `update` / `delete` on `ODATA_V2` is refused at startup, and so
|
|
49
|
+
is the `EXTERNAL_ERASURE_OPERATION` stance (a remote DELETE). Declare `NO_SUBJECT_DATA` or
|
|
50
|
+
`CONTROLLER_ACKNOWLEDGED_NON_ERASURE`.
|
|
51
|
+
- **Filter or sort by a complex-typed property,** or by `Edm.Time` / `Edm.Binary`: those are refused by
|
|
52
|
+
name.
|
|
53
|
+
- **Run actions** (OData function imports) — declared actions are v4-only.
|
|
54
|
+
|
|
55
|
+
## Checklist
|
|
56
|
+
|
|
57
|
+
- [ ] The instance and the binding both say `ODATA_V2`, and the instance's `baseUrl` is the v2 service root.
|
|
58
|
+
- [ ] Every mapped field exists in the service's `$metadata` (a pipeline's run report warns when one is missing).
|
|
59
|
+
- [ ] The erasure stance is `NO_SUBJECT_DATA` or `CONTROLLER_ACKNOWLEDGED_NON_ERASURE`.
|
|
60
|
+
- [ ] No `create` / `update` / `delete` is opened.
|
|
@@ -0,0 +1,179 @@
|
|
|
1
|
+
# OUTBOUND pipelines — sending the application's own rows to a system of record
|
|
2
|
+
|
|
3
|
+
Read this when the application is where a record is BORN and a system of record must receive it: leads captured
|
|
4
|
+
in the application that belong in the company's Odoo, service requests that the ERP must hold, anything the
|
|
5
|
+
application owns first and another system must also have.
|
|
6
|
+
|
|
7
|
+
An OUTBOUND pipeline is the same `externalDataPipeline` declaration with the arrows reversed. The destination is an
|
|
8
|
+
ordinary local resource whose rows your users create and edit. The pipeline sends each changed row to the system of
|
|
9
|
+
record: a **create** the first time, an **update** after that.
|
|
10
|
+
|
|
11
|
+
## When to use it — and when not
|
|
12
|
+
|
|
13
|
+
| You need | Use |
|
|
14
|
+
|---|---|
|
|
15
|
+
| A local row created or changed by the application should also exist in the ERP, eventually | **OUTBOUND pipeline** |
|
|
16
|
+
| One user action must change the ERP NOW, and the user must see the result or the refusal | a write through a VIRTUAL resource (`read-through-writes.md`) |
|
|
17
|
+
| The ERP owns the data and the application copies it | an INBOUND pipeline (the default direction) |
|
|
18
|
+
| The ERP must run a business step (post an invoice, confirm an order) | a declared action (`system-of-record-actions.md`) |
|
|
19
|
+
| The same row is edited on BOTH sides | not yet — a conflict policy is a separate direction, not built |
|
|
20
|
+
|
|
21
|
+
The difference from a virtual write is WHEN and WHO: a virtual write happens inside the user's request and fails
|
|
22
|
+
it when the ERP refuses. An outbound pipeline sends later, on its own schedule, and a refusal is retried and
|
|
23
|
+
reported — the user's save always succeeds locally.
|
|
24
|
+
|
|
25
|
+
## The declaration
|
|
26
|
+
|
|
27
|
+
```ts
|
|
28
|
+
import { ExternalDataMappingEntryKind, ExternalDataPipelineDirection, HttpApiKeyComponentCodec, HttpApiWriteConcurrencyMode, HttpApiWriteVerb } from '@wildo-ai/saas-models/external-data';
|
|
29
|
+
import { HttpApiErasureStance, HttpApiTransportDialect } from '@wildo-ai/saas-models';
|
|
30
|
+
|
|
31
|
+
externalDataPipeline: {
|
|
32
|
+
direction: ExternalDataPipelineDirection.OUTBOUND,
|
|
33
|
+
binding: {
|
|
34
|
+
dialect: HttpApiTransportDialect.ODOO_JSONRPC, system: 'odoo', entityRef: 'crm.lead',
|
|
35
|
+
keyFields: [{ localField: 'id', remoteField: 'id', codec: HttpApiKeyComponentCodec.INTEGER }],
|
|
36
|
+
erasure: { stance: HttpApiErasureStance.NO_SUBJECT_DATA },
|
|
37
|
+
writableVerbs: [HttpApiWriteVerb.CREATE, HttpApiWriteVerb.UPDATE],
|
|
38
|
+
writeConcurrency: { mode: HttpApiWriteConcurrencyMode.LAST_WRITER_WINS },
|
|
39
|
+
},
|
|
40
|
+
remoteKeyLocalField: 'odooRef',
|
|
41
|
+
mapping: [
|
|
42
|
+
{ kind: ExternalDataMappingEntryKind.REMOTE_FIELD, remoteField: 'name', localField: 'title' },
|
|
43
|
+
{ kind: ExternalDataMappingEntryKind.REMOTE_REFERENCE, remoteField: 'partner_id', localField: 'accountId', targetResourceType: 'accounts' },
|
|
44
|
+
],
|
|
45
|
+
scheduleCron: '*/5 * * * *',
|
|
46
|
+
},
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
What each part means, and what startup refuses:
|
|
50
|
+
|
|
51
|
+
- **`writableVerbs` must include `CREATE`.** A row gets its remote key only from the create that sends it, so an
|
|
52
|
+
update-only pipeline could never send anything. `UPDATE` is optional: without it the pipeline is INSERT-ONLY —
|
|
53
|
+
each row is created once and later edits are not sent. `DELETE` is refused: removing a record of the system of
|
|
54
|
+
record is its operator's decision, never the side effect of a local delete.
|
|
55
|
+
- **`writeConcurrency` is `LAST_WRITER_WINS`.** The local row is the source of every field it sends. A version
|
|
56
|
+
check compares a version a CALLER read, and a pass has no such caller.
|
|
57
|
+
- **Only `REMOTE_FIELD` and `REMOTE_REFERENCE` entries.** A declared expression derives a local value from remote
|
|
58
|
+
ones and has no inverse. `required`, `coercion` and a non-default `unresolved` are refused: they describe
|
|
59
|
+
loading, and this direction loads nothing. `orphanCascadeAcknowledged` is ADMITTED and means what it means
|
|
60
|
+
inbound: when the reference's target is an INBOUND destination that deletes orphans, and the relationship
|
|
61
|
+
deletes children with their parent, a record vanishing from the target's source takes these rows with it.
|
|
62
|
+
- **Nothing that describes READING the source:** `sourceFilter`, `incremental`, `archivedRecords`,
|
|
63
|
+
`partitionKeyLocalField`, and a `population` or `orphanPolicy` other than the defaults are refused.
|
|
64
|
+
- **`erasure.stance` must be `NO_SUBJECT_DATA`, and no sent field may declare `.dataCategories()`.** A system of
|
|
65
|
+
record receiving rows about people is their recipient, and no subject erasure reaches the copy it holds yet. Until
|
|
66
|
+
it does, this direction sends records about organizations and things (a company lead, an order, an asset), never
|
|
67
|
+
about a person.
|
|
68
|
+
|
|
69
|
+
## The destination schema — the ownership rules reversed
|
|
70
|
+
|
|
71
|
+
An INBOUND destination's mapped fields are pipeline-owned and read-only. An OUTBOUND destination's are the
|
|
72
|
+
APPLICATION's:
|
|
73
|
+
|
|
74
|
+
| Field | Rule | Why |
|
|
75
|
+
|---|---|---|
|
|
76
|
+
| each mapped `localField` | writable by callers (NOT excluded from both create and update) | a field nobody can set would send a value nobody decided |
|
|
77
|
+
| `remoteKeyLocalField` | `z.string().optional().isUnique().excludeFromCreate().excludeFromUpdate()` — optional, never `.nullable()` | empty until the first send; the engine writes it ONCE from the key the create answered, and a caller who could write it could point a local row at any remote record. UNIQUE because one remote record may have one local row: two rows on one key would overwrite each other's record. The plain (sparse) unique ignores rows with no key yet; an explicit null would not be ignored on MongoDB, so the field refuses null |
|
|
78
|
+
| a `REMOTE_REFERENCE` `localField` | an optional string foreign key of a declared relationship to `targetResourceType` | the target's REMOTE key is sent in its place |
|
|
79
|
+
| the tenant foreign key | exactly as for any pipeline destination: ORGANIZATIONS scope, a routed required foreign key, engine-supplied | see "The destination's tenant is ENGINE-SUPPLIED" in the skill |
|
|
80
|
+
|
|
81
|
+
`remoteKeyLocalField` needs no `.isBusinessKey()` here — nothing merges on it. Its `.isUnique()` is what the store
|
|
82
|
+
enforces on every path that writes the key (the pass, the operator door), so a PostgreSQL destination owes a migration
|
|
83
|
+
for the index. A create that lands with a key another row already holds is not linked and not re-sent: it waits for
|
|
84
|
+
an operator like an unknown create (`lastOutcomeCode: remote-key-held-by-another-row`).
|
|
85
|
+
|
|
86
|
+
## What is sent, and when
|
|
87
|
+
|
|
88
|
+
Every create or update of a destination row through the application's service tier records a CHANGE MARKER for that
|
|
89
|
+
row. On the markers' own store it joins the write's transaction, so a failed save records nothing; on a different
|
|
90
|
+
store it commits just BEFORE the write, the direction that can only over-send (a rolled-back save makes the next pass
|
|
91
|
+
resend the row's unchanged state) and never lose a change. This includes system writes and custom operations that
|
|
92
|
+
borrow `create` or `update`. An operation that overrides the core write entirely records nothing itself: its change
|
|
93
|
+
is sent only if it writes the row through the service registry, which records it like any other write.
|
|
94
|
+
|
|
95
|
+
Each pass (on `scheduleCron`, or `POST …/run`) reads the markers and, for each row **as it stands now**:
|
|
96
|
+
|
|
97
|
+
- **no remote key yet → CREATE**, then writes the answered key onto the row;
|
|
98
|
+
- **a remote key → UPDATE** of every mapped field. A field that is empty locally is CLEARED remotely, because the
|
|
99
|
+
local row is the source. (A create simply omits it.)
|
|
100
|
+
- **several edits between two passes → ONE write**, of the latest state;
|
|
101
|
+
- **a `REMOTE_REFERENCE`** sends the target row's remote key — an Odoo many2one as the bare record id. A target not
|
|
102
|
+
sent yet makes the row WAIT (`deferred.reference-target-not-sent`), because sending it without its link would
|
|
103
|
+
create a record nothing ever links afterwards. It goes the pass after its target does.
|
|
104
|
+
|
|
105
|
+
Never sent:
|
|
106
|
+
|
|
107
|
+
- **a row of another organization.** A system of record belongs to the organization that owns the application;
|
|
108
|
+
another tenant's rows are never sent, and their markers are dropped (`droppedOtherOrganization`);
|
|
109
|
+
- **a row that is gone** or hidden by an erasure (`droppedRowGone`);
|
|
110
|
+
- **an edit on an insert-only pipeline** (`droppedNothingToSend`);
|
|
111
|
+
- **a local delete** — ever.
|
|
112
|
+
|
|
113
|
+
## When the instance is PARTITIONED
|
|
114
|
+
|
|
115
|
+
A created record must land in ONE partition (an Odoo company). Declare `partitionUnitLocalField`: an optional string
|
|
116
|
+
field holding the organization unit the row belongs to. The engine places the create in the partition the operator
|
|
117
|
+
assigned to that unit, exactly as a read-through create is placed. A row naming no unit, or a unit assigned no
|
|
118
|
+
single partition, waits (`deferred.partition-unplaced`) and is retried each time its backoff elapses — assign the partition, or set the
|
|
119
|
+
row's unit. An update never moves a record between partitions. Do not map anything onto the partition field
|
|
120
|
+
itself: startup refuses it, because the partition is derived.
|
|
121
|
+
|
|
122
|
+
## The order changes are sent in, and the backoff
|
|
123
|
+
|
|
124
|
+
A pass takes only the changes that are DUE, oldest first. A new local change is due at once. A change a pass could
|
|
125
|
+
not send — refused, waiting for a reference or a partition, of unknown outcome, waiting for an operator — is moved
|
|
126
|
+
out by a backoff that doubles from one minute to a ceiling of one day, and a new edit of the row clears it. So a row
|
|
127
|
+
the system of record keeps refusing never stands in front of a new change, and costs one attempt (one ledger row,
|
|
128
|
+
one audit row) per backoff rather than one per scheduled pass. A pass run before anything is due reads nothing.
|
|
129
|
+
|
|
130
|
+
## Failures, and the one that waits for you
|
|
131
|
+
|
|
132
|
+
Every write goes through the same write ledger and Idempotency-Key discipline as a read-through write, keyed per
|
|
133
|
+
row change, and every write leaves an `HTTP_API_WRITE_THROUGH` audit row naming the member whose change was sent and
|
|
134
|
+
the local row it came from.
|
|
135
|
+
|
|
136
|
+
| What happened | What the pipeline does |
|
|
137
|
+
|---|---|
|
|
138
|
+
| The system of record refused the write | retried under a NEW key once its backoff has elapsed; counted in `remoteRefused` |
|
|
139
|
+
| It could not be reached | the pass stops (`stoppedBecauseUnreachable`); the row that met it is backed off, and the rows not reached are taken by the next pass |
|
|
140
|
+
| The write landed, and recording it locally failed | nothing is sent again: the next pass settles it (`replayed`) — from the row's key if it was written, from the write ledger if not |
|
|
141
|
+
| The pass stopped after sending, before the answer was recorded | the next pass asks the write ledger. Applied → settled, nothing sent (`replayed`). Still in flight → left for later (`leftForNextPass`), then UNKNOWN once its deadline passes. A CREATE whose ledger entry is gone (a day passed) is UNKNOWN — never sent afresh |
|
|
142
|
+
| **The outcome is UNKNOWN** (a timeout after sending) | never sent again under that change. An UPDATE is sent again once the row changes again (`awaitingNewerChange` until then). A **CREATE waits for an operator** (`awaitingOperator`): sending it again could create the record twice |
|
|
143
|
+
|
|
144
|
+
An unknown CREATE is answered by someone who looked in the system of record, through the admin door (same
|
|
145
|
+
`X-Admin-Secret` as the other pipeline doors; see `framework-pipeline-admin-endpoints-api.md`):
|
|
146
|
+
|
|
147
|
+
- `GET /internal/admin/external-data/outbound-changes?resourceType=<destination>` lists the changes of unknown
|
|
148
|
+
outcome: the local row, the write that was sent, who made the change and when;
|
|
149
|
+
- `POST /internal/admin/external-data/outbound-changes/resolve` answers ONE of them, with a written `reason`:
|
|
150
|
+
- **it was created** — `"answer": "applied"` with `"remoteKey"`, the key of the record you found. It is checked
|
|
151
|
+
against the binding's key fields and written onto the row, so later edits UPDATE that record instead of creating
|
|
152
|
+
another. Refused (409) if the row already holds a different key, ANOTHER row already holds that key (one record,
|
|
153
|
+
one row), the row is gone, or it is not the owner organization's;
|
|
154
|
+
- **it was not** — `"answer": "not-applied"`: the row is sent again at once, under a new key. Refused (409) when the
|
|
155
|
+
row already holds a key — the create landed, so answer `applied`;
|
|
156
|
+
- an unknown UPDATE answered `applied` needs no key; one answered `not-applied` is sent again.
|
|
157
|
+
|
|
158
|
+
Every answer is recorded on the audit trail (`external_data_outbound_unknown_resolved`) with the reason, who said they
|
|
159
|
+
answered, and what it changed. 409 means the change is not of unknown outcome any more — list again.
|
|
160
|
+
|
|
161
|
+
## What a pass reports
|
|
162
|
+
|
|
163
|
+
A sending pass's run report carries `passMode: 'send'` (an OUTBOUND pipeline runs no other kind, and `POST …/run`
|
|
164
|
+
refuses `full` or `incremental` for it) and an `outbound` summary: `changesRead`, `created`, `updated`, `replayed`,
|
|
165
|
+
`deferred` per reason, `remoteRefused`, `refused`, `outcomeUnknown`, `awaitingOperator`, `awaitingNewerChange`,
|
|
166
|
+
`leftForNextPass`, the three `dropped…` counts, and `stoppedBecauseUnreachable` / `stoppedAtDeadline`. Every marker
|
|
167
|
+
read lands in exactly one count. A pass that stopped at its bound (`maxRowsPerRun`), its deadline
|
|
168
|
+
(`maxRunDurationMs`) or an unreachable source is a partial pass; the next continues.
|
|
169
|
+
|
|
170
|
+
Those counts are what THIS pass did with the changes due by its start: a change in backoff is not read and appears in
|
|
171
|
+
none of them. What still waits is `waiting`, counted over every change, due or not: `awaitingOperator` (creates to
|
|
172
|
+
answer), `awaitingNewerChange`, `deferred` per reason and `backedOff`. **`waiting.awaitingOperator` above zero is the
|
|
173
|
+
signal to look** — those rows are never sent again on their own.
|
|
174
|
+
|
|
175
|
+
## Database migrations
|
|
176
|
+
|
|
177
|
+
On PostgreSQL the change markers live in an engine table, `externalDataOutboundChanges`, and the destination's
|
|
178
|
+
`remoteKeyLocalField` is an ordinary column. Both arrive through the application's normal migration step
|
|
179
|
+
(`application-database-migrations`) — run `wildo db diff` after adding the pipeline or upgrading the framework.
|
package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md
CHANGED
|
@@ -40,4 +40,4 @@ application decides in fields the mapping never names.
|
|
|
40
40
|
| `must be optional/nullable/defaulted, or declare required: true` | an absent remote value has nowhere honest to land |
|
|
41
41
|
| `population CLOSED` | a caller CREATE operation is declared on a row set the pipeline owns — the message names it, including custom create-shaped operations |
|
|
42
42
|
| `cannot ALSO declare a pipeline` | both lanes on one resource; a virtual resource is already the remote side |
|
|
43
|
-
| `
|
|
43
|
+
| `must walk a declared KEYSET` | a REST_JSON source whose `list` statement declares no `keyset` — offset paging could skip or double rows whenever the remote set shifts mid-run. Declare the keyset; see `rest-keyset-sources.md` |
|