feat: Link-Taxonomie u2 - kb/entities/people, projects, kb/comparisons gelabelt

Files changed:
- kb/comparisons/amd-pstate vs acpi-cpufreq.md
- kb/concepts/RAG.md
- kb/entities/people/Andrej Karpathy.md
- kb/entities/people/E3DC GmbH.md
- kb/entities/people/Rohit Gupta.md
- kb/entities/people/Vannevar Bush.md
- kb/entities/projects/BCDModule.md
- kb/entities/projects/Chemenu.md
- kb/entities/projects/andybalholm-edl.md
- kb/entities/projects/goresponsiveness.md
- kb/entities/projects/ha-core.md
- kb/entities/projects/hacs-e3dc.md
- kb/entities/projects/hacs-integration-blueprint.md
- kb/entities/projects/kfchou/wiki-skills.md
- kb/entities/projects/plugnburn-edl.md
- kb/entities/projects/vanillaflava/wiki-skills-vanillaflava.md
- kb/entities/projects/yugasun/llm-wiki-skills.md
- kb/entities/tools/Agent Memory.md
- kb/log.md
- work/link-taxonomy-migration/README.md
- work/link-taxonomy-migration/glossary.md

work/link-taxonomy-migration/glossary.md

@@ -60,3 +60,31 @@ Deferred edges for later units, discovered while processing systems:
   software (E3DC implements Modbus).
 - Two entities in the same wiki cited as parallel real-world examples of the same concept, with
   no sharper label fitting: `see-also` is correct and not a cop-out (Memex/Tolkien Gateway).
+- **Taxonomy gap, confirmed while processing u2 (people):** there is no "created by" / "authored"
+  / "extends the work of" label for a person-entity pointing at another entity or at a concept.
+  `owns` covers a person being *accountable for* an entity going forward (used for `Vannevar
+  Bush owns Memex`, `Rohit Gupta owns Agent Memory`, `E3DC GmbH owns E3DC`), but a one-time
+  historical act of creating/originating a *concept* (Karpathy authoring the LLM Wiki Pattern,
+  Bush originating Memex-the-idea) or of one person's work building on another's (Gupta extending
+  Karpathy) has nothing in Realization or Lineage that is authorised for a person: those
+  registers are concept-to-concept or concept-to-entity, never entity-to-entity or
+  entity-to-concept for authorship. Resolved as `see-also` in every such case on Karpathy's,
+  Gupta's and Bush's own pages, checked against every register first - not a stretch, a genuine
+  gap. Worth proposing a label (`originates`/`authored-by`?) if this recurs in u3/u4.
+- **comparisons pages carry no `related:` field at all.** `types/comparison.md` declares only
+  `entities` (`page_ref_fields: [entities]`) - unlabelled by the schema, like `sources:`. `xref
+  add`/`xref remove` refuse on this type ("type does not declare a related: field"). The
+  `compares-with` label from `kb/comparisons/COLLECTION.md`'s `outbound:` block is documentational
+  only for this type: it is written into the `## Beziehungen` prose by hand (there is no marker
+  region either), never into machine data. Confirmed on `amd-pstate vs acpi-cpufreq.md`.
+- A dependent-side project whose own page only names the platform vaguely ("Kernintegrationsbibliothek
+  für E3DC-Systeme") while a specific downstream package (a HACS component, an automation
+  blueprint) explicitly wraps it: assert `required-by` from the depended-upon project's page for
+  each specific downstream package, mirroring `depends-on` asserted on each dependent's own page -
+  the same genuine two-sided pair as `E3DC`/`ha-core` from u1, one level up the stack
+  (`ha-core`/`hacs-e3dc`, `ha-core`/`hacs-integration-blueprint`).
+- An external, out-of-wiki reference project cited only as "look how someone else solved this" (a
+  GitHub repo mentioned as a structural analogue, no functional dependency): `see-also` asserted
+  from the external project's own page toward the project it inspired, not the reverse - matches
+  "reads correctly from the source page" even though nothing here is a stretch, just weak by
+  nature (`wiki-skills`, `wiki-skills-vanillaflava`, `llm-wiki-skills` -> `Chemenu`).