torben/chemenu
1
1
Fork 0
Code Issues 26 Pull Requests Actions Packages Releases 32 Activity

fix: update entity naming conventions to use singular form for consistency
CI / verify (push) Successful in 56s
Details
Release / release (push) Successful in 34s
Details

Browse Source
This commit is contained in:
Torben Nehmer
2026-09-05 11:14:47 +02:00
parent 0b3c496fff
commit 63b4bb82d9
7 changed files with 8 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGES.md
+2 -1
View File
@@ -35,7 +35,7 @@ dev-checkout concern - readable here, never shipped as something to parse.
--- ---
## 4.8.0-beta.4 - 2026-09-05 - raw accept: Stem-Eindeutigkeit im Typverzeichnis erzwingen, --replaces als einziger Weg daran vorbei (schliesst #64) ## 4.8.0-beta.5 - 2026-09-05 - update entity naming conventions to use singular form for consistency
**Author:** Torben Nehmer **Author:** Torben Nehmer
@@ -45,6 +45,7 @@ dev-checkout concern - readable here, never shipped as something to parse.
- kb/CONTRACT.md: Tiefe 1 als Grenze - Katalog liest nur eine Area-Ebene - kb/CONTRACT.md: Tiefe 1 als Grenze - Katalog liest nur eine Area-Ebene
- raw accept: incoming/ als abgeleiteter Rohablage-Eingang (schliesst #58) - raw accept: incoming/ als abgeleiteter Rohablage-Eingang (schliesst #58)
- raw accept: Stem-Eindeutigkeit im Typverzeichnis erzwingen, --replaces als einziger Weg daran vorbei (schliesst #64) - raw accept: Stem-Eindeutigkeit im Typverzeichnis erzwingen, --replaces als einziger Weg daran vorbei (schliesst #64)
- update entity naming conventions to use singular form for consistency
<!-- /wikitool:bumps --> <!-- /wikitool:bumps -->
Das Label `status/incoming` gibt es seit heute in Gitea: der Mensch legt einen Das Label `status/incoming` gibt es seit heute in Gitea: der Mensch legt einen
INSTALL.md
-26
View File
@@ -265,32 +265,6 @@ ausführen kann), findet die Dateiliste im `files`-Block der `.wikitool-release.
Ausnahmen (`kb/CONVENTIONS.md`, `kb/*/COLLECTION.md`, `.wikitool-kb.json`) in Ausnahmen (`kb/CONVENTIONS.md`, `kb/*/COLLECTION.md`, `.wikitool-kb.json`) in
[tools/CONTRACT.md](tools/CONTRACT.md)s `dist upgrade`-Zeile. [tools/CONTRACT.md](tools/CONTRACT.md)s `dist upgrade`-Zeile.
### Sonderfall: Update von 1.x auf 2.0.0
Mit `2.0.0` wurde das Ursprungs-Repo von `torben/llm-wiki-test1` auf `torben/chemenu`
umbenannt. Eine Instanz, die vor diesem Release exportiert wurde, trägt in
`.wikitool-release.json` noch den alten Feed - und `version check` fragt damit einen Pfad ab,
den es unter diesem Namen nicht mehr gibt. Der Befehl bricht also nicht kaputt, er erfährt nur
nichts mehr. Einmalig überschreiben:
```bash
export WIKITOOL_UPDATE_URL="https://gitea.nehmer.net/api/v1/repos/torben/chemenu/releases/latest"
tools/wikitool version check
```
Danach den Tarball aus Weg A holen - er heißt seit `2.0.0` `chemenu-stack-<version>.tar.gz`
statt `llm-wiki-stack-<version>.tar.gz` - und den Ablauf oben normal durchlaufen. Das
mitkopierte `.wikitool-release.json` trägt den neuen Feed, die Variable wird danach nicht mehr
gebraucht.
Zwei Nachräumarbeiten, weil Schritt 3 `tools/` kopiert und nichts löscht: das alte Paket
`tools/wiki_tools/` bleibt neben dem neuen `tools/chemenu/` liegen und kann weg - der
`tools/wikitool`-Shim ruft seit `2.0.0` `-m chemenu.cli` auf und rührt es nicht mehr an. Und
eigene Skripte, die `from wiki_tools import …` machen, müssen auf `chemenu` gezogen werden.
Eine Inhaltsmigration verlangt dieses Release nicht: `migrate status` bleibt leer, `kb/`
behält Schema und Shape.
## Konfiguration ## Konfiguration
| Variable | Zweck | Fallback | | Variable | Zweck | Fallback |
README.md
+2 -2
View File
@@ -157,7 +157,7 @@ working *on* that layer, the contract is what binds an agent working *with* it.
Ask questions naturally: Ask questions naturally:
- "What projects use MQTT?" - "What projects use MQTT?"
- "Show me the architecture of ha-core" - "Show me the architecture of HA Integration"
- "Compare gdeploy and plugnburn-edl" - "Compare gdeploy and plugnburn-edl"
- "What decisions were made about E3DC integration?" - "What decisions were made about E3DC integration?"
@@ -247,7 +247,7 @@ Ingest incoming/notes/my-notes.md
### Naming ### Naming
- Use human-readable titles with spaces for files: `Hybrid Search.md`, not kebab-case - Use human-readable titles with spaces for files: `Hybrid Search.md`, not kebab-case
- Use singular for entities: `ha-core.md` (not `ha-cores.md`) - Use singular for entities: `HA Integration.md` (not `HA Integration.md`)
- Use wikilinks matching the file name exactly: `[[Entity Name]]` - Use wikilinks matching the file name exactly: `[[Entity Name]]`
- **Titles follow the subject's own established name, not the wiki's language.** `Act Runner` and - **Titles follow the subject's own established name, not the wiki's language.** `Act Runner` and
`GitOps Ownership Model` keep theirs. A title is the only identifier a page has - it also lives `GitOps Ownership Model` keep theirs. A title is the only identifier a page has - it also lives
VERSION
+1 -1
View File
@@ -1 +1 @@
4.8.0-beta.4 4.8.0-beta.5
instructions/wiki-query/SKILL.md
+1 -1
View File
@@ -79,6 +79,6 @@ An answer in chat, with citations. Occasionally a new page.
**Example queries:** **Example queries:**
- "What projects use MQTT?" - "What projects use MQTT?"
- "Show me the architecture of ha-core" - "Show me the architecture of HA Integration"
- "Compare gdeploy and plugnburn-edl" - "Compare gdeploy and plugnburn-edl"
- "What decisions were made about E3DC integration?" - "What decisions were made about E3DC integration?"
kb/CONVENTIONS.md
+1 -1
View File
@@ -60,7 +60,7 @@ There is no `## Siehe auch` region any more. It was the reciprocal half of a bid
## Naming ## Naming
- Human-readable titles with spaces: `Hybrid Search.md`, `Gitea Actions.md` - not kebab-case. - Human-readable titles with spaces: `Hybrid Search.md`, `Gitea Actions.md` - not kebab-case.
- Singular for entities: `ha-core.md`, not `ha-cores.md`. - Singular for entities: `HA Integration.md`, not `HA Integrations.md`.
- Comparison pages read as a comparison: `Go vs Rust.md`. - Comparison pages read as a comparison: `Go vs Rust.md`.
- A decision (`concept_type: decision`) is named like any other concept - no `adr-NNN-` prefix. - A decision (`concept_type: decision`) is named like any other concept - no `adr-NNN-` prefix.
See [kb/concepts/COLLECTION.md § Decisions](concepts/COLLECTION.md#decisions). See [kb/concepts/COLLECTION.md § Decisions](concepts/COLLECTION.md#decisions).
kb/entities/COLLECTION.md
+1 -1
View File
@@ -80,4 +80,4 @@ the *why* lives, and the entity page should not restate it.
- A pattern, protocol, architecture or decision - those are concepts, even when only one entity - A pattern, protocol, architecture or decision - those are concepts, even when only one entity
uses them. uses them.
- A page about a source document - that is a `source` page in `kb/sources/`. - A page about a source document - that is a `source` page in `kb/sources/`.
- Singular naming is required: `ha-core.md`, not `ha-cores.md`. - Singular naming is required: `HA Integration.md`, not `HA Integrations.md`.