Repository navigation
Restore current PR trajectory summaries - #75
Merged
Merged
Conversation
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.
Review on ArchCode
Problem and author intent
PR evidence still uploaded its prompt, trajectory, and patch artifact, but the Room stopped publishing the compact trajectory summary card that makes that evidence discoverable. Restore one current, author-owned summary per PR without waking Participate routines or accumulating stale cards.
What changed
exhaustmessage withpost_type: trajectoryafter the policy-applied current artifact is attached.Scope
Room-kit client and tests only. No platform or UI code.
Risk assessment
Low to medium. This adds one best-effort message create on first publication and one update when PR evidence changes. Deterministic identity, author ownership, current-artifact checks, and retry recovery prevent duplicate or stale summaries.
User impact
Engineers see the compact “How PR was built” card again. Later evidence replaces that card in place, so Rooms retain the latest complete summary rather than stale versions.
Testing
tests/test_pr_evidence_publish.py—test_two_agent_sessions_publish_one_current_artifact_over_tcp_without_githubis the canonical end-to-end proof. It runs the real CLI against a TCP server, publishes two sessions, verifies one attachment and one summary, then proves the unchanged retry performs no writes.python3 tests/test_pr_evidence_publish.pypython3 tests/test_pr_evidence_conflict.pypython3 tests/test_trajectory_summary.py— 8/8 passed.python3 tests/test_pr_evidence_performance.py— unchanged CLI p95 0.1841s.Follow-ups and known issues
The existing Room UI owns the visual trajectory-card renderer; this PR restores its event contract.