fix: retain sessions when project discovery fails #15

Merged
kakashi-forgejo-writer merged 1 commit from fix/session-discovery-partial-failure into main 2026-11-17 17:59:20 +00:00
Member

Focus

Retain successfully fetched conversations when remote project discovery fails. Previously Promise.all discarded both results, replacing the agent tree with an empty unavailable snapshot even when stream discovery succeeded.

Use independent settled responses; retain successful streams/projects and stream feature flags. Display a partial-discovery notice when one request fails. Both failures remain unavailable. No retries, sharing changes, stored-session writes or fabricated cached sessions.

This fixes a reproduced visibility failure, not proof that it caused the reported missing history. Complements already merged layout PR #14; does not recreate it or replace the newer PI deployment.

Verification

  • npm run build: PASS
  • node --test test/*.test.mjs: 18/18 PASS
  • Four discovery regression cases cover all success/failure combinations and unchanged read-only request payloads.
  • git diff --check: PASS

Delivery

Source change only. Current central PI image source/build provenance remains unresolved; this PR does not claim live activation.

## Focus Retain successfully fetched conversations when remote project discovery fails. Previously Promise.all discarded both results, replacing the agent tree with an empty unavailable snapshot even when stream discovery succeeded. Use independent settled responses; retain successful streams/projects and stream feature flags. Display a partial-discovery notice when one request fails. Both failures remain unavailable. No retries, sharing changes, stored-session writes or fabricated cached sessions. This fixes a reproduced visibility failure, not proof that it caused the reported missing history. Complements already merged layout PR #14; does not recreate it or replace the newer PI deployment. ## Verification - npm run build: PASS - node --test test/*.test.mjs: 18/18 PASS - Four discovery regression cases cover all success/failure combinations and unchanged read-only request payloads. - git diff --check: PASS ## Delivery Source change only. Current central PI image source/build provenance remains unresolved; this PR does not claim live activation.
fix: retain sessions when project discovery fails
All checks were successful
dashboard-ci / check (push) Successful in 35s
b304cc527f
Collaborator

Kakashi review — head b304cc527fac835bb7f51956fb5b8bde0b3c46de, base 12d0458174a0e04345a7ecd221ccd945d246ba58

review_clear

Kakashi review — head `b304cc527fac835bb7f51956fb5b8bde0b3c46de`, base `12d0458174a0e04345a7ecd221ccd945d246ba58` review_clear <!-- kakashi-review:0b1c94f54e80cc402167885a38aa5317db92cc08ca5c497dbc39b3cba275af8e -->
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/webui!15
No description provided.