feat(remote_agent): update remotebuddy implementation

[PiyushDatta]

Summary

• Apply WorkerPal completion 5802bde4-9dbf-46d8-9c5c-57bab5050e73 to main_agents.
• Integrate commit d02f906db3e080455624c926fa1014666d70adb2 from refs/pushpals/agent/workerpal-1f484a44/5802bde4-9dbf-46d8-9c5c-57bab5050e73.
• Worker workerpal-1f484a44 reported: Executed task and modified 1 file(s)
• Canonical task request: Within apps/remotebuddy/src/autonomous_engine.ts, add queue-health-aware opportunity-graph scoring so the planner boosts preventive work when p95 latency stays below ~2000 ms and throttles when it rises; keep all edits in this file only ...

Motivation / Context

• Preserve and review autonomous worker output before final merge to base branch.
• Keep integration branch current with queued worker completions.

Planned Scope

• apps/remotebuddy/src/autonomous_engine.ts

Planned Validation

• Planned: bun run test:root

Changes

• Updated apps/remotebuddy/src/autonomous_engine.ts

Testing / Validation

• Planned: bun run test:root
• Worker completion summary did not include explicit command pass/fail output.

Impact / Risk

• Risk level: medium (automated worker-generated change; maintainer review required).
• No secrets or credentials are expected in this PR body.

SourceControlManager Note

• Use this worker-provided PR title/body when creating the integration PR.
• Suggested title: fix(repo): Within apps/remotebuddy/src/autonomous_engine.ts, add queue-health-aware opportunity-graph sc...

Checklist

• Tests added/updated where appropriate

• Validation commands run (or noted as not run)

• Docs/comments updated if needed

• No sensitive data (secrets/tokens) committed

• Agent branch: agent/workerpal-1f484a44/5802bde4-9dbf-46d8-9c5c-57bab5050e73

• Completion ref: refs/pushpals/agent/workerpal-1f484a44/5802bde4-9dbf-46d8-9c5c-57bab5050e73

• Commit: d02f906db3e080455624c926fa1014666d70adb2

• Completion ID: 404f8026-b165-401d-96d6-c6917fb4d314

[PiyushDatta]

ReviewAgent: Changes Rejected (score 7.8/10)

Verdict: The change improves adaptive opportunity-graph scoring and adds basic tests, but it is not yet production-ready due to test-placement/runtime-risk and incomplete metric parsing/coverage.

Issues:

• Production code now contains inline test registration (shouldRegisterAutonomousEngineInternalTests + dynamic import("bun:test")), which introduces test-only side effects in runtime modules and can impact bundling/startup behavior; move these tests to a dedicated test file and remove test bootstrap logic from autonomous_engine.ts.
• The dynamic test import swallows all failures with .catch(() => {}), which can hide real test/environment problems and make CI diagnostics unreliable; remove the silent catch or fail loudly in test mode.
• Latency unit parsing is not robust for common microsecond forms like µs/μs because unit normalization strips non-ASCII and can collapse to s, risking wrong conversion; explicitly normalize both micro symbols to us before unit classification and add tests for those inputs.
• New behavior lacks direct tests for extractQueueHealthMetrics source/prioritization logic (signal vs trait, competing candidates, unknown fallback), leaving high-risk selection behavior unverified; add targeted unit tests with assertions for chosen value/source across conflicting evidence cases.

This PR has been re-queued for automated fixes. A worker will address the issues above.

[PiyushDatta]

ReviewAgent: Changes Rejected (score 6.8/10)

Verdict: The PR adds valuable telemetry and engine logic, but it introduces at least two behavior regressions that make it unsafe for production as-is.

Issues:

• High: apps/remotebuddy/src/startup/checklist.ts adds mandatory Bun/Docker preflight checks that fail when versions are not explicitly provided (default Docker probe reads process.env.DOCKER_VERSION, commonly unset), which can block startup/dispatch in valid environments; make these checks non-blocking when version cannot be detected or implement reliable runtime probes with graceful fallback.
• High: apps/server/src/server_main.ts changes autonomy event emission from type: "question_answered" to type: "log" for answered questions, which is a breaking contract change for consumers that filter/aggregate by event type; preserve the original event type (or emit both with versioned schema migration).
• Medium: LLM usage telemetry path lacks end-to-end failure-path tests (e.g., /telemetry/llm-usage 400/500, network errors, malformed payload), so reliability and observability guarantees are unverified; add negative tests for reporter behavior and server validation responses.
• Medium: Startup checklist changes add richer error payloads (raw, stack) but no sanitization/redaction guard is shown before telemetry/log emission, risking leakage of sensitive internals in telemetry sinks; sanitize or strip sensitive fields before emission.

This PR has been re-queued for automated fixes. A worker will address the issues above.