@wildo-ai/framework-knowledge 1.1.8 → 1.1.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (226) hide show
  1. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  3. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  5. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +29 -5
  6. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  8. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  9. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  10. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  11. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  12. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +11 -1
  13. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  14. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  15. package/dist/esm/framework-knowledge.definitions.js +11 -1
  16. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  18. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  19. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
  21. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  23. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -3
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +59 -10
  27. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  30. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +1 -1
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +5 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  41. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  43. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  45. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +85 -43
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +40 -0
  49. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +41 -0
  51. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +199 -0
  53. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +201 -0
  55. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +67 -0
  57. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  58. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +76 -0
  59. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  60. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  61. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  63. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  65. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  67. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  69. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  71. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  75. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  77. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  79. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  81. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +36 -2
  83. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  85. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  87. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  89. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  91. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  93. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +30 -17
  95. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  96. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  97. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  98. package/dist/knowledge/manifest.json +8 -8
  99. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  100. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  101. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  102. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  103. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  104. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  105. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +117 -28
  106. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +4 -4
  107. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +133 -59
  108. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  109. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  110. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  111. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  112. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  113. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  114. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +2 -2
  115. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  116. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  117. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +22 -6
  118. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -3
  119. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  120. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +5 -2
  121. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  122. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  123. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  124. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +71 -37
  125. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  126. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +105 -0
  127. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +55 -0
  128. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  129. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  130. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +78 -0
  131. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +63 -0
  132. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  133. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +65 -0
  134. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  135. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  136. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  137. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  138. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  139. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  140. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  141. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  142. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  143. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  144. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  145. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  146. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  147. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  148. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  149. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +10 -0
  150. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +40 -17
  151. package/dist/knowledge/references/brand.name-choice.config.md +127 -0
  152. package/dist/knowledge/references/brand.name-screening.config.md +253 -0
  153. package/dist/knowledge/references/build-plan.task-graph.config.md +64 -11
  154. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  155. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  156. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  157. package/dist/knowledge/references/capability-composition.config.md +67 -4
  158. package/dist/knowledge/references/example.data-seeding.minimal.md +29 -1
  159. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  160. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  161. package/dist/knowledge/references/saas.data-seeding.definition-input.md +6 -0
  162. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  163. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  164. package/dist/knowledge/references/saas.website.astro.label-loader.md +9 -0
  165. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  166. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  167. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  168. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  169. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  170. package/dist/knowledge/registries/framework-topics.json +38 -1
  171. package/dist/knowledge/registries/playbooks.json +68 -20
  172. package/dist/knowledge/registries/source-tags.json +748 -695
  173. package/dist/knowledge/rules/live-context-door.md +5 -2
  174. package/dist/knowledge/skills/INDEX.md +2 -1
  175. package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -1
  176. package/dist/knowledge/skills/brand-name-screening/SKILL.md +154 -0
  177. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +394 -0
  178. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +65 -0
  179. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +5 -2
  180. package/dist/knowledge/skills/config-saas/SKILL.md +31 -4
  181. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +14 -1
  182. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  183. package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
  184. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
  185. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  186. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +11 -1
  187. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  188. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  189. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  190. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -1
  191. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +11 -1
  192. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  193. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -1
  194. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  195. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  196. package/dist/knowledge/skills/module-relationships/SKILL.md +6 -4
  197. package/dist/knowledge/skills/seeding-authoring/SKILL.md +51 -3
  198. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +6 -0
  199. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  200. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  201. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -0
  202. package/dist/knowledge/skills/website-page-authoring/SKILL.md +84 -3
  203. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  204. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  205. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  206. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  207. package/dist/knowledge/skills/website-section-faq/SKILL.md +15 -0
  208. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  209. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +15 -0
  210. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  211. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +15 -0
  212. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  213. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  214. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  215. package/dist/knowledge/skills/website-section-hero/SKILL.md +27 -9
  216. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  217. package/dist/knowledge/skills/website-section-pricing/SKILL.md +15 -0
  218. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  219. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +15 -0
  220. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  221. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +1 -1
  222. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  223. package/dist/knowledge/topic-index.json +169 -43
  224. package/dist/tsconfig.build.tsbuildinfo +1 -1
  225. package/dist/tsconfig.tsbuildinfo +1 -1
  226. package/package.json +4 -4
