Skip to content

test PR (debug) - #3

Closed
7723qqq wants to merge 1 commit into
mainfrom
feat/native-tools-fallback-telemetry
Closed

test PR (debug)#3
7723qqq wants to merge 1 commit into
mainfrom
feat/native-tools-fallback-telemetry

Conversation

@7723qqq

@7723qqq 7723qqq commented Jul 23, 2026

Copy link
Copy Markdown
Owner

debug

Each tryNative* call now records a native_tool_fallback telemetry event
with one of disabled | load_failed | function_missing | function_threw,
and logs once per (tool, reason) via console.warn so broken native
binaries are visible without spam.

The internal loader is now an explicit four-state machine
(unloaded | disabled | load_failed | loaded) so flag-off vs binary-
missing/ABI-mismatch are distinguishable in telemetry. setNativeTelemetry
is wired automatically in SDKRpcClient from the harness telemetry option,
so app code needs no change.

No new lint warnings, typecheck clean, two new vitest cover the disabled
branch and the warn-once-vs-telemetry-each-call semantics.
@7723qqq 7723qqq closed this Jul 23, 2026
7723qqq added a commit that referenced this pull request Aug 10, 2026
- http.rs: widen the shared turn-context grace period from 100ms to 2s —
  a lagging WS projector could miss turn.started after the async-submit
  cleanup, silently dropping the whole turn projection and leaving its
  messages stuck in pending (v1 #2/MoonshotAI#5)
- kimi-web agent projector: only emit the client-accumulated usage
  snapshot at turn end when the turn actually reported step usage, so the
  authoritative event.session.usage_updated numbers are no longer
  clobbered with zeros (v1 #3)
- regression tests for the usage gating
7723qqq added a commit that referenced this pull request Aug 10, 2026
…MoonshotAI#5)

- eventReducer messageUpdated now stores the protocol status on the
  message instead of dropping it, so streamed assistant messages leave
  their initial/pending state when the Rust server projects the
  completed close-out
- AppMessage gains an optional status field; REST snapshot messages map
  as completed history (toAppMessage status param), WS-created messages
  stay unset until message.updated arrives
- regression test covers the status hand-off; G-2 #2/#3 verified already
  fixed (take_turn 2s grace, usage_updated consumption)
7723qqq added a commit that referenced this pull request Aug 10, 2026
…shotAI#5)

- new mappers-to-app-event tests lock message.updated status and
  session.usage_updated normalization onto the AppEvent shapes the
  Rust server projects
- toAppMessage status parameter covered: snapshot loads carry
  'completed', WS-created messages stay unset until message.updated
- record the G-3 entry-switch assessment: the TS command surface is
  equivalent (plugin_run_node is superseded by the engine plugin model);
  the remaining blocker is the stage-F distribution packaging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant