docs(phase-3): keep the index-entry grammar on one line

The code span holding `* [Title](link) - description` wrapped across a
line break, so a line-oriented reader sees `[Title](link)` as a real
link into docs/ and reports a broken target. The three sibling
occurrences in this repo all keep the span intact on one line; this one
was incidental wrapping, not a decision.

Reflowing is the local fix. It is not the same as widening a checker's
code-span stripping to span line breaks, which this repo argued against
on 2026-08-03: that would hide the class instead of resolving it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TJUFZhHzf9AqLucMsJy6u1
This commit is contained in:
Kjell Tore Guttormsen 2026-08-04 12:37:02 +02:00
commit 6e0e8eb533

View file

@ -246,10 +246,10 @@ them:
as a message before it can be read out of their code.
- **The index shape is not negotiable downward**, which makes "express both
shapes rather than generalise one into the other" the right call: one index
per directory, exactly one `# ` heading, entries `* [Title](link) -
description` and nothing else, directory and index matching in both
directions, and a root index carrying `okf_version` / `bundle_profile` /
`okf_spec_commit` frontmatter in that key order.
per directory, exactly one `# ` heading, entries
`* [Title](link) - description` and nothing else, directory and index
matching in both directions, and a root index carrying `okf_version` /
`bundle_profile` / `okf_spec_commit` frontmatter in that key order.
## The index policy, and the conflict that shaped it