Decompose roadmap task for CLI and daemon work

[leynos]

Summary

• break down the Phase 1 roadmap entry for implementing weaver-cli and weaverd into scoped sub-tasks covering configuration, CLI behaviour, daemon bootstrap, process management, and lifecycle commands.

Testing

• make fmt (fails: existing markdownlint violations in docs/weaver-design.md)

---

https://chatgpt.com/codex/tasks/task_e_68e05c9ac038832289ec9dfc2118b8fa

Summary by Sourcery

Decompose the Phase 1 roadmap entry into scoped sub-tasks for configuration, CLI behaviour, daemon bootstrap, process management, and lifecycle commands, and align checklist formatting across all roadmap phases.

Documentation:

• Break down Phase 1 roadmap into discrete checklist items for shared configuration, CLI executable, daemon bootstrap, daemonisation, and lifecycle commands
• Normalize list formatting and indentation for roadmap entries across phases 1–4

[sourcery-ai]

Reviewer's Guide

This PR restructures the Phase 1 roadmap entry in docs/roadmap.md by breaking down broad CLI and daemon goals into fine‐grained subtasks covering configuration, CLI behavior, daemon bootstrap, process management, and lifecycle commands, while also normalizing markdown list formatting and indentation throughout the document.

Class diagram for new and updated CLI/daemon components in roadmap

classDiagram
    class WeaverConfig {
      +schema
      +mergeConfigFiles()
      +environmentOverrides()
      +cliFlags()
    }
    class WeaverCLI {
      +initialiseConfig()
      +probeCapabilities()
      +streamRequests()
      +lifecycleCommands()
    }
    class Weaverd {
      +bootstrap()
      +consumeConfig()
      +startBackends()
      +superviseBackends()
      +structuredLogging()
      +errorReporting()
      +daemonise()
      +processManagement()
      +healthChecks()
      +gracefulShutdown()
    }
    WeaverCLI --> WeaverConfig : uses
    Weaverd --> WeaverConfig : uses

Loading

File-Level Changes

Change	Details	Files
Decompose Phase 1 roadmap entry into detailed sub-tasks	Define shared configuration schema using ortho-config Implement weaver-cli as a JSONL client over stdio with --capabilities probe Implement weaverd bootstrap with lazy backend startup and structured logging Add daemonisation and process management (daemonize-me, PID/lock files, health checks, signal shutdown) Provide CLI lifecycle commands (daemon start/stop/status) with socket checks and error handling	docs/roadmap.md
Normalize markdown formatting and list indentation	Convert unchecked items to consistent hyphen-prefixed lists Wrap goal descriptions across lines for readability Adjust indentation for nested list items to match style guidelines	docs/roadmap.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Summary by CodeRabbit

• Documentation
  • Expanded roadmap with detailed, step-by-step plans across Phases 1–4, replacing placeholders with concrete deliverables and acceptance criteria.
  • Clarified MVP sequencing, including configuration, CLI/daemon lifecycle, and security/sandboxing emphasis.
  • Standardised wording, formatting, and indentation for consistency across phases.
  • Refined descriptions for plugin and analysis components, aligning with human-in-the-loop and Meta-RAG flows.
  • Updated Phase goals to clearer, multi-line statements.
  • Minor correction in Phase 0 checklist state.

Walkthrough

Summarise the docs/roadmap.md updates: rewrite and expand Phase 1–4 roadmap entries into stepwise, actionable tasks with explicit deliverables, acceptance criteria, and named crates/files; adjust formatting and wording across phases; no code, API, or control-flow changes.

Changes

Cohort / File(s)

Summary

Roadmap documentation docs/roadmap.md

