feat(remote_agent): seed adjacent possible objectives via gated fusion

[PiyushDatta]

Summary

• Apply WorkerPal completion a512bc2e-f8d5-4c3b-9b5f-45cd99fdd814 to main_agents.
• Integrate commit baf2883fa7e3ca462863590eb043a02a86a79157 from refs/pushpals/agent/workerpal-f399b0a7/a512bc2e-f8d5-4c3b-9b5f-45cd99fdd814.
• Worker workerpal-f399b0a7 reported: Executed task and modified 1 file(s)
• Canonical task request: Update apps/remotebuddy/src/autonomous_engine.ts so the autonomous planner builds an adjacent-possible graph from recent successful motifs, recombines them into candidate objectives, and only seeds the new ideas when queue slack and idle...

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): Update apps/remotebuddy/src/autonomous_engine.ts so the autonomous planner builds an adjacent...

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-f399b0a7/a512bc2e-f8d5-4c3b-9b5f-45cd99fdd814

• Completion ref: refs/pushpals/agent/workerpal-f399b0a7/a512bc2e-f8d5-4c3b-9b5f-45cd99fdd814

• Commit: baf2883fa7e3ca462863590eb043a02a86a79157

• Completion ID: 12da7f4e-287c-42d8-a2e9-ce02a1312d6d

[PiyushDatta]

ReviewAgent: Changes Rejected (score 7.8/10)

Verdict: The feature is thoughtfully implemented with solid core tests, but it has maintainability and correctness gaps around test placement, external-status failure handling coverage, and candidate-scope fallback behavior.

Issues:

• Production source now embeds extensive test code behind process.env.NODE_ENV === "test" in apps/remotebuddy/src/autonomous_engine.ts; this couples runtime and test concerns, increases file complexity, and risks accidental bundle/runtime side effects if environment handling changes. Move these tests into dedicated test files.
• New /system/status integration (fetchSystemStatus) lacks direct tests for HTTP non-OK, JSON parse failure, empty payload, and transport exceptions, so key gating behavior is unverified at the boundary where seeding is enabled/disabled.
• In buildAdjacentPossibleCandidates, when validateScopeInvariants fails, logic silently falls back to base motif paths/globs but still emits an 'adjacent fusion' candidate; this can misrepresent fused scope and produce seeds that do not include partner-area changes. Either skip such candidates or emit explicit degraded metadata and title/problem text that matches the reduced scope.
• Seeding candidates are always generated before gate evaluation in the main tick path; under sustained congestion this does unnecessary graph/candidate work each cycle. Gate first (or add a fast precheck) to reduce avoidable CPU overhead in degraded states.

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

[PiyushDatta]

ReviewAgent: Changes Rejected (score 7.6/10)

Verdict: The feature is thoughtfully implemented and well-tested in core paths, but it has idempotency and test-structure risks that make it short of production-ready quality.

Issues:

• Adjacent seed IDs are salted with runId (deterministicAdjacentCandidateId(pairKey, params.seedSalt) with seedSalt: runId), which makes the same motif pair generate a different candidate ID every tick; this breaks idempotency and can create duplicate objectives across retries/runs instead of allowing stable dedupe.
• Tests are embedded in the production module behind if (process.env.NODE_ENV === "test") and wrapped in an async IIFE; this can cause brittle test registration/timing behavior with runners and increases runtime/module risk for non-test execution paths.
• Gating computes queueLatencyP95 but does not enforce any latency threshold, so seeding can proceed while queue latency is severely degraded as long as slack/idle thresholds pass; this is an operational regression risk for overload scenarios.

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