@@ -807,7 +807,7 @@ function detectMissingPositioningForIcp(snapshot: MarketSnapshot, issues: Market
807
807
  const positionedIcpRefs = new Set(snapshot.positionings.map(p => p.icpRef));
808
808
 
809
809
  for (const [iIdx, icp] of snapshot.icps.entries()) {
810
- if (icp.priority !== ICPPriority.CORE && icp.priority !== ICPPriority.EXPANSION) continue;
810
+ if (!TARGETED_ICP_PRIORITIES.has(icp.priority)) continue;
811
811
  if (positionedIcpRefs.has(icp.ref)) continue;
812
812
 
813
813
  issues.push({
@@ -666,7 +666,7 @@ function detectMissingPositioningForIcp(snapshot: MarketSnapshot, issues: Market
666
666
  const positionedIcpRefs = new Set(snapshot.positionings.map(p => p.icpRef));
667
667
 
668
668
  for (const [iIdx, icp] of snapshot.icps.entries()) {
669
- if (icp.priority !== ICPPriority.CORE && icp.priority !== ICPPriority.EXPANSION) continue;
669
+ if (!TARGETED_ICP_PRIORITIES.has(icp.priority)) continue;
670
670
  if (positionedIcpRefs.has(icp.ref)) continue;
671
671
 
672
672
  issues.push({
@@ -132,6 +132,8 @@ export interface SpecificationsCompanionExports<
132
132
  TIntegrationPlan = IntegrationPlan,
133
133
  // Appended STRICTLY LAST: where the application stands against its own requirements (#1496).
134
134
  TApplicationMaturity = ApplicationMaturity,
135
+ // Appended STRICTLY LAST: the screened brand-name candidates the brand-identity interview chooses from.
136
+ TBrandNameScreening = BrandNameScreening,
135
137
  > {
136
138
  resourceSpecifications: TResourceSpecifications;
137
139
  applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
@@ -662,6 +664,14 @@ export interface SpecificationsCompanionExports<
662
664
  * never a gate. Read by the coherence report and the workbench.
663
665
  */
664
666
  applicationMaturity?: TApplicationMaturity;
667
+ /**
668
+ * WHICH NAMES were proposed for the brand and what a minimal trademark screening of each found —
669
+ * registers, classes and jurisdictions searched, per-register results with sources and dates, and the
670
+ * competitor collisions beside them. Produced by `top_down.brand-naming`; the brand-identity interview's
671
+ * `brand-name` CHOICE is computed from it, and the coherence report reads it to say where the chosen
672
+ * brand name stands. A screening, never a legal clearance opinion.
673
+ */
674
+ brandNameScreening?: TBrandNameScreening;
665
675
  /**
666
676
  * Accepted application-declared semantic causality between whole
667
677
  * specification-family states. This is not the registry's physical
@@ -526,11 +526,13 @@ read it back after the build settles, not mid-edit.
526
526
  rg -c "allowCycle: true" ./shared-lib/src/modules/**/*.relationships.ts
527
527
 
528
528
  # an allowCycle edge with no explicit foreignKeyField — two edges between one pair of types are
529
- # told apart ONLY by their columns, so an implicit one is ambiguous (must return empty)
530
- rg -A 6 "allowCycle: true" ./shared-lib/src/modules/**/*.relationships.ts | rg -B 6 -L "foreignKeyField"
529
+ # told apart ONLY by their columns, so an implicit one is ambiguous (must return empty). One
530
+ # match is one createResourcesRelationship(...) call holding allowCycle and no foreignKeyField,
531
+ # wherever in the call either appears.
532
+ rg -U -P -l 'createResourcesRelationship\((?:(?!createResourcesRelationship\(|foreignKeyField)[\s\S])*?allowCycle: true(?:(?!createResourcesRelationship\(|foreignKeyField)[\s\S])*(?=createResourcesRelationship\(|\z)' ./shared-lib/src/modules --glob '*.relationships.ts'
531
533
 
532
- # a lateral reference to a non-tenant-scoped target that does NOT confine itself
533
- rg -A 8 "foreignKeyField: '(assignedTo|sharedWith|reviewer|owner)\w*'" ./shared-lib/src/modules/**/*.relationships.ts | rg -L "scopeMembership"
534
+ # a lateral reference to a non-tenant-scoped target that does NOT confine itself (must return empty)
535
+ rg -U -P -l "createResourcesRelationship\((?:(?!createResourcesRelationship\(|scopeMembership)[\s\S])*?foreignKeyField: '(?:assignedTo|sharedWith|reviewer|owner)\w*'(?:(?!createResourcesRelationship\(|scopeMembership)[\s\S])*(?=createResourcesRelationship\(|\z)" ./shared-lib/src/modules --glob '*.relationships.ts'
534
536
 
535
537
  # a per-variant policy naming a foreign key no relationship confines is INERT
536
538
  rg -A 4 "referenceConstraints" ./shared-lib/src/modules/**/*.resources-config.ts
@@ -64,7 +64,7 @@ metrics, `DataSeedRun` ledger queries) is covered by
64
64
 
65
65
  | Surface | Glob (relative to app root) |
66
66
  |----------------------------|-------------------------------------------------------------------------------------------------------------------|
67
- | Seed declaration | `backend-api/src/modules/<module>/seeds/<seed-key>.seed.ts` (recommended: one file per seed; default-export the `DataSeedDefinition`. No factory-enforced naming yet — pick a stable convention per module.) |
67
+ | Seed declaration | `backend-api/src/modules/<module>/seeds/<seedKey with ':' as '.'>.seed.ts` — `crm:demo-customers` lives in `crm.demo-customers.seed.ts`. One file per seed. A build task that produces a seed is proven landed by THIS name and by the module importing it, so follow it exactly. |
68
68
  | Module seed aggregator | `backend-api/src/modules/<module>/seeds/index.ts` (recommended: default-export `DataSeedDefinition[]` so the backend module record can `seeds: <module>Seeds`) |
69
69
  | Resource schema (business key) | `shared-lib/src/modules/<module>/resources/<resource>/<resource>.schemas.ts` (`isBusinessKey()` / `businessKeySet([...])`) |
70
70
  | Module backend record | `backend-api/src/modules/<module>/index.ts` — `seeds?: DataSeedDefinition[]` slot on the typed `BackendDomainModule` (the wrapper exposed via `BackendOwnedModule.backendModule`). Aggregated by `mergeBackendDomainModules` and threaded through `ApplicationInitializationConfig.dataSeeds`. |
@@ -72,6 +72,8 @@ metrics, `DataSeedRun` ledger queries) is covered by
72
72
  ## When to Use
73
73
 
74
74
  - Adding a new seed (any mode, any level)
75
+ - Giving a freshly created application demonstration data — sample rows
76
+ that must never reach production (Decision 6)
75
77
  - Changing the business key on a seeded resource (must ship a
76
78
  `renames[]` entry on every seed targeting that resource)
77
79
  - Bumping `version` on a UPGRADE seed (must verify migrators cover
@@ -92,7 +94,7 @@ metrics, `DataSeedRun` ledger queries) is covered by
92
94
  - Adding `__seed` overlay to user-authored data (non-seed) → the
93
95
  overlay is dispatcher-managed; never write it from app code
94
96
 
95
- ## The Five Authoring Decisions
97
+ ## The Six Authoring Decisions
96
98
 
97
99
  ### Decision 1: Level — A vs B
98
100
 
@@ -247,6 +249,20 @@ Factory-time invariants (rejected with actionable errors):
247
249
  - `rename.to` MUST appear as a declared business-key value in
248
250
  `entries[*].businessKey` (catches typos like `'welcome-emai'`).
249
251
 
252
+ ### Decision 6: Where may these rows exist? — reference vs demonstration
253
+
254
+ | Kind | What it is | `allowedApplicationEnvironments` |
255
+ |------|------------|----------------------------------|
256
+ | Reference data | rows the application needs to work: a closed list stored as rows, a default record | OMIT — every environment, production included |
257
+ | Demonstration data | sample rows that make a fresh application look lived-in (customers, projects) | DECLARE, without `RuntimeEnvironment.PRODUCTION` — e.g. development and staging |
258
+
259
+ A restricted seed is withheld at registration in every other environment, so no trigger, schedule
260
+ or manual run reaches it there, and it is withheld when the deployment declares no environment at
261
+ all. Never mix the two kinds in one seed: the restriction applies to every row the seed writes.
262
+ For demonstration data, `ADDITIVE` at `ON_APP_INIT` with `existingRowTreatment: FILL_MISSING_DEFAULTS`
263
+ is the usual shape — people edit sample rows while trying the application, and the default
264
+ treatment would re-stamp them on every pass. `RuntimeEnvironment` comes from `@wildo-ai/saas-models`.
265
+
250
266
  ## Workflow
251
267
 
252
268
  ### Step 1: Confirm the resource has a business key
@@ -337,8 +353,10 @@ dedicated example file co-located with the runtime contract:
337
353
  ## Usage Example
338
354
 
339
355
  ```typescript
356
+ import { RuntimeEnvironment } from '@wildo-ai/saas-models';
340
357
  import {
341
358
  createDataSeedDefinition,
359
+ DataSeedExistingRowTreatment,
342
360
  DataSeedMode,
343
361
  DataSeedResourceLifecyclePhase,
344
362
  DataSeedScopeKind,
@@ -443,7 +461,33 @@ const organizationDefaultWorkspaceSeed = createDataSeedDefinition({
443
461
  }),
444
462
  });
445
463
 
446
- export { organizationDefaultWorkspaceSeed, systemEmailTemplatesSeed };
464
+ // ─────────────────────────────────────────────────────────────────────
465
+ // Demonstration data — sample rows that make a freshly created application
466
+ // look lived-in, kept OUT of production by `allowedApplicationEnvironments`.
467
+ // Without it these customers would be inserted beside real ones the first
468
+ // time the application starts in production. A restricted seed is withheld
469
+ // at registration, so no trigger, schedule or manual run can reach it there.
470
+ //
471
+ // `FILL_MISSING_DEFAULTS`: a person edits demo rows while trying the app, and
472
+ // the default treatment would re-stamp the declared payload over their edits
473
+ // on every pass.
474
+ // ─────────────────────────────────────────────────────────────────────
475
+ const demoCustomersSeed = createDataSeedDefinition({
476
+ seedKey: 'crm:demo-customers',
477
+ scope: { kind: DataSeedScopeKind.APPLICATION },
478
+ resourceType: 'customer',
479
+ triggers: [{ triggerKind: DataSeedTriggerKind.ON_APP_INIT }],
480
+ mode: DataSeedMode.ADDITIVE,
481
+ version: 1,
482
+ existingRowTreatment: DataSeedExistingRowTreatment.FILL_MISSING_DEFAULTS,
483
+ allowedApplicationEnvironments: [RuntimeEnvironment.DEVELOPMENT, RuntimeEnvironment.STAGING],
484
+ entries: [
485
+ { businessKey: { email: 'ana.martin@example.com' }, data: { name: 'Ana Martin', company: 'Martin Renovations' } },
486
+ { businessKey: { email: 'luc.bernard@example.com' }, data: { name: 'Luc Bernard', company: 'Bernard Plumbing' } },
487
+ ],
488
+ });
489
+
490
+ export { demoCustomersSeed, organizationDefaultWorkspaceSeed, systemEmailTemplatesSeed };
447
491
  ```
448
492
 
449
493
  What earns its place in this block:
@@ -509,6 +553,7 @@ What is **not** in this block (and shouldn't be):
509
553
  - [ ] SYNC seeds declare `onOrphan` explicitly
510
554
  - [ ] `renames[*].field` is a business-key field on the resource
511
555
  - [ ] `renames[*].to` matches a declared `entries[*].businessKey[field]`
556
+ - [ ] A demonstration seed declares `allowedApplicationEnvironments` without `production`; a reference seed omits it
512
557
  - [ ] Seed surfaced on the module's `BackendDomainModule.seeds?: DataSeedDefinition[]` slot
513
558
  (aggregated by `mergeBackendDomainModules` and threaded into the assembly's `dataSeeds`)
514
559
 
@@ -523,6 +568,7 @@ Run from the app root, substituting `<module>` and `<seed-key>`:
523
568
  | Seed file does NOT import from the package root | `rg -n "from '@wildo-ai/saas-backend-lib'" backend-api/src/modules/<module>/seeds/` (must be empty for seed files) |
524
569
  | Resource schema declares a business key | `rg -n 'isBusinessKey\(\)\|businessKeySet\(' shared-lib/src/modules/<module>/resources/<resource>/<resource>.schemas.ts` |
525
570
  | Module record wires `seeds` | `rg -n '\bseeds\s*:' backend-api/src/modules/<module>/index.ts` |
571
+ | Demonstration seeds are kept out of production | `rg --files-without-match 'allowedApplicationEnvironments' backend-api/src/modules/<module>/seeds/*demo*.seed.ts` (must be empty); `rg -n 'RuntimeEnvironment.PRODUCTION' backend-api/src/modules/<module>/seeds/*demo*.seed.ts` (must be empty) |
526
572
 
527
573
  The high-signal invariants are **"resource schema declares a
528
574
  business key"** combined with **"seed file uses
@@ -560,6 +606,8 @@ with an actionable error.
560
606
  - Seed declared on a resource with cascade-delete relationships and
561
607
  no `onOrphan: REPORT` first pass to confirm the orphan set is
562
608
  empty
609
+ - A demonstration seed with no `allowedApplicationEnvironments`, or one that lists
610
+ production (its sample rows land beside real ones; catch with the demonstration-seed grep above)
563
611
  - `schedule.cron` declared on a LAZY seed (factory rejects — LAZY's
564
612
  contract is "first access creates the row, never re-applied")
565
613
 
@@ -132,6 +132,12 @@ export enum DataSeedMode {
132
132
  * - `schedule` — optional cron-driven re-run binding; presence is the
133
133
  * sole opt-in signal for the engine cron batch. FORBIDDEN for
134
134
  * `mode === LAZY`.
135
+ * - `allowedApplicationEnvironments` — optional; omit for reference data the
136
+ * application needs everywhere. DEMONSTRATION data (sample rows that make a
137
+ * fresh application look lived-in) MUST declare it without `production`, e.g.
138
+ * `[RuntimeEnvironment.DEVELOPMENT, RuntimeEnvironment.STAGING]` (import
139
+ * `RuntimeEnvironment` from `@wildo-ai/saas-models`). A restricted seed is never
140
+ * registered elsewhere, and is withheld when the deployment declares no environment.
135
141
  */
136
142
  export interface DataSeedDefinitionInput extends DataSeedDefinitionAuthored, DataSeedDefinitionCallbacks {}
137
143
 
@@ -641,7 +641,13 @@ export function wireDataSeedingDeclarations(
641
641
  * of the collision a reader can act on.
642
642
  */
643
643
  const engineOwned = registersEngineOwnedSeeds ? ENGINE_OWNED_DATA_SEEDS : [];
644
- const seeds = [...engineOwned, ...(dataSeeds ?? [])];
644
+ /*
645
+ * Admitted over the MERGED list (#2234), so a restricted seed is withheld at registration whoever owns it — the
646
+ * promise `allowedApplicationEnvironments` makes. The application's own seeds were already admitted where
647
+ * `start-application` took them (its seeding gates read that set); re-admitting them here is idempotent, and it is
648
+ * what reaches the engine's.
649
+ */
650
+ const seeds = admitDataSeedsForApplicationEnvironment([...engineOwned, ...(dataSeeds ?? [])], readDeclaredApplicationEnvironment(process.env)).admitted;
645
651
  logDebug('🌱 Registering data-seed definitions...', {
646
652
  count: seeds.length,
647
653
  engineOwned: engineOwned.length,
@@ -121,6 +121,8 @@ export interface SpecificationsCompanionExports<
121
121
  TIntegrationPlan = IntegrationPlan,
122
122
  // Appended STRICTLY LAST: where the application stands against its own requirements (#1496).
123
123
  TApplicationMaturity = ApplicationMaturity,
124
+ // Appended STRICTLY LAST: the screened brand-name candidates the brand-identity interview chooses from.
125
+ TBrandNameScreening = BrandNameScreening,
124
126
  > {
125
127
  resourceSpecifications: TResourceSpecifications;
126
128
  applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
@@ -651,6 +653,14 @@ export interface SpecificationsCompanionExports<
651
653
  * never a gate. Read by the coherence report and the workbench.
652
654
  */
653
655
  applicationMaturity?: TApplicationMaturity;
656
+ /**
657
+ * WHICH NAMES were proposed for the brand and what a minimal trademark screening of each found —
658
+ * registers, classes and jurisdictions searched, per-register results with sources and dates, and the
659
+ * competitor collisions beside them. Produced by `top_down.brand-naming`; the brand-identity interview's
660
+ * `brand-name` CHOICE is computed from it, and the coherence report reads it to say where the chosen
661
+ * brand name stands. A screening, never a legal clearance opinion.
662
+ */
663
+ brandNameScreening?: TBrandNameScreening;
654
664
  /**
655
665
  * Accepted application-declared semantic causality between whole
656
666
  * specification-family states. This is not the registry's physical
@@ -101,6 +101,8 @@ export interface DefineWebsiteSectionInput<TProps> {
101
101
  sectionRef: WebsiteSectionRef | string;
102
102
  category: WebsiteSectionCategory;
103
103
  expectedLabelKeys: readonly (WebsiteLabelKey | string)[];
104
+ /** The section's DOM id, so a link can target it (`<a href="#tiers">`). See `WebsiteSectionDefinition.anchorId`. */
105
+ anchorId?: string;
104
106
  Component: ComponentType<TProps>;
105
107
  /**
106
108
  * See `WebsiteSectionDefinition.getStructuredData?` JSDoc for the
@@ -183,6 +185,7 @@ export function defineWebsiteSection<TProps>(
183
185
  sectionRef: input.sectionRef,
184
186
  category: input.category,
185
187
  expectedLabelKeys: input.expectedLabelKeys,
188
+ anchorId: input.anchorId,
186
189
  Component: input.Component,
187
190
  getStructuredData: input.getStructuredData,
188
191
  });
@@ -195,6 +198,7 @@ export function defineWebsiteSection<TProps>(
195
198
  sectionRef: parsed.sectionRef,
196
199
  category: parsed.category,
197
200
  expectedLabelKeys: parsed.expectedLabelKeys,
201
+ ...(parsed.anchorId !== undefined ? { anchorId: parsed.anchorId } : {}),
198
202
  Component: input.Component,
199
203
  ...(input.getStructuredData ? { getStructuredData: input.getStructuredData } : {}),
200
204
  };
@@ -59,10 +59,19 @@ each with the skill that authors it. The plan split the page into sections on pu
59
59
 
60
60
  - **Author the page, not its sections.** Write the route, bridge, page component and manifest,
61
61
  register the page, and create `<page>.sections.tsx` with an empty sections list the page
62
- renders from — registered in `sections/index.ts` (re-exported, and spread into
62
+ renders from, DECLARED WITH ITS TYPE — `export const HOME_SECTIONS: readonly
63
+ WebsiteSectionDefinition[] = [];` — because an unannotated empty array is `never[]` and the
64
+ page that maps over it does not compile until the first section lands. Register it in
65
+ `sections/index.ts` (re-exported, and spread into
63
66
  `WEBSITE_SECTIONS`), or the label audit never sees the page's sections. Each section is its
64
67
  own build task, authored with its own `website-section-*` skill, and it adds itself to that
65
68
  list.
69
+ - **Render the list through `<WebsitePageSections pageRef="home" sections={HOME_SECTIONS} />`**,
70
+ never a hand-written `map`. While the list is empty the page shows a marked pending block, so
71
+ `astro dev` serves it, and the page visibly says its sections are still to come. `astro build`
72
+ refuses a page with no section: publish only once each page has one. A section an in-page link
73
+ targets (`<a href="#tiers">`) declares `anchorId: 'tiers'` in its `defineWebsiteSection` call;
74
+ the component turns it into the section's DOM `id`.
66
75
  - **Keep the plan's identities.** The plan says `page-home`; the tree spells the page `home`
67
76
  (`home.page.tsx`, `HOME_PAGE_MANIFEST`, `home.sections.tsx`). Section refs are used verbatim.
68
77
  - **Do not re-decide the message.** Purpose, audience and tone were decided from the market
@@ -531,6 +540,77 @@ function renderConsentSurface(
531
540
  }
532
541
  ```
533
542
 
543
+ ## Import Origins
544
+
545
+ - `@wildo-ai/saas-website`
546
+
547
+ ## Source Excerpts
548
+
549
+ ### Origin Package: `@wildo-ai/saas-website`
550
+
551
+ ```tsx
552
+ *
553
+ * `WebsitePageSections` — renders a page's ordered sections list, each inside its `WebsiteSection`
554
+ * wrapper, and a visible PENDING marker while the list is still empty.
555
+ *
556
+ * A page component should render its sections through this rather than mapping the list by hand:
557
+ *
558
+ * ```tsx
559
+ * export function PricingPage(): ReactNode {
560
+ * return <WebsitePageSections pageRef="pricing" sections={PRICING_SECTIONS} />;
561
+ * }
562
+ * ```
563
+ *
564
+ * **Why the empty state is the point.** A page's sections list starts EMPTY when its page
565
+ * is authored before its sections — the application-creation build lane does exactly that, one task
566
+ * per page and one per section. An empty page is a valid manifest and a dev server serves it; the
567
+ * production build refuses it (`assertWebsitePagesHaveSections`). Mapped by hand, an empty list
568
+ * renders nothing at all, which is indistinguishable from a page that failed. This renders a
569
+ * marked block instead, so the page visibly says its sections are still to come.
570
+ *
571
+ * A section's `anchorId`, declared on its definition, becomes the wrapper's DOM `id`, so in-page links
572
+ * still have a target when no page places its sections by hand.
573
+ *
574
+ * **The marker carries identifiers, not prose.** It shows the page ref and the empty list as code,
575
+ * deliberately: words a person reads come from the label packs, and a label for a state no built
576
+ * page can ever reach (the build refuses an empty page) would be a key every locale must carry for
577
+ * nothing. A missing section must LOOK missing, which a raw identifier does.
578
+ */
579
+ export interface WebsitePageSectionsProps {
580
+ /** The page's ref, as its manifest declares it. Shown in the pending marker. */
581
+ pageRef: string;
582
+ /** The page's ordered sections list — the same array its manifest's `sectionRefs` derive from. */
583
+ sections: readonly WebsiteSectionDefinition[];
584
+ }
585
+
586
+ export function WebsitePageSections({ pageRef, sections }: WebsitePageSectionsProps): ReactNode {
587
+ if (sections.length === 0) {
588
+ return (
589
+ <section
590
+ data-website-pending-page={pageRef}
591
+ aria-busy="true"
592
+ style={{ margin: '2rem auto', maxWidth: '48rem', padding: '2rem', border: '2px dashed currentColor', opacity: 0.6, textAlign: 'center' }}
593
+ >
594
+ <code>{`${pageRef}: sections = []`}</code>
595
+ </section>
596
+ );
597
+ }
598
+ return (
599
+ <>
600
+ {sections.map((section) => {
601
+ const SectionComponent = section.Component as React.ComponentType;
602
+ return (
603
+ <WebsiteSection key={String(section.sectionRef)} sectionRef={section.sectionRef} category={section.category} id={section.anchorId}>
604
+ <SectionComponent />
605
+ </WebsiteSection>
606
+ );
607
+ })}
608
+ </>
609
+ );
610
+ }
611
+ WebsitePageSections.displayName = 'WebsitePageSections';
612
+ ```
613
+
534
614
  These source-backed contracts are the page-manifest and structural composition
535
615
  authority for the workflow below.
536
616
 
@@ -549,9 +629,10 @@ authority for the workflow below.
549
629
  |---|---|
550
630
  | Page has a manifest declaration | `rg -n "defineWebsitePageManifest" website/src/pages-impl/` (must include the new page) |
551
631
  | Page is registered | `rg -n "_PAGE_MANIFEST" website/src/website-root.config.ts` (must include the new page) |
552
- | Every route forwards both origins | `rg -L "apiOrigin=\{WEBSITE_SITE_CONTEXT" website/src/pages --glob '*.astro'` (must print nothing) |
632
+ | Every route forwards both origins | `rg --files-without-match "apiOrigin=\{WEBSITE_SITE_CONTEXT" website/src/pages --glob '*.astro'` (must print nothing) |
553
633
  | No hardcoded host in pages | `rg -n "localhost:[0-9]" website/src --glob "!**/generated/**"` (must print nothing; the generated CSP legitimately names the local backend) |
554
- | Labels complete in every locale | `wildo website audit` (exit 0) |
634
+ | Page renders through `WebsitePageSections` | `rg --files-without-match "WebsitePageSections" website/src/pages-impl --glob '*.page.tsx' --glob '!blog-post.page.tsx'` (must print nothing; a hand-written map renders an empty page blank. The blog post page renders one post, not a sections list) |
635
+ | Labels complete in every locale, no empty page | `wildo website audit` (exit 0; it fails a page with no section, which `astro build` refuses) |
555
636
  | Discovery entry is deliberate | `rg -n "^## " website/src/content/llms.txt` (must include the page title where public) |
556
637
 
557
638
  ## Common Rationalizations
@@ -155,6 +155,14 @@ compile-time prop checking.
155
155
  * and is caught by nothing until a reviewer reads the page. The
156
156
  * build and `wildo website audit` check the pack against the
157
157
  * DECLARED keys, so declare every slot the component reads.
158
+ * - `anchorId?` — the section's DOM id, so a link (`<a href="#tiers">`)
159
+ * can target it. Belongs to the DEFINITION because a page renders its
160
+ * sections list through `WebsitePageSections`, which places every
161
+ * section itself: an anchor a page author would otherwise write on a
162
+ * hand-placed `<WebsiteSection id=…>` has nowhere else to live. A
163
+ * valid HTML id that is also URL-fragment-safe: a letter, then
164
+ * letters, digits, `-` or `_`. Uniqueness on a page is the author's
165
+ * to keep, like the id attribute it becomes.
158
166
  * - `Component` — the React component that renders the section. Typed
159
167
  * as `ComponentType<unknown>` here because schema-layer cannot lock
160
168
  * the component's prop shape (props vary per section). The factory
@@ -181,6 +189,9 @@ const _WebsiteSectionDefinitionSchema = z.object({
181
189
  sectionRef: WebsiteSectionRefSchema,
182
190
  category: WebsiteSectionCategorySchema,
183
191
  expectedLabelKeys: z.array(WebsiteLabelKeySchema).readonly(),
192
+ anchorId: z.string().regex(/^[A-Za-z][A-Za-z0-9_-]*$/, {
193
+ error: 'A section anchorId must start with a letter and contain only letters, digits, "-" or "_"',
194
+ }).optional(),
184
195
  Component: z.unknown(),
185
196
  getStructuredData: z.unknown().optional(),
186
197
  });
@@ -269,6 +280,8 @@ export interface DefineWebsiteSectionInput<TProps> {
269
280
  sectionRef: WebsiteSectionRef | string;
270
281
  category: WebsiteSectionCategory;
271
282
  expectedLabelKeys: readonly (WebsiteLabelKey | string)[];
283
+ /** The section's DOM id, so a link can target it (`<a href="#tiers">`). See `WebsiteSectionDefinition.anchorId`. */
284
+ anchorId?: string;
272
285
  Component: ComponentType<TProps>;
273
286
  /**
274
287
  * See `WebsiteSectionDefinition.getStructuredData?` JSDoc for the
@@ -351,6 +364,7 @@ export function defineWebsiteSection<TProps>(
351
364
  sectionRef: input.sectionRef,
352
365
  category: input.category,
353
366
  expectedLabelKeys: input.expectedLabelKeys,
367
+ anchorId: input.anchorId,
354
368
  Component: input.Component,
355
369
  getStructuredData: input.getStructuredData,
356
370
  });
@@ -363,6 +377,7 @@ export function defineWebsiteSection<TProps>(
363
377
  sectionRef: parsed.sectionRef,
364
378
  category: parsed.category,
365
379
  expectedLabelKeys: parsed.expectedLabelKeys,
380
+ ...(parsed.anchorId !== undefined ? { anchorId: parsed.anchorId } : {}),
366
381
  Component: input.Component,
367
382
  ...(input.getStructuredData ? { getStructuredData: input.getStructuredData } : {}),
368
383
  };
@@ -137,6 +137,14 @@ compile-time prop checking.
137
137
  * and is caught by nothing until a reviewer reads the page. The
138
138
  * build and `wildo website audit` check the pack against the
139
139
  * DECLARED keys, so declare every slot the component reads.
140
+ * - `anchorId?` — the section's DOM id, so a link (`<a href="#tiers">`)
141
+ * can target it. Belongs to the DEFINITION because a page renders its
142
+ * sections list through `WebsitePageSections`, which places every
143
+ * section itself: an anchor a page author would otherwise write on a
144
+ * hand-placed `<WebsiteSection id=…>` has nowhere else to live. A
145
+ * valid HTML id that is also URL-fragment-safe: a letter, then
146
+ * letters, digits, `-` or `_`. Uniqueness on a page is the author's
147
+ * to keep, like the id attribute it becomes.
140
148
  * - `Component` — the React component that renders the section. Typed
141
149
  * as `ComponentType<unknown>` here because schema-layer cannot lock
142
150
  * the component's prop shape (props vary per section). The factory
@@ -163,6 +171,9 @@ const _WebsiteSectionDefinitionSchema = z.object({
163
171
  sectionRef: WebsiteSectionRefSchema,
164
172
  category: WebsiteSectionCategorySchema,
165
173
  expectedLabelKeys: z.array(WebsiteLabelKeySchema).readonly(),
174
+ anchorId: z.string().regex(/^[A-Za-z][A-Za-z0-9_-]*$/, {
175
+ error: 'A section anchorId must start with a letter and contain only letters, digits, "-" or "_"',
176
+ }).optional(),
166
177
  Component: z.unknown(),
167
178
  getStructuredData: z.unknown().optional(),
168
179
  });
@@ -251,6 +262,8 @@ export interface DefineWebsiteSectionInput<TProps> {
251
262
  sectionRef: WebsiteSectionRef | string;
252
263
  category: WebsiteSectionCategory;
253
264
  expectedLabelKeys: readonly (WebsiteLabelKey | string)[];
265
+ /** The section's DOM id, so a link can target it (`<a href="#tiers">`). See `WebsiteSectionDefinition.anchorId`. */
266
+ anchorId?: string;
254
267
  Component: ComponentType<TProps>;
255
268
  /**
256
269
  * See `WebsiteSectionDefinition.getStructuredData?` JSDoc for the
@@ -333,6 +346,7 @@ export function defineWebsiteSection<TProps>(
333
346
  sectionRef: input.sectionRef,
334
347
  category: input.category,
335
348
  expectedLabelKeys: input.expectedLabelKeys,
349
+ anchorId: input.anchorId,
336
350
  Component: input.Component,
337
351
  getStructuredData: input.getStructuredData,
338
352
  });
@@ -345,6 +359,7 @@ export function defineWebsiteSection<TProps>(
345
359
  sectionRef: parsed.sectionRef,
346
360
  category: parsed.category,
347
361
  expectedLabelKeys: parsed.expectedLabelKeys,
362
+ ...(parsed.anchorId !== undefined ? { anchorId: parsed.anchorId } : {}),
348
363
  Component: input.Component,
349
364
  ...(input.getStructuredData ? { getStructuredData: input.getStructuredData } : {}),
350
365
  };
@@ -155,6 +155,14 @@ compile-time prop checking.
155
155
  * and is caught by nothing until a reviewer reads the page. The
156
156
  * build and `wildo website audit` check the pack against the
157
157
  * DECLARED keys, so declare every slot the component reads.
158
+ * - `anchorId?` — the section's DOM id, so a link (`<a href="#tiers">`)
159
+ * can target it. Belongs to the DEFINITION because a page renders its
160
+ * sections list through `WebsitePageSections`, which places every
161
+ * section itself: an anchor a page author would otherwise write on a
162
+ * hand-placed `<WebsiteSection id=…>` has nowhere else to live. A
163
+ * valid HTML id that is also URL-fragment-safe: a letter, then
164
+ * letters, digits, `-` or `_`. Uniqueness on a page is the author's
165
+ * to keep, like the id attribute it becomes.
158
166
  * - `Component` — the React component that renders the section. Typed
159
167
  * as `ComponentType<unknown>` here because schema-layer cannot lock
160
168
  * the component's prop shape (props vary per section). The factory
@@ -181,6 +189,9 @@ const _WebsiteSectionDefinitionSchema = z.object({
181
189
  sectionRef: WebsiteSectionRefSchema,
182
190
  category: WebsiteSectionCategorySchema,
183
191
  expectedLabelKeys: z.array(WebsiteLabelKeySchema).readonly(),
192
+ anchorId: z.string().regex(/^[A-Za-z][A-Za-z0-9_-]*$/, {
193
+ error: 'A section anchorId must start with a letter and contain only letters, digits, "-" or "_"',
194
+ }).optional(),
184
195
  Component: z.unknown(),
185
196
  getStructuredData: z.unknown().optional(),
186
197
  });
@@ -269,6 +280,8 @@ export interface DefineWebsiteSectionInput<TProps> {
269
280
  sectionRef: WebsiteSectionRef | string;
270
281
  category: WebsiteSectionCategory;
271
282
  expectedLabelKeys: readonly (WebsiteLabelKey | string)[];
283
+ /** The section's DOM id, so a link can target it (`<a href="#tiers">`). See `WebsiteSectionDefinition.anchorId`. */
284
+ anchorId?: string;
272
285
  Component: ComponentType<TProps>;
273
286
  /**
274
287
  * See `WebsiteSectionDefinition.getStructuredData?` JSDoc for the
@@ -351,6 +364,7 @@ export function defineWebsiteSection<TProps>(
351
364
  sectionRef: input.sectionRef,
352
365
  category: input.category,
353
366
  expectedLabelKeys: input.expectedLabelKeys,
367
+ anchorId: input.anchorId,
354
368
  Component: input.Component,
355
369
  getStructuredData: input.getStructuredData,
356
370
  });
@@ -363,6 +377,7 @@ export function defineWebsiteSection<TProps>(
363
377
  sectionRef: parsed.sectionRef,
364
378
  category: parsed.category,
365
379
  expectedLabelKeys: parsed.expectedLabelKeys,
380
+ ...(parsed.anchorId !== undefined ? { anchorId: parsed.anchorId } : {}),
366
381
  Component: input.Component,
367
382
  ...(input.getStructuredData ? { getStructuredData: input.getStructuredData } : {}),
368
383
  };
@@ -137,6 +137,14 @@ compile-time prop checking.
137
137
  * and is caught by nothing until a reviewer reads the page. The
138
138
  * build and `wildo website audit` check the pack against the
139
139
  * DECLARED keys, so declare every slot the component reads.
140
+ * - `anchorId?` — the section's DOM id, so a link (`<a href="#tiers">`)
141
+ * can target it. Belongs to the DEFINITION because a page renders its
142
+ * sections list through `WebsitePageSections`, which places every
143
+ * section itself: an anchor a page author would otherwise write on a
144
+ * hand-placed `<WebsiteSection id=…>` has nowhere else to live. A
145
+ * valid HTML id that is also URL-fragment-safe: a letter, then
146
+ * letters, digits, `-` or `_`. Uniqueness on a page is the author's
147
+ * to keep, like the id attribute it becomes.
140
148
  * - `Component` — the React component that renders the section. Typed
141
149
  * as `ComponentType<unknown>` here because schema-layer cannot lock
142
150
  * the component's prop shape (props vary per section). The factory
@@ -163,6 +171,9 @@ const _WebsiteSectionDefinitionSchema = z.object({
163
171
  sectionRef: WebsiteSectionRefSchema,
164
172
  category: WebsiteSectionCategorySchema,
165
173
  expectedLabelKeys: z.array(WebsiteLabelKeySchema).readonly(),
174
+ anchorId: z.string().regex(/^[A-Za-z][A-Za-z0-9_-]*$/, {
175
+ error: 'A section anchorId must start with a letter and contain only letters, digits, "-" or "_"',
176
+ }).optional(),
166
177
  Component: z.unknown(),
167
178
  getStructuredData: z.unknown().optional(),
168
179
  });
@@ -251,6 +262,8 @@ export interface DefineWebsiteSectionInput<TProps> {
251
262
  sectionRef: WebsiteSectionRef | string;
252
263
  category: WebsiteSectionCategory;
253
264
  expectedLabelKeys: readonly (WebsiteLabelKey | string)[];
265
+ /** The section's DOM id, so a link can target it (`<a href="#tiers">`). See `WebsiteSectionDefinition.anchorId`. */
266
+ anchorId?: string;
254
267
  Component: ComponentType<TProps>;
255
268
  /**
256
269
  * See `WebsiteSectionDefinition.getStructuredData?` JSDoc for the
@@ -333,6 +346,7 @@ export function defineWebsiteSection<TProps>(
333
346
  sectionRef: input.sectionRef,
334
347
  category: input.category,
335
348
  expectedLabelKeys: input.expectedLabelKeys,
349
+ anchorId: input.anchorId,
336
350
  Component: input.Component,
337
351
  getStructuredData: input.getStructuredData,
338
352
  });
@@ -345,6 +359,7 @@ export function defineWebsiteSection<TProps>(
345
359
  sectionRef: parsed.sectionRef,
346
360
  category: parsed.category,
347
361
  expectedLabelKeys: parsed.expectedLabelKeys,
362
+ ...(parsed.anchorId !== undefined ? { anchorId: parsed.anchorId } : {}),
348
363
  Component: input.Component,
349
364
  ...(input.getStructuredData ? { getStructuredData: input.getStructuredData } : {}),
350
365
  };
@@ -155,6 +155,14 @@ compile-time prop checking.
155
155
  * and is caught by nothing until a reviewer reads the page. The
156
156
  * build and `wildo website audit` check the pack against the
157
157
  * DECLARED keys, so declare every slot the component reads.
158
+ * - `anchorId?` — the section's DOM id, so a link (`<a href="#tiers">`)
159
+ * can target it. Belongs to the DEFINITION because a page renders its
160
+ * sections list through `WebsitePageSections`, which places every
161
+ * section itself: an anchor a page author would otherwise write on a
162
+ * hand-placed `<WebsiteSection id=…>` has nowhere else to live. A
163
+ * valid HTML id that is also URL-fragment-safe: a letter, then
164
+ * letters, digits, `-` or `_`. Uniqueness on a page is the author's
165
+ * to keep, like the id attribute it becomes.
158
166
  * - `Component` — the React component that renders the section. Typed
159
167
  * as `ComponentType<unknown>` here because schema-layer cannot lock
160
168
  * the component's prop shape (props vary per section). The factory
@@ -181,6 +189,9 @@ const _WebsiteSectionDefinitionSchema = z.object({
181
189
  sectionRef: WebsiteSectionRefSchema,
182
190
  category: WebsiteSectionCategorySchema,
183
191
  expectedLabelKeys: z.array(WebsiteLabelKeySchema).readonly(),
192
+ anchorId: z.string().regex(/^[A-Za-z][A-Za-z0-9_-]*$/, {
193
+ error: 'A section anchorId must start with a letter and contain only letters, digits, "-" or "_"',
194
+ }).optional(),
184
195
  Component: z.unknown(),
185
196
  getStructuredData: z.unknown().optional(),
186
197
  });
@@ -269,6 +280,8 @@ export interface DefineWebsiteSectionInput<TProps> {
269
280
  sectionRef: WebsiteSectionRef | string;
270
281
  category: WebsiteSectionCategory;
271
282
  expectedLabelKeys: readonly (WebsiteLabelKey | string)[];
283
+ /** The section's DOM id, so a link can target it (`<a href="#tiers">`). See `WebsiteSectionDefinition.anchorId`. */
284
+ anchorId?: string;
272
285
  Component: ComponentType<TProps>;
273
286
  /**
274
287
  * See `WebsiteSectionDefinition.getStructuredData?` JSDoc for the
@@ -351,6 +364,7 @@ export function defineWebsiteSection<TProps>(
351
364
  sectionRef: input.sectionRef,
352
365
  category: input.category,
353
366
  expectedLabelKeys: input.expectedLabelKeys,
367
+ anchorId: input.anchorId,
354
368
  Component: input.Component,
355
369
  getStructuredData: input.getStructuredData,
356
370
  });
@@ -363,6 +377,7 @@ export function defineWebsiteSection<TProps>(
363
377
  sectionRef: parsed.sectionRef,
364
378
  category: parsed.category,
365
379
  expectedLabelKeys: parsed.expectedLabelKeys,
380
+ ...(parsed.anchorId !== undefined ? { anchorId: parsed.anchorId } : {}),
366
381
  Component: input.Component,
367
382
  ...(input.getStructuredData ? { getStructuredData: input.getStructuredData } : {}),
368
383
  };