@wildo-ai/framework-knowledge 1.1.2 → 1.1.3
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/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +228 -6
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
- 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 -4
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -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 +4 -4
- 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 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
- 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 +0 -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 +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
- 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 +1 -2
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -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 +3 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
- 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 +1 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -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 +0 -1
- 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 +0 -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 +0 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
- 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 +0 -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 +0 -2
- 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 +2 -2
- 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 +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
- 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 +9 -4
- 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 +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -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 +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/manifest.json +8 -9
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
- package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
- package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
- package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
- package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +0 -51
- package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
- package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
- package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
- package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
- package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
- package/dist/knowledge/registries/framework-topics.json +11 -146
- package/dist/knowledge/registries/playbooks.json +18 -154
- package/dist/knowledge/registries/source-tags.json +630 -883
- package/dist/knowledge/skills/INDEX.md +3 -4
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
- package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
- package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
- package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
- package/dist/knowledge/topic-index.json +220 -725
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
- package/dist/knowledge/references/placement-plan.config.md +0 -330
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
- package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
- package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
- package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
- /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md
CHANGED
|
@@ -16,7 +16,7 @@ Source-backed display and edit mode contracts for form chrome.
|
|
|
16
16
|
*
|
|
17
17
|
* These values are not the persisted resource semantics themselves. They are
|
|
18
18
|
* consumed by the frontend resource UI behavior layer, typically in
|
|
19
|
-
* files like `
|
|
19
|
+
* files like `app/src/modules/<module>/resources/<resource>/<resource>.ui-behavior.tsx`, where the AI
|
|
20
20
|
* calls decorators like `.stringUI()`, `.enumUI()`, `.booleanUI()`, etc. on the
|
|
21
21
|
* schema shape exposed to `resourceUIBehavior(...)`.
|
|
22
22
|
*
|
|
@@ -82,12 +82,6 @@ export const StringDisplayMode = {
|
|
|
82
82
|
* `TEXTAREA` — the edit side stays markdown SOURCE either way.
|
|
83
83
|
*/
|
|
84
84
|
MARKDOWN: 'markdown',
|
|
85
|
-
/**
|
|
86
|
-
* A MACHINE IDENTIFIER — a slug, a ref, an addressable key (`success-criterion-…`). Rendered
|
|
87
|
-
* small, muted and monospace so it stays greppable and verbatim while RECEDING behind the prose
|
|
88
|
-
* it identifies. Use for values a reader needs to copy or trace, never to read as content.
|
|
89
|
-
*/
|
|
90
|
-
IDENTIFIER: 'identifier',
|
|
91
85
|
COLOR: 'color',
|
|
92
86
|
LINK: 'link',
|
|
93
87
|
EMAIL: 'email',
|
|
@@ -206,106 +206,6 @@ export enum ActionPlacement {
|
|
|
206
206
|
DANGER_ZONE = 'danger_zone',
|
|
207
207
|
}
|
|
208
208
|
|
|
209
|
-
/**
|
|
210
|
-
* HOW an operation's action collects its input and shows its result — the chrome the user meets
|
|
211
|
-
* when they click the button.
|
|
212
|
-
*
|
|
213
|
-
* ## Why this axis exists
|
|
214
|
-
*
|
|
215
|
-
* Until this axis, one rule decided the answer for every custom operation:
|
|
216
|
-
* *has a `requestDto` ⇒ navigate*. So an action asking for a single reason string got the same
|
|
217
|
-
* full-page treatment as a multi-step wizard, and the only way out was to author
|
|
218
|
-
* `navigationOverrides` — per operation, in terms of a zone, a transition verb and an appearance.
|
|
219
|
-
* Three concepts to answer one question.
|
|
220
|
-
*
|
|
221
|
-
* This is that one question. It is a **display-only** axis: backend authorization is untouched and
|
|
222
|
-
* `roles` remain the only security authority, exactly like its siblings {@link ActionVisibility},
|
|
223
|
-
* {@link ActionPlacement} and {@link ResourceOperationActionScope}.
|
|
224
|
-
*
|
|
225
|
-
* ## It is an ALIAS, not a parallel mechanism
|
|
226
|
-
*
|
|
227
|
-
* `MODAL` and `PAGE` do not render anything themselves — they resolve to the navigation transitions
|
|
228
|
-
* that already exist (`OVERLAY`, and the ordinary chain), so there is one runtime mechanism and one
|
|
229
|
-
* set of zone/appearance/URL semantics. `DIRECT`, `POPOVER` and `INLINE` never enter navigation at
|
|
230
|
-
* all, because none of them is a destination: nothing is pushed, no zone changes, and there is
|
|
231
|
-
* nothing for a back button to pop. `INLINE` is hosted by the collection the element belongs to —
|
|
232
|
-
* see `InPlaceOperationContext` for why that is not the navigation layer's job.
|
|
233
|
-
*
|
|
234
|
-
* Consequently an explicit `navigationOverrides` entry still WINS over a presentation authored here
|
|
235
|
-
* (it is the more specific instrument, and it is checked first in the resolution chain). Author this
|
|
236
|
-
* axis to say what KIND of chrome the action wants; author `navigationOverrides` when you need to
|
|
237
|
-
* name the zone, the appearance or the viewport yourself.
|
|
238
|
-
*
|
|
239
|
-
* ## When omitted
|
|
240
|
-
*
|
|
241
|
-
* It is DERIVED from the operation — see `resolveResourceOperationActionPresentation()`. An
|
|
242
|
-
* operation that asks for nothing executes directly; a small field set opens a modal; input the
|
|
243
|
-
* framework cannot fit in an overlay (files, nested writes, a large field set) keeps the page it
|
|
244
|
-
* has always had. An operation whose `surface` is `ADDRESSABLE` always keeps its page: the author
|
|
245
|
-
* has already said it is a deep-linkable destination.
|
|
246
|
-
*/
|
|
247
|
-
export enum ResourceOperationActionPresentation {
|
|
248
|
-
/**
|
|
249
|
-
* Execute on click, with no form at all — the confirmation dialog for a risky operation is the
|
|
250
|
-
* only thing between the click and the request.
|
|
251
|
-
*
|
|
252
|
-
* Only meaningful for an operation that needs no caller input. Declaring it on an operation that
|
|
253
|
-
* DOES have required request fields would send an empty body, so the resolver refuses to derive it
|
|
254
|
-
* there and an author who declares it anyway gets the operation's fields dropped — check
|
|
255
|
-
* `requestDto` before reaching for this.
|
|
256
|
-
*/
|
|
257
|
-
DIRECT = 'direct',
|
|
258
|
-
/**
|
|
259
|
-
* A small form anchored to the button that opened it, dismissed by clicking away.
|
|
260
|
-
*
|
|
261
|
-
* The single-input idiom ("assign to…", "snooze until…"). Transient by construction: no URL, no
|
|
262
|
-
* history entry, nothing to deep-link. Use it when the surrounding context is the point — the user
|
|
263
|
-
* is reading the row they are acting on and must not lose sight of it.
|
|
264
|
-
*/
|
|
265
|
-
POPOVER = 'popover',
|
|
266
|
-
/**
|
|
267
|
-
* The element being acted on transforms in place to collect the input, leaving its neighbours
|
|
268
|
-
* visible — the row becomes the form rather than being covered by one.
|
|
269
|
-
*
|
|
270
|
-
* Use it when the surrounding rows are the point: the user is comparing, and an overlay would hide
|
|
271
|
-
* the very thing that made them act on this row.
|
|
272
|
-
*
|
|
273
|
-
* **Transient, like {@link POPOVER}, and for the same reason.** Nothing is pushed, no URL changes,
|
|
274
|
-
* and a reload returns the list to rest. An inline row-edit is a momentary state of a listing, not
|
|
275
|
-
* a place — which is also why no admin framework deep-links one, and why anything that SHOULD be
|
|
276
|
-
* linkable, reloadable or reachable by a back button wants {@link PAGE}.
|
|
277
|
-
*
|
|
278
|
-
* **It requires a collection.** The host is provided by the list the element belongs to
|
|
279
|
-
* (`InPlaceOperationProvider`); the same action rendered on a detail page, in a danger zone or in a
|
|
280
|
-
* picker has no row to transform and degrades to an overlay rather than becoming a dead button.
|
|
281
|
-
*
|
|
282
|
-
* Note it does NOT resolve to `NavigationTransition.INPLACE`. Element-level hosting uses none of
|
|
283
|
-
* what the navigation layer offers — no zone, no stack entry, no appearance — and routing it there
|
|
284
|
-
* is exactly why that transition has never done what its own docstring promises. See
|
|
285
|
-
* `InPlaceOperationContext`.
|
|
286
|
-
*/
|
|
287
|
-
INLINE = 'inline',
|
|
288
|
-
/**
|
|
289
|
-
* An overlay above the layout — the workhorse for "a handful of fields", and the default the
|
|
290
|
-
* derivation reaches for.
|
|
291
|
-
*
|
|
292
|
-
* Resolves to {@link NavigationTransition.OVERLAY}. The concrete appearance (dialog / sheet /
|
|
293
|
-
* drawer / panel) stays the app's decision, resolved from its navigation layout exactly as any
|
|
294
|
-
* other overlay: this axis says "an overlay", not "a dialog specifically". Author
|
|
295
|
-
* `navigationOverrides` when you need to name one.
|
|
296
|
-
*/
|
|
297
|
-
MODAL = 'modal',
|
|
298
|
-
/**
|
|
299
|
-
* A routable page, resolved through the ordinary navigation chain (zone transitions, viewport
|
|
300
|
-
* overrides, the framework `PUSH` fallback) — i.e. exactly the behaviour every parameterised
|
|
301
|
-
* action had before this axis existed.
|
|
302
|
-
*
|
|
303
|
-
* The right answer for complex or multi-step input, and for anything a user should be able to
|
|
304
|
-
* link to, reload, or reach with a back button.
|
|
305
|
-
*/
|
|
306
|
-
PAGE = 'page',
|
|
307
|
-
}
|
|
308
|
-
|
|
309
209
|
/**
|
|
310
210
|
* Does an operation's action target a SINGLE resource instance, or the WHOLE
|
|
311
211
|
* collection in the current scope?
|
|
@@ -434,26 +334,6 @@ export const CardActionPlacementSchema = z.object({
|
|
|
434
334
|
/** Authored 2-axis card action placement — inferred from {@link CardActionPlacementSchema}. */
|
|
435
335
|
export type CardActionPlacement = z.infer<typeof CardActionPlacementSchema>;
|
|
436
336
|
|
|
437
|
-
/**
|
|
438
|
-
* Who paints the identity GLYPH on this operation's page header.
|
|
439
|
-
*
|
|
440
|
-
* The header band renders the resource's registry icon beside the identity line by default. A
|
|
441
|
-
* `layout.header` template that composes its own record-linked glyph (a per-row kind icon, a
|
|
442
|
-
* per-family symbol) would otherwise sit BESIDE the resource icon — two glyphs naming one thing.
|
|
443
|
-
*
|
|
444
|
-
* Declared at the OPERATION layer rather than detected from the template, deliberately: the
|
|
445
|
-
* resource icon renders before the template mounts, so detection could only suppress it after the
|
|
446
|
-
* fact — a glyph that flashes and vanishes on every load. Mirrors
|
|
447
|
-
* `SummaryTitlePlacement.TEMPLATE_OWNED`, the same contract one surface over: ceding a
|
|
448
|
-
* framework-owned element to the template is a declaration, not an inference.
|
|
449
|
-
*/
|
|
450
|
-
export enum HeaderIconPlacement {
|
|
451
|
-
/** The framework renders the resource's registry icon (default). */
|
|
452
|
-
AUTO = 'auto',
|
|
453
|
-
/** The header template owns the glyph; the framework renders none. */
|
|
454
|
-
TEMPLATE_OWNED = 'template_owned',
|
|
455
|
-
}
|
|
456
|
-
|
|
457
337
|
export const ResourceOperationFrontendConfigSchema = z.object({
|
|
458
338
|
/**
|
|
459
339
|
* The operation's frontend **surface** — see {@link ResourceOperationFrontendSurface}.
|
|
@@ -465,8 +345,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
465
345
|
* Replaces the former `isAddressable` boolean — read via `isOperationAddressable()`.
|
|
466
346
|
*/
|
|
467
347
|
surface: z.enum(ResourceOperationFrontendSurface),
|
|
468
|
-
/** Who paints the page header's identity glyph — see {@link HeaderIconPlacement}. Omitted = AUTO. */
|
|
469
|
-
headerIconPlacement: z.enum(HeaderIconPlacement).optional(),
|
|
470
348
|
/**
|
|
471
349
|
* How this operation's action is surfaced — see {@link ActionVisibility}. Omitted
|
|
472
350
|
* (the common case) behaves as `ALWAYS`.
|
|
@@ -502,15 +380,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
502
380
|
* row id still rides the URL path too, which the handler may ignore.)
|
|
503
381
|
*/
|
|
504
382
|
rowTargetRequestField: z.string().optional(),
|
|
505
|
-
/**
|
|
506
|
-
* HOW this action collects its input — see {@link ResourceOperationActionPresentation}.
|
|
507
|
-
* Omitted derives from the operation (`resolveResourceOperationActionPresentation`): no input
|
|
508
|
-
* executes directly, a small field set opens a modal, complex input keeps its page.
|
|
509
|
-
*
|
|
510
|
-
* Display-only. An explicit `navigationOverrides` entry is the more specific instrument and wins
|
|
511
|
-
* over whatever this resolves to.
|
|
512
|
-
*/
|
|
513
|
-
actionPresentation: z.enum(ResourceOperationActionPresentation).optional(),
|
|
514
383
|
customView: z.any().optional(),
|
|
515
384
|
displayPresetOverride: z.object({
|
|
516
385
|
resourceLayoutPresetKey: z.string().optional(),
|
|
@@ -546,30 +415,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
546
415
|
* without a date heading rather than being dropped.
|
|
547
416
|
*/
|
|
548
417
|
temporalGroupField: z.string().optional(),
|
|
549
|
-
/**
|
|
550
|
-
* Group CARDS-mode rows into buckets by this ENUM field, rendering the
|
|
551
|
-
* enum value's own label as a heading between groups.
|
|
552
|
-
*
|
|
553
|
-
* Sibling of {@link temporalGroupField}, and deliberately NOT the same
|
|
554
|
-
* algorithm. Temporal grouping ADJACENT-MERGES in server order, because
|
|
555
|
-
* dates are open-ended and a page can legitimately revisit one. An enum is
|
|
556
|
-
* a CLOSED, ORDERED vocabulary, so its buckets are emitted in the enum's
|
|
557
|
-
* DECLARATION ORDER regardless of the order rows arrived in — the
|
|
558
|
-
* declaration is the authority for "which concern comes first", and a
|
|
559
|
-
* server sort cannot express it without a second, drifting copy of that
|
|
560
|
-
* order. Rows are therefore collected across the whole fetched page rather
|
|
561
|
-
* than merged adjacently, and no sort needs pairing with it.
|
|
562
|
-
*
|
|
563
|
-
* Headings resolve through `tResourceFieldEnumValue` — the SAME source the
|
|
564
|
-
* filters panel and the promoted quick-filter tabs use, so a bucket
|
|
565
|
-
* heading and its tab can never disagree.
|
|
566
|
-
*
|
|
567
|
-
* Ignored in TABLE mode (column sorting owns the ordering there). Rows
|
|
568
|
-
* whose value is absent, or outside the vocabulary, render in a trailing
|
|
569
|
-
* bucket with no heading rather than being dropped — the same fail-open
|
|
570
|
-
* the temporal grouping makes.
|
|
571
|
-
*/
|
|
572
|
-
enumGroupField: z.string().optional(),
|
|
573
418
|
/**
|
|
574
419
|
* CARDS-mode arrangement — a single-column bordered LIST (default) or an
|
|
575
420
|
* N-column responsive GRID. See {@link CardLayoutStyle}. `columns` (1–6) is
|
|
@@ -623,49 +468,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
623
468
|
* into a description via the `.describe()` decorator.
|
|
624
469
|
*/
|
|
625
470
|
hasDescription: z.boolean().optional(),
|
|
626
|
-
/**
|
|
627
|
-
* What happens to an ADJACENT zone (secondary / companion) this operation
|
|
628
|
-
* splits into, once that zone's last content is dismissed — overriding the
|
|
629
|
-
* zone's own `onEmpty` while this operation occupies primary.
|
|
630
|
-
*
|
|
631
|
-
* The zone-level `ZoneConfig.onEmpty` is one value for every destination that
|
|
632
|
-
* splits into that zone, and destinations legitimately disagree: a LIST wants
|
|
633
|
-
* the detail pane to stay put (`EMPTY_STATE`) so the layout does not reflow
|
|
634
|
-
* while a reviewer steps through rows, while a CANVAS wants its width back
|
|
635
|
-
* (`COLLAPSE`) the moment nothing is selected. Both share one secondary zone,
|
|
636
|
-
* so without this override one of them is always wrong.
|
|
637
|
-
*
|
|
638
|
-
* Declared on the SOURCE operation — the one occupying primary — not on the
|
|
639
|
-
* operation that lands in the pane: it answers "what should MY layout do when
|
|
640
|
-
* the detail closes", which is a property of the surface being returned to.
|
|
641
|
-
*
|
|
642
|
-
* Omitted (the common case) defers to the zone, which itself defaults to
|
|
643
|
-
* `ZoneEmptyBehavior.COLLAPSE`. Resolution order is destination → zone →
|
|
644
|
-
* COLLAPSE; see `resolveZoneEmptyBehavior`.
|
|
645
|
-
*/
|
|
646
|
-
adjacentZoneOnEmpty: z.enum(ZoneEmptyBehavior).optional(),
|
|
647
|
-
/**
|
|
648
|
-
* How wide this destination's content may grow in the zone, in the framework's shared width
|
|
649
|
-
* vocabulary — the SAME `ResponsiveMaxWidth` a Surface, a `DisplayLayout` and a `FormLayout` use.
|
|
650
|
-
*
|
|
651
|
-
* Omitted (the common case) is `'content'`: capped and centred at `var(--content-max-width, 80rem)`,
|
|
652
|
-
* right for a form, a list or a detail page and wrong only for content whose value IS the space it
|
|
653
|
-
* occupies — a board, a wide table, a canvas — which declare `'none'`.
|
|
654
|
-
*/
|
|
655
|
-
zoneContentMaxWidth: z.enum(RESPONSIVE_MAX_WIDTH_VALUES).optional(),
|
|
656
|
-
/**
|
|
657
|
-
* Whether this destination's content fills the zone's HEIGHT as well.
|
|
658
|
-
*
|
|
659
|
-
* `true` makes the zone's content boundary a definite-height flex column, so this view's root may use
|
|
660
|
-
* `flex-1 min-h-0` and resolve against something real. Without it a canvas has no intrinsic height
|
|
661
|
-
* and collapses to zero — which is why one had to hand-roll `h-[70vh]`, sizing against the WINDOW
|
|
662
|
-
* rather than the container it sits in. PRIMARY only: an adjacent zone scrolls, so a filling child
|
|
663
|
-
* and a scrolling parent contradict each other.
|
|
664
|
-
*
|
|
665
|
-
* Separate from the width above ON PURPOSE — see `zone-content-geometry.ts` for why the enum that
|
|
666
|
-
* fused them could not express a capped width with a definite height.
|
|
667
|
-
*/
|
|
668
|
-
zoneContentFillsHeight: z.boolean().optional(),
|
|
669
471
|
});
|
|
670
472
|
|
|
671
473
|
/**
|
package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md
CHANGED
|
@@ -20,7 +20,7 @@ Per-primitive UI parameter surfaces (string, number, enum, etc.).
|
|
|
20
20
|
*
|
|
21
21
|
* They belong to the frontend resource behavior layer, not to shared resource
|
|
22
22
|
* schemas. In application code, they are typically authored in files like:
|
|
23
|
-
* `
|
|
23
|
+
* `app/src/modules/<module>/resources/<resource>/<resource>.ui-behavior.tsx`
|
|
24
24
|
*
|
|
25
25
|
* The shared schema establishes structural meaning (`isSummaryField`,
|
|
26
26
|
* `isForeignKey`, `excludeFromUpdate`, ...). These UI parameter types control
|
|
@@ -354,42 +354,11 @@ export interface ForeignKeyUIParams {
|
|
|
354
354
|
// ARRAY UI
|
|
355
355
|
//------------------------------------------------------------------------------------------------
|
|
356
356
|
|
|
357
|
-
/**
|
|
358
|
-
* List marker treatment for a PRIMITIVE array's display items.
|
|
359
|
-
*
|
|
360
|
-
* Its own enum rather than a new `DisplayDirection` member on purpose: direction answers "which
|
|
361
|
-
* axis do items flow on", marker style answers "does each item announce itself as one of several" —
|
|
362
|
-
* merging them would make `BULLETS × horizontal` an unrepresentable-but-meaningful combination and
|
|
363
|
-
* overload an enum that alignment code also reads.
|
|
364
|
-
*/
|
|
365
|
-
export enum ArrayListStyle {
|
|
366
|
-
/** Bare stacked values — the historical default. */
|
|
367
|
-
PLAIN = 'plain',
|
|
368
|
-
/** A real bulleted list. For enumerations a reader SCANS — alternatives, consequences, principles — where bare stacked lines read as one run-on paragraph. */
|
|
369
|
-
BULLETS = 'bullets',
|
|
370
|
-
/**
|
|
371
|
-
* A RULED list: one hairline between entries, none above the first or below the last.
|
|
372
|
-
*
|
|
373
|
-
* For OBJECT entries a reader compares — an ICP after an ICP, a persona after a persona — where
|
|
374
|
-
* spacing alone stops saying where one ends. It is the alternative to framing each entry as a
|
|
375
|
-
* card, and the reason to prefer it is compounding chrome: inside a section that is already a
|
|
376
|
-
* bounded region, a card per entry is a third frame around content that has two. Unlike
|
|
377
|
-
* {@link ArrayListStyle.BULLETS}, which is for primitive lines, this is for entries.
|
|
378
|
-
*/
|
|
379
|
-
SEPARATED = 'separated',
|
|
380
|
-
}
|
|
381
|
-
|
|
382
357
|
export interface ArrayUIDisplayParams extends PrimitiveUIBaseDisplayParams {
|
|
383
358
|
/** Direction for rendering items in display context. */
|
|
384
359
|
displayMode?: DisplayDirection;
|
|
385
360
|
/** Max items shown in display (rest truncated). */
|
|
386
361
|
maxItems?: number;
|
|
387
|
-
/**
|
|
388
|
-
* Marker treatment for PRIMITIVE items (see {@link ArrayListStyle}). No effect on object arrays —
|
|
389
|
-
* their items are cards/rows, not list lines — and no effect on horizontal flow, where markers
|
|
390
|
-
* have no line to anchor to.
|
|
391
|
-
*/
|
|
392
|
-
listStyle?: ArrayListStyle;
|
|
393
362
|
}
|
|
394
363
|
|
|
395
364
|
/**
|
|
@@ -480,18 +449,6 @@ export interface ObjectUIDisplayParams extends PrimitiveUIBaseDisplayParams {
|
|
|
480
449
|
displayMode?: DisplayDirection;
|
|
481
450
|
/** Max properties shown in display (rest truncated). */
|
|
482
451
|
maxItems?: number;
|
|
483
|
-
/**
|
|
484
|
-
* The member that IS this object's headline when the object renders as a unit (a nested object
|
|
485
|
-
* block, an array item card): it renders FIRST, label hidden, with title emphasis; the remaining
|
|
486
|
-
* members follow in schema order.
|
|
487
|
-
*
|
|
488
|
-
* Explicit rather than detected: "the first string field" guesses wrong the moment a stable
|
|
489
|
-
* identifier precedes the human statement in the schema — exactly the shape ref-addressable
|
|
490
|
-
* entries have (`ref` first, `statement` second), where detection would headline the machine key.
|
|
491
|
-
* Names a member that does not exist → ignored, so a schema rename degrades to the old uniform
|
|
492
|
-
* rendering instead of crashing the display.
|
|
493
|
-
*/
|
|
494
|
-
primaryField?: string;
|
|
495
452
|
}
|
|
496
453
|
|
|
497
454
|
export type ObjectUIEditParams = PrimitiveUIBaseEditParams;
|
|
@@ -22,9 +22,6 @@ export interface PrimitiveUIBaseDisplayParams {
|
|
|
22
22
|
/** Chrome layout mode for the field wrapper in display context. */
|
|
23
23
|
chromeMode?: ResponsiveAware<DisplayChromeMode>;
|
|
24
24
|
|
|
25
|
-
/** Label styling, orthogonal to `chromeMode` (which decides LAYOUT). See `DisplayLabelStyle`. */
|
|
26
|
-
labelStyle?: DisplayLabelStyle;
|
|
27
|
-
|
|
28
25
|
/** Force-hide specific chrome sub-elements in display context. Plain object = all breakpoints. */
|
|
29
26
|
forceHide?: ResponsiveAware<ForceHideDisplayConfig>;
|
|
30
27
|
|
|
@@ -253,7 +253,6 @@ export const specificationsCompanionExports: SpecificationsCompanionExports<
|
|
|
253
253
|
* decisions remain private runtime state.
|
|
254
254
|
*/
|
|
255
255
|
documentFactSpecification: applicationDocumentFactSpecification,
|
|
256
|
-
authoredDocumentFactSpecification: applicationAuthoredDocumentFactSpecification,
|
|
257
256
|
/**
|
|
258
257
|
* The accepted typed build plan (`build-plan` family, `BuildPlanTaskGraph`).
|
|
259
258
|
* The bottom-up dispatch playbook's coding owner reads it from the verified
|
|
@@ -57,7 +57,6 @@ export interface SpecificationsCompanionExports<
|
|
|
57
57
|
TRequirementsSnapshot = RequirementsSnapshot,
|
|
58
58
|
TRoadmapSnapshot = RoadmapSnapshot,
|
|
59
59
|
TBuildPlanTaskGraph = BuildPlanTaskGraph,
|
|
60
|
-
TPlacementPlan = PlacementPlan,
|
|
61
60
|
TDomainPlanOutputSet = DomainPlanOutputSet,
|
|
62
61
|
TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
|
|
63
62
|
// Appended STRICTLY LAST (positional generics — never insert mid-list):
|
|
@@ -85,14 +84,6 @@ export interface SpecificationsCompanionExports<
|
|
|
85
84
|
// Appended STRICTLY LAST: release-process selection is a separate accepted
|
|
86
85
|
// decision, never an implicit default of routing or document necessity.
|
|
87
86
|
TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
|
|
88
|
-
// Appended STRICTLY LAST: WHO else processes personal data, under what legal
|
|
89
|
-
// identity and where (issue #88). Optional, and the optionality is the design:
|
|
90
|
-
// a partial register is useful and its holes are REPORTED per provider against
|
|
91
|
-
// the application's configured set, rather than blocking anything.
|
|
92
|
-
TProcessorRegister = ApplicationProcessorRegister,
|
|
93
|
-
// Appended STRICTLY LAST: the human half of the document facts, in its own
|
|
94
|
-
// family, because the derived one is REGENERATED whole (#192).
|
|
95
|
-
TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,
|
|
96
87
|
> {
|
|
97
88
|
resourceSpecifications: TResourceSpecifications;
|
|
98
89
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -323,22 +314,6 @@ export interface SpecificationsCompanionExports<
|
|
|
323
314
|
* `validateBuildPlanTaskGraph` on the value before wiring it here.
|
|
324
315
|
*/
|
|
325
316
|
buildPlanSpecification?: TBuildPlanTaskGraph;
|
|
326
|
-
/**
|
|
327
|
-
* Application **placement** specification — WHERE every settings destination,
|
|
328
|
-
* resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
|
|
329
|
-
* `_core/placement-plan/`).
|
|
330
|
-
*
|
|
331
|
-
* Produced by the `bottom_up.placement-plan` playbook as an expert-panel
|
|
332
|
-
* DELIBERATION rather than a creator elicitation: the creator does not choose
|
|
333
|
-
* placement, so each decision carries a `rationale` that answers "why is this
|
|
334
|
-
* here?" without re-running the panel. Consumed by build-decompose, which
|
|
335
|
-
* turns it into the coding tasks that author `settings-hub.config.ts` and
|
|
336
|
-
* `app-shell.config.ts`.
|
|
337
|
-
*
|
|
338
|
-
* Optional until an application reaches the bottom-up phase; app bootstraps
|
|
339
|
-
* should run `validatePlacementPlan` on the value before wiring it here.
|
|
340
|
-
*/
|
|
341
|
-
placementPlanSpecification?: TPlacementPlan;
|
|
342
317
|
/**
|
|
343
318
|
* Application **domain-plan** specification — the atomic module decomposition
|
|
344
319
|
* PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
|
|
@@ -477,37 +452,6 @@ export interface SpecificationsCompanionExports<
|
|
|
477
452
|
* Omitting it is honest: unresolved document facts remain visible gaps.
|
|
478
453
|
*/
|
|
479
454
|
documentFactSpecification?: TDocumentFactSpecification;
|
|
480
|
-
/**
|
|
481
|
-
* Accepted application governed-document facts **only a human may establish** — a creator decision
|
|
482
|
-
* or a qualified review (`document-facts-authored`).
|
|
483
|
-
*
|
|
484
|
-
* The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`
|
|
485
|
-
* rewrites the derived file whole, so a human decision sharing that file is destroyed on the next
|
|
486
|
-
* run with nothing to notice: there is no compare-and-swap here, deliberately
|
|
487
|
-
* (`.claude/rules/one-source-of-truth.md` Rule 0). Two families put the two writers out of each
|
|
488
|
-
* other's reach.
|
|
489
|
-
*
|
|
490
|
-
* No producer may write this family — it has no generation contract, and that absence is the design
|
|
491
|
-
* rather than an omission.
|
|
492
|
-
*
|
|
493
|
-
* A reader wanting "the application's facts" needs BOTH slots. `collectComplianceDocumentFactAvailability`
|
|
494
|
-
* is variadic for exactly that reason.
|
|
495
|
-
*/
|
|
496
|
-
authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;
|
|
497
|
-
/**
|
|
498
|
-
* WHO else processes this application's personal data — legal identity, processing region and the
|
|
499
|
-
* processor's own subprocessors (issue #88).
|
|
500
|
-
*
|
|
501
|
-
* A configured provider already establishes THAT a third party is involved and what function it
|
|
502
|
-
* performs. None of that is what a privacy notice's recipient statement needs, and an
|
|
503
|
-
* international-transfer statement cannot be made at all without a region.
|
|
504
|
-
*
|
|
505
|
-
* Optional, and its holes are reported rather than blocking: the companion compares this register
|
|
506
|
-
* against the application's CONFIGURED providers and names each one that is undeclared, so a partial
|
|
507
|
-
* register is useful and an empty one still produces an actionable document. An absent entry means
|
|
508
|
-
* nobody has established that processor's identity — never that the provider is unused.
|
|
509
|
-
*/
|
|
510
|
-
processorRegister?: TProcessorRegister;
|
|
511
455
|
/**
|
|
512
456
|
* Accepted application-declared semantic causality between whole
|
|
513
457
|
* specification-family states. This is not the registry's physical
|
package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md
CHANGED
|
@@ -84,34 +84,15 @@ export enum CodeDeclarationKind {
|
|
|
84
84
|
}
|
|
85
85
|
|
|
86
86
|
/**
|
|
87
|
-
*
|
|
87
|
+
* Public-import-oriented symbol reference used by semantic specifications.
|
|
88
88
|
*
|
|
89
|
-
* Downstream transposers
|
|
90
|
-
*
|
|
91
|
-
* and they are not the same fact, so they have separate fields:
|
|
92
|
-
*
|
|
93
|
-
* - `importPath` is an IMPORT SPECIFIER — something a generated `import` statement
|
|
94
|
-
* can actually resolve, declared in the owning package's `package.json#exports`.
|
|
95
|
-
* - `filePathHint` is a LOCATION — where a maintainer opens the file. It is never
|
|
96
|
-
* rendered as something importable.
|
|
97
|
-
*
|
|
98
|
-
* Authoring a source path in `importPath` is the defect issue #150 records: it made
|
|
99
|
-
* the companion hand a coding agent an import specifier that cannot resolve, because
|
|
100
|
-
* an application package typically declares no export map entry for its internal
|
|
101
|
-
* modules. When in doubt, author `filePathHint` — a location that is merely useful
|
|
102
|
-
* is better than an address that is wrong.
|
|
89
|
+
* Downstream transposers/prompts should prefer these refs over file-path
|
|
90
|
+
* guesses so generated code imports the right public symbol.
|
|
103
91
|
*/
|
|
104
92
|
export interface CodeSymbolRef {
|
|
105
93
|
/** Package name to import from (for example `@wildo-ai/saas-models`). */
|
|
106
94
|
packageName: string;
|
|
107
|
-
/**
|
|
108
|
-
* Optional PUBLIC SUBPATH, when the package root is not the import target.
|
|
109
|
-
*
|
|
110
|
-
* Must be a subpath the owning package declares in `package.json#exports`, so that
|
|
111
|
-
* `${packageName}/${importPath}` is a resolvable import specifier. If the symbol has
|
|
112
|
-
* no public door, leave this unset and author `filePathHint` instead — do NOT put a
|
|
113
|
-
* path inside `src/` here.
|
|
114
|
-
*/
|
|
95
|
+
/** Optional public subpath when the package root is not the import target. */
|
|
115
96
|
importPath?: string;
|
|
116
97
|
/** Literal exported symbol name. */
|
|
117
98
|
exportName: string;
|
|
@@ -119,14 +100,7 @@ export interface CodeSymbolRef {
|
|
|
119
100
|
symbolKind: CodeSymbolKind;
|
|
120
101
|
/** More specific declaration family for code-generation handling. */
|
|
121
102
|
declarationKind?: CodeDeclarationKind;
|
|
122
|
-
/**
|
|
123
|
-
* Optional MODULE LOCATION — where the symbol is defined inside the owning package,
|
|
124
|
-
* relative to that package's source root (for example
|
|
125
|
-
* `modules/tasks-manager/resources/tasks/tasks.ui-behavior`).
|
|
126
|
-
*
|
|
127
|
-
* This is a navigation aid, not an import target: it is rendered as a location and
|
|
128
|
-
* must never be concatenated onto `packageName` to build an import specifier.
|
|
129
|
-
*/
|
|
103
|
+
/** Optional local-path hint for companion-side tooling/debugging. */
|
|
130
104
|
filePathHint?: string;
|
|
131
105
|
/** Extra caveats or usage notes for downstream prompts. */
|
|
132
106
|
notes?: string[];
|
|
@@ -2356,28 +2356,6 @@ export type ResourceSpecificationConfig<
|
|
|
2356
2356
|
businessRole: string;
|
|
2357
2357
|
/** How the resource evolves over time (lifecycle semantics). */
|
|
2358
2358
|
lifecycleRole?: string;
|
|
2359
|
-
/**
|
|
2360
|
-
* Which part of the product this resource belongs to, WITHIN its owner.
|
|
2361
|
-
*
|
|
2362
|
-
* A second grouping axis under the one that already exists. An application's resources are grouped
|
|
2363
|
-
* by the module that registers them; the engine's are grouped by nothing, so every surface that
|
|
2364
|
-
* has to present them — the domain-model graph, `wildo context`, generated documentation, an
|
|
2365
|
-
* application-creation playbook — meets one flat set of 85 and either shows it undifferentiated or
|
|
2366
|
-
* invents a grouping of its own and drifts from the next surface that does the same.
|
|
2367
|
-
*
|
|
2368
|
-
* Typed `string` and OPEN on purpose. The engine's values are a closed vocabulary with a named
|
|
2369
|
-
* runtime source, {@link EngineResourceSubDomain} in this package's `engine` surface, and engine
|
|
2370
|
-
* specs must use it. An application's sub-domains are its own — this repository cannot enumerate
|
|
2371
|
-
* a vocabulary it does not own, and a union that tried would refuse every real application.
|
|
2372
|
-
*
|
|
2373
|
-
* Optional, and its absence means exactly "unclassified" rather than "belongs to a default". A
|
|
2374
|
-
* consumer grouping by it must carry a bucket for that and say so; silently folding unclassified
|
|
2375
|
-
* rows into a real group is how a grouping starts lying.
|
|
2376
|
-
*
|
|
2377
|
-
* Distinct from {@link ResourceSpecificationConfig.resourcePrimaryScope}, which answers WHO a row
|
|
2378
|
-
* belongs to. This answers what it is ABOUT, and one sub-domain spans several scopes.
|
|
2379
|
-
*/
|
|
2380
|
-
subDomain?: string;
|
|
2381
2359
|
/**
|
|
2382
2360
|
* Intended READER of this resource's generated labels — the register the label
|
|
2383
2361
|
* generator should adopt: {@link LabelAudience.END_USER} for consumer surfaces
|
|
@@ -41,45 +41,6 @@ export interface CompositeViewAuthoringConfig {
|
|
|
41
41
|
* overlays) render the authored icon.
|
|
42
42
|
*/
|
|
43
43
|
icon?: IconLike;
|
|
44
|
-
/**
|
|
45
|
-
* What happens to an ADJACENT zone (secondary / companion) this destination
|
|
46
|
-
* splits into, once that zone's last content is dismissed — overriding the
|
|
47
|
-
* zone's own `onEmpty` while this destination occupies primary.
|
|
48
|
-
*
|
|
49
|
-
* The zone-level `ZoneConfig.onEmpty` is one value for every destination that
|
|
50
|
-
* splits into that zone, and destinations legitimately disagree: a LIST wants
|
|
51
|
-
* the detail pane to stay put (`EMPTY_STATE`) so the layout does not reflow
|
|
52
|
-
* while a reviewer steps through rows, while a CANVAS wants its width back
|
|
53
|
-
* (`COLLAPSE`) the moment nothing is selected. Both share one secondary zone,
|
|
54
|
-
* so without this override one of them is always wrong.
|
|
55
|
-
*
|
|
56
|
-
* Omitted (the common case) defers to the zone, which itself defaults to
|
|
57
|
-
* `ZoneEmptyBehavior.COLLAPSE`. Resolution order is destination → zone →
|
|
58
|
-
* COLLAPSE; see `resolveZoneEmptyBehavior`.
|
|
59
|
-
*/
|
|
60
|
-
adjacentZoneOnEmpty?: ZoneEmptyBehavior;
|
|
61
|
-
/**
|
|
62
|
-
* How wide this destination's content may grow in the zone, in the framework's shared width
|
|
63
|
-
* vocabulary — the SAME `ResponsiveMaxWidth` a Surface, a `DisplayLayout` and a `FormLayout` use.
|
|
64
|
-
*
|
|
65
|
-
* Omitted (the common case) is `'content'`: capped and centred at `var(--content-max-width, 80rem)`,
|
|
66
|
-
* right for a form, a list or a detail page and wrong only for content whose value IS the space it
|
|
67
|
-
* occupies — a board, a wide table, a canvas — which declare `'none'`.
|
|
68
|
-
*/
|
|
69
|
-
zoneContentMaxWidth?: ResponsiveMaxWidth;
|
|
70
|
-
/**
|
|
71
|
-
* Whether this destination's content fills the zone's HEIGHT as well.
|
|
72
|
-
*
|
|
73
|
-
* `true` makes the zone's content boundary a definite-height flex column, so this view's root may use
|
|
74
|
-
* `flex-1 min-h-0` and resolve against something real. Without it a canvas has no intrinsic height
|
|
75
|
-
* and collapses to zero — which is why one had to hand-roll `h-[70vh]`, sizing against the WINDOW
|
|
76
|
-
* rather than the container it sits in. PRIMARY only: an adjacent zone scrolls, so a filling child
|
|
77
|
-
* and a scrolling parent contradict each other.
|
|
78
|
-
*
|
|
79
|
-
* Separate from the width above ON PURPOSE — see `zone-content-geometry.ts` for why the enum that
|
|
80
|
-
* fused them could not express a capped width with a definite height.
|
|
81
|
-
*/
|
|
82
|
-
zoneContentFillsHeight?: boolean;
|
|
83
44
|
}
|
|
84
45
|
|
|
85
46
|
/**
|
|
@@ -135,12 +96,6 @@ export interface CompositeViewDefinition {
|
|
|
135
96
|
* `CoreIconRegistry.compositeView`, keyed by `ref`.
|
|
136
97
|
*/
|
|
137
98
|
icon?: IconLike;
|
|
138
|
-
/** See {@link CompositeViewAuthoringConfig.adjacentZoneOnEmpty}. Mirrored from authoring. */
|
|
139
|
-
adjacentZoneOnEmpty?: ZoneEmptyBehavior;
|
|
140
|
-
/** See {@link CompositeViewAuthoringConfig.zoneContentMaxWidth}. Mirrored from authoring. */
|
|
141
|
-
zoneContentMaxWidth?: ResponsiveMaxWidth;
|
|
142
|
-
/** See {@link CompositeViewAuthoringConfig.zoneContentFillsHeight}. Mirrored from authoring. */
|
|
143
|
-
zoneContentFillsHeight?: boolean;
|
|
144
99
|
}
|
|
145
100
|
|
|
146
101
|
export type AppCompositeViewsConfig = Record<string, CompositeViewAuthoringConfig>;
|