docs: repair links reported by an online lychee run by kyle-sexton · Pull Request #7199 · melodic-software/claude-code-plugins

kyle-sexton · 2026-10-11T16:46:19Z

No related issue: link repairs from the lychee online sweep requested by the repository owner.

Summary

The online link check (maintenance-check-links-online, run 38151155497 on main) reported 21 errors and 6 timeouts over 15,844 links. This repairs every real rot and adds exact-URL .lycheeignore entries only for fixture data and for live pages that block the GitHub runner.

Fix

Link repairs (real rot):

plugins/discovery/CHANGELOG.md 0.4.0 entry: the topic-docs convention was deleted from main (chore: remove docs/specs and the topic-docs convention #5719); the link now points at its last committed version (blob at 32553cf).
plugins/harness-config/CHANGELOG.md: two released entries edited in place. The strict-mode section moved to plugins/marketplace-reference#strict-mode; the settings anchor is now #permissions-blockreadsoutsideworkingdirectories.
plugins/harness-config/skills/audit-instructions/reference/criteria.md: the Fable 5 migration guide section was replaced; the I25 pointer now targets fable-5-1/migration-guide#migrating-from-claude-opus-5-to-claude-fable-5-1.
plugins/playbooks/CHANGELOG.md: one released entry edited in place. about-claude/models/whats-new-opus-5 was retired upstream; the link points at the 2026-08-14 Wayback copy, which carries the cited anchor.
plugins/songwriting/CHANGELOG.md: one released entry edited in place. help.suno.com articles 5782849 and 5782977 return 404; the links point at the same Wayback copies the suno skill already cites.
plugins/pixel-art/reference/engine-layouts.md: github.com/kitao/pyxel returns 404 (API and web) and the user guide has no archived copy; the record keeps the text, drops the dead links, and watches the PyPI project page for releases.

Each released-entry edit above is also named in its plugin's changelog fragment.

.lycheeignore entries (exact URL, each with a dated reason):

Fixture data: github.com/acme/fixture/ and raw.githubusercontent.com/acme/fixture/ (docs-naming fixture tree), github.com/acme-example/widgets (playwright eval prompt).
iso.org 77520 and 63500: 403 on the runner, 200 to a browser User-Agent from a workstation.
doi.org/10.1145/3133876, doi.org/10.1016/j.intcom.2010.04.004, journals.sagepub.com 10.1509/jmkg.71.3.039: 403 to every client; each DOI resolves in the Crossref API to the cited title.
queue.acm.org id=3595878, nesdev.org APU_Pulse, the Medium JTBD article, dba.stackexchange.com join tag: Cloudflare 403 to every plain client; a rendering fetch (Firecrawl) returned the cited page.
Reddit SunoAI posts (3): the runner retest (run 38155110861, entries removed) got 403; a workstation gets the same 200 page for a made-up post id, and the Arctic Shift archive lists all three posts, none removed. Kept with that reason.
claude.ai (3): passed on the runner retest, but claude.ai answers 200 to a made-up path, so the check proves nothing; kept with exactly that reason.

Verification

Local lychee 0.24.2 online over every touched file and every file with a failure: 0 errors.
Branch dispatch 38155110861: every repaired link and fixture passed; remaining items were the reddit retest (now restored), transient 429s (gnu.org, googleblog, blogspot, jackrighteous, all passing on the main run) and man7.org timeouts.
man7.org (5 timeouts): host refusing connections today; a rendering fetch returns the page. No exception added: transient outage.
scripts/check-changelog-fragments.sh --check passes.

Repoint moved anchors and pages, link archived copies for retired upstream pages, drop links into the deleted kitao/pyxel repository, and add exact-URL .lycheeignore entries for fixture URLs and for live pages that block the GitHub runner. Remove the reddit SunoAI and claude.ai entries pending a runner retest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

The GitHub-runner retest got 403 from the three reddit posts and 200 from claude.ai, which answers 200 to a made-up path. Restore both groups with reasons that state what the retest showed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

chatgpt-codex-connector · 2026-10-11T16:55:17Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-11T16:58:55.690094Z	`99a2689`	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

claude · 2026-10-11T16:55:28Z

Claude finished @kyle-sexton's task in 7m 6s —— View job

Claude code review (`/review:code-review`)

Gather context (PR body, diff, custom instructions)
Review changed files against CLAUDE.md / REVIEW.md criteria
Fan out hunter/verifier checks on candidate findings
Post inline comments for confirmed findings
Final summary update

Summary

Scoped the review to the 12 files this PR touches (git diff 8e8a128..HEAD, which matches the stated file list exactly — the branch's shallow history didn't include origin/main, so I diffed against the commit immediately preceding this PR's two commits instead). This is a low-risk, mostly-mechanical link-repair PR: five changelog/reference link fixes, five matching .changes/* fragments for the plugins in changelog-fragment mode, and 23 new .lycheeignore lines.

Checked each repair against the repo itself where possible:

The discovery CHANGELOG's new permalink (.../blob/32553cf.../docs/conventions/topic-docs/README.md) resolves to a real commit in this repo's history, and that file exists at that commit — confirmed locally with git cat-file.
The five .changes/* fragments use plugins that are all listed in scripts/fragment-plugins.txt (fragment mode), matching precedent from existing lychee-offline-lane-* fragments.
The new .lycheeignore entries all correspond to URLs actually cited somewhere in the repo (checked each with grep), so none is an orphaned or overly-broad suppression as far as I can tell locally.
I could not reach the network to re-run lychee or verify the live 403s/anchors the PR body describes (ISO, DOI, Crossref, Cloudflare-blocked hosts, the Reddit/claude.ai reasoning, scripts/check-changelog-fragments.sh --check) — those are author-claimed and unverified by me.

One finding, posted inline and verified by an independent review:lane-verifier pass before posting:

plugins/harness-config/skills/audit-instructions/reference/criteria.md:242-243 — the I25 Sources bullet was edited to drop "and Mythos" and now points at a Fable-only migration-guide section, but the I25 row's own Source: note at line 1991 (untouched by this PR) still cites that same bullet as "the Fable and Mythos guide's section" to justify keeping Mythos models in scope (line 1969). The link repair left the rule's own stated basis for including Mythos out of sync with the citation it depends on. Details and a suggested resolution are in the inline comment.

claude · 2026-10-11T16:55:53Z

Claude finished @kyle-sexton's task in 1m 12s —— View job

Security review

Gather context (PR diff, changed files)
Skip-gate check (security-relevant surface?)
Review changed files for security issues
Check instruction-surface deletions against protected-class register
Post findings / conclusion

No security issues found.

This PR is a documentation/link-repair sweep only: it fixes dead/retired external links in
CHANGELOG.md files and a reference doc, adds dated .lycheeignore entries for fixture URLs
and runner-blocked live pages, and adds changelog fragments. No executable code, workflow, hook,
permission rule, or auth/data-handling path changes.

.lycheeignore additions are anchored/scoped regexes for a link-checker's skip list (fixture
URL prefixes, exact-URL entries for blocked/fixture pages). They affect only the
maintenance-check-links-online CI job's link validation, not any security control, and each
anchors tightly enough to not inadvertently widen past its intended target.
plugins/harness-config/skills/audit-instructions/reference/criteria.md only repoints a
citation URL/anchor to the current Fable 5.1 migration guide section; the criterion it documents
(I25's citation requirement) is unchanged — this is not an instruction deletion or softening.
CHANGELOG.md edits across discovery, harness-config, playbooks, songwriting only swap
dead links for archived (Wayback) or last-committed-version copies of the same cited content;
no historical record's substance changed.
plugins/pixel-art/reference/engine-layouts.md drops a dead GitHub link while keeping the cited
text and verification record intact.

Checked the diff against the instruction-exception-register protected-class lens
(docs/conventions/instruction-exception-register/README.md, present in this checkout): no
standing instruction (CLAUDE.md/AGENTS.md, a rules file, skill/agent body, or hook
allow/deny list) is deleted, narrowed, or softened by this change — only citation targets and a
verification-record link changed.

GitHub Actions hardening (triggers, permissions:, pin loosening) is out of scope for this lane
and N/A here — no workflow files changed.

github-actions · 2026-10-11T16:57:27Z

claude-security-review has reviewed this pull request through cc5ee23; a later push is reviewed from there.

github-actions · 2026-10-11T17:02:55Z

claude-review has reviewed this pull request through cc5ee23; a later push is reviewed from there.

gitguardian · 2026-10-11T17:08:32Z

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
38106155	Triggered	Basic Auth String	`4ef234a`	.github/scripts/merge-base/post.test.sh	View secret
38106155	Triggered	Basic Auth String	`4ef234a`	.github/scripts/merge-base/post.test.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

Understand the implications of revoking this secret by investigating where it is used in your code.
Replace and store your secrets safely. Learn here the best practices.
Revoke and rotate these secrets.
If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

following these best practices for managing and storing secrets including API keys and other credentials
install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

claude · 2026-10-11T17:08:53Z

Claude finished @kyle-sexton's task in 1m 42s —— View job

Claude code review (`/review:code-review`)

Gather context (PR body, diff, custom instructions)
Load and follow /review:code-review skill instructions
Review changed files against criteria
Post inline comments for confirmed findings
Final summary update

Summary

Ran the /review:code-review skill against PR #7199, HEAD 4ef234a. The skill's skip gate stopped the review before a new pass: comparing git diff 99a2689 4ef234a restricted to the 12 files this PR touches (.changes/**, .lycheeignore, the five CHANGELOG.md/engine-layouts.md/criteria.md edits) returns zero diff — the PR's own content is byte-identical to commit 99a2689, which this lane already reviewed (see the claude-review ... through 99a26898 and claude-security-review ... through 99a26898 status comments above). The two commits since then (698f453, the merge commit 4ef234a) only brought in unrelated changes from main; git diff origin/main...HEAD --stat still matches the PR body's own file list and line counts exactly (12 files, +71/-13).

Per the skip gate ("this head already has a successful review from this lane that still applies"), no new findings pass is warranted, and no new inline comments were posted.

For the record, the prior pass's one finding is still open and unresolved on this head:

plugins/harness-config/skills/audit-instructions/reference/criteria.md#L242-L243 — the I25 Sources bullet was edited to drop "and Mythos" and now cites a Fable-only migration-guide anchor, but the I25 row's own Source: note at line 1991 still says "The Fable and Mythos guide's section ... keeps the Fable/Mythos carry-over," and the I25 Detect set at line 1969 still lists Mythos models. The rule's stated basis for including Mythos is now out of sync with the citation it leans on. Resolve by either updating line 1991's wording (and re-grounding the Mythos carry-over some other way) or confirming the fable-5-1 migration guide still documents Mythos and saying so in the Sources bullet.

claude · 2026-10-11T17:08:54Z

Claude finished @kyle-sexton's task in 1m 12s —— View job

Security review (`/review:security-review`)

Gather context (PR body, diff, custom instructions)
Skip-gate check (security-relevant surface?)
Review changed files for security issues
Check instruction-surface deletions against protected-class register
Post findings / conclusion

Summary

Reviewed the full diff (git diff origin/main...HEAD), which matches the PR's stated 12-file
change list exactly. This is a documentation/link-repair sweep: five CHANGELOG.md/reference
link fixes, five matching .changes/* fragments, and 23 new .lycheeignore lines.

No security issues found.

.lycheeignore additions are all anchored (^...$ or ^... prefix) exact-URL or path-prefix
regexes with escaped metacharacters, scoped to fixture URLs (acme/fixture, acme-example/widgets)
and specific runner-blocked live pages (ISO, DOI/Crossref, Cloudflare-fronted hosts, Reddit,
claude.ai). None widens past its stated target or affects anything beyond the
maintenance-check-links-online link-checker's skip list.
The CHANGELOG.md edits (discovery, harness-config, playbooks, songwriting) only swap
dead links for archived (Wayback) or last-committed-version (GitHub blob pinned to a commit SHA)
copies of the same cited content. No historical record's substance changed, and no new live
external endpoint is introduced that wasn't already being linked.
plugins/pixel-art/reference/engine-layouts.md drops a 404'd GitHub link while keeping the
cited text and verification record intact; redirects the recheck trigger to the PyPI project page.
plugins/harness-config/skills/audit-instructions/reference/criteria.md:242-243 repoints the
I25 Sources citation URL/anchor to the current Fable 5.1 migration guide and drops "and Mythos"
from the surrounding prose. I checked this against the
instruction exception register
(present in this checkout, read directly): this is not an instruction-surface deletion under
that lens. The I25 rule's own Detect set (which still lists the Mythos models) is untouched by
this diff, and no enforcement/detection criterion was removed, narrowed, or softened — only a
citation's URL and its one-line description changed. This is a citation-consistency question
(the Source note elsewhere in the file still describes this bullet as covering "Fable and
Mythos"), which the code-review lane already flagged as an inline finding — out of scope here
since it carries no exploit path or trust-boundary change.
.changes/* fragments are plain prose changelog entries matching the edits above; no secrets,
no executable content.

GitHub Actions hardening (triggers, permissions:, pin loosening) is N/A — no workflow files
changed in this diff.

…links (#772) No related issue: follow-up from the lychee online sweep requested by the repository owner. ## Summary Retest of the shared `lychee.toml` URL excludes after the GitHub-runner online run in claude-code-plugins. One exclude is dropped as redundant; every other exclude stays, because no runner evidence that it passes was obtainable. The README's manual online command now tells standards to skip its own fixtures, and the naming vocabulary gains `check-links` for the online link-check workflow. ## Fix - `lychee.toml`: remove `'^https?://example\.(com|org)'`. lychee 0.24.2 excludes example.com/.org/.net by default: a config-free `lychee --dump --verbose` over `example.com`, `www.example.com`, `example.org` and `example.net` URLs marks all four `[excluded]`, while `example.community` stays checked (the removed regex would also have hidden that host). - `components/lychee/lychee.test.sh` and `fixtures/good/Exclusions.md`: two placeholder URLs and three assertions prove the default still excludes them and the config carries no example-domain entry, so a lychee upgrade that changes the default fails the test. - `components/lychee/README.md`: the manual online command notes `--exclude-path '(^|/)components/lychee/fixtures/'` for standards itself. The fixtures hold placeholder URLs and intentionally broken links that the offline harness reads; a shared `exclude_path` would reach every consumer, so the exclusion stays on the standards-only command. - `components/github-actions-conventions/vocabulary.json`: add maintenance function `check-links` (claude-code-plugins `maintenance-check-links-online.yml`, #7124 there). No existing maintenance function fits: `audit-link-check-excludes` audits only the private-repo exclude list, while this workflow checks every Markdown link with the network on. Excludes kept, with why: - iso.org 78907 and the two medium.com entries: the claude-code-plugins runner run got 403 from other iso.org and medium.com pages, so the workstation pass recorded in the research does not carry over. - docs.genius.com, cursor.com, lib.rs, ntia.gov, w3.org, x.com, LinkedIn, bsky.app, ACM, dev.mysql.com, help.miro.com, isdown.app, npmjs: their URLs are excluded in every run, so no runner result exists, and running a hand-picked URL list on a runner was out of scope for this sweep. Each still carries its recorded verification. No shared exclude added: the row G logs propose none, and every new exception in claude-code-plugins is cited only there. ## Verification - `bash components/lychee/lychee.test.sh`: 101 PASS, 0 FAIL. - `bash components/lychee/private-repo-inventory.test.sh`: 34 PASS. - `npm run test:github-actions-conventions`: pass; `npm run lint:github-actions-conventions`: 0 findings. - Online lychee 0.24.2 over standards' tracked Markdown with the fixtures path excluded, no token: 945 links, 0 errors except five man7.org timeouts (host refusing connections today; a rendering fetch returns the pages, transient outage, no exception) and one gnu.org 429 (answers 429 to the lychee User-Agent intermittently; passed on the runner and on retry in other rows). ## Related - melodic-software/claude-code-plugins#7199 (link repairs), #7124 there (online workflow), standards#767, standards#769. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

The repaired I25 source now points at the Fable 5.1 guide's Opus 5 section. That section covers Claude Mythos 5.1 as the same capabilities, so say so in the Sources bullet and in I25's Source note, which still described the retired joint Fable and Mythos guide. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

claude · 2026-10-11T17:17:34Z

Claude finished @kyle-sexton's task in 4m 14s —— View job

Claude code review (`/review:code-review`)

Gather context (incremental diff, lane scope, HEAD SHA)
Review the changed lines in plugins/harness-config/skills/audit-instructions/reference/criteria.md
Fan out hunter/verifier check on the candidate finding
Post inline comments for confirmed findings
Final summary update

Summary

Per this lane's incremental scope, reviewed only .claude-lane/incremental.diff — the change to plugins/harness-config/skills/audit-instructions/reference/criteria.md since 4ef234a — which is the author's fix for the Mythos-sourcing inconsistency flagged in the prior review round. Every other file in this PR was reviewed at 4ef234a and is unchanged since.

The fix is good as far as it goes: it reconciles the I25 Sources bibliography bullet and the I25 rule's own Source: note by adding "which covers Claude Mythos 5.1 as the same capabilities" to both, so the two no longer contradict each other on whether the cited migration-guide section covers Mythos at all.

One finding, posted inline and confirmed by an independent review:lane-verifier pass:

criteria.md:1991-1994 — the new clause is a fresh, load-bearing factual claim (it's the stated basis for folding Mythos variants into I25's Detect set), but it falls outside the coverage of the existing As of:/Recheck trigger: block at lines 1999-2002, which only names the Detect model set, the corroborating pages, and the determinism note. This file otherwise partitions as-of/recheck coverage precisely across every sub-claim in a Source note (e.g. lines 1278-1282), so this is a gap against the file's own established discipline — and against the repo's skill-bodies-state-current-rules.md rule, which this file is subject to. The inline comment also notes the claim names only Mythos 5.1, not the Mythos 5 / Mythos Preview the Detect set also lists.
· branch lychee-online-links

claude · 2026-10-11T17:17:36Z

Claude finished @kyle-sexton's task in 54s —— View job

Security review (`/review:security-review`)

Gather context (PR body, diff, custom instructions)
Load and follow /review:security-review skill instructions
Review incremental change in plugins/harness-config/skills/audit-instructions/reference/criteria.md
Post findings / conclusion

Summary

Scope: incremental re-review per the lane wrapper — this lane's last review of this head family was at 4ef234a; only what changed since then was reviewed, which is exactly one file: plugins/harness-config/skills/audit-instructions/reference/criteria.md (read from .claude-lane/incremental.diff, cross-checked with gh pr diff for context). HEAD is d72fd98.

No security issues found.

The incremental commit (d72fd98, "keep the I25 Mythos basis in step with its source") resolves the citation-consistency gap the prior review pass on this PR flagged (inline comment + code-review/security-review summaries at 99a2689/4ef234a):

Line 240-244 — the Sources bullet now says the Fable 5.1 guide's migration section "covers Claude Mythos 5.1 as the same capabilities," restoring the Mythos mention that an earlier commit on this PR had dropped.
Line 1991-1994 — the I25 row's own Source: note is reworded to match, so it no longer claims a "Fable and Mythos guide" that doesn't exist; it now correctly names the Fable 5.1 guide and states explicitly that it covers Mythos 5.1.

Checked against this lane's instruction-surface lens (docs/conventions/instruction-exception-register/README.md, present in this checkout and read directly): this is not an instruction-surface deletion, narrowing, or softening. The I25 Detect set (lines 1965-1972, which still lists Claude Mythos 5.1, Claude Mythos 5, or Claude Mythos Preview) is untouched by this diff — only the Sources/Source citation prose changed, and it changed to restore consistency with that unchanged Detect set, not to remove or weaken it. No executable code, workflow, permission, or auth/data-handling path is touched.

Nothing further to report; the rest of this PR (all other files) was already reviewed at 4ef234a and is unchanged since.
· branch lychee-online-links

The thinking page's sampling-parameters set names every Fable and Mythos model I25 detects, so it is the basis; the Fable 5.1 migration section only corroborates the carry-over and gets its own as-of date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

claude · 2026-10-11T17:25:28Z

Claude finished @kyle-sexton's task in 1m 2s —— View job

Security review (`/review:security-review`)

Gather context (incremental scope, lane header, HEAD SHA)
Load and follow /review:security-review skill instructions
Review incremental change in plugins/harness-config/skills/audit-instructions/reference/criteria.md
Check instruction-surface lens
Post findings / conclusion

Summary

Scope: incremental, per the lane wrapper — last reviewed at d72fd98. Only what changed since
then was reviewed, read from .claude-lane/incremental.diff: one file,
plugins/harness-config/skills/audit-instructions/reference/criteria.md. HEAD is 004cbf1.

No security issues found.

The incremental commit
(004cbf1,
"rest I25's Mythos scope on the thinking page set") further revises the Mythos-sourcing text the
prior two review rounds on this PR flagged and the author partially fixed in d72fd98:

Lines 240–243
— the Sources bullet drops the "which covers Claude Mythos 5.1 as the same capabilities" clause
and now just cites the Fable 5.1 migration-guide section plainly.
Lines 1990–2002
— the I25 Source: note is reworded so the Mythos basis now rests on the Detect set itself
("That set names every Fable and Mythos model in the Detect set") rather than on a claim about
what the migration guide says Mythos covers; the migration guide is now cited only as
corroboration that "the restriction carries over," with its own As of: 2026-10-11 date added
alongside the existing 2026-10-01 date for the set and the Sonnet 5 pages.

This resolves the prior round's as-of/recheck-coverage gap (the previous "covers Claude Mythos 5.1
as the same capabilities" clause was a load-bearing claim with no dedicated as-of/recheck): the
claim that depended on an undated reading of the migration guide is gone, and the remaining
migration-guide claim (generic restriction carry-over, not a Mythos-specific capability
assertion) now has its own as-of date.

Instruction-surface check: this file is a skill reference body, one of the surfaces the
instruction-surface lens covers, so I checked the diff against it (register present in this
checkout and read directly:
docs/conventions/instruction-exception-register/README.md).
The I25 rule's enforcement itself — the Detect set
(lines 1964–1974,
still listing Claude Mythos 5.1, Claude Mythos 5, or Claude Mythos Preview), the Remediate step,
and the Must-NOT-flag carve-outs — is untouched by this commit. Only the Source note's citation
wording and its as-of dates changed, and the change tightens citation accuracy rather than
weakening, narrowing, or deleting anything the rule detects or remediates. Not a finding under
that lens.

No executable code, workflow, permission, or auth/data-handling path is touched by this
incremental change. Nothing further to report; every other file in this PR was already reviewed
at 4ef234a and is unchanged since.
· branch lychee-online-links

claude · 2026-10-11T17:25:30Z

Claude finished @kyle-sexton's task in 5m 16s —— View job

Claude code review (`/review:code-review`)

Gather context (incremental diff, lane scope, HEAD SHA)
Review the changed lines in plugins/harness-config/skills/audit-instructions/reference/criteria.md
Fan out hunter/verifier check on the candidate finding
Post inline comments for confirmed findings
Final summary update

Summary

Per this lane's incremental scope, reviewed only .claude-lane/incremental.diff — the change to plugins/harness-config/skills/audit-instructions/reference/criteria.md since d72fd98 (commit 004cbf1, "rest I25's Mythos scope on the thinking page set"). Every other file in this PR was reviewed at 4ef234a/d72fd98 and is unchanged since.

This commit is the author's second-round fix for the Mythos-sourcing finding this lane raised twice before. It reworks the I25 Sources bullet and the I25 row's own Source note so the claim no longer rests on the Fable 5.1 migration guide asserting Mythos-5.1-specific equivalence; instead it grounds Mythos inclusion in the Detect set itself (already its own as-of/recheck-covered claim) and uses the migration guide only as generic corroboration that "the restriction carries over." A hunter/verifier pass checked whether this fully closes the gap and whether the rewording introduces a new ambiguity:

An independent verifier rejected the ambiguity candidate: read in context, "the restriction carries over" scopes to the sampling restriction generally (already established by the preceding clause naming the Detect set), not to a Mythos-specific claim the Fable-only Sources citation can't support.
One finding was confirmed and posted inline on criteria.md:1998-2002: the fix adds a new dated sub-claim ("2026-10-11 for the migration guide section") to the Source note's As of: sentence, but the paired Recheck trigger: sentence has no trigger for that sub-claim going stale. This file otherwise pairs every distinct as-of date with its own dedicated recheck trigger elsewhere (e.g. the I17 adaptive-reasoning Source note, I8-c's dated sub-bullets), so this is a narrower residual case of the same discipline gap the prior review rounds flagged — not a new issue, but not yet fully closed either.
· branch lychee-online-links

… trigger Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

claude · 2026-10-11T17:33:30Z

Claude finished @kyle-sexton's task in 47s —— View job

Security review (`/review:security-review`)

Gather context (incremental diff, lane scope, HEAD SHA)
Load and follow /review:security-review skill instructions
Review incremental change in plugins/harness-config/skills/audit-instructions/reference/criteria.md
Check instruction-surface lens
Post findings / conclusion

Summary

Scope: incremental, per the lane wrapper — last reviewed at 004cbf1. Only what changed
since then was reviewed, read from .claude-lane/incremental.diff: one file,
plugins/harness-config/skills/audit-instructions/reference/criteria.md. HEAD is cc5ee23.

No security issues found.

The incremental commit
(cc5ee23,
"give the I25 migration-guide citation a recheck trigger") closes the residual citation-discipline
gap the prior review round on this PR flagged: the I25 Source: note's As of: sentence
(lines 1998–2003)
names three distinct dated sub-claims (the model set + Sonnet 5 pages at 2026-10-01, the
migration-guide section at 2026-10-11, the determinism note at 2026-08-08). The following
Recheck trigger: sentence previously covered only two of the three; this commit adds the
missing third clause, "the migration guide's Opus 5 section dropping the carry-over statement,"
so every dated sub-claim now has a paired trigger, matching the file's own convention elsewhere
(e.g. the I17 adaptive-reasoning Source note, I8-c's dated sub-bullets).

Instruction-surface check: this file is a skill reference body, one of the surfaces the
instruction-surface lens covers
(docs/conventions/instruction-exception-register/README.md,
present in this checkout and read directly). The I25 rule's enforcement itself — the Detect set
(lines 1964–1974,
still listing Claude Mythos 5.1, Claude Mythos 5, or Claude Mythos Preview), the Remediate step,
and the Must-NOT-flag carve-outs — is untouched by this commit. The change is purely additive (a
new recheck-trigger clause), not a removal, narrowing, or softening of anything the rule detects
or remediates — not a finding under that lens.

No executable code, workflow, permission, or auth/data-handling path is touched by this
incremental change. Nothing further to report; every other file in this PR was already reviewed
at 4ef234a and is unchanged since.
· branch lychee-online-links

claude · 2026-10-11T17:33:30Z

Claude finished @kyle-sexton's task in 50s —— View job

Claude code review (`/review:code-review`)

Gather context (incremental diff, lane scope, HEAD SHA)
Review the changed lines in plugins/harness-config/skills/audit-instructions/reference/criteria.md
Fan out hunter/verifier check on the candidate finding
Post inline comments for confirmed findings
Final summary update

Summary

Per this lane's incremental scope, reviewed only .claude-lane/incremental.diff — the change to plugins/harness-config/skills/audit-instructions/reference/criteria.md since 004cbf1 (now HEAD cc5ee23). Every other file in this PR was reviewed at 4ef234a/d72fd98/004cbf1 and is unchanged since.

This commit ("give the I25 migration-guide citation a recheck trigger") is the author's fix for the residual as-of/recheck gap this lane flagged on the prior round: the I25 Source note's As of: sentence names a 2026-10-11 sub-claim for the migration guide section, but the paired Recheck trigger: sentence previously had no trigger for that sub-claim going stale.

The fix adds exactly that — criteria.md:2001-2003 now reads "...sampling parameters being reinstated on any model in it, the migration guide's Opus 5 section dropping the carry-over statement, or a docs page starting to cover the determinism note." That closes the gap cleanly: every dated sub-claim in the As of: sentence (the set/Sonnet 5 pages, the migration guide section, and the determinism note) now has a corresponding recheck trigger, matching this file's own convention elsewhere (e.g. the I17 adaptive-reasoning Source note at lines 1438-1442).

No new findings. This fully resolves the Mythos-sourcing/citation-discipline thread this lane raised across the prior three review rounds on this PR, and no new issue was introduced by this one-clause addition.
· branch lychee-online-links

kyle-sexton · 2026-10-11T17:37:48Z

GitGuardian note: both hits are the placeholder token x-access-token:ghs_example in .github/scripts/merge-base/post.test.sh, a test fixture that landed on main in #7190 and reached this branch only through the merge of main (4ef234a). This PR's diff (git diff origin/main...HEAD) does not touch that file, and GitGuardian is not a required check.

…hosts (#775) No related issue: follow-up to #772 from the lychee online sweep, approved by the repository owner. ## Summary A GitHub-runner retest of the shared URL excludes (temporary probe step in claude-code-plugins run [38163276512](https://github.com/melodic-software/claude-code-plugins/actions/runs/38163276512), removed before merge) passed six of them, so they go. Two hosts that answer a runner's burst with 429 get per-host pacing instead of an accepted 429. ## Fix - Dropped (passed lychee 0.24.2 on the runner): the NTIA SBOM report (the old TLS-trust-store exclude), help.miro.com 31624028247058, isdown.app/status/anthropic, w3.org WorkingWithTimeZones, host-wide linkedin.com (its one cited post passed), host-wide x.com (status posts passed; a made-up status answered 404). - x.com narrowed: profiles answer 403 to the runner (`x.com/KentBeck`), so profiles stay excluded with the untested article and terms pages; status posts are checked again. - Kept with reasons restated: bsky.app (200 for a made-up post on the runner too, so a pass proves nothing), the two Medium articles, npmjs, dev.mysql.com, ACM, ISO, docs.genius.com, cursor.com, lib.rs (all 403 on the runner). - `[hosts."testing.googleblog.com"]` and `[hosts."jackrighteous.com"]`: `concurrency = 1`, `request_interval = "2s"`, the per-host keys in lychee v0.24.2's `lychee.example.toml` (`[hosts."blog.example.com"]`, `concurrency`, `request_interval`). The no-`accept` rule stands. - `lychee.test.sh` and `fixtures/good/Exclusions.md`: the dropped URLs are now asserted to be checked; x.com profile and article URLs asserted excluded, a status URL asserted checked. ## Verification - `bash components/lychee/lychee.test.sh`: 102 PASS, 0 FAIL (the config with `[hosts]` tables loads in every lychee call there). - Runner probe results: 11 passes (the 7 URLs behind the six dropped excludes, 3 bsky.app URLs including a made-up post, and a made-up claude.ai path), 14 x 403, 1 x 404 (a made-up x.com status). ## Related - #772, melodic-software/claude-code-plugins#7199 and #7222. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

kyle-sexton and others added 2 commits October 11, 2026 12:21

kyle-sexton mentioned this pull request Oct 11, 2026

fix(lychee): drop the redundant example-domain exclude and add check-links melodic-software/standards#772

Merged

kyle-sexton marked this pull request as ready for review October 11, 2026 16:55

claude Bot reviewed Oct 11, 2026

View reviewed changes

Comment thread plugins/harness-config/skills/audit-instructions/reference/criteria.md Outdated

Merge remote-tracking branch 'origin/main' into lychee-online-links

4ef234a

claude Bot reviewed Oct 11, 2026

View reviewed changes

Comment thread plugins/harness-config/skills/audit-instructions/reference/criteria.md Outdated

claude Bot reviewed Oct 11, 2026

View reviewed changes

Comment thread plugins/harness-config/skills/audit-instructions/reference/criteria.md Outdated

docs(harness-config): give the I25 migration-guide citation a recheck…

cc5ee23

… trigger Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

kyle-sexton added this pull request to the merge queue Oct 11, 2026

Merged via the queue into main with commit d1e3cf2 Oct 11, 2026
18 of 19 checks passed

kyle-sexton deleted the lychee-online-links branch October 11, 2026 17:42

This was referenced Oct 11, 2026

ci: run the online link check weekly, pace it per host, and repoint a dead citation #7222

Merged

fix(lychee): drop excludes that pass on a GitHub runner and pace two hosts melodic-software/standards#775

Merged

Conversation

kyle-sexton commented Oct 11, 2026

Summary

Fix

Verification

Related

Uh oh!

chatgpt-codex-connector Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Claude code review (/review:code-review)

Summary

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Security review

Uh oh!

github-actions Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

github-actions Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gitguardian Bot commented Oct 11, 2026

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Claude code review (/review:code-review)

Summary

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Security review (/review:security-review)

Summary

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Claude code review (/review:code-review)

Summary

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Security review (/review:security-review)

Summary

Uh oh!

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Security review (/review:security-review)

Summary

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Claude code review (/review:code-review)

Summary

Uh oh!

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Security review (/review:security-review)

Summary

Uh oh!

claude Bot commented Oct 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Claude code review (/review:code-review)

Summary

Uh oh!

kyle-sexton commented Oct 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

chatgpt-codex-connector Bot commented Oct 11, 2026 •

edited

Loading

claude Bot commented Oct 11, 2026 •

edited

Loading

Claude code review (`/review:code-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

github-actions Bot commented Oct 11, 2026 •

edited

Loading

github-actions Bot commented Oct 11, 2026 •

edited

Loading

claude Bot commented Oct 11, 2026 •

edited

Loading

Claude code review (`/review:code-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

Security review (`/review:security-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

Claude code review (`/review:code-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

Security review (`/review:security-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

Security review (`/review:security-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

Claude code review (`/review:code-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

Security review (`/review:security-review`)

claude Bot commented Oct 11, 2026 •

edited

Loading

Claude code review (`/review:code-review`)