anchor_resolve
Resolve code finding anchors to current HEAD lines, returning statuses for moved, lost, or ambiguous locations to keep tracking accurate.
Instructions
Resolve stored location anchors to their current lines on HEAD.
Each anchored finding gets a record: status (current / moved /
moved_file / lost / ambiguous / unknown), the coordinate, the channel
that produced it ("git" for reverse blame, "content" for the secondary
text channel), a reason token when there is no answer, and
survived as "/" when part of a span outlived the rest.
moved_file is a status of its own, not moved with a different path:
the code left the file the finding names, and a consumer must see that
rather than receive a line number in a file it never asked about.
THE SUMMARY'S DENOMINATOR IS anchored, NOT total. anchored counts
the rows that CARRY an anchor (a persisted refusal and the tombstone
included); rows filed before anchors existed carry none and are counted
in without_anchor instead. So a moved_file share is
summary["moved_file"] / anchored; computing it against total is a
share of a population the number does not describe.
Args:
finding_id: Resolve one finding instead of a population
status: Status filter; "all" widens to every status (default: open)
category: Restrict to one category
file: Restrict to one file (the finding's
filecolumn)project_dir: The repository the anchors resolve against. Omitting it reports
no_rootrather than reading whatever tree the server process happens to stand in — a long-lived server's cwd has nothing to do with the tracker a call is aboutlimit: Maximum findings examined (default 10000). 0 means NO findings are examined; a negative value is an error (it used to mean "no limit").
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | ||
| limit | No | ||
| status | No | open | |
| category | No | ||
| finding_id | No | ||
| project_dir | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||