Struct DanglingLink 

pub struct DanglingLink {
    pub kind: DanglingLinkKind,
    pub from: EntityId,
    pub target_id: EntityId,
    pub target_path: String,
    pub section: Option<String>,
}

One dangling-reference finding surfaced by memstead_health include=["dangling_links"] and projected onto the consistency axis by include=["integrity"].

Three conditions reach this type, and kind says which: a body wiki-link whose target has no markdown file (the post-delete / renamed-without-rewrite / typo signal), a body wiki-link to a fully written entity that the referrer does not relate to, and a relationships row naming an entity absent from the store. Their repairs differ, so the codes differ; see DanglingLinkKind.

The prose this replaces described only the first condition, which is how the fusion survived: the type read as if it had one subject while producing three (04/06, criterion 6).

Fields

kind: DanglingLinkKind

Which of the three conditions this is, and therefore which repair applies. Carried from the one producer, never re-derived: the split happens where the conditions are distinguished (04/06).

from: EntityId

target_id: EntityId

Canonical ID the wiki-link resolves to.

NOT necessarily a stub: it is a stub or absent for DanglingLinkKind::LinkTargetMissing and DanglingLinkKind::RelationTargetMissing, and a real, non-stub entity for DanglingLinkKind::LinkNotRelated, where the entity is fine and the relationship row is what is missing. The old wording said “stub-typed in the store”, which was true of one of the three conditions this type carried.

target_path: String

Resolved mem-relative path segment of the target ID (e.g. gone for specs--gone). This is the normalised form the engine records — not the literal [[…]] characters as authored. Widening WikiLink to preserve the authored form is a future-work item if agents need grep-to-source precision.

section: Option<String>

Section key the body wiki-link appears in (e.g. "purpose").

None for DanglingLinkKind::RelationTargetMissing, whose source is the auto-managed relationships block rather than a body section. That absence used to be the ONLY way to tell that condition apart, which is why kind exists: a reader should not have to inspect a payload for nulls to learn which repair applies (04/06, criterion 4).

Trait Implementations

impl Clone for DanglingLink

fn clone(&self) -> DanglingLink

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for DanglingLink

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Serialize for DanglingLink

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.