Skip to content

fix(dsh): honor server fallback flag in Context tab ownership check #2

Closed

Description

@Moeblack

Model: gpt-6-astra (audit and regression by deepseek-flash-vision)

Baseline 07888d7 / 0.1.204. Category: DSH UI/session binding.

handlePluginStatus emits fallback:true for fallback=latest responses, while parseCtxStatus reads only viaFallback. The Context tab ownership guard therefore never fires for real server responses. Opening conversation B before its first model call can embed conversation A’s compression view.

The existing regression mock used viaFallback:true, unlike the actual server contract. Fix: accept the real fallback field, retaining the legacy alias; test real server-shaped foreign fallback rejection and own-conversation fallback acceptance.

This is a functional display bug, not a security audit. No server protocol or config changes are needed. Related upstream ranxianglei#4118 established the guard but did not align the field name; source at the current fork baseline still mismatches.

Activity

  1. added
    p2Functional defect with a workaround or local impact
    scope/uiUser interface and controls
    dshDeepSeek Harness host integration
    on Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dshDeepSeek Harness host integrationp2Functional defect with a workaround or local impactscope/uiUser interface and controls

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions