kevinveenbirkenbachandClaude Opus 5 fcc98bcad1 fix(docs): require a README behind every directory link ...

The lint accepted a link that resolved to a file or a directory. myst
builds a document reference only when the target is_file(), so a link to
a directory without a README is a bare file listing on GitHub and a dead
cross-reference in the documentation build. It now reports which of the
two reasons applies.

The tightened rule found 41 links. Where a README backs the directory,
bd15eae9fa's resolver carries the link and it stays. Where none exists,
the link becomes a code span rather than an invented README: 15 of them
point at a role's meta/addons/, whose addon table already sits below the
sentence, and the rest at code directories such as utils/ or
cli/administration/deploy/runner/.

The changed sentences are msgids, so these entries return to the
translator on the next extract.

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

2026-09-25 18:42:23 +02:00

..

cli

Merge branch 'feature/svc-ai-litellm/remote-models-config' into feature/store-i18n

2026-09-25 16:45:16 +02:00

group_vars

feat(readme): let a role name the companions its documented deploy needs

2026-09-25 09:03:56 +02:00

library

…

plugins

Merge branch 'feature/svc-ai-litellm/remote-models-config' into feature/store-i18n

2026-09-25 16:45:16 +02:00

roles

test(docs): cover the yaml parser and the directory resolver

2026-09-25 18:27:40 +02:00

scripts

fix(diagnostics): let the in-zone probes read the drop-in that holds the zone

2026-09-03 12:50:58 +02:00

utils

fix(docs): require a README behind every directory link

2026-09-25 18:42:23 +02:00

__init__.py

…