mikkeli 841229715e 274: rename the roster to 274-lookup.md, method notes to 274-dev.md
The file called 274-dev.md was never dev notes — it was the roster. It
now sits alongside 274-lookup.csv and 274-lookup.geojson under the same
stem, since all three carry the same table.

  274-dev.md    -> 274-lookup.md   the roster, source of truth
  274-method.md -> 274-dev.md      how it was built

References updated: DOC in 274-romaji.py, the roster path in
274-transect-build.py, and the docstrings in both. 274.md now links to
the dev notes and the reference tables separately; each of the two docs
links to the other and back to the song page.

Titles follow: "274 - reference tables" and "274 - how the roster was
built".

Verified after renaming: 274-romaji.py --check reports no changes and
274-transect-build.py rebuilds 168 entries, so neither script lost its
input.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
2026-09-12 20:35:44 +09:00
2026-02-17 14:10:46 +09:00

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.

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:

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 ===:

```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. See kairo/kimito_en.md for a real example.

S
Description
Lyrics repo
Readme 1.2 MiB
Languages
Markdown 100%