Naiyuan Qing b5992c4454 fix(featureflags): publish the hang stack capture flag to clients (MUL-5345) (#6079) ...

#6026 shipped the desktop half of hang stack capture fail-closed: the renderer
only enables it when `desktop_hang_stack_capture` arrives from `/api/config` as
an explicit true. The server half was missing — the key was never added to
`frontendPublicFlags`, so `/api/config` never published it and the client had
nothing to receive.

The effect in production is that capture has been inert since release. 0.4.13
recorded two real hard hangs in its first 14 hours and both came back with
empty `stack_*` fields, which reads like "nobody turned the flag on" but is not
fixable that way: with the key absent from the published set, enabling it in
the flag service would not have reached any client.

Publishing it changes no behaviour on its own — the default is off, and the
desktop side still requires an explicit true — it only makes the switch
reachable.

Co-authored-by: multica-agent <github@multica.ai>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

2026-07-29 13:37:53 +08:00

..

keys_test.go

fix(featureflags): publish the hang stack capture flag to clients (MUL-5345) (#6079)

2026-07-29 13:37:53 +08:00

keys.go

fix(featureflags): publish the hang stack capture flag to clients (MUL-5345) (#6079)

2026-07-29 13:37:53 +08:00