GitHub returns 404 for /stargazers and /network/members to anonymous clients
(anti-scraping); the README social-footer badges link there, so the lychee link
check (the non-blocking ci.yml job and the standalone links.yml, both using this
config) flagged them as dead. The pages are live in a browser. Exclude them.
* release: bump 0.9.8 -> 0.9.9
* ci(lychee): exclude the CHANGELOG version-compare links
The CHANGELOG compare URLs point at the release tag created *after* the bump is
merged; ci.yml runs on push/PR (never on the tag), so the tag never exists when
lychee runs and 'compare/vX...vY' / 'compare/vY...HEAD' 404. Excluded by the same
pattern mechanism already used for the crates.io / npm package URLs — one pattern
covers every future version, no per-release change needed.
* ci: add external link check (lychee, scheduled + on-demand)
Adds a non-blocking external-link checker mirroring wickra-docs: an
authoritative weekly + on-demand lychee run (this workflow), kept off the
PR/release path so a flaky third-party site can never block a merge or an
irreversible publish. Fixes the one redirecting link it would flag
(docs.rs/wickra -> docs.rs/wickra/latest/wickra/ in SUPPORT.md).
* ci: run lychee as a non-blocking PR job (continue-on-error)
Hybrid link-check: the authoritative run is the scheduled links.yml; this
adds an early heads-up on PRs that never gates the merge. release.yml stays
ungated so a flaky third-party site can never block an irreversible publish.
kingchenc