Replace terse placeholders with explicit, stepwise plans for Phase 0–4: mark Phase 0 checkbox; restructure Phase 1 into CLI/daemon foundation (weaver-cli, weaverd, weaver-config, ortho-config), deliverables, acceptance criteria, streaming/probing, daemonisation and lifecycle commands; standardise Phase 2 wording for weaver-syntax and weaver-graph; reflow Phase 3 plugin architecture (weaver-plugins, rope, srgn, Jedi) and graceful degradation; update Phase 4 onboarding/interactive-mode and dynamic analysis ingestion wording. Pure documentation changes; no functional code edits.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant User
    participant CLI as weaver-cli
    participant Config as ortho-config / weaver-config
    participant Daemon as weaverd
    rect rgb(235,245,255)
      Note over CLI,Daemon: Phase 1 — CLI/Daemon lifecycle (new doc plan)
    end
    User->>CLI: invoke command (start|status|stop|bootstrap)
    CLI->>Config: load/validate config schema
    CLI->>Daemon: send bootstrap/start request (IPC)
    Daemon->>Config: read runtime config
    Daemon-->>CLI: ack / streaming logs
    alt daemon not running
      CLI->>Daemon: request daemonisation (fork/exec)
      Daemon->>Daemon: initialise namespaces/seccomp (weaver-sandbox)
    end
    CLI->>Daemon: lifecycle commands (stop|restart|status)
    Daemon-->>User: stream events/logs (async)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

Roadmap lines now stand in files bright, ✨
Steps named clear beneath the planning light.
Daemons dream on paper plains,
Plugins plotted, graphs and chains.
No code stirs — just paths to write.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	Acknowledge that the title accurately encapsulates the decomposition of the Phase 1 roadmap tasks for CLI and daemon work, reflecting the primary change concisely and with clarity. Highlight its focused wording and absence of extraneous elements.
Description Check	✅ Passed	Recognise that the description outlines the breakdown of the Phase 1 roadmap into scoped sub-tasks for CLI and daemon work and provides context on testing, aligning directly with the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/update-roadmap-with-sub-tasks-for-weaver-cli

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d09327d and 88c8dd3.

📒 Files selected for processing (1)

• docs/roadmap.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.md

⚙️ CodeRabbit configuration file

**/*.md: * Avoid 2nd person or 1st person pronouns ("I", "you", "we")

• Use en-GB-oxendict (-ize / -yse / -our) spelling and grammar
• Headings must not be wrapped.
• Documents must start with a level 1 heading
• Headings must correctly increase or decrease by no more than one level at a time
• Use GitHub-flavoured Markdown style for footnotes and endnotes.
• Numbered footnotes must be numbered by order of appearance in the document.

Files:

• docs/roadmap.md

🔍 Remote MCP Deepwiki

Summary of additional context relevant to this PR (docs/roadmap.md edits):

• Changed file: docs/roadmap.md (repository root). Edits expand Phase 1–4 roadmap items into concrete, stepwise deliverables (adds named crates/files: weaver-cli, weaverd, weaver-config, weaver-lsp-host, weaver-sandbox, weaver-schemas, etc.).
• Repo documentation/wiki contains detailed design and component pages describing the client-daemon architecture, RPC protocol, schemas (weaver_schemas), CLI command surface and daemon handlers — useful to verify roadmap alignment with existing modules (weaver CLI, weaverd, weaver_schemas).
• Project wiki index confirms docs/roadmap.md is part of the repo docs and lists core components and pages you may reference while reviewing scope/terminology.

Notes for reviewers (actionable):

• This PR is documentation-only (roadmap content) — no code/API changes detected in the repo docs snapshot above; review focus should be clarity, correctness, and alignment with existing module names/architecture.
• Cross-check newly mentioned items (e.g., "ortho-config") against the codebase and packaging (weaver_schemas, weaver/cli, weaverd) to ensure names and proposed crates/configs map to actual modules or require new work; the repo docs/wiki are the authoritative reference for current module names.

Sources:

• Repository wiki structure and pages: Deepwiki_read_wiki_structure, Deepwiki_read_wiki_contents.,

⏰ Context from checks skipped due to timeout of 120000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Sourcery review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `docs/roadmap.md:14` </location>
<code_context>
+for write operations from day one.*
+
+- [ ] Define the shared configuration schema for `weaver-cli` and `weaverd`
+        in `weaver-config`, using `ortho-config` to merge config files,
+        environment overrides, and CLI flags for daemon sockets, logging, and
+        the capability matrix defaults.
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point exceeds the 80 column wrapping limit for paragraphs and bullets.

Please ensure that all bullet points and paragraphs are wrapped to 80 columns for readability and consistency.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 2
<location> `docs/roadmap.md:15` </location>
<code_context>
+
+- [ ] Define the shared configuration schema for `weaver-cli` and `weaverd`
+        in `weaver-config`, using `ortho-config` to merge config files,
+        environment overrides, and CLI flags for daemon sockets, logging, and
+        the capability matrix defaults.
+- [ ] Implement the `weaver-cli` executable as the thin JSONL client that
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Consider wrapping this line to 80 columns to comply with the formatting guidelines.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 3
<location> `docs/roadmap.md:16` </location>
<code_context>
+- [ ] Define the shared configuration schema for `weaver-cli` and `weaverd`
+        in `weaver-config`, using `ortho-config` to merge config files,
+        environment overrides, and CLI flags for daemon sockets, logging, and
+        the capability matrix defaults.
+- [ ] Implement the `weaver-cli` executable as the thin JSONL client that
+        initialises configuration via `ortho-config`, exposes the
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns as per the review instructions.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 4
<location> `docs/roadmap.md:18` </location>
<code_context>
+        environment overrides, and CLI flags for daemon sockets, logging, and
+        the capability matrix defaults.
+- [ ] Implement the `weaver-cli` executable as the thin JSONL client that
+        initialises configuration via `ortho-config`, exposes the
+        `--capabilities` probe, and streams requests to a running daemon over
+        standard IO.
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns for consistency with the formatting requirements.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 5
<location> `docs/roadmap.md:19` </location>
<code_context>
+        the capability matrix defaults.
+- [ ] Implement the `weaver-cli` executable as the thin JSONL client that
+        initialises configuration via `ortho-config`, exposes the
+        `--capabilities` probe, and streams requests to a running daemon over
+        standard IO.
+- [ ] Implement the `weaverd` daemon bootstrap that consumes the shared
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns as per the formatting guidelines.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 6
<location> `docs/roadmap.md:20` </location>
<code_context>
+- [ ] Implement the `weaver-cli` executable as the thin JSONL client that
+        initialises configuration via `ortho-config`, exposes the
+        `--capabilities` probe, and streams requests to a running daemon over
+        standard IO.
+- [ ] Implement the `weaverd` daemon bootstrap that consumes the shared
+        configuration, starts the Semantic Fusion backends lazily, and
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns for improved readability.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 7
<location> `docs/roadmap.md:22` </location>
<code_context>
+        `--capabilities` probe, and streams requests to a running daemon over
+        standard IO.
+- [ ] Implement the `weaverd` daemon bootstrap that consumes the shared
+        configuration, starts the Semantic Fusion backends lazily, and
+        supervises them with structured logging and error reporting.
+- [ ] Implement robust daemonisation and process management for `weaverd`,
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns as required by the review instructions.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 8
<location> `docs/roadmap.md:23` </location>
<code_context>
+        standard IO.
+- [ ] Implement the `weaverd` daemon bootstrap that consumes the shared
+        configuration, starts the Semantic Fusion backends lazily, and
+        supervises them with structured logging and error reporting.
+- [ ] Implement robust daemonisation and process management for `weaverd`,
+        including backgrounding with `daemonize-me`, PID/lock file handling,
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns for consistency.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 9
<location> `docs/roadmap.md:25` </location>
<code_context>
+        configuration, starts the Semantic Fusion backends lazily, and
+        supervises them with structured logging and error reporting.
+- [ ] Implement robust daemonisation and process management for `weaverd`,
+        including backgrounding with `daemonize-me`, PID/lock file handling,
+        health checks, and graceful shutdown on signals.
+- [ ] Provide lifecycle commands in `weaver-cli` (e.g. `daemon start`, `daemon
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns as per the formatting requirements.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 10
<location> `docs/roadmap.md:26` </location>
<code_context>
+        supervises them with structured logging and error reporting.
+- [ ] Implement robust daemonisation and process management for `weaverd`,
+        including backgrounding with `daemonize-me`, PID/lock file handling,
+        health checks, and graceful shutdown on signals.
+- [ ] Provide lifecycle commands in `weaver-cli` (e.g. `daemon start`, `daemon
+        stop`, `daemon status`) that manage the daemon process, verify socket
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns for improved readability.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 11
<location> `docs/roadmap.md:28` </location>
<code_context>
+        including backgrounding with `daemonize-me`, PID/lock file handling,
+        health checks, and graceful shutdown on signals.
+- [ ] Provide lifecycle commands in `weaver-cli` (e.g. `daemon start`, `daemon
+        stop`, `daemon status`) that manage the daemon process, verify socket
+        availability, and surface actionable errors when start-up fails.
+
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns as per the formatting guidelines.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 12
<location> `docs/roadmap.md:29` </location>
<code_context>
+        health checks, and graceful shutdown on signals.
+- [ ] Provide lifecycle commands in `weaver-cli` (e.g. `daemon start`, `daemon
+        stop`, `daemon status`) that manage the daemon process, verify socket
+        availability, and surface actionable errors when start-up fails.
+
+- [ ] Build the `weaver-lsp-host` crate with support for initialisation,
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns for consistency.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 13
<location> `docs/roadmap.md:76` </location>
<code_context>

-    -   [ ] A plugin for `srgn` to provide high-performance, precision syntactic editing.
+  - [ ] A plugin for `srgn` to provide high-performance, precision
+        syntactic editing.

--   [ ] Develop the first specialist sensor plugin:
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns for improved readability.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 14
<location> `docs/roadmap.md:96` </location>
<code_context>
--   [ ] Implement a hybrid interactive mode (`--interactive`) that, in case of a "Double-Lock" verification failure, presents the proposed diff and the resulting errors to a human user for manual review, approval, or rejection.
+- [ ] Implement the `onboard-project` command based on the "Meta-RAG" design,
+    orchestrating other Weaver components to generate the `PROJECT.dna` summary
+    file.

--   [ ] Begin research and development for the Dynamic Analysis Ingestion provider for `weaver-graph`, allowing it to consume and merge profiling data from tools like `gprof` and `callgrind`.
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns for improved readability.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

### Comment 15
<location> `docs/roadmap.md:103` </location>
<code_context>
+    resulting errors to a human user for manual review, approval, or rejection.

+- [ ] Begin research and development for the Dynamic Analysis Ingestion
+    provider for `weaver-graph`, allowing it to consume and merge profiling
+    data from tools like `gprof` and `callgrind`.
</code_context>

<issue_to_address>
**issue (review_instructions):** This bullet point line exceeds the 80 column wrapping limit for paragraphs and bullets.

Please wrap this line to 80 columns as per the formatting guidelines.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `**/*.md`

**Instructions:**
Paragraphs and bullets must be wrapped to 80 columns

</details>
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bee57da and d09327d.

📒 Files selected for processing (1)

• docs/roadmap.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.md

⚙️ CodeRabbit configuration file

**/*.md: * Avoid 2nd person or 1st person pronouns ("I", "you", "we")

• Use en-GB-oxendict (-ize / -yse / -our) spelling and grammar
• Headings must not be wrapped.
• Documents must start with a level 1 heading
• Headings must correctly increase or decrease by no more than one level at a time
• Use GitHub-flavoured Markdown style for footnotes and endnotes.
• Numbered footnotes must be numbered by order of appearance in the document.

Files:

• docs/roadmap.md

🔍 Remote MCP Ref

Additional Relevant Context for PR Review

1. Roadmap Document Location
   The file docs/roadmap.md is the source of the PR changes and lives at the repository root under docs/roadmap.md.
   Citation:

2. Ortho-config Usage
   A key new sub-task in Phase 1 mentions “Define shared configuration schema for weaver-cli/weaverd using ortho-config.”

   • Grepping the codebase shows no occurrences of “ortho-config” in any .py, .md, or config files.
   • Therefore, the repository does not currently integrate or reference ortho-config anywhere.
     Citation: search over Deepwiki and repo contents via Deepwiki_ask_question (no hits).

3. Markdownlint Failures
   The PR description notes make fmt errors due to existing markdownlint violations in docs/weaver-design.md. These pre-existing lint issues are unrelated to the PR changes in docs/roadmap.md.
   Citation: PR testing notes.

4. No Functional Impact
   All changes are documentation only; no code, schema, or CLI/daemon logic is affected, so no additional testing beyond markdown validation is required.
   Citation: AI summary of PR ([ai_summary]).

⏰ Context from checks skipped due to timeout of 120000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Sourcery review