Brings in the auto-wiki pipeline update: wiki.siblings frontmatter dropped
repo-wide in favour of ordinary relative Markdown links, plus the README
section documenting it.
No conflicts. 274.md and 274-dev.md were already authored under the new
convention and are unchanged by this.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
Follows the pulse / pulse_dev split. 274.md keeps the frontmatter, the
intro and the lyrics workspace; everything below moves to 274-dev.md,
which will document how the PoI candidates were assembled and hold the
filtered charts.
Uses the new relative-Markdown-link convention rather than a siblings
macro, in both directions. Dev page carries publish: false to match
274.md while both are under wip/.
Contents moved verbatim; the dev page's own prose is still to be written.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
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>
Drops the `wiki.siblings` frontmatter block from all eight files that carried
one — six of them declared it empty — and replaces the two live `ALL_CAPS`
placeholders with ordinary relative Markdown links:
see PULSE_DEV. -> see [Dev gibberish](pulse_dev.md).
Both now resolve to real wikilinks at publish time, and both read as links in
Gitea's blob view instead of as a naked token in the middle of a sentence.
Requires the matching renderer change in novoyuuparosk-auto-wiki; the macro
substitution it depended on no longer exists.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replace the 由仁-十勝清水 reference section with the narrowed
川端橋 - 右左府 scope.
- structures table gains a kilometre key, derived two ways: sequence
alignment of the 北海道開発局 register against OSM way geometry by
length, and watercourse crossings as anchors where a bridge is named
after the stream it crosses (草木橋, ポン久留喜橋, オロロップ橋,
モトツ橋, 福山大橋, 新川橋)
- watercourses deduplicated 176 -> 32; the inflation was single rivers
split across many OSM ways
- PoI and watercourse tables sorted on the same datum so all three
interleave by distance
- working language switched to English, Japanese kept for proper nouns
- gloss fixed: 川端 as 'riverside', not 'end of a river'
Distances are measured from a datum near 上野幌 and are not official
kiloposts (official KP is roughly this plus 14 km). Full-route data and
the source registers live in the KB at ~/infra/kb/inbox/surreal/.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
This repo and novoyuuparosk-auto-wiki both moved out of the `mikkeli`
account, so the reusable-workflow reference follows. Same owner on both
sides means no cross-owner read gate on the private callee.
Point to the songs pipeline schema in the novoyuuparosk-auto-wiki repo
next door, and document the side-by-side `columns` fenced-block shorthand
(=== separators, Markdown emphasis) with kairo/kimito_en.md as an example.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Convert 'You and me and a gentle journey' side-by-side lyrics to the auto-wiki columns shorthand (```columns fence, columns split by ===, **bold** titles). Rendered wiki output is unchanged; the source is now Markdown-native rather than raw HTML.
2026-06-14 21:19:52 +09:00
12 changed files with 394 additions and 17 deletions
Codename `Yuubari 2` but I've decided that this will be more about Route 274. Thus the name.
## Lyrics (working)
```
// Kawabata, lit. 'riverside'
// Before Yuubari (west)
// Yuubari
// Past Yuubari (east), Kaede, Noborikawa
// Hidaka / Sarukawa
右左府発電所
東に続く
```
For how the reference material was produced and the feature tables themselves, see
[274 development notes](274-dev.md).
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.