chore: add few last fixes

[coodos]

Description of change

Issue Number

Type of change

• Breaking (any change that would cause existing functionality to not work as expected)
• New (a change which implements a new feature)
• Update (a change which updates existing functionality)
• Fix (a change which fixes an issue)
• Docs (changes to the documentation)
• Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• New Features

  • Added top-level service nodes to the monitoring graph.
  • Status area is always visible with clear step labels and final “Complete” state.
  • Header now shows dynamic counts and current step.

• Refactor

  • Auto-starts live event subscription on load and avoids redundant reconnections.
  • Data Flow panel is now non-interactive to prevent accidental clicks.

• Style

  • Removed header shadow and adjusted cursor/interaction cues.
  • Reorganized node layout for clarity.
  • Hid connection handles on service nodes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Introduces three top-level service nodes (registry, ontology, provisioner), repositions existing eVault and platform nodes, auto-starts SSE subscription on mount with initial sequence state, updates SSE subscription guard to avoid redundant reconnects, makes Data Flow panel non-interactive with revised status text, tweaks header/panel styling, and hides handles on service nodes.

Changes

Cohort / File(s)	Summary of Changes
Monitoring page layout and nodes infrastructure/control-panel/src/routes/monitoring/+page.svelte	Added service nodes (registry, ontology, provisioner) at y=50; moved eVault and platform nodes to start at y=500 with index-based spacing; hid Svelte Flow handles for service nodes.
SSE lifecycle and initialization .../monitoring/+page.svelte	On mount: auto-subscribe to SSE and set sequenceStarted=true, currentFlowStep=0; replaced close-and-restart with guarded subscribe (only if no active EventSource); retained existing try/catch parsing.
Data Flow panel behavior and text .../monitoring/+page.svelte	Removed onclick/cursor-pointer; panel is non-interactive; always shows status with “Current Step: Waiting for events...” at step 0 and explicit labels for steps 1–5 through “Complete”.
UI styling adjustments .../monitoring/+page.svelte	Removed header shadow; updated panel classes for non-interactive state; minor header text updates to show dynamic counts and current step when available.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor U as User
  participant P as Monitoring Page
  participant SSE as EventSource
  participant S as Server

  U->>P: Navigate to page
  activate P
  note right of P: onMount()
  P->>P: sequenceStarted=true<br/>currentFlowStep=0
  alt No active EventSource
    P->>SSE: subscribeToEvents()
    SSE->>S: Open SSE stream
  else EventSource exists
    P->>P: Keep existing connection
  end

  rect rgba(200,230,255,0.3)
  SSE-->>P: message(event)
  P->>P: parse JSON (try/catch)
  P->>P: update currentFlowStep/status
  end

  opt Reset action
    P->>P: Reset sequence state only
    note right of P: Connection persists (no close/restart)
  end

  U->>P: View non-interactive Data Flow panel
  deactivate P

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

I hop through streams of SSE,
Ears up for steps one through three—
New service nodes above the fray,
Flow panels calm, no clicks today.
Handles hidden, headers light—
Carrots count the steps just right. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e9c7b6d and 19a6a9f.

📒 Files selected for processing (1)

• infrastructure/control-panel/src/routes/monitoring/+page.svelte (7 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/control-panel-auto-subscribe

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.