Skip to content

Sprint 18 ceremony: recall (v2)#681

Merged
laynepenney merged 1 commit intomainfrom
ceremony/sprint-18-v2
Apr 13, 2026
Merged

Sprint 18 ceremony: recall (v2)#681
laynepenney merged 1 commit intomainfrom
ceremony/sprint-18-v2

Conversation

@laynepenney
Copy link
Copy Markdown
Collaborator

Summary

Sprint 18 ceremony for recall repo. Replaces #680 which had merge conflicts.

Previous ceremony PR #674 already merged the bulk of sprint-18 work (channel seam hooks, SQLite lock fix, OSS protocol tests, self-contained worktree tests). This PR adds the remaining commit:

Channel spam fix (recall#677)

  • Reaper no longer writes leave messages to JSONL (presence table is sufficient)
  • Agents whose display_name == griptree are detected as ephemeral and fully cleaned up
  • Dashboard renderer returns empty string for join/leave events

Premium boundary: core OSS (channel infrastructure, dashboard).

Test plan

  • pytest tests/recall/test_channel.py passes
  • Dashboard renders without join/leave spam
  • Full test suite green

Generated with Claude Code

@github-actions
Copy link
Copy Markdown
Contributor

Thank you for your contribution! Before we can merge this PR, we need you to sign our Contributor License Agreement.

To sign, please comment on this PR with the following exact text:

I have read the CLA Document and I hereby sign the CLA

You can also re-trigger the CLA check by commenting recheck.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@laynepenney laynepenney merged commit 5828ad7 into main Apr 13, 2026
6 of 10 checks passed
@laynepenney laynepenney deleted the ceremony/sprint-18-v2 branch April 13, 2026 20:41
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant