fix(data): regenerate stale anchor metadata, sitemap, and llms.txt

Several anchors (kano-model, double-diamond, hoshin-kanri,
kotter-8-step-change-model, decisional-balance-sheet and others) were
added as .adoc files without rerunning extract-metadata.js, so the
committed data files drifted out of sync — 15 anchors missing from
anchors.json / categories.json and from llms.txt.

The deployed site was unaffected: CI runs extract-metadata.js,
generate-sitemap.js and generate-llms-txt.js before building, so
production always regenerates these. The staleness only affected the
committed copies (which `npm run dev` reads directly) and made the
repo misleading to read.

Regenerated all four data files plus sitemap.xml and llms.txt.
anchors.json now holds all 147 anchors.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: raifdmueller

website/public/data/anchors.json

@@ -449,6 +449,37 @@
     "filePath": "docs/anchors/cynefin-framework.adoc",
     "tier": 3
   },
+  {
+    "id": "decisional-balance-sheet",
+    "title": "Decisional Balance Sheet",
+    "categories": [
+      "problem-solving",
+      "strategic-planning"
+    ],
+    "roles": [
+      "consultant",
+      "team-lead",
+      "product-owner",
+      "business-analyst"
+    ],
+    "related": [
+      "pugh-matrix",
+      "adr-according-to-nygard",
+      "moscow"
+    ],
+    "proponents": [
+      "Irving Janis",
+      "Leon Mann"
+    ],
+    "tags": [
+      "decision-making",
+      "pros-cons",
+      "ambivalence",
+      "motivational-interviewing"
+    ],
+    "filePath": "docs/anchors/decisional-balance-sheet.adoc",
+    "tier": 3
+  },
   {
     "id": "definition-of-done",
     "title": "Definition of Done",
@@ -552,6 +583,38 @@
     "filePath": "docs/anchors/domain-driven-design.adoc",
     "tier": 3
   },
+  {
+    "id": "double-diamond",
+    "title": "Double Diamond",
+    "categories": [
+      "problem-solving",
+      "requirements-engineering"
+    ],
+    "roles": [
+      "ux-designer",
+      "product-owner",
+      "business-analyst",
+      "consultant"
+    ],
+    "related": [
+      "jobs-to-be-done",
+      "problem-space-nvc",
+      "xy-problem",
+      "mvp"
+    ],
+    "proponents": [
+      "UK Design Council"
+    ],
+    "tags": [
+      "design-thinking",
+      "problem-framing",
+      "divergent-convergent",
+      "ux",
+      "innovation"
+    ],
+    "filePath": "docs/anchors/double-diamond.adoc",
+    "tier": 3
+  },
   {
     "id": "ears-requirements",
     "title": "EARS-Requirements",
@@ -1810,6 +1873,36 @@
     "filePath": "docs/anchors/hexagonal-architecture.adoc",
     "tier": 3
   },
+  {
+    "id": "hoshin-kanri",
+    "title": "Hoshin Kanri",
+    "categories": [
+      "strategic-planning"
+    ],
+    "roles": [
+      "team-lead",
+      "consultant",
+      "product-owner"
+    ],
+    "related": [
+      "kotter-8-step-change-model",
+      "moscow",
+      "kano-model"
+    ],
+    "proponents": [
+      "Yoji Akao",
+      "Thomas L. Jackson"
+    ],
+    "tags": [
+      "strategy-deployment",
+      "lean",
+      "alignment",
+      "x-matrix",
+      "catchball"
+    ],
+    "filePath": "docs/anchors/hoshin-kanri.adoc",
+    "tier": 3
+  },
   {
     "id": "iec-61508-sil-levels",
     "title": "IEC 61508 SIL Levels",
@@ -1943,6 +2036,36 @@
     "filePath": "docs/anchors/jobs-to-be-done.adoc",
     "tier": 3
   },
+  {
+    "id": "kano-model",
+    "title": "Kano Model",
+    "categories": [
+      "strategic-planning",
+      "requirements-engineering"
+    ],
+    "roles": [
+      "product-owner",
+      "business-analyst",
+      "ux-designer",
+      "team-lead"
+    ],
+    "related": [
+      "moscow",
+      "jobs-to-be-done",
+      "ears-requirements"
+    ],
+    "proponents": [
+      "Noriaki Kano"
+    ],
+    "tags": [
+      "customer-satisfaction",
+      "feature-prioritization",
+      "product-management",
+      "requirements"
+    ],
+    "filePath": "docs/anchors/kano-model.adoc",
+    "tier": 3
+  },
   {
     "id": "kishotenketsu",
     "title": "Kishōtenketsu",
@@ -2010,6 +2133,35 @@
     "filePath": "docs/anchors/kiss-principle.adoc",
     "tier": 1
   },
+  {
+    "id": "kotter-8-step-change-model",
+    "title": "Kotter’s 8-Step Change Model",
+    "categories": [
+      "strategic-planning"
+    ],
+    "roles": [
+      "team-lead",
+      "consultant",
+      "product-owner",
+      "business-analyst"
+    ],
+    "related": [
+      "swot",
+      "cynefin-framework",
+      "wardley-mapping"
+    ],
+    "proponents": [
+      "John P. Kotter"
+    ],
+    "tags": [
+      "change-management",
+      "transformation",
+      "leadership",
+      "organizational-change"
+    ],
+    "filePath": "docs/anchors/kotter-8-step-change-model.adoc",
+    "tier": 3
+  },
   {
     "id": "lasr",
     "title": "LASR according to Toth/Zörner",
@@ -3696,6 +3848,140 @@
     "filePath": "docs/anchors/what-would-chuck-norris-do.adoc",
     "tier": 3
   },
+  {
+    "id": "workflow-architecture-documentation",
+    "title": "Workflow: Architecture Documentation",
+    "categories": [
+      "workflow"
+    ],
+    "roles": [
+      "software-architect",
+      "technical-writer"
+    ],
+    "related": [],
+    "proponents": [
+      "Ralf D. Müller",
+      "Gernot Starke",
+      "Michael Nygard"
+    ],
+    "tags": [],
+    "filePath": "docs/anchors/workflow-architecture-documentation.adoc",
+    "tier": 3
+  },
+  {
+    "id": "workflow-code-review",
+    "title": "Workflow: Structured Code Review",
+    "categories": [
+      "workflow"
+    ],
+    "roles": [
+      "software-developer",
+      "team-lead",
+      "qa-engineer"
+    ],
+    "related": [],
+    "proponents": [
+      "Michael Fagan",
+      "Robert C. Martin"
+    ],
+    "tags": [],
+    "filePath": "docs/anchors/workflow-code-review.adoc",
+    "tier": 3
+  },
+  {
+    "id": "workflow-requirements-to-spec",
+    "title": "Workflow: Requirements to Specification",
+    "categories": [
+      "workflow"
+    ],
+    "roles": [
+      "business-analyst",
+      "product-owner",
+      "qa-engineer"
+    ],
+    "related": [],
+    "proponents": [
+      "Dan North",
+      "Jeff Patton",
+      "Mike Cohn"
+    ],
+    "tags": [],
+    "filePath": "docs/anchors/workflow-requirements-to-spec.adoc",
+    "tier": 3
+  },
+  {
+    "id": "workflow-strategic-analysis",
+    "title": "Workflow: Strategic Architecture Analysis",
+    "categories": [
+      "workflow"
+    ],
+    "roles": [
+      "software-architect",
+      "consultant",
+      "team-lead"
+    ],
+    "related": [],
+    "proponents": [
+      "Simon Wardley",
+      "Fritz Zwicky",
+      "Dave Snowden"
+    ],
+    "tags": [],
+    "filePath": "docs/anchors/workflow-strategic-analysis.adoc",
+    "tier": 3
+  },
+  {
+    "id": "workflow-tdd-clean-architecture",
+    "title": "Workflow: TDD with Clean Architecture",
+    "categories": [
+      "workflow"
+    ],
+    "roles": [
+      "software-developer",
+      "software-architect"
+    ],
+    "related": [],
+    "proponents": [
+      "Robert C. Martin",
+      "Steve Freeman",
+      "Nat Pryce"
+    ],
+    "tags": [],
+    "filePath": "docs/anchors/workflow-tdd-clean-architecture.adoc",
+    "tier": 3
+  },
+  {
+    "id": "xy-problem",
+    "title": "XY Problem",
+    "categories": [
+      "dialogue-interaction",
+      "problem-solving"
+    ],
+    "roles": [
+      "software-developer",
+      "team-lead",
+      "consultant",
+      "business-analyst"
+    ],
+    "related": [
+      "socratic-method",
+      "bluf",
+      "problem-space-nvc"
+    ],
+    "proponents": [
+      "Mark Jason Dominus",
+      "Eric S. Raymond"
+    ],
+    "tags": [
+      "communication",
+      "troubleshooting",
+      "requirements",
+      "problem-framing",
+      "anti-pattern"
+    ],
+    "filePath": "docs/anchors/xy-problem.adoc",
+    "tier": 3
+  },
   {
     "id": "yagni",
     "title": "YAGNI (You Aren’t Gonna Need It)",

website/public/data/categories.json

@@ -94,7 +94,8 @@
     "id": "dialogue-interaction",
     "name": "Dialogue Interaction",
     "anchors": [
-      "socratic-method"
+      "socratic-method",
+      "xy-problem"
     ]
   },
   {
@@ -127,21 +128,26 @@
     "name": "Problem Solving",
     "anchors": [
       "chain-of-thought",
+      "decisional-balance-sheet",
       "devils-advocate",
+      "double-diamond",
       "feynman-technique",
       "five-whys",
       "morphological-box",
       "occams-razor",
-      "what-would-chuck-norris-do"
+      "what-would-chuck-norris-do",
+      "xy-problem"
     ]
   },
   {
     "id": "requirements-engineering",
     "name": "Requirements Engineering",
     "anchors": [
       "cockburn-use-cases",
+      "double-diamond",
       "ears-requirements",
       "invest",
+      "kano-model",
       "moscow",
       "prd",
       "problem-space-nvc",
@@ -185,8 +191,12 @@
     "name": "Strategic Planning",
     "anchors": [
       "cynefin-framework",
+      "decisional-balance-sheet",
+      "hoshin-kanri",
       "impact-mapping",
       "jobs-to-be-done",
+      "kano-model",
+      "kotter-8-step-change-model",
       "mvp",
       "pert",
       "pugh-matrix",
@@ -219,5 +229,16 @@
       "test-double-stub",
       "testing-pyramid"
     ]
+  },
+  {
+    "id": "workflow",
+    "name": "Workflow",
+    "anchors": [
+      "workflow-architecture-documentation",
+      "workflow-code-review",
+      "workflow-requirements-to-spec",
+      "workflow-strategic-analysis",
+      "workflow-tdd-clean-architecture"
+    ]
   }
 ]