Repository navigation
StaticRepoImporter: incremental skip fires on an EMPTY partition (phantom manifest checkpoint) #640
Description
A failed/ghost-era import left a checkpoint that made subsequent real imports report 'Imported Skipped (0 node(s))' against a partition with no content. Skip must verify the partition actually holds the manifest's content (verify-before-skip).
From the 2026-07-24 plugin-install retrospective.
🤖 Generated with Claude Code
Activity
rbuergi commentedon Aug 8, 2026
Fixed on main by the content-sentinel verify-before-skip that landed with #708 (StaticRepoImporter.cs — "SELF-HEAL CONTENT, not just governance"): before honoring a Succeeded fingerprint marker, the importer now queries a content sentinel node from the manifest; if it is missing (the empty-partition / phantom-checkpoint case this issue describes), it falls through to a full idempotent re-import instead of reporting 'Skipped (0 nodes)'. A forced import additionally always re-runs regardless of fingerprint.
Pinned by
StaticRepoImporterTests.Reimport_SameFingerprint_ButContentDeleted_SelfHeals(test/MeshWeaver.Hosting.PostgreSql.Test): Succeeded marker + deleted content → re-import restores the partition; the old behavior skipped forever.