feat(remote_agent): add queue telemetry driven adjacent blocks

[PiyushDatta]

Summary

• Apply WorkerPal completion 7aaa522c-836c-42c1-9284-4ac66dbca7e0 to main_agents.
• Integrate commit 42724a7741230f45937a549ba723bc0d50edf2cb from refs/pushpals/agent/workerpal-04dc03e6/7aaa522c-836c-42c1-9284-4ac66dbca7e0.
• Worker workerpal-04dc03e6 reported: Executed task and modified 3 file(s) (quality gate soft-pass after 4 auto-revision attempt(s))
• Canonical task request: In apps/remotebuddy/src/autonomous_engine.ts add an adjacent-possible objective generator that recombines recent successful motifs with current queue telemetry to propose scoped RemoteBuddy objectives, including exposing lightweight expl...

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): In apps/remotebuddy/src/autonomous_engine.ts add an adjacent-possible objective generator tha...

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-04dc03e6/7aaa522c-836c-42c1-9284-4ac66dbca7e0

• Completion ref: refs/pushpals/agent/workerpal-04dc03e6/7aaa522c-836c-42c1-9284-4ac66dbca7e0

• Commit: 42724a7741230f45937a549ba723bc0d50edf2cb

• Completion ID: 8a0e7531-07ea-46e1-a26c-7c1e09cbf59b

[PiyushDatta]

ReviewAgent: Changes Rejected (score 7.5/10)

Verdict: The feature is thoughtfully integrated and mostly coherent, but it introduces correctness and resilience risks in telemetry parsing plus lacks targeted test coverage for the new decision path.

Issues:

• Potential runtime crash when normalizing evidence: normalizeQueueSignalEvidence calls JSON.stringify(...) on arbitrary unknown values (array/object branches) without guarding against circular references, which can throw and abort objective generation; wrap stringification in a safe helper with try/catch fallback.
• Unit coercion is context-free and can corrupt non-latency metrics: coerceMetricNumber converts { value, unit: 's' } to milliseconds for any metric key, so pending/idle_workers objects with second-based units would be multiplied by 1000 incorrectly; make unit conversion key-aware (apply ms conversion only to latency keys) or pass metric-key context into coercion.
• Selection helper can emit duplicate IDs from preferred lists: selectPriorityIdsFromContext does not dedupe during the preferred-order pass, so duplicate IDs in preferredOrder can propagate into objective_ids/gap_ids; add selected.includes(id) guard in the first loop.
• No tests are shown for the new queue telemetry pipeline and adjacent block generation path: missing negative/edge tests for malformed evidence, JSON/code-fence payloads, mixed units, absent metrics, duplicate preferred IDs, and circular structures leaves regressions likely.

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

[PiyushDatta]

ReviewAgent: Changes Rejected (score 7.7/10)

Verdict: The feature is thoughtfully integrated and mostly consistent with existing patterns, but it is not production-ready yet due to missing coverage and metric-sanitization gaps that can generate misleading queue-driven decisions.

Issues:

• Missing targeted tests for new telemetry parsing and adjacent block generation paths in apps/remotebuddy/src/autonomous_engine.ts (no demonstrated positive/negative coverage for coerceMetricNumber, normalizeQueueSignalEvidence, deriveQueueTelemetry, and buildAdjacentPossibleBlocks).
• deriveQueueTelemetry accepts and propagates invalid negative metric values (e.g., negative p95Ms, pending, idleWorkers) without normalization, which can misclassify bands (latency_normal, pending_light, etc.) and skew scoring decisions.
• buildAdjacentPossibleBlocks can emit queue-driven candidates when metricConfidence is 0 (no parsed queue metrics) as long as queue_signal is high, creating low-evidence recommendations; this should be explicitly gated or down-weighted to avoid false positives.

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