Skip to content

feat(discovery): require inline source links when research findings are presented - #7946

Merged
melodic-automation-lanes[bot] merged 1 commit into
mainfrom
work-resolve-issue/issue-7840-39092789214-1
Oct 18, 2026
Merged

melodic-automation-lanes[bot] merged 1 commit into
mainfrom
work-resolve-issue/issue-7840-39092789214-1

Conversation

@melodic-automation-lanes

Copy link
Copy Markdown
Contributor

Closes #7840

Summary

Opened by the work-resolve-issue lane. The run's own summary:

The research skill's Output Format now requires the parent to cite each accepted claim with inline Markdown links from sources[].url wherever it presents findings, including a short chat recap. A local probe cites the artifact file holding its command, and a bare source name is not a citation. A new eval case checks it.

Fix

  • plugins/discovery/skills/research/SKILL.md: added a 'Cite by link wherever you present findings' rule after the Output Format list
  • plugins/discovery/skills/research/evals/evals.json: added case 44 (presented-summary-links-each-claim)
  • .changes/discovery/feat-research-inline-source-links-5b2e7a41.md: minor changelog fragment

Verification

The run reports:

Left out: nothing the run reported.

Related

#7840

…re presented

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

claude-security-review reviewed 4dcf95df64432ebce2719893d80f93d883719803: 0 finding(s), 0 as inline comments.

No security issues found in PR #7946 at head 4dcf95d.

The PR touches three files:

  • A changelog fragment.
  • A new paragraph in plugins/discovery/skills/research/SKILL.md that requires inline source links when findings are presented.
  • A new eval case, id 44, in evals.json.

The change adds an instruction and removes, narrows or softens nothing, so the instruction-surface deletion check finds no protected-class rule to compare. It adds no code, hook, permission, workflow, token or credential handling. The eval case uses public sqlite.org URLs and holds no transcript.

I did not consult the instruction exception register, because the diff removes no rule.

@github-actions

Copy link
Copy Markdown
Contributor

claude-review reviewed 4dcf95df64432ebce2719893d80f93d883719803: 0 finding(s), 0 as inline comments.

No findings on 4dcf95d. I ran no tests or validators myself; the PR body's check results (fragment validation, check-skill, check-evals-quality) are author-claimed and I did not check them.

What I checked

  • Closing issue discovery:research: require inline source links when the parent presents findings #7840: each acceptance criterion maps to the diff.
    • The new paragraph in plugins/discovery/skills/research/SKILL.md (line 256) says each accepted claim carries its primary and counted corroborators as inline [label](url) links from sources[].url.
    • It says a local probe cites the artifact file that holds its command, and that a bare source name is not a citation.
    • It covers the Summary, the Evidence table and any shorter chat recap.
    • Eval case 44 checks per-claim links and fails a name-only citation.
    • The minor changelog fragment is in .changes/discovery/.
  • Consistency with the skill's own definitions:
    • context/discipline.md:33 defines Tier 0 as direct tool output. The new text says "Tier 0 local probe", which narrows to local reads and commands. A Tier 0 gh api or MCP source that carries a URL stays covered by the link rule.
    • The sources[] schema in context/artifact-shape.md:~87 matches the sources[].url field the new text names.
    • The new paragraph does not contradict the Evidence-table wording at line 248, which asks for "the URL/command". It tightens it to a clickable link.
  • Path-scoped rules: no cost claims, no volatile upstream specifics, and no raw transcripts in eval case 44. The prompt is a synthetic scenario with example.org-free, public sqlite.org URLs.
  • Scope: the diff stays inside the discovery plugin, and the out-of-scope items (sidecar schema, enforcement hook, /discovery:explore) are untouched.

Non-blocking observation (not reported inline)

  • The eval names a probe artifact RESEARCH-probes.md. The skill only defines sidecars as RESEARCH-<section>.md, so no section by that name is defined. This is harmless because the case states the filename in its own prompt.

@melodic-automation-lanes

Copy link
Copy Markdown
Contributor Author

The unattended merge path enqueued this pull request at head 4dcf95df64432ebce2719893d80f93d883719803.

@melodic-automation-lanes
melodic-automation-lanes Bot added this pull request to the merge queue Oct 18, 2026
Merged via the queue into main with commit e0b5f1f Oct 18, 2026
24 checks passed
@melodic-automation-lanes
melodic-automation-lanes Bot deleted the work-resolve-issue/issue-7840-39092789214-1 branch October 18, 2026 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

discovery:research: require inline source links when the parent presents findings

0 participants