Repository navigation
lance-graph-r2il joins the workspace; OGAR by git main (D-FOLD-CORE-a) - #1534
Conversation
R2IL is the procedure executor NAL lowers through; it was excluded only because it path-depped the OGAR sibling. It now takes ogar-loco/ogar-r2il by git main, the coordinate lance-graph-ogar already uses, so: - the workspace holds one ogar-loco and one ogar-r2il (path and git copies were about to coexist once r2il joined); - a repo that pulls lance-graph by git can resolve it (a ../../../OGAR path escapes the fetched repository, the medcare-rs #565 failure). lance-graph-nal and r2il-mask-abi-probe follow, so each of their own workspaces still sees one ogar-loco. The root patches the contract's git URL to the member, since the OGAR crates take the contract from git main. Verified: cargo metadata shows one lance-graph-contract, one ogar-loco, one ogar-r2il; tests r2il 19/19 (member), nal 8/8, probe 40/40; clippy -D warnings and fmt clean for lance-graph-r2il. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011BMJnDBAfzcuQh5HeT39Rh
|
Warning Review limit reachedYour organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Next included review available in 57 minutes. View limit details
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
board: #1534 entries (D-FOLD-CORE-a shipped)
2 participants
First step of D-FOLD-CORE, which makes the fold path a core capability: R2IL becomes a workspace member.
Changes
lance-graph-r2ilmoves fromexcludetomembers, and its own[workspace]and[patch]sections are removed.ogar-locoandogar-r2ilby gitmaininstead of../../../OGARpaths. That is the coordinatelance-graph-ogaralready uses. There are two reasons:ogar-loco, one from the path and one from git vialance-graph-ogar.lance-graphby git cannot follow a path that leaves the fetched repository. That is what broke medcare-rs feat: kanban×Rubicon SoA tenant + per-tenant counters + capstone plan + golden-image wiring #565.lance-graph-nalandr2il-mask-abi-probe(both excluded, each with its own workspace) take the same git coordinate, so each of them still sees oneogar-loco.[patch."https://github.com/AdaWorldAPI/lance-graph"] lance-graph-contract = { path = "crates/lance-graph-contract" }. The OGAR crates take the contract by gitmain, and this keeps one contract in the graph.Verified here
cargo metadata: exactly onelance-graph-contract(the member), oneogar-locoand oneogar-r2il.lance-graph-r2il19/19 as a member,lance-graph-nal8/8,r2il-mask-abi-probe40/40.cargo clippy -p lance-graph-r2il --all-targets -D warningsandcargo fmt --checkare clean.Note: this replaces an earlier plan to make OGAR a required sibling checkout. With git dependencies, no sibling is needed.
🤖 Generated with Claude Code
https://claude.ai/code/session_011BMJnDBAfzcuQh5HeT39Rh
Generated by Claude Code