Link checker report

[github-actions]

Full Github Actions output

[kyle-sexton]

Root cause identified — no links in this repo are dead. Every scheduled run of the online link-check lane failed before checking a single URL:

error: unexpected argument '--accept-timeouts' found

The reusable workflow's default args pass --accept-timeouts, but lychee-action v2.8.0 installs lychee v0.23.0 by default, and that flag only exists from lychee 0.24.0. A local run of this repo's ruleset with lychee 0.24.2 (online) passes clean: 33/33 OK, 0 errors.

Fix is upstream in the platform repo: melodic-software/ci-workflows#52 (green, awaiting human merge) pins lycheeVersion: v0.24.2 and moves lychee-action past v2.8.0 so its installer handles the nested 0.24.x archive layout.

Remaining steps to close this issue:

1. Merge fix(link-check): pin lychee v0.24.2 so --accept-timeouts is recognized ci-workflows#52.
2. Bump this repo's ci-workflows pins to the resulting main SHA (all uses: sites, per the existing pin-bump convention).
3. workflow_dispatch the link-check workflow and confirm a green run.

🤖 Generated with Claude Code

https://claude.ai/code/session_017K9RRMdUKD7HLExmHwMXAe

[kyle-sexton]

Status update

PR #208 is open and closes this issue (Closes #18). All of its own CI checks currently pass — the original --accept-timeouts root cause (ci-workflows#52) was merged upstream 2026-07-07 and this repo's pin is already current, so that part of the earlier remediation plan above is done.

Current blocker: #208 is intentionally left in draft pending melodic-software/standards#135 (merged) syncing into this repo via the automated sync PR #223 (chore: sync standards components, open). That sync brings the shared lychee.toml exclusions (private raw-content inventory + five exact bot-blocked public paths) that #208's own branch-local .lycheeignore doesn't yet carry. Once #223 merges and #208 is re-verified green against it, it can be marked ready for review and merged, closing this issue.

No action needed here beyond waiting on #223 — flagging for visibility per the current audit pass, not requesting a merge (that PR is standards-repo-owned, out of this repo's scope to force).