mirror of
https://github.com/mvschwarz/openrig.git
synced 2026-11-07 05:56:21 -10:00
dev60-review
cbeb87d776
A client reviewing a finished item as a diff, such as the VS Code extension,
had only free text: a branch or a commit somewhere in the resolution, with a
guessed base. Now an assignee can record a code result as the item's
existing evidenceRef. It's a JSON file of kind openrig.code-result/v1, with:
- repo;
- base and revision as full commit ids;
- optionally paths, branch, and fetch: {remote, ref}.
rig_artifact_read (MCP) and the new rig queue artifact <qitemId> (CLI) read
the item's file through the daemon's shared roots, as before. Both now add
codeResult when the whole file is that kind and both commits are exact. A
manifest whose base or revision isn't a full commit id gets codeResultIssue,
saying why. A branch or a fetch ref stays a hint, never the revision. Any
other file reads as it did. There's no new column, store or queue state.
The CLI command and the MCP tool share one rule for which file an item's
evidenceRef names (planItemArtifact), with the tool's existing reasons.