Merge branch 'chore/md-links': Markdown links replace the siblings macros

Brings the source files in line with the renderer already deployed on
novoyuuparosk-auto-wiki master, which no longer substitutes ALL_CAPS macro
placeholders. Without this, pulse.md would publish the literal text PULSE_DEV.

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

.gitea/workflows/publish.yml

@@ -10,7 +10,7 @@ on:
 
 jobs:
   publish:
-    uses: mikkeli/novoyuuparosk-auto-wiki/.gitea/workflows/publish-songs.yml@master
+    uses: novoyuuparosk-wiki/novoyuuparosk-auto-wiki/.gitea/workflows/publish-songs.yml@master
     with:
       SOURCE_REF: ${{ github.sha }}
       # Empty on workflow_dispatch — the reusable workflow treats that as

README.md

@@ -1,2 +1,76 @@
 # Northwich committee of magic researches songs repository
+
 Just a collection of lyrics of songs. Probably will be managed into proper folders. Probably will have LRCs.
+
+## Publishing to the wiki
+
+Song pages are auto-published to <https://wiki.novoyuuparosk.org> by the
+**songs pipeline** in the companion repo `novoyuuparosk-auto-wiki` (the
+"repo next door"). It triggers on push to `master`.
+
+- **Source-file contract** (frontmatter fields, body conventions): see
+  [`pipelines/songs/SCHEMA.md`](../novoyuuparosk-auto-wiki/pipelines/songs/SCHEMA.md)
+  in `novoyuuparosk-auto-wiki`.
+- **Pipeline overview** (branch convention, triggers, categories, LRC, etc.):
+  [`pipelines/songs/README.md`](../novoyuuparosk-auto-wiki/pipelines/songs/README.md).
+
+In short: a file is published when its frontmatter has `wiki.publish: true`
+and it isn't under `wip/`. The `title` field becomes the wiki page name.
+
+## Linking to another song page
+
+Write an ordinary relative Markdown link. There is nothing to declare in the
+frontmatter:
+
+```markdown
+For more behind-the-scene shenanigans, see [Dev gibberish](pulse_dev.md).
+```
+
+At publish time the `.md` target is swapped for the target file's own `title`,
+giving a proper wikilink — so renaming a page means editing its `title` and
+nothing else. The link keeps working in Gitea's blob view and in any editor
+preview, because it is just a link.
+
+Two things to know:
+
+- The target must be published too (`wiki.publish: true`, outside `wip/`).
+  Linking to a file does **not** publish it; an unresolvable link fails the CI
+  run instead of quietly turning into plain text.
+- Links do not work inside a ` ```columns ` fence — that block is verbatim by
+  design. Put them in ordinary prose.
+
+This replaces the old `wiki.siblings` frontmatter block and its `ALL_CAPS`
+placeholders, which are gone.
+
+## Side-by-side lyrics (columns shorthand)
+
+To lay two (or more) versions of a song next to each other — e.g. an original
+and its translation — use a fenced code block tagged `columns`, with each
+column separated by a line containing only `===`:
+
+````markdown
+```columns
+**原題**
+
+一行目
+二行目
+===
+**Title**
+
+first line
+second line
+```
+````
+
+Notes:
+
+- Line breaks and blank lines are preserved verbatim (each column is rendered
+  with line breaks intact).
+- `N` columns ⇒ `N − 1` `===` separators.
+- Use Markdown emphasis inside the block: `*italic*`, `**bold**`,
+  `***bold-italic***`. (No need for raw HTML.)
+
+This is implemented entirely by the auto-wiki pipeline at publish time; the
+authoritative description lives in
+[`SCHEMA.md`](../novoyuuparosk-auto-wiki/pipelines/songs/SCHEMA.md#columns-side-by-side-shorthand).
+See [`kairo/kimito_en.md`](kairo/kimito_en.md) for a real example.

paxprotej/fuxingdao.md

@@ -5,7 +5,6 @@ categories:
   - Paxprotej
 wiki:
   publish: true
-  siblings: 
 release_date: 2023-12-25
 lrc: fuxingdao.lrc
 ---

paxprotej/paranoma.md

@@ -5,7 +5,6 @@ categories:
   - Paxprotej
 wiki:
   publish: true
-  siblings: 
 release_date: 2024-06-09
 lrc: paranoma.lrc
 ---

paxprotej/rover.md

@@ -5,7 +5,6 @@ categories:
   - Paxprotej
 wiki:
   publish: true
-  siblings: 
 release_date: 2023-11-03
 lrc: rover.lrc
 ---

paxprotej/sauna_v2.md

@@ -5,7 +5,6 @@ categories:
   - Paxprotej
 wiki:
   publish: true
-  siblings: 
 release_date: 2024-06-13
 lrc: sauna_v2.lrc
 ---

paxprotej/shimizusawa.md

@@ -5,7 +5,6 @@ categories:
   - Paxprotej
 wiki:
   publish: true
-  siblings: 
 release_date: 2023-12-09
 lrc: shimizusawa.lrc
 ---

ses/pulse.md

@@ -3,10 +3,6 @@ title: pulse under latent semantic envelopes
 album: Shirakaba Express Service
 wiki:
   publish: true
-  siblings: 
-    - path: pulse_dev.md
-      tag: PULSE_DEV
-      label: Dev gibberish
 release_date: 2026-06-18
 lrc: pulse.lrc
 ---
@@ -14,7 +10,7 @@ lrc: pulse.lrc
 # pulse under latent semantic envelopes
 
 The name of the song is stylised in all-lowercase, `pulse under latent semantic envelopes`, but Mediawiki loves a Capital letter.   
-For more behind-the-scene shenanigans, see PULSE_DEV.  
+For more behind-the-scene shenanigans, see [Dev gibberish](pulse_dev.md).  
 
 *This page is proudly the first to be maintained by Gitea actions.*  
 

ses/pulse_dev.md

@@ -4,14 +4,11 @@ categories:
   - Songwriting notes
 wiki:
   publish: true
-  siblings:
-    - path: pulse.md
-      tag: PULSE_SONG
 ---
 
 # pulse under latent semantic envelopes: personal dev notes
 
-The remaining bits of how I came to all this. For the actual song page, see PULSE_SONG.  
+The remaining bits of how I came to all this. For the actual song page, see [pulse under latent semantic envelopes](pulse.md).  
 
 ## Planning area
 

ses/tunnels.md

@@ -3,7 +3,6 @@ title: Tunnels
 album: Shirakaba Express Service
 wiki:
   publish: true
-  siblings: 
 release_date: 2026-03-01
 lrc: tunnels.lrc
 ---