Add final-report mutation ledger verifier #331

Closed
opened 2026-07-07 02:16:27 -05:00 by jcwalker3 · 1 comment
Owner

Problem:

Reviewer final reports have claimed "File edits by reviewer: none" even after the action log showed Edited walkthrough.md. This makes final reports untrustworthy and hides local artifacts or repo mutations.

Required behavior:

Final reports must be mechanically checked for consistency against observed file write/edit actions and mutation categories.

Acceptance criteria:

  • Any Edited, Created, Wrote, generated artifact, or local file modification must appear in the mutation ledger.
  • If a file was written outside the repo, the report must include the exact path and state that it was outside the repo.
  • If a file was written inside the repo, the report must state whether it was tracked or untracked.
  • The reviewer may not claim File edits by reviewer: none if any local file was edited or generated.
  • If an artifact is written after git status, the reviewer must run and report a new final git status.
  • Default reviewer behavior should be: do not create walkthrough artifacts unless explicitly requested by the workflow or operator.
  • Rejected/no-op gated tool calls must be reported separately from performed mutations.
Problem: Reviewer final reports have claimed "File edits by reviewer: none" even after the action log showed `Edited walkthrough.md`. This makes final reports untrustworthy and hides local artifacts or repo mutations. Required behavior: Final reports must be mechanically checked for consistency against observed file write/edit actions and mutation categories. Acceptance criteria: * Any `Edited`, `Created`, `Wrote`, generated artifact, or local file modification must appear in the mutation ledger. * If a file was written outside the repo, the report must include the exact path and state that it was outside the repo. * If a file was written inside the repo, the report must state whether it was tracked or untracked. * The reviewer may not claim `File edits by reviewer: none` if any local file was edited or generated. * If an artifact is written after `git status`, the reviewer must run and report a new final `git status`. * Default reviewer behavior should be: do not create walkthrough artifacts unless explicitly requested by the workflow or operator. * Rejected/no-op gated tool calls must be reported separately from performed mutations.
jcwalker3 added the status:in-progress label 2026-07-07 03:07:44 -05:00
Author
Owner

Claiming #331 as prgs-author / jcwalker3.

Branch: feat/issue-331-mutation-ledger-verifier
Worktree: branches/feat-issue-331-mutation-ledger-verifier
LLM-Agent-SHA: llm-9f2c4a1b8e37

Claiming #331 as `prgs-author` / `jcwalker3`. Branch: `feat/issue-331-mutation-ledger-verifier` Worktree: `branches/feat-issue-331-mutation-ledger-verifier` LLM-Agent-SHA: llm-9f2c4a1b8e37
sysadmin removed the status:in-progress label 2026-07-07 03:10:32 -05:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#331