@wildo-ai/framework-knowledge 1.1.11 → 1.1.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +4 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +3 -3
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
- package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +170 -32
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
- 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 +4 -12
- 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.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
- 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 +7 -4
- 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 +76 -14
- 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 +0 -4
- 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 +3 -15
- 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.map +1 -1
- 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.map +1 -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.map +1 -1
- 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 +1 -1
- 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 +1 -1
- 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 +35 -14
- 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 +16 -8
- 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 +19 -8
- 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 +29 -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 +80 -16
- 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.map +1 -1
- 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 +2 -2
- 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 +2 -2
- 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 +5 -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 +3 -2
- 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.map +1 -1
- 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 +45 -10
- 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 +61 -21
- 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 +4 -3
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
- 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.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +8 -6
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +11 -3
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -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 +4 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
- 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 +5 -2
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +4 -3
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
- 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 +22 -10
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
- 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.map +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 +8 -3
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -7
- 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.map +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.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +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.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
- 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.d.ts.map +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 +1 -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.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
- 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 +3 -7
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
- 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 +3 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -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 +3 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -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 +4 -2
- 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 +34 -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 +35 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
- package/dist/esm/source-anchor-grammar.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
- 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 +439 -27
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +104 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +51 -7
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +10 -2
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -3
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +43 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -6
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
- package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
- package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
- package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
- package/dist/knowledge/references/application-maturity.config.md +27 -1
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
- package/dist/knowledge/references/brand.name-screening.config.md +30 -3
- package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
- package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
- package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
- package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
- package/dist/knowledge/references/companion.market.generation-service.md +46 -5
- package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
- package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
- package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
- package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
- package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
- package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
- package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
- package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
- package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
- package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
- package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
- package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
- package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
- package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
- package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
- package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
- package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
- package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
- package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
- package/dist/knowledge/references/example.website.section.stats.md +1 -1
- package/dist/knowledge/references/experience-plan.config.md +111 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
- package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
- package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
- package/dist/knowledge/references/integration-plan.config.md +7 -7
- package/dist/knowledge/references/placement-plan.config.md +19 -0
- package/dist/knowledge/references/platform.config.backing-services.md +9 -11
- package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
- package/dist/knowledge/references/platform.config.infrastructure-host.md +0 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +84 -8
- package/dist/knowledge/references/platform.config.saas.md +20 -18
- package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
- package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
- package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
- package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +4 -4
- package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +29 -2
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
- package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
- package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
- package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
- package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +363 -2
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
- package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
- package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
- package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard.md +130 -0
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
- package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
- package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
- package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
- package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
- package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
- package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
- package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
- package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
- package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
- package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
- package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
- package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
- package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
- package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
- package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
- package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
- package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
- package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
- package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
- package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
- package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
- package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
- package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
- package/dist/knowledge/references/service-method.config.md +35 -2
- package/dist/knowledge/references/vision.constraint.config.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
- package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
- package/dist/knowledge/references/zod.factories.code.md +4 -4
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +4 -4
- package/dist/knowledge/references/zod.factories.phone.md +4 -4
- package/dist/knowledge/references/zod.factories.year-month.md +79 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +415 -2
- package/dist/knowledge/registries/playbooks.json +51 -39
- package/dist/knowledge/registries/source-tags.json +2412 -1604
- package/dist/knowledge/rules/database-migration-obligation.md +6 -7
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +3 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
- package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +79 -0
- package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
- package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
- package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +197 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
- package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
- package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
- package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +61 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +18 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +44 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +375 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +3 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +37 -14
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
- package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +125 -77
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +0 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +84 -8
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +255 -12
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
- package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
- package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +33 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +7 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
- package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
- package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
- package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
- package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
- package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
- package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
- package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +244 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
- package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
- package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
- package/dist/knowledge/topic-index.json +2275 -715
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +6 -6
- package/dist/tsconfig.tsbuildinfo +0 -1
|
@@ -149,10 +149,12 @@ classifier the application's agents use (for example
|
|
|
149
149
|
`AI_CONTENT_SAFETY` in `engineCapabilities`, and set its key with
|
|
150
150
|
`wildo secrets set`. The companion then screens each such element before
|
|
151
151
|
it enters a brief, and withholds from that brief one the classifier flags.
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
152
|
+
`wildo context elements` screens the same elements before it answers, so a
|
|
153
|
+
flagged one is withheld there too, and a research step's evidence is screened
|
|
154
|
+
before the playbook steps beside it read it. The element itself stays in your
|
|
155
|
+
specifications, with its `researchedBy` provenance. Without a classifier the
|
|
156
|
+
element still reaches the brief and the door, marked as unscreened, and the
|
|
157
|
+
build continues.
|
|
156
158
|
|
|
157
159
|
A CATALOGUE-tier provider (the common case for a packaged integration,
|
|
158
160
|
and the tier of most registry modules) claims no engine capability at
|
|
@@ -180,7 +182,11 @@ that can run a coding agent must declare `complianceProfile`.
|
|
|
180
182
|
the vendor offers and the regions it processes in — possibilities, not the
|
|
181
183
|
operator's choice. Its schema refuses a `VENDOR_HOSTED` profile with no
|
|
182
184
|
region, but nothing parses a package's profile at startup, so validate it
|
|
183
|
-
in the package's own tests.
|
|
185
|
+
in the package's own tests. Say how each region is REACHED
|
|
186
|
+
(`processingRegionReach`): by its own endpoint, which the application's
|
|
187
|
+
choice then selects for every arm, or by where the operator's account
|
|
188
|
+
lives. Composition refuses an endpoint region that leaves an arm on its
|
|
189
|
+
default host — see `references/framework-provider-processing-region-api.md`. What a compliance document says about the
|
|
184
190
|
provider comes from the operator's `providerComplianceChoices`: a
|
|
185
191
|
configured provider with no choice declared is reported as not
|
|
186
192
|
established — see `compliance-document-authoring`.
|
|
@@ -275,6 +281,35 @@ machine, in any form, stops the backend at startup and refuses every request,
|
|
|
275
281
|
so a stand-in's address can never carry a real key off to a local process.
|
|
276
282
|
Set the vendor's own host in every other environment.
|
|
277
283
|
|
|
284
|
+
An arm names such a slot with `baseUrlHostEnvVarName`, in place of its fixed
|
|
285
|
+
`baseUrl`. The REST, document-extraction, content-safety, LLM, image and
|
|
286
|
+
embeddings arms all take it, and each must name exactly one endpoint source
|
|
287
|
+
(the REST arm has a third, `baseUrlEnvVarName`, for a whole URL), or the
|
|
288
|
+
engine refuses the arm. On the LLM, image and embeddings arms the engine also
|
|
289
|
+
hands the result to your `sdkFactory`: it is called as
|
|
290
|
+
`sdkFactory(apiKey, { baseUrl })`, with `baseUrl` already resolved
|
|
291
|
+
(`https://<host>`, or the local double's address). Pass it to your SDK client
|
|
292
|
+
(an Azure OpenAI client's `baseURL`, say); never read the host from the
|
|
293
|
+
environment yourself, because a module reads only the secrets the engine gives
|
|
294
|
+
it. A vendor with one fixed host keeps its `baseUrl` and may ignore the second
|
|
295
|
+
argument.
|
|
296
|
+
|
|
297
|
+
An LLM, embeddings or image arm whose vendor authenticates with a SERVICE ACCOUNT
|
|
298
|
+
rather than an API key (Google Vertex AI) declares two more fields:
|
|
299
|
+
|
|
300
|
+
- `serviceAccountToken: { keyFormat, tokenUrl, tokenHosts, scope, algorithm }`
|
|
301
|
+
— `apiKey.secretRef` then holds the account's key file
|
|
302
|
+
(`ProviderServiceAccountKeyFormat.GOOGLE_SERVICE_ACCOUNT_JSON`), the engine
|
|
303
|
+
exchanges it at `tokenUrl` (a JWT-bearer grant signed with the key, sent to no
|
|
304
|
+
host outside `tokenHosts`, never to a `token_uri` the key file names), caches
|
|
305
|
+
the token until a minute before it expires, and calls your `sdkFactory` with
|
|
306
|
+
the TOKEN as its first argument. Send it as `Authorization: Bearer <token>`;
|
|
307
|
+
your module never sees the key.
|
|
308
|
+
- `deploymentParameterEnvVarNames: { project: 'X_PROJECT', location: 'X_LOCATION' }`
|
|
309
|
+
— values the request path names, each read by the engine from a slot your
|
|
310
|
+
secrets contract declares, admitted only as an identifier (letters, digits,
|
|
311
|
+
`.`, `_`, `-`), and handed to `sdkFactory` as `context.deploymentParameters`.
|
|
312
|
+
|
|
278
313
|
This covers the API calls only. When the same slot also fills an OAuth2
|
|
279
314
|
endpoint host (Workday's `WORKDAY_API_HOST` names its token endpoint too),
|
|
280
315
|
the connect flow refuses a loopback host in every environment, because that
|
|
@@ -339,6 +374,40 @@ refuses it when the range is missing or excludes the installed base.
|
|
|
339
374
|
Read `references/framework-provider-augmentation-api.md` for the full
|
|
340
375
|
contract and every refusal.
|
|
341
376
|
|
|
377
|
+
### A GraphQL vendor: the operation sends a document the provider owns
|
|
378
|
+
|
|
379
|
+
GitHub v4, Linear, Shopify Admin and monday.com expose ONE endpoint and tell operations apart by a query document.
|
|
380
|
+
Never make the document an input (that hands the caller the vendor's whole schema). Declare `graphql: { document,
|
|
381
|
+
operationName }` on the operation: `method: POST`, `pathTemplate` the GraphQL endpoint (`/graphql`), no
|
|
382
|
+
`requestBody`, and no parameter fed by the input (a `constantValue` header such as a pinned API version is fine). The
|
|
383
|
+
input IS the variables, so `inputSchema` declares exactly the variables the document declares, and `inputOptions` work
|
|
384
|
+
on them. The document holds exactly one operation of that name: a `query` classified READ or a `mutation` classified
|
|
385
|
+
WRITE (a `subscription` is refused). `resultPath` and `outputSchema` read the answer's `data`. Add `errorCodePath`
|
|
386
|
+
(inside each error, such as `extensions.code`) only when the vendor documents a code there. When the vendor documents
|
|
387
|
+
a code meaning the CREDENTIAL itself was refused (a dead or expired token, inside a 200 or a 4xx error list), list it in
|
|
388
|
+
`credentialRefusedErrorCodes` beside `errorCodePath`: the stored credential is then recorded as rejected, as a REST
|
|
389
|
+
vendor's `applicationOutcome.credentialRefusedErrorCodes` does. Never list a code for a resource the token may not reach
|
|
390
|
+
or a missing scope: that credential still works. A vendor that refuses a bad token with an HTTP 401 (GitHub) lists none:
|
|
391
|
+
the engine reads a 401 itself. A 401 to a credential that IS the stored value (an API key in a header or the query, a
|
|
392
|
+
pasted token) records it as rejected; a 401 to an OAuth2 access token records nothing, because renewal decides (a grant
|
|
393
|
+
the vendor refuses to renew is retired there); a 403 never moves the credential.
|
|
394
|
+
A vendor that refuses a WRITE in its payload rather than in `errors` (Shopify's `userErrors`, Linear's `success`) is
|
|
395
|
+
declared on the mutation as `graphql.payloadRefusal`: `{ kind: ProviderGraphqlPayloadRefusalKind.USER_ERRORS, path:
|
|
396
|
+
'productCreate.userErrors', messagePath: 'message', fieldPath: 'field' }` or `{ kind:
|
|
397
|
+
ProviderGraphqlPayloadRefusalKind.SUCCESS_FLAG, path: 'issueCreate.success' }`, paths from `data`. A non-empty list or a
|
|
398
|
+
`false` flag then FAILS the call with the vendor's messages instead of returning a refused write as a result; only a
|
|
399
|
+
mutation may declare it.
|
|
400
|
+
The catalogue load, the
|
|
401
|
+
augmentation merge and `wildo registry publish` refuse a document that disagrees with its declaration. The OpenAPI
|
|
402
|
+
conformance check skips a GraphQL operation; instead, a module declaring one must pin the vendor's published schema in
|
|
403
|
+
`wildo.module.json` under `provider.graphqlSchema`: `url`, a URL that does not move (for GitHub, its docs
|
|
404
|
+
repository's `src/graphql/data/fpt/schema.docs.graphql` at a commit), and `revision`, `sha256:<hex>` of that
|
|
405
|
+
document's bytes (`shasum -a 256`). The document is SDL or an introspection result as JSON. Publish validates every
|
|
406
|
+
GraphQL document against it and refuses a field, an argument or a variable type the vendor's schema does not have,
|
|
407
|
+
naming the operation; it also refuses a module with GraphQL operations and no pin, a pin with no GraphQL operation,
|
|
408
|
+
and a document whose bytes no longer match `revision`. The contract is in the `provider-operation-calls` skill's
|
|
409
|
+
`references/framework-rest-operation-contract-api.md`.
|
|
410
|
+
|
|
342
411
|
### What a provider module tells you about vendors and engine refs
|
|
343
412
|
|
|
344
413
|
Two things in a provider module are easy to misread:
|
|
@@ -380,6 +449,143 @@ refused for a missing scope then offers a re-authorization that asks for that
|
|
|
380
449
|
scope only, and the stored grant keeps what was granted before. Read
|
|
381
450
|
`references/framework-provider-incremental-consent-api.md`.
|
|
382
451
|
|
|
452
|
+
### A connected-account provider: declare how the client authenticates to the token endpoint
|
|
453
|
+
|
|
454
|
+
The code exchange, every refresh and the revocation all send the application's client id and
|
|
455
|
+
secret to the vendor. By default they go in a form-encoded body (`client_secret_post`). Read the
|
|
456
|
+
vendor's token-endpoint documentation (or its discovery document's
|
|
457
|
+
`token_endpoint_auth_methods_supported`) and, when it shows an `Authorization: Basic` header,
|
|
458
|
+
declare it on the `oauth2` block:
|
|
459
|
+
|
|
460
|
+
- `tokenEndpointAuthMethod: ProviderOAuth2ClientAuthenticationMethod.CLIENT_SECRET_BASIC` — the
|
|
461
|
+
framework sends `Basic base64(id:secret)` (each half form-urlencoded first, as RFC 6749 asks) and
|
|
462
|
+
puts neither value in the body. It applies to the exchange, the refresh and the revocation alike.
|
|
463
|
+
- `tokenRequestBodyEncoding: ProviderOAuth2RequestBodyEncoding.JSON` — for a vendor whose token
|
|
464
|
+
endpoint takes a JSON body (Notion). Absent means a form body.
|
|
465
|
+
- `revocationRequestBodyEncoding: ProviderOAuth2RequestBodyEncoding.JSON` — the same choice for the
|
|
466
|
+
revocation request, declared separately because a vendor can differ there (Intuit: form token
|
|
467
|
+
request, JSON revocation).
|
|
468
|
+
|
|
469
|
+
Both enums come from `@wildo-ai/external-connectors-models`; their definitions are in
|
|
470
|
+
`references/framework-provider-incremental-consent-api.md` beside the other `oauth2` vocabularies.
|
|
471
|
+
Declaring nothing keeps the default bytes, so declare only what the vendor documents; a wrong guess
|
|
472
|
+
surfaces as the vendor refusing the connect with `invalid_client`.
|
|
473
|
+
|
|
474
|
+
Two more `oauth2` declarations, each only when the vendor documents it:
|
|
475
|
+
|
|
476
|
+
- `codeExchangeParameters` — fixed extra parameters of the AUTHORIZATION-CODE exchange, never the
|
|
477
|
+
refresh: Shopify's `{ expiring: '1' }`, which asks for an expiring token with a refresh token. A name
|
|
478
|
+
the framework writes itself (`grant_type`, `code`, `redirect_uri`, `code_verifier`, the client's
|
|
479
|
+
credentials, `refresh_token`, `scope`) is refused at startup.
|
|
480
|
+
- `refreshRefusals` — the refresh refusals the vendor documents as a dead refresh token, beside
|
|
481
|
+
`invalid_grant`: `[{ error: 'invalid_request', errorDescription: 'This request requires an active
|
|
482
|
+
refresh_token' }]` for Shopify. A refresh refused that way retires the connection instead of being
|
|
483
|
+
retried. Give `errorDescription` whenever the code is a generic one, so a malformed request is not
|
|
484
|
+
read as a dead grant; `invalid_client` is refused (it names the application's registration).
|
|
485
|
+
|
|
486
|
+
### The application's own account of a connected-account provider: a client-credentials grant
|
|
487
|
+
|
|
488
|
+
A pasted access token in the `apiKey` slot is right for a vendor whose keys last (an API token).
|
|
489
|
+
It is wrong when the vendor's tokens expire within hours: the application's own connection stops
|
|
490
|
+
working the same day. When the vendor offers a server-to-server grant, declare `clientCredentials`
|
|
491
|
+
on the REST contract BESIDE `oauth2`. The framework then mints the APPLICATION's token from it,
|
|
492
|
+
caches it until a minute before it expires and mints anew, while people and organizations keep
|
|
493
|
+
connecting through the exchange. Admit the `APPLICATION × SERVICE` connection, and keep
|
|
494
|
+
`apiKey.secretRef` on the exchanged token's slot (startup refuses the client secret's slot there).
|
|
495
|
+
|
|
496
|
+
- `tokenUrl` / `tokenHosts` — the https token endpoint and the hosts it may be on; the client
|
|
497
|
+
secret is sent nowhere else. When the token endpoint is on the deployment's OWN vendor instance
|
|
498
|
+
(Okta's org, `https://<org>/oauth2/v1/token`), write `tokenUrl: '{deploymentOrigin}/oauth2/v1/token'`
|
|
499
|
+
(`PROVIDER_CLIENT_CREDENTIALS_DEPLOYMENT_ORIGIN_PLACEHOLDER`) and `tokenHosts: []`: the framework fills it
|
|
500
|
+
with the origin of the base URL your contract's `baseUrlHostEnvVarName` (or `baseUrlEnvVarName`) names,
|
|
501
|
+
the same host your operations go to. Admitted for the application's own connection only.
|
|
502
|
+
- `clientIdSecretRef` / `clientSecretSecretRef` — the slots of the vendor's SERVER app, which is
|
|
503
|
+
usually a separate app from the OAuth one (Box's Server Authentication app, Zoom's
|
|
504
|
+
Server-to-Server OAuth app). Declare them in the secrets contract with
|
|
505
|
+
`scope: ExternalProvider_SecretScope.REGISTRATION`.
|
|
506
|
+
- `scope` — only when the vendor takes one; omitted, none is sent.
|
|
507
|
+
- `grantType` — `ProviderClientCredentialsGrantType.ACCOUNT_CREDENTIALS` for Zoom; omitted,
|
|
508
|
+
`client_credentials`.
|
|
509
|
+
- `tokenEndpointAuthMethod` — `CLIENT_SECRET_BASIC` when the vendor documents the Basic header;
|
|
510
|
+
omitted, the id and secret go in the body.
|
|
511
|
+
- `privateKeyJwt` — INSTEAD of `clientSecretSecretRef`, when the vendor authenticates the client
|
|
512
|
+
with a key (`private_key_jwt`: Okta service apps, certificate credentials): `privateKeySecretRef`
|
|
513
|
+
(an unencrypted PEM, PKCS#8 or RSA PKCS#1 / EC; literal `\n` is read as a newline), `algorithm`
|
|
514
|
+
(`ProviderClientAssertionSigningAlgorithm.ES256` or `RS256`, matching the key), optional
|
|
515
|
+
`keyIdSecretRef` (sent as `kid`) and `assertionLifetimeSeconds` (default 300, at most 3600). The
|
|
516
|
+
framework signs a fresh assertion per token request (`iss` = `sub` = the client id, `aud` = the
|
|
517
|
+
token URL, a new `jti`) and sends no secret.
|
|
518
|
+
- `tokenRequestParameters` — further parameters the vendor requires, each a fixed `value` or a slot
|
|
519
|
+
(`secretRef`): Box's `box_subject_type: { value: 'enterprise' }` and
|
|
520
|
+
`box_subject_id: { secretRef: 'BOX_ENTERPRISE_ID' }`, Zoom's `account_id`. The grant's own
|
|
521
|
+
parameters (`grant_type`, `client_id`, `client_secret`, `scope`) are refused here.
|
|
522
|
+
|
|
523
|
+
Alone (no `oauth2`), `clientCredentials` serves every connection, an organization typing its own
|
|
524
|
+
client id and secret (a Teams bot), and `apiKey.secretRef` IS the client secret's slot. The
|
|
525
|
+
contract's definitions (`ProviderRestClientCredentials` and its vocabularies) are in the
|
|
526
|
+
`provider-operation-calls` skill's `references/framework-rest-operation-contract-api.md`.
|
|
527
|
+
|
|
528
|
+
### The application's own account of a vendor whose host is per customer
|
|
529
|
+
|
|
530
|
+
A base URL such as `https://{subdomain}.zendesk.com` is filled from the answer a person gave when
|
|
531
|
+
connecting, admitted against `baseUrlHostAllowances`. The application's own account has no
|
|
532
|
+
connection and answers nothing, so every call it makes (a subject erasure's included) is refused.
|
|
533
|
+
Declare what it answers instead, read from the deployment:
|
|
534
|
+
|
|
535
|
+
```ts
|
|
536
|
+
applicationConnectionAnswers: { subdomain: 'ZENDESK_SUBDOMAIN' },
|
|
537
|
+
```
|
|
538
|
+
|
|
539
|
+
The key is the answer's name: a placeholder of the base URL, or the `answer` a
|
|
540
|
+
`DERIVED_FROM_CONNECTION_ANSWER` allowance follows (Intercom's `appHost`, whose API host follows the
|
|
541
|
+
region). The value is the env var of a secrets-contract slot declared with
|
|
542
|
+
`scope: ExternalProvider_SecretScope.REGISTRATION` and `holdsDeploymentHost: true`; anything else
|
|
543
|
+
is refused without being read. The deployment's answer goes through the SAME allowance a person's
|
|
544
|
+
does, so it reaches no host a person could not connect to. Unset, the call is refused naming the
|
|
545
|
+
variable (or takes a derived allowance's `whenUnanswered` host). Admit the
|
|
546
|
+
`APPLICATION × SERVICE` connection.
|
|
547
|
+
|
|
548
|
+
### A connected account addressed by a fact its vendor reports
|
|
549
|
+
|
|
550
|
+
Some vendors address every path to the account the person connected: QuickBooks' `/v3/company/{realmId}/…`.
|
|
551
|
+
Never make that an operation input. Declare the fact under `oauth2.reportedAccountFacts` with a
|
|
552
|
+
`pathSegmentPattern` (the shape the whole value must have, anchored for you), and name it on the PATH
|
|
553
|
+
parameter with `connectionFact` (the second line, in `operations.ts`); the operation's `inputSchema` must not
|
|
554
|
+
declare it:
|
|
555
|
+
|
|
556
|
+
```ts
|
|
557
|
+
reportedAccountFacts: {
|
|
558
|
+
realmId: { responsePath: 'realmId', source: ProviderOAuth2ReportedFactSource.AUTHORIZATION_REDIRECT_QUERY, pathSegmentPattern: '\\d+' },
|
|
559
|
+
},
|
|
560
|
+
{ name: 'realmId', in: ProviderRestParameterLocation.PATH, required: true, connectionFact: 'realmId' },
|
|
561
|
+
```
|
|
562
|
+
|
|
563
|
+
`source` says where the vendor puts it: the token answer (the default), its ID token's claims, or the query of the
|
|
564
|
+
authorization redirect (Intuit's `realmId`). The connect is refused when the fact is missing or outside the pattern,
|
|
565
|
+
every call re-admits the stored value, and a caller value under that name is refused. A redirect value crosses the
|
|
566
|
+
person's browser, so it is admitted only as a path value of a vendor that checks it against the token; it may never be
|
|
567
|
+
an `origin`, fill a host, or route deliveries. A token-answer fact may instead fill a base URL host placeholder with
|
|
568
|
+
`fillsBaseUrlHost: true`, admitted against the `baseUrlHostAllowances` entry of the same name, as a typed host is.
|
|
569
|
+
Undeclared, a reported fact fills nothing.
|
|
570
|
+
|
|
571
|
+
When the vendor names the account only at its USERINFO endpoint (DocuSign's `accounts[].account_id` and
|
|
572
|
+
`base_uri`), declare `oauth2.userInfoUrl` and read the facts with `source: ProviderOAuth2ReportedFactSource.USERINFO_RESPONSE`.
|
|
573
|
+
The engine calls it once, with the token the person just granted, when they connect; never at a refresh. It may carry
|
|
574
|
+
only the host placeholders the token endpoint carries. A `responsePath` step may pick ONE array element by a stated
|
|
575
|
+
condition, so two facts come from the same element:
|
|
576
|
+
|
|
577
|
+
```ts
|
|
578
|
+
userInfoUrl: 'https://{accountServerHost}/oauth/userinfo',
|
|
579
|
+
reportedAccountFacts: {
|
|
580
|
+
accountId: { responsePath: 'accounts[is_default=true].account_id', source: ProviderOAuth2ReportedFactSource.USERINFO_RESPONSE, pathSegmentPattern: '[0-9A-Fa-f-]{36}' },
|
|
581
|
+
baseUri: { responsePath: 'accounts[is_default=true].base_uri', source: ProviderOAuth2ReportedFactSource.USERINFO_RESPONSE, fillsBaseUrlHost: true },
|
|
582
|
+
},
|
|
583
|
+
```
|
|
584
|
+
|
|
585
|
+
An answer where zero or several elements meet the condition refuses the connect
|
|
586
|
+
(`REPORTED_FACT_SELECTION_NOT_SINGLE`); a `fillsBaseUrlHost` fact missing from the answer refuses it too, since every
|
|
587
|
+
call goes there.
|
|
588
|
+
|
|
383
589
|
### A connected-account provider: the revocation endpoint is used on every teardown
|
|
384
590
|
|
|
385
591
|
A provider whose REST contract carries `oauth2` lets people and tenants connect their own accounts.
|
|
@@ -393,13 +599,15 @@ erasure also reports it in the erasure receipt's external effects.
|
|
|
393
599
|
|
|
394
600
|
What that means for the provider author:
|
|
395
601
|
|
|
396
|
-
- Declare the URL only if the endpoint is really RFC 7009-shaped (
|
|
397
|
-
success). A Web-API revocation method (Slack's `auth.revoke`) or a
|
|
398
|
-
leave the field absent and every teardown honestly records `not_declared`.
|
|
602
|
+
- Declare the URL only if the endpoint is really RFC 7009-shaped (a `token` parameter, 200 on
|
|
603
|
+
success). A Web-API revocation method (Slack's `auth.revoke`) or a `DELETE` (GitHub's) is not;
|
|
604
|
+
leave the field absent and every teardown honestly records `not_declared`. A vendor that takes
|
|
605
|
+
`token` as a JSON body (Intuit, Notion) still qualifies: declare
|
|
606
|
+
`revocationRequestBodyEncoding: ProviderOAuth2RequestBodyEncoding.JSON` beside the URL.
|
|
399
607
|
- The call uses the application's own client registration (`clientIdSecretRef` /
|
|
400
|
-
`clientSecretSecretRef`)
|
|
401
|
-
|
|
402
|
-
hosts connected accounts.
|
|
608
|
+
`clientSecretSecretRef`), authenticated exactly as at the token endpoint (the client-authentication section above). If those
|
|
609
|
+
secrets are unset, the outcome is `not_configured`, and on an erasure the person's grant stays
|
|
610
|
+
live at the vendor — so set them in every environment that hosts connected accounts.
|
|
403
611
|
- Nothing ever retries a revocation: the token exists only in the destroyed row. The recorded
|
|
404
612
|
outcome is the whole record.
|
|
405
613
|
|
|
@@ -434,7 +642,7 @@ Read `references/framework-provider-file-storage-adapter-api.md`.
|
|
|
434
642
|
|
|
435
643
|
### Receiving your vendor's requests: an endpoint the engine verifies
|
|
436
644
|
|
|
437
|
-
Name an engine scheme (`SVIX_V1`, `SLACK_V0`, `BOT_FRAMEWORK_JWT`) on a `WEBHOOK_ORIGINATOR` endpoint and the engine
|
|
645
|
+
Name an engine scheme (`SVIX_V1`, `SLACK_V0`, `BOT_FRAMEWORK_JWT`, `ED25519`, `BASIC_CREDENTIAL`, `MAILGUN_FORWARD_JSON`) on a `WEBHOOK_ORIGINATOR` endpoint and the engine
|
|
438
646
|
verifies every request; the endpoint adds pure `identifyEvent` / `answerHandshake` / `acknowledge` functions and its
|
|
439
647
|
`contentTypes`, and an inbound handler serves it. Read `references/framework-provider-inbound-endpoint-api.md`.
|
|
440
648
|
|
|
@@ -451,6 +659,25 @@ those references, the effect is not registered and erasure reports your vendor N
|
|
|
451
659
|
when the operator declared the vendor's own deletion window instead), with a boot warning saying why. It runs for
|
|
452
660
|
`eraseSubjectAsSystem` only. Read `references/framework-provider-subject-erasure-effect-api.md`.
|
|
453
661
|
|
|
662
|
+
### Checking a setting only your vendor can judge: a configuration check
|
|
663
|
+
|
|
664
|
+
When a setting can be well-formed and still wrong (an account id that must be the one the API key belongs to, a
|
|
665
|
+
workspace that must be the one the bot token is installed in), ship `configurationCheck` on the backend module: an
|
|
666
|
+
async function of your declared secrets (`readSecret`) and your own READ operations on the application's connection
|
|
667
|
+
(`execute`), answering one sentence per problem. The backend runs it once at boot in the background and logs each
|
|
668
|
+
sentence as a WARN; `wildo local doctor` runs it against the local environment and prints a WARN line. It never stops
|
|
669
|
+
anything: a check that throws or overruns is reported as "could not be run". Read
|
|
670
|
+
`references/framework-provider-configuration-check-api.md`.
|
|
671
|
+
|
|
672
|
+
### Reporting what your provider can say about its own state: a compliance-state collector
|
|
673
|
+
|
|
674
|
+
When your provider holds state an auditor would ask about (which account the application uses at your vendor, whether
|
|
675
|
+
it is the vendor's built-in administrator, how your client trusts the server), ship `complianceStateCollectorFactory` on
|
|
676
|
+
the backend module. It receives your resolved secrets and where each came from (platform-minted or operator-authored),
|
|
677
|
+
and returns facts: vocabulary members and booleans, never a value and never a verdict. The application's assurance
|
|
678
|
+
cycle reads every declared provider through one evidence door and records the snapshot; a provider declared but not
|
|
679
|
+
configured is recorded as absent, never guessed. Read `references/framework-provider-compliance-state-collector-api.md`.
|
|
680
|
+
|
|
454
681
|
### What the engine records for each call your capability provider makes
|
|
455
682
|
|
|
456
683
|
An email, SMS, billing or storage provider is called by the engine's own egress, never by
|
|
@@ -543,7 +770,12 @@ providers: defineSaaSProviders({
|
|
|
543
770
|
- `references/framework-provider-subject-erasure-effect-api.md` — reaching
|
|
544
771
|
your vendor when a person is erased: the effect contract, what the
|
|
545
772
|
application declares, how the outcome is decided (source-backed)
|
|
773
|
+
- `references/framework-provider-configuration-check-api.md` — checking a setting only your vendor can judge: the
|
|
774
|
+
`configurationCheck` contract, where it runs (backend boot, `wildo local doctor`) and why it never refuses (source-backed)
|
|
775
|
+
- `references/framework-provider-compliance-state-collector-api.md` — reporting what your provider can say about its own state:
|
|
776
|
+
the `complianceStateCollectorFactory` contract, the facts vocabulary, and why a value can never reach the evidence (source-backed)
|
|
546
777
|
- `references/framework-provider-inbound-endpoint-api.md` — receiving your vendor's requests: engine-verified schemes, handshake, event naming, synchronous answer (source-backed)
|
|
778
|
+
- `references/framework-provider-processing-region-api.md` — declaring how each processing region is reached (its own endpoint, or the operator's account), what an application's region choice then does to every arm, and when it is refused (source-backed)
|
|
547
779
|
|
|
548
780
|
## Verification
|
|
549
781
|
|
|
@@ -558,6 +790,9 @@ providers: defineSaaSProviders({
|
|
|
558
790
|
- [ ] The process starts and its provider count includes the new ref.
|
|
559
791
|
- [ ] An augmentation is named under `providers.augmentations.<baseRef>`
|
|
560
792
|
and appears in the host's artifact under `providerRuntimeAugmentations`.
|
|
793
|
+
- [ ] A setting that can be well-formed and wrong is checked by the module's
|
|
794
|
+
`configurationCheck`, and `wildo local doctor` shows its
|
|
795
|
+
`provider configuration (<ref>)` line.
|
|
561
796
|
|
|
562
797
|
### Grep invariants
|
|
563
798
|
|
|
@@ -584,6 +819,10 @@ rg -n "acme" backend-api/src/provider-contributions.ts
|
|
|
584
819
|
# an erasure stance that reaches the vendor has the effect that does it, and the application said where the ids are
|
|
585
820
|
rg -n "EXTERNAL_ERASURE_OPERATION|subjectErasureEffect" providers/acme/backend/src
|
|
586
821
|
rg -n "subjectReferences" wildo.saas.config.ts
|
|
822
|
+
|
|
823
|
+
# a setting only the vendor can judge is checked by the module, and doctor runs it
|
|
824
|
+
rg -n "configurationCheck" providers/acme/backend/src
|
|
825
|
+
wildo local doctor
|
|
587
826
|
```
|
|
588
827
|
|
|
589
828
|
The last one should find NOTHING for a package provider. A package is
|
|
@@ -603,6 +842,7 @@ disagree with the package.
|
|
|
603
842
|
| "The engine already has this vendor, so I will publish our own provider with the same ref." | Composition refuses two owners of one ref. Ship an augmentation of the engine's ref and have the application opt it in under `providers.augmentations`; it adds operations and leaves the vendor's identity, credential and connection with its owner. |
|
|
604
843
|
| "The augmentation is installed, so its operations are available." | Nothing applies until `providers.augmentations.<baseRef>` names the package and `wildo config sync` records it; the artifact grep below shows whether it did. |
|
|
605
844
|
| "I declared `EXTERNAL_ERASURE_OPERATION`, so an erasure reaches the vendor." | Only with a `subjectErasureEffect` on the module AND the application's `subjectReferences`. Without the effect the stance promises a door nobody built; without the references the engine has nothing to erase by. Either way every erasure reads NOT_REGISTERED, unless the operator declared the vendor's own deletion window as the answer instead. |
|
|
845
|
+
| "I will document the setting and ask the application to call my validation function at boot." | Nothing calls a function an application was asked to call. Declare it as `configurationCheck`: the backend runs it at boot and `wildo local doctor` runs it, both as a WARN, with no application code. |
|
|
606
846
|
| "I will override the provider's `runtimeContract.baseUrl` in `providerConfigurations` to reach my local double." | The configuration is refused: the module owns where its key goes. Set the host slot to `127.0.0.1:<port>` in a development environment instead; staging and production refuse it. |
|
|
607
847
|
| "Our provider also handles email, so I will give it the email arm." | Composition refuses a non-MAIN provider that declares an engine slot's runtime arm while claiming no capability for it. Declare the capability that names the slot — that is what makes it a deliberate substitution rather than an accident. |
|
|
608
848
|
|
|
@@ -630,6 +870,9 @@ disagree with the package.
|
|
|
630
870
|
- A module declaring `EXTERNAL_ERASURE_OPERATION` with no `subjectErasureEffect` —
|
|
631
871
|
catch with the erasure grep above; startup refuses the reverse (an effect on
|
|
632
872
|
any other stance).
|
|
873
|
+
- A provider skill telling the application to log a validation function
|
|
874
|
+
"once at boot": that is a `configurationCheck` the module should declare —
|
|
875
|
+
catch with the `configurationCheck` grep above.
|
|
633
876
|
- A `runtimeContract` or `endpoints` key under `providerConfigurations` —
|
|
634
877
|
catch with the re-point grep above; every configuration door refuses it.
|
|
635
878
|
- A host slot set to `127.0.0.1:<port>` in a staging or production
|
|
@@ -7,13 +7,12 @@ is yours to install in the runtime that enables it.
|
|
|
7
7
|
|
|
8
8
|
In a registry provider module (`providers/<ref>/`), the facet declares the SDK as `"*"` and the module's
|
|
9
9
|
`wildo.module.json` records its exact version once, in `dependsOn.npm.dependencies`: the version the module was
|
|
10
|
-
proven with. Installing the module writes that version into your application's `pnpm.
|
|
10
|
+
proven with. Installing the module writes that version into your application's overrides in `pnpm-workspace.yaml` (an update moves it,
|
|
11
11
|
a remove takes out what the install wrote). An SDK whose install script must run (a native addon) is also listed in
|
|
12
|
-
`dependsOn.npm.onlyBuiltDependencies`, and the install adds it to your root `
|
|
12
|
+
`dependsOn.npm.onlyBuiltDependencies`, and the install adds it to `onlyBuiltDependencies` in your root `pnpm-workspace.yaml`
|
|
13
13
|
and runs `pnpm rebuild -r <name>` after its install, which is what runs the script of a package already installed. If you
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
a `neverBuiltDependencies` list) and warns you: add the name where your list lives, then run
|
|
14
|
+
run every script but a `neverBuiltDependencies` list, the install writes nothing (pnpm refuses to install with both an
|
|
15
|
+
allow-list and a `neverBuiltDependencies` list) and warns you: take the name out of that list, then run
|
|
17
16
|
`pnpm rebuild -r <name>`, or run `pnpm approve-builds`, which does both. Publishing refuses a module whose record, facets
|
|
18
17
|
and `requiredPackages` disagree.
|
|
19
18
|
|
|
@@ -0,0 +1,96 @@
|
|
|
1
|
+
# Reporting what your provider can say about its own state: the compliance-state collector
|
|
2
|
+
|
|
3
|
+
Read this when your provider holds state an auditor would ask about and only your provider can describe: which account
|
|
4
|
+
the application uses at your vendor, whether that account is the vendor's built-in administrator, whether its password
|
|
5
|
+
is the vendor's packaged default, how your client trusts the server. The application's assurance cycle asks every
|
|
6
|
+
declared provider, records the answer in the application's assurance repository, and a demand weighs it. Your module
|
|
7
|
+
only states facts.
|
|
8
|
+
|
|
9
|
+
## What you implement
|
|
10
|
+
|
|
11
|
+
Declare `complianceStateCollectorFactory` on your backend module. The engine hands it your resolved secrets (platform-minted
|
|
12
|
+
slots first, exactly as your audit sink or capability receives them) and, per slot, where the value came from. It returns
|
|
13
|
+
a collector whose `collect()` answers a list of facts, or `undefined` to decline when the connection material is
|
|
14
|
+
incomplete.
|
|
15
|
+
|
|
16
|
+
## Import Origins
|
|
17
|
+
|
|
18
|
+
- `@wildo-ai/external-connectors-private`
|
|
19
|
+
|
|
20
|
+
## Source Excerpts
|
|
21
|
+
|
|
22
|
+
### Origin Package: `@wildo-ai/external-connectors-private`
|
|
23
|
+
|
|
24
|
+
```typescript
|
|
25
|
+
/**
|
|
26
|
+
* Resolved config the engine hands a provider's {@link BackendProviderModule.complianceStateCollectorFactory} (#298):
|
|
27
|
+
* the same secrets the audit sink builder resolves, through the same resolution (`resolveProviderSecrets`), plus where
|
|
28
|
+
* each slot's value came from. The origins are the one fact a collector cannot read off a value: an account the platform
|
|
29
|
+
* minted for this application and one an operator typed look identical as strings.
|
|
30
|
+
*
|
|
31
|
+
* A collector READS these to describe the connection; it must never copy a value into a fact. The fact schema admits
|
|
32
|
+
* vocabulary members and booleans only, and the builder refuses anything else, so a leaked value fails the snapshot
|
|
33
|
+
* rather than reaching the evidence repository.
|
|
34
|
+
*/
|
|
35
|
+
export interface ProviderComplianceStateCollectorConfig {
|
|
36
|
+
readonly secrets: Readonly<Record<string, string>>;
|
|
37
|
+
readonly secretOrigins: Readonly<Record<string, ProviderCredentialOrigin>>;
|
|
38
|
+
}
|
|
39
|
+
|
|
40
|
+
/**
|
|
41
|
+
* A provider's compliance-state collector (#298): asked once per evidence read, it returns the facts the provider can
|
|
42
|
+
* state about its own state. DETERMINISTIC, and never a judgement: what a fact means for an objective is the demand's
|
|
43
|
+
* question, judged elsewhere. It may throw, or return facts the schema refuses; the builder records either as an absence
|
|
44
|
+
* (`COLLECTION_FAILED`), never as a partial snapshot.
|
|
45
|
+
*/
|
|
46
|
+
export interface ProviderComplianceStateCollector {
|
|
47
|
+
collect(): Promise<ReadonlyArray<ProviderComplianceStateFactRecord>>;
|
|
48
|
+
}
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
A fact is `{ fact, value, source }`: `fact` a member of `ProviderComplianceStateFact` (from `@wildo-ai/saas-models`), its
|
|
52
|
+
`value` the type that member fixes (a boolean or a vocabulary member), and `source` where you read it
|
|
53
|
+
(`ProviderComplianceStateSource`). Report each fact at most once.
|
|
54
|
+
|
|
55
|
+
## What the engine guarantees, and what it refuses
|
|
56
|
+
|
|
57
|
+
| Your module | What the application's evidence records |
|
|
58
|
+
|---|---|
|
|
59
|
+
| declares no collector | the provider, ABSENT, `NO_COLLECTOR` |
|
|
60
|
+
| a required secret is not configured | ABSENT, `NOT_CONFIGURED`; your factory is never called |
|
|
61
|
+
| your factory returns `undefined` | ABSENT, `COLLECTOR_DECLINED` |
|
|
62
|
+
| `collect()` throws, or returns anything the schema refuses | ABSENT, `COLLECTION_FAILED` |
|
|
63
|
+
| `collect()` returns valid facts | CAPTURED, with your facts and the instant |
|
|
64
|
+
|
|
65
|
+
The schema admits no free string anywhere in a fact, so a value you read (a password, an account name, a host, a
|
|
66
|
+
database name) can never reach the evidence: report a COMPARISON (`PASSWORD_IS_VENDOR_PACKAGED_DEFAULT: true`), never the
|
|
67
|
+
value. A collector that tries to return one produces no snapshot at all, and the failure is logged by provider, never
|
|
68
|
+
with the value.
|
|
69
|
+
|
|
70
|
+
## How to write a collector
|
|
71
|
+
|
|
72
|
+
- State facts, never a verdict. Whether a built-in administrator account is acceptable is the demand's question; do not
|
|
73
|
+
add a "secure" or "compliant" fact.
|
|
74
|
+
- Deterministic or absent. When you cannot read something, decline or throw; never report a plausible default.
|
|
75
|
+
- Report only facts a demand reads. A new fact needs a member in `ProviderComplianceStateFact` and a demand clause that
|
|
76
|
+
reads it, in the same change.
|
|
77
|
+
- Load no SDK at module load. A collector that asks your vendor's API loads its client inside `collect()`; the module
|
|
78
|
+
stays data plus lazy factories.
|
|
79
|
+
|
|
80
|
+
## Worked shape
|
|
81
|
+
|
|
82
|
+
The engine's immudb provider reads everything off its resolved configuration and asks the server nothing:
|
|
83
|
+
|
|
84
|
+
```ts
|
|
85
|
+
complianceStateCollectorFactory: ({ secrets, secretOrigins }) => {
|
|
86
|
+
if (!secrets.user || !secrets.password) return undefined;
|
|
87
|
+
const source = ProviderComplianceStateSource.RESOLVED_CONFIGURATION;
|
|
88
|
+
return {
|
|
89
|
+
collect: async () => [
|
|
90
|
+
{ fact: ProviderComplianceStateFact.ACCOUNT_IS_VENDOR_BUILT_IN_ADMINISTRATOR, value: secrets.user === 'immudb', source },
|
|
91
|
+
{ fact: ProviderComplianceStateFact.PASSWORD_IS_VENDOR_PACKAGED_DEFAULT, value: secrets.password === 'immudb', source },
|
|
92
|
+
{ fact: ProviderComplianceStateFact.TRUST_ANCHOR_PERSISTENCE, value: secrets.stateDir ? ProviderTrustAnchorPersistence.DURABLE : ProviderTrustAnchorPersistence.EPHEMERAL, source },
|
|
93
|
+
],
|
|
94
|
+
};
|
|
95
|
+
},
|
|
96
|
+
```
|
|
@@ -0,0 +1,130 @@
|
|
|
1
|
+
# Checking how an application configured your provider: the configuration check
|
|
2
|
+
|
|
3
|
+
Read this when your provider has a setting that can be well-formed and still WRONG, and only your provider can tell:
|
|
4
|
+
an account id that must be the account the API key belongs to, a workspace that must be the one the bot token is
|
|
5
|
+
installed in, a region that must match the endpoint the key was issued for. Nothing else refuses such a value, because
|
|
6
|
+
nothing else knows what it should be.
|
|
7
|
+
|
|
8
|
+
## What you implement
|
|
9
|
+
|
|
10
|
+
Declare `configurationCheck` on your backend module: an async function answering one sentence per problem, and an
|
|
11
|
+
empty list when the configuration is right. It is given exactly two things:
|
|
12
|
+
|
|
13
|
+
- `readSecret(envVarName)`: the value of one of YOUR module's declared secret slots, or `undefined` when it has none. A
|
|
14
|
+
name your `secretsContract` does not declare always reads `undefined`.
|
|
15
|
+
- `execute(operationId, input?)`: one of YOUR provider's operations on the APPLICATION's own connection (its own
|
|
16
|
+
account, acting as itself), answering the operation's output and throwing when the call is refused or fails. Call
|
|
17
|
+
only READ operations: a check must change nothing at the vendor.
|
|
18
|
+
|
|
19
|
+
## Import Origins
|
|
20
|
+
|
|
21
|
+
- `@wildo-ai/external-connectors-private`
|
|
22
|
+
|
|
23
|
+
## Source Excerpts
|
|
24
|
+
|
|
25
|
+
### Origin Package: `@wildo-ai/external-connectors-private`
|
|
26
|
+
|
|
27
|
+
```typescript
|
|
28
|
+
/**
|
|
29
|
+
* What a provider's configuration check is given (#2711): the provider's own declared values, and its own operations on
|
|
30
|
+
* the application's own account. Nothing else: a check cannot read another provider's secrets or spend another
|
|
31
|
+
* provider's connection.
|
|
32
|
+
*/
|
|
33
|
+
export interface ProviderConfigurationCheckInput {
|
|
34
|
+
/**
|
|
35
|
+
* The value of one of THIS module's declared secret slots, by its environment variable name (`SLACK_ACCESS_TOKEN`), or
|
|
36
|
+
* `undefined` when it has no value. A name the module's `secretsContract` does not declare always reads `undefined`.
|
|
37
|
+
* The backend reads its own environment; `wildo local doctor` reads the environment's `providerEnv` (a variable set in
|
|
38
|
+
* the shell running doctor takes precedence, so `SLACK_APPLICATION_WORKSPACE_ID=T000WRONG wildo local doctor` tries a
|
|
39
|
+
* value without editing the secrets).
|
|
40
|
+
*/
|
|
41
|
+
readonly readSecret: (envVarName: string) => string | undefined;
|
|
42
|
+
/**
|
|
43
|
+
* Calls one of THIS provider's operations on the APPLICATION's own connection (the floor: its own account, acting as
|
|
44
|
+
* itself) and answers the operation's output. Throws when the call is refused or fails, exactly as an application's
|
|
45
|
+
* call would; the backend records it in the audit trail like any provider call. Call only READ operations: a check must
|
|
46
|
+
* change nothing at the vendor.
|
|
47
|
+
*/
|
|
48
|
+
readonly execute: (operationId: string, input?: Readonly<Record<string, unknown>>) => Promise<unknown>;
|
|
49
|
+
}
|
|
50
|
+
|
|
51
|
+
/**
|
|
52
|
+
* A provider's own check of how an application configured it (#2711): an async function answering one sentence per
|
|
53
|
+
* problem found, and nothing when the configuration is right (or is not set, which is not a problem the check owns).
|
|
54
|
+
*
|
|
55
|
+
* It exists for the mistakes only the provider can see: a value that is well-formed and wrong, which nothing refuses
|
|
56
|
+
* because nothing else knows what it should be. Slack's is the reference case: `SLACK_APPLICATION_WORKSPACE_ID` must
|
|
57
|
+
* name the workspace the application's own bot token is installed in, which only `auth.test` on that token answers.
|
|
58
|
+
*
|
|
59
|
+
* NEVER a refusal, and the engine guarantees it:
|
|
60
|
+
* - the application backend runs every loaded module's check ONCE at boot, in the background, and logs each sentence as a
|
|
61
|
+
* WARN naming the provider; startup neither waits for it nor fails on it;
|
|
62
|
+
* - `wildo local doctor` runs it against the local environment's values and prints a WARN line per provider with a
|
|
63
|
+
* finding (a PASS line when the check found nothing);
|
|
64
|
+
* - a check that THROWS, or does not answer within the engine's deadline, is reported as "could not be run" with the
|
|
65
|
+
* reason, never propagated.
|
|
66
|
+
*
|
|
67
|
+
* So write it to say what is wrong and how to fix it, in one sentence each, naming the setting. A comparison it could not
|
|
68
|
+
* make (the vendor call failed) is a sentence too ("could not be compared, because …"): a check that cannot run must not
|
|
69
|
+
* read as one that passed. Make at most a few READ calls; it runs on every boot.
|
|
70
|
+
*
|
|
71
|
+
* @example
|
|
72
|
+
* ```ts
|
|
73
|
+
* export const AcmeBackendProvider: BackendProviderModule = {
|
|
74
|
+
* // …
|
|
75
|
+
* configurationCheck: async ({ readSecret, execute }) => {
|
|
76
|
+
* const declared = readSecret('ACME_ACCOUNT_ID');
|
|
77
|
+
* if (declared === undefined) return [];
|
|
78
|
+
* const { accountId } = (await execute('whoami')) as { accountId?: string };
|
|
79
|
+
* return accountId === declared ? [] : [`ACME_ACCOUNT_ID is ${declared}, but ACME_API_KEY belongs to account ${accountId}.`];
|
|
80
|
+
* },
|
|
81
|
+
* };
|
|
82
|
+
* ```
|
|
83
|
+
*/
|
|
84
|
+
export type ProviderConfigurationCheck = (input: ProviderConfigurationCheckInput) => Promise<readonly string[]>;
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
## When it runs, and what the engine guarantees
|
|
88
|
+
|
|
89
|
+
| Where | When | What a finding becomes |
|
|
90
|
+
|---|---|---|
|
|
91
|
+
| The application backend | Once at boot, in the background: startup does not wait for it | A WARN log line per sentence, `[provider configuration] <ref>: <sentence>` |
|
|
92
|
+
| `wildo local doctor` | Every run, against the local environment's values | A WARN line `provider configuration (<ref>)` carrying the sentences |
|
|
93
|
+
|
|
94
|
+
Never a refusal, in either place. A check that throws, answers something other than a list of sentences, or does not
|
|
95
|
+
answer within 30 seconds is reported as "could not be run", with the reason, and nothing else is affected. A module
|
|
96
|
+
with no check gets no line at all. Minions do not run checks: the backend already asked the same question of the same
|
|
97
|
+
configuration.
|
|
98
|
+
|
|
99
|
+
`wildo local doctor` reads a variable from the shell first, then from the environment's stored secrets, so
|
|
100
|
+
`ACME_ACCOUNT_ID=A2 wildo local doctor` tries a value without changing anything. Every credential is masked out of
|
|
101
|
+
what it prints.
|
|
102
|
+
|
|
103
|
+
## How to write the sentences
|
|
104
|
+
|
|
105
|
+
- Say what is wrong and how to fix it, naming the setting and both values (a non-secret value only).
|
|
106
|
+
- A comparison you could not make is a sentence too ("could not be compared, because the call failed: …"). A check
|
|
107
|
+
that cannot run must not read as one that passed.
|
|
108
|
+
- Return nothing when the setting is not set and that is a legitimate configuration: the check is about values that are
|
|
109
|
+
wrong, not about values that are optional.
|
|
110
|
+
- Keep it to a few calls: it runs on every boot.
|
|
111
|
+
|
|
112
|
+
## Worked shape
|
|
113
|
+
|
|
114
|
+
The registry Slack provider's check: `SLACK_APPLICATION_WORKSPACE_ID` must name the workspace `SLACK_ACCESS_TOKEN` is
|
|
115
|
+
installed in, which only `auth.test` on that token answers.
|
|
116
|
+
|
|
117
|
+
```ts
|
|
118
|
+
configurationCheck: async ({ readSecret, execute }) => {
|
|
119
|
+
const declared = readSecret('SLACK_APPLICATION_WORKSPACE_ID')?.trim() ?? '';
|
|
120
|
+
if (declared === '') return [];
|
|
121
|
+
if (!/^T[A-Z0-9]{2,31}$/.test(declared)) return [`SLACK_APPLICATION_WORKSPACE_ID is "${declared}", which is not a Slack workspace id (T…).`];
|
|
122
|
+
if (readSecret('SLACK_ACCESS_TOKEN') === undefined) return [`SLACK_APPLICATION_WORKSPACE_ID is ${declared}, and SLACK_ACCESS_TOKEN has no value to compare it with.`];
|
|
123
|
+
try {
|
|
124
|
+
const { team_id } = (await execute('auth.test', {})) as { team_id?: string };
|
|
125
|
+
return team_id === declared ? [] : [`SLACK_APPLICATION_WORKSPACE_ID is ${declared}, but SLACK_ACCESS_TOKEN is installed in ${team_id}. Set it to ${team_id}.`];
|
|
126
|
+
} catch (error) {
|
|
127
|
+
return [`SLACK_APPLICATION_WORKSPACE_ID could not be compared: auth.test failed (${error instanceof Error ? error.message : String(error)}).`];
|
|
128
|
+
}
|
|
129
|
+
},
|
|
130
|
+
```
|
|
@@ -84,6 +84,12 @@ export enum ProviderFileStorageFailureKind {
|
|
|
84
84
|
INVALID_REFERENCE = 'INVALID_REFERENCE',
|
|
85
85
|
/** The vendor failed or could not be reached. */
|
|
86
86
|
VENDOR_FAILURE = 'VENDOR_FAILURE',
|
|
87
|
+
/**
|
|
88
|
+
* The vendor's hash of the stored file differs from the hash of the bytes the adapter sent (#2965). The adapter removes
|
|
89
|
+
* its copy at the vendor before throwing and says in the message whether that worked: a mismatched copy is the
|
|
90
|
+
* adapter's own upload, never the owner's document. The engine refuses it as `FileIntegrityErrorCode.CONTENT_CHECKSUM_MISMATCH`.
|
|
91
|
+
*/
|
|
92
|
+
CONTENT_CHECKSUM_MISMATCH = 'CONTENT_CHECKSUM_MISMATCH',
|
|
87
93
|
}
|
|
88
94
|
|
|
89
95
|
/**
|
|
@@ -139,7 +145,8 @@ export interface ProviderFileStorageUploadRequest {
|
|
|
139
145
|
readonly body: AsyncIterable<Uint8Array>;
|
|
140
146
|
/**
|
|
141
147
|
* SHA-256 of `body`, lowercase hex, when the engine computed it before uploading (#2900). An adapter whose vendor
|
|
142
|
-
* reports a hash of the stored bytes
|
|
148
|
+
* reports a hash of the stored bytes compares it (the hash itself, or a vendor hash of the bytes it hashed and sent)
|
|
149
|
+
* and throws `CONTENT_CHECKSUM_MISMATCH` on a mismatch, as the engine's `ONEDRIVE` adapter does (#2965). The engine
|
|
143
150
|
* checks the bytes it streamed to the adapter against this hash either way.
|
|
144
151
|
*/
|
|
145
152
|
readonly contentSha256?: string;
|