fleet/fleetd
3
0
Fork 0
Code Issues 73 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

CB-584: carry agentSessionId on a failed ticket's ReleaseDetail #101

Closed
agent wants to merge 0 commits from worker/cb584-8c2281-22 into main
pull from: worker/cb584-8c2281-22
merge into: fleet:main
Conversation 1 Commits - Files Changed -
agent commented 2026-08-16 18:25:38 +02:00
Member
Copy Link
Copy Source

Closes issue #65's residual scope (item 5), the one piece 5d5b3bd deliberately left out: a failed member's agentSessionId now survives onto the failure detail a lead sees.

  • ReleaseDetail gains an agentSessionId field, populated from the released MemberSession alongside worktree/branch/snapshotRef.
  • Bridged's onRelease handler names agentSessionId=... in the abandon reason when present, alongside the existing worktree=/branch=/snapshot= fields.
  • Updates the CLAUDE.md primary intent-to-tool table row for bridge_spawn/bridge_list, which 5d5b3bd shipped the sessionName/resumeSessionId/agentSessionId surface for but never updated (out of scope for that PR, in scope for this one per issue #65's prompt-surface rule).
  • Adds a WorktreeSessionManagerTest case asserting the id actually arrives on ReleaseDetail, not just that the field exists.

Items 1-4 and 6 of the ticket (MemberSession recording agentSessionId, PeerHandle losing its default, roster exposure, bridge_spawn accepting sessionName/resumeSessionId, and refusing resumeSessionId without Capability.SESSION_RESUME) were already shipped in 5d5b3bd and verified present on main before starting this PR.

Tests: mvn clean install, unpiped -> Tests run: 830, Failures: 0, Errors: 0, Skipped: 0, BUILD SUCCESS.

Closes issue #65's residual scope (item 5), the one piece 5d5b3bd deliberately left out: **a failed member's agentSessionId now survives onto the failure detail a lead sees.** - ReleaseDetail gains an agentSessionId field, populated from the released MemberSession alongside worktree/branch/snapshotRef. - Bridged's onRelease handler names agentSessionId=... in the abandon reason when present, alongside the existing worktree=/branch=/snapshot= fields. - Updates the CLAUDE.md primary intent-to-tool table row for bridge_spawn/bridge_list, which 5d5b3bd shipped the sessionName/resumeSessionId/agentSessionId surface for but never updated (out of scope for that PR, in scope for this one per issue #65's prompt-surface rule). - Adds a WorktreeSessionManagerTest case asserting the id actually arrives on ReleaseDetail, not just that the field exists. Items 1-4 and 6 of the ticket (MemberSession recording agentSessionId, PeerHandle losing its default, roster exposure, bridge_spawn accepting sessionName/resumeSessionId, and refusing resumeSessionId without Capability.SESSION_RESUME) were already shipped in 5d5b3bd and verified present on main before starting this PR. Tests: mvn clean install, unpiped -> Tests run: 830, Failures: 0, Errors: 0, Skipped: 0, BUILD SUCCESS.
agent added 1 commit 2026-08-16 18:25:39 +02:00
CB-584: carry agentSessionId on a failed ticket's ReleaseDetail
CI / contract (pull_request) Successful in 1m6s
Details
CI / build (pull_request) Successful in 1m42s
Details
cc1df11f69 
Closes the one piece issue #65 deliberately left out of 5d5b3bd: a
released member's agentSessionId now rides alongside worktree, branch
and snapshotRef on ReleaseDetail, and Bridged's onRelease handler
names it in the abandon reason, so a lead can resume the member's
conversation instead of only re-dispatching a fresh one onto the same
files.

Also updates the CLAUDE.md bridge_spawn/bridge_list table row, which
5d5b3bd shipped the sessionName/resumeSessionId/agentSessionId surface
for but never updated.
ltms commented 2026-08-16 18:30:35 +02:00
Owner
Copy Link
Copy Source

Merged locally into main and pushed. Gitea cannot mark a locally merged PR as merged, so closing by hand — merged, not rejected. Verification is on #65. Scoping the ticket down to what was actually left, and saying so plainly, was the most useful part of this delivery.

Merged locally into `main` and pushed. Gitea cannot mark a locally merged PR as merged, so closing by hand — **merged, not rejected**. Verification is on #65. Scoping the ticket down to what was actually left, and saying so plainly, was the most useful part of this delivery.
ltms closed this pull request 2026-08-16 18:30:35 +02:00
Some checks are pending
CI / contract (pull_request) Successful in 1m6s
Details
CI / build (pull_request) Successful in 1m42s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
blocked
Cannot start until something else lands. The body says what.
 needs-live-proof
Merged and green, but never shown working on the running daemon. Not the same as done.
 ready-to-delegate
Scope, files and acceptance criteria are written. A worker can be briefed from the body alone.
 silent-default
A feature that compiles, passes tests, and ships turned off. Nine recurrences and counting.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent kevin ltms
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fleet/fleetd#101
Delete Branch "worker/cb584-8c2281-22"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?