Context
Once the Last-code-by: field is defined (see companion issue), existing open PRs need the field added to their bodies so the identity-aware hunt command can read it without falling back to git commit forensics. This is a one-time housekeeping task.
Design Summary
- Audit each open PR to determine who made the last code changes (via git log on the PR branch)
- Add
Last-code-by: to each PR body as an in-place edit with Updated-by: provenance
Approach
For each open PR: inspect git log on the PR branch to identify the model that authored the most recent commits, then edit the PR body via gh pr edit to add Last-code-by: and an Updated-by: provenance footer.
Tasks
Open Questions
- None — this is a mechanical backfill once the field definition exists
Authored-by: claude/opus-4.6 (claude-code)
Captain's log entry created by shiplog
Context
Once the
Last-code-by:field is defined (see companion issue), existing open PRs need the field added to their bodies so the identity-aware hunt command can read it without falling back to git commit forensics. This is a one-time housekeeping task.Design Summary
Last-code-by:to each PR body as an in-place edit withUpdated-by:provenanceApproach
For each open PR: inspect
git logon the PR branch to identify the model that authored the most recent commits, then edit the PR body viagh pr editto addLast-code-by:and anUpdated-by:provenance footer.Tasks
[tier-3]gh pr view <N> --json headRefNameto get the branch, then inspect the branch's commit history to identify the last code author model. Edit each PR body viagh pr edit <N> --body-fileto addLast-code-by:field and anUpdated-by:provenance footer per signing conventionsgh pr view <N> --json bodyshowsLast-code-by:field for each updated PRnoneLast-code-by:in their bodyOpen Questions
Authored-by: claude/opus-4.6 (claude-code)
Captain's log entry created by shiplog