[Upstream-Sync] [FEATURE] Add Ladybug target (Kuzu successor) — upstream PR #1487

[bashandbone]

Summary

Adapt the upstream new target from cocoindex-io/cocoindex#1487: add Ladybug as a new target-ladybug feature-gated graph database target in Recoco, replacing the archived Kuzu project.

Background

• Kuzu (MIT-licensed property graph DB) was archived in October 2025.
• Ladybug is its actively maintained fork with an identical Cypher API server interface.
• Upstream PR #1487 adds Ladybug as a first-class target, with a note to eventually retire the Kuzu target.
• Recoco already has a full target-kuzu implementation in crates/recoco-core/src/ops/targets/kuzu.rs using the same API server-based thin-client approach.

What changes upstream?

• New file: rust/cocoindex/src/ops/targets/ladybug.rs — a near-identical copy of kuzu.rs with all Kuzu* symbols renamed to Ladybug*
• rust/cocoindex/src/ops/targets/mod.rs — adds pub mod ladybug
• rust/cocoindex/src/ops/registration.rs — registers the Ladybug factory, cloning the reqwest_client

Action for Recoco

1. Create crates/recoco-core/src/ops/targets/ladybug.rs by adapting the upstream file. This is largely a mechanical rename of kuzu → ladybug, with one API callsite to verify (see note below).
2. Update crates/recoco-core/src/ops/targets/mod.rs to add:

   #[cfg(feature = "target-ladybug")]
   pub mod ladybug;

   Also update the #[cfg(any(...))] guard on pub mod shared to include target-ladybug.
3. Update crates/recoco-core/Cargo.toml:
   • Add target-ladybug feature: target-ladybug = ["dep:reqwest", "recoco-utils/reqwest", "target-neo4j"] (same deps as target-kuzu)
   • Add target-ladybug to the all-targets and full bundles
4. Register the Ladybug factory in registration (wherever kuzu::register is called).
5. Decide on a deprecation or migration path for target-kuzu — upstream recommends retiring Kuzu in favour of Ladybug.

⚠️ API compatibility note

Recoco's kuzu.rs calls http::request(|| ...) (zero-arg closure), while the upstream ladybug.rs calls http::request(&self.reqwest_client, |client| ...) (two-arg form). Verify which signature recoco-utils/http currently exposes before copying the upstream code verbatim.

Recoco mapping

Upstream	Recoco
rust/cocoindex/src/ops/targets/ladybug.rs	crates/recoco-core/src/ops/targets/ladybug.rs
rust/cocoindex/src/ops/targets/mod.rs	crates/recoco-core/src/ops/targets/mod.rs
rust/cocoindex/src/ops/registration.rs	Registration module in recoco-core
Feature target-kuzu (upstream, to be deprecated)	target-kuzu in Recoco (consider deprecation path)

References

• Upstream PR: cocoindex-io/cocoindex#1487
• Upstream ladybug.rs at merge commit: https://github.com/cocoindex-io/cocoindex/blob/1c5cf67587e7fe769f129b78f603956c9824061a/rust/cocoindex/src/ops/targets/ladybug.rs
• Bootstrap tracking issue: #27

[github-actions]

🤖 Hi @bashandbone, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[github-actions]

Claude finished @bashandbone's task —— View job • claude/issue-52-20260310-2134 • Create PR ➔

---

Task Complete ✅

I've successfully added the Ladybug target to Recoco as a new target-ladybug feature-gated graph database target.

Summary of Changes

Files Modified:

1. crates/recoco-core/src/ops/targets/ladybug.rs (new) - Complete Ladybug target implementation

   • Mechanical rename of all Kuzu* symbols to Ladybug*
   • Updated API documentation to reference Ladybug's Cypher-compatible API
   • Uses the same HTTP thin-client approach with http::request (zero-arg closure form)

2. crates/recoco-core/src/ops/targets/mod.rs - Added Ladybug module

   • Added #[cfg(feature = "target-ladybug")] for the ladybug module
   • Updated shared module guard to include target-ladybug

3. crates/recoco-core/Cargo.toml - Added feature configuration

   • Added target-ladybug = ["dep:reqwest", "recoco-utils/reqwest", "target-neo4j"]
   • Included target-ladybug in both all-targets and full feature bundles

4. crates/recoco-core/src/ops/registration.rs - Registered Ladybug factory

   • Updated feature guards to include target-ladybug
   • Registered targets::ladybug::register() with shared reqwest_client

Verification

✅ Code successfully compiles with cargo check -p recoco-core --features target-ladybug
✅ Follows the same pattern as existing target-kuzu implementation
✅ All feature gates properly configured

Notes on Implementation

• The Ladybug implementation is API-compatible with Kuzu (identical Cypher interface)
• Used the same dependencies as target-kuzu since Ladybug is a direct fork
• The http::request signature in recoco-utils/http.rs matches the zero-arg closure form used in the implementation
• No deprecation of target-kuzu was implemented (per issue note suggesting this should be decided separately)

---

Branch: claude/issue-52-20260310-2134