Skip to content

Active BackendHandle probe via running-process backend_sdk (SDK measurement run) #540

Description

@zackees

Downstream follow-up from the running-process broker v1 second-pass API post-mortem (zackees/running-process#412, §7.4 — the §6 measurement run).

fbuild currently has only a service-metadata/direct-fallback seam + diagnostics preview (fbuild#529/#530), no running-process code dependency. The second-pass backend_sdk now ships in running-process, so the deferred active BackendHandle probe is the natural fresh-integration measurement run.

Scope

  • Add the running-process dep (features client, backend-sdk).
  • Probe via BackendHandle::probe_with_service_async + a DaemonProcess identity sidecar in daemon discovery.
  • Serve probes via BackendEndpointMux in the fbuild daemon accept loop.
  • Validate with the conformance kit per running-process docs/INTEGRATE.md.

Acceptance (measurement target)

  • One PR, < 100 consumer LOC, single-doc context (INTEGRATE.md + SDK rustdoc).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions