[mrizzi]

Summary

• PR feat(triage-security): add discover entry point for untriaged Vulnerabilities #344 was rebase-merged, so the triage-security pin 9fabe0ef is not an ancestor of main. It only resolves through refs/pull/344/head, which goes against the merge-commit rule in fullsend.md.
• This re-pins the triage-security base: to c4891346, the same commit as it landed on main. The base hash is unchanged (110fb33d…). Only triage-security is re-locked.
• No behaviour change: every pinned file hash in lock.yaml is the same. Only URLs, timestamps and the child-harness hash differ (the child file holds the new URL). .fullsend/harness/verify-pr.yaml and its lock entry are untouched.

Merge with a merge commit (not squash/rebase): the re-pinned c4891346 is already on main, but a rebase would rewrite this PR's own commit as well.

Test plan

• git show c4891346:harness/triage-security.yaml | shasum -a 256 gives 110fb33d…, matching the pin
• fullsend lock triage-security --fullsend-dir .fullsend succeeds; no 9fabe0ef left in lock.yaml
• git diff main -- .fullsend/harness/verify-pr.yaml is empty

Refs TC-6931

🤖 Generated with Claude Code

Summary by Sourcery

Enhancements:

• Re-pin the triage-security harness and its locked dependencies to the commit already present on main without changing pinned file content.

[sourcery-ai]

Reviewer's Guide

Re-pins triage-security to commit c489134, which is present on main, and regenerates only its lock metadata; content hashes and runtime behavior remain unchanged.

File-Level Changes

Change	Details	Files
Re-pin the triage-security harness and all resolved dependency URLs from the obsolete pull-request ref to the corresponding commit on main, while preserving content integrity.	Change the triage-security base URL from 9fabe0e to c489134 without changing its SHA-256 pin. Regenerate triage-security lock metadata so dependency URLs use c489134 and timestamps reflect the relock. Verify that all pinned file and directory hashes remain unchanged and leave verify-pr unchanged.	.fullsend/harness/triage-security.yaml .fullsend/lock.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[fullsend-ai-review]

🤖 Finished Verify Pr · ⏭️ Skipped (no Jira issue links PR #345 in its Git Pull Request field) · Started 12:11 PM UTC · Completed 12:11 PM UTC

Commit: 6bffb30 · View workflow run →

Effort: high