What
agentdiff remote-status should surface per-developer health alongside per-branch ref state:
- Which developers have pushed traces recently
- Which branches are silent (no traces in >7 days)
- Which hooks may be broken (branch exists in git but no agentdiff traces)
Why
An eng manager deploying agentdiff to 10 developers has no way to know if all 10 are actually capturing traces. Currently remote-status only shows refs/agentdiff/traces/{branch} ref state — not who's contributing or who went silent.
How
In remote_status.rs, after listing refs:
- Group by developer (parse author from trace entries or from ref name)
- Show last-active timestamp per developer
- Add a
--since flag to filter for recent activity only (e.g., --since 7d)
Effort
~45 min. Additive to existing remote-status command. No dependencies.
What
agentdiff remote-statusshould surface per-developer health alongside per-branch ref state:Why
An eng manager deploying agentdiff to 10 developers has no way to know if all 10 are actually capturing traces. Currently
remote-statusonly showsrefs/agentdiff/traces/{branch}ref state — not who's contributing or who went silent.How
In
remote_status.rs, after listing refs:--sinceflag to filter for recent activity only (e.g.,--since 7d)Effort
~45 min. Additive to existing remote-status command. No dependencies.