README: link sibling repos, which this tree already does and I did not
The convention was already here — favela-web and favela-node link siblings as
[hyper-proto-peer](../hyper-proto-peer), favela-community as [hyper-rooms](../hyper-rooms).
The READMEs I wrote from scratch had ZERO of them; the ones I only edited kept theirs.
Measured before fixing: favela-bridge, favela-host, favela-identity, favela-markdown,
favela-peer, favela-surface and favela-surface-android each had 0 relative links while
mentioning 5-10 siblings by name.
Linked on FIRST mention only, prose only. Skipped code fences, tables, existing links
and URLs, and left later mentions as code spans so a paragraph does not turn into a row
of blue.
One case the automated pass got wrong and I reverted by hand: favela-surface's Boundary
section lists the modules it may NOT import, as a uniform run of code spans. Linking
hyper-overlay and ap-bridge there broke the list's formatting and read as "go read
these" when the point is "never import these". Those two are code spans again.
Rewrapped the lines the inserted links pushed past 100 columns, which is where the rest
of this tree wraps. The long lines that remain in favela-community and favela-node are
pre-existing prose — verified against HEAD — and one is inside a code fence.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
640023e801a197c0f96c0644aa7d4a85836316ee
by plankatron <fleeky@gmail.com> · 2026-09-20T21:23:03.000Z