docs: point bridge references at lance-graph-ogar after #585 OGIT/OGAR split#92
Merged
Merged
Conversation
…R split
lance-graph #585 moved the OGAR-driven port bridges (UnifiedBridge<P: PortSpec>
harness + OpenProject/Redmine/Medcare bridges) from lance-graph-ontology (OGIT)
to lance-graph-ogar (OGAR). Two OGAR-side docs still pointed at the old home:
1. ogar-vocab::ports rustdoc (live docs.rs surface) — 4 references to
`lance_graph_ontology::{UnifiedBridge, bridges::OPENPROJECT_CODEBOOK}` and
`lance_graph_ontology`'s `MedcareBridge` repointed to `lance_graph_ogar`.
(Also dropped one square-bracket intra-doc link to a lance-graph path that
ogar-vocab can't resolve — now a plain code span.)
2. CLASSVIEW-MATERIALIZATION-PLAN.md — §0 dataflow picture pointed the
bridge box at [lance-graph-ontology]; §3 C4/C5 rows listed the bridges
landing in openproject-nexgen-rs / redmine-rs 'sibling of MedcareBridge'.
Added a 'how C4+C5 actually landed' note recording the real path: planned
in the port repos -> converged on UnifiedBridge<P: PortSpec> type aliases
(ports in ogar-vocab::ports, lance-graph #570) -> first in
lance-graph-ontology (#558/#559) -> moved to lance-graph-ogar (#585) to
keep OGIT free of ogar-vocab.
Docs-only. `cargo check -p ogar-vocab` clean.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc drift from lance-graph #585
lance-graph #585 ("move OGAR port bridges to lance-graph-ogar — restore OGIT/OGAR SoC") relocated the
UnifiedBridge<P: PortSpec>harness and the OpenProject/Redmine/Medcare bridges out oflance-graph-ontology. Two OGAR-side docs still described the old location.1.
ogar-vocab::portsrustdoc (live docs.rs surface)Four references repointed
lance_graph_ontology→lance_graph_ogar:UnifiedBridgeconsumerPortSpecdoc: the generic harness pathOPENPROJECT_ALIASESdoc: theOPENPROJECT_CODEBOOKre-exportHealthcarePortdoc:MedcareBridgecollapse note(One square-bracket intra-doc link pointing at a lance-graph path — never resolvable from
ogar-vocab, which doesn't depend on lance-graph — demoted to a plain code span.)2.
CLASSVIEW-MATERIALIZATION-PLAN.md§0 dataflow picture: the bridge box
[lance-graph-ontology]→[lance-graph-ogar], andNamespaceBridge<OpenProject>→UnifiedBridge<OpenProjectPort>(the shape it actually landed as).§3 C4/C5 table:
Repocolumnopenproject-nexgen-rs/redmine-rs→lance-graph-ogar, plus a "how C4+C5 actually landed" note tracing the real path:Companion
lance-graph #586 fixes the one code consumer #585 missed (
lance-graph-consumer-conformance). This PR is the docs half.Docs-only;
cargo check -p ogar-vocabclean.🤖 Generated with Claude Code