docs(issues): add external-link triage specification

[josecelano]

Summary

• adds the approved EPIC Overhaul: Automation Tools and AI Agent Guardrails #2003 subissue specification for advisory external-link triage
• records the current merged-develop hosted workflow baseline and a classification-first remediation plan
• adds Triage advisory external-link check findings #2185 to the EPIC's approved early implementation candidates

Validation

• linter markdown
• linter cspell
• linter lychee
• ./contrib/dev-tools/git/hooks/pre-commit.sh
• ./contrib/dev-tools/git/hooks/pre-push.sh

Related to #2185
Related to #2003

[Copilot]

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Pull request overview

Adds the approved EPIC #2003 sub-issue specification for triaging advisory external-link check failures, and registers it as an early implementation candidate under the EPIC.

Changes:

• Added a new folder-style issue specification for #2185 documenting baseline evidence, scope, plan, and verification steps for external-link triage.
• Updated EPIC #2003 “early implementation candidates” table to include #2185.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
docs/issues/open/2185-2003-triage-advisory-external-link-check-findings/ISSUE.md	Introduces the #2185 issue specification with baseline run evidence and an incremental remediation/exclusion plan.
docs/issues/open/2003-overhaul-guardrails-and-automation/EPIC.md	Adds #2185 as an approved early implementation candidate linked to its local specification.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟡 Changes recommended

The new spec frontmatter uses issue-spec file paths in semantic-links.related-artifacts (risking stale links) and the EPIC entry title is inconsistent with the spec’s issue name.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Suppressed comments (1)

Previously missed (1) — in code that hasn't changed since the last review.

docs/issues/open/2185-2003-triage-advisory-external-link-check-findings/ISSUE.md:18

• semantic-links.related-artifacts links to other issue specs via file paths under docs/issues/open/..., but issue specs can move to docs/issues/closed/. The repository convention recommends using issue #NNNN instead of an issue-spec file path to avoid stale links (see docs/skills/semantic-skill-link-convention.md:169-205).

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Lite

[josecelano]

ACK e1f44a1