Repository navigation
docs: require runner name on every agent comment - #41
Merged
Merged
Conversation
Debugging triage and handoff comments is hard when the runner is not identified. Update handoff.md so every outcome, handoff and escalation comment records the runner. Log templates already require it; restate the rule for clarity. Closes #36.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Debugging triage and other agent runs is hard when comments do not identify which runner produced them.
Changes
references/handoff.md: require**Runner:** $runner(or equivalent) on every outcome, handoff, triage notes, and escalation comment; add Runner to the contents table for Shepherding and Reviewing handoffs.references/log.md: restate that the YAMLrunnerkey and the prose**Runner:**line are required, and point issue/PR comments at the handoff rule.Evidence / verification
runnerin the machine-readable header — this makes the rule consistent across all agent-authored comments.ADR check
No conflict with existing ADRs.
Closes #36.