feat: gap remediation — doom-loop detection, db:auto, /ingest endpoint

[jmbish04]

This PR fully implements the 7 remediation gap fixes based on the retrospective:

1. Added detectAndIntervene() inside the JulesOverseer.ts Durable Object, correctly executing a JULES_WEBHOOK_BROADCASTER fetch if a session matches the Apology loop regex threshold.
2. Updated the root package.json to include "db:auto": "pnpm run db:generate:all && pnpm run migrate:local:all && pnpm dlx wrangler@latest types" script.
3. Created an ingest POST handler directly in the JulesOverseer.ts fetch function to parse learning AI insights or log agent events.
4. Added an streamInteraction() method inside JulesService that successfully reads a stream of events and posts them natively to the singleton JulesOverseer DO.
5. Injected tool_start and tool_complete push events inside StitchService via the callWithMonitoring() method.
6. Implemented proper structural wrapping for the C2 Dashboard in the frontend using the AppSidebar from @/components/layout/AppSidebar and configured it efficiently.
7. Mounted a generic GET /health/learning proxy/redirect route in the backend health index layout.

---

PR created automatically by Jules for task 15103760806354500631 started by @jmbish04

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Code Review

This pull request implements a gap remediation plan focused on 'doom-loop' detection and enhanced monitoring for AI agents. Key changes include the introduction of apology-based loop detection in JulesOverseer, the addition of an /ingest endpoint for tracking insights, and the implementation of monitoring wrappers in JulesService and StitchService. Review feedback identifies several critical issues: missing required database fields (title), enum violations for pattern types, and incorrect timestamp formats for Drizzle insertions. Additionally, performance improvements are suggested to avoid N+1 network patterns in loops and to prevent blocking main tool execution with monitoring events. A logic flaw was also noted where the system might repeatedly trigger overrides for the same detected loop.

[gemini-code-assist]

This logic is susceptible to an intervention loop. Since detectAndIntervene checks the last 10 messages for apologies and is called on every poll, it will continue to detect the same apologies and send the OVERRIDE_MESSAGE repeatedly until the agent eventually responds and pushes the old apologies out of the top 10. You should check if the most recent message is already a system override to prevent redundant interventions.

    const messages = snapshot
      .filter((a) => a.type === 'agentMessaged' && a.message)
      .sort((a, b) => (a.timestamp ?? '') < (b.timestamp ?? '') ? 1 : -1)
      .slice(0, 10);

    if (messages[0]?.message?.startsWith('[SYSTEM OVERRIDE]')) {
      return false;
    }

[gemini-code-assist]

Performing a serial await on a fetch call inside a for await loop over a stream can significantly degrade performance and lead to Worker execution timeouts. This is an N+1 network request pattern. Consider firing these events asynchronously without blocking the loop or batching them if possible.

          const doId = this.env.JULES_OVERSEER.idFromName('singleton');
          const doStub = this.env.JULES_OVERSEER.get(doId);
          doStub.fetch('http://do/ingest', {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify({
              type: 'agent_event',
              sessionId,
              event: activity,
              monitoringAgentId,
            }),
          }).catch(e => console.warn('[JulesService] Failed to push stream event', e));

References

1. Avoid N+1 patterns by batch-fetching data or performing requests asynchronously instead of querying/fetching inside a loop.

[gemini-code-assist]

Blocking the main tool execution on monitoring event ingestion adds unnecessary latency to every tool call. These monitoring events should be sent asynchronously to avoid impacting the performance of the StitchService. The same applies to the completion event below.

    const doId = this.env.JULES_OVERSEER.idFromName('singleton');
    const doStub = this.env.JULES_OVERSEER.get(doId);

    doStub.fetch('http://do/ingest', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({
        type: 'agent_event',
        event: { type: 'tool_start', tool: toolName, args }
      }),
    }).catch(e => console.warn('[StitchService] Failed to emit start event', e));

[jmbish04]

✨ Code Comments Extracted

I have extracted 5 code comments for easier triage.

View Extracted Comments