feat(git): expose commit path provenance - #1624
Draft
ohdearquant wants to merge 1 commit into
Draft
Conversation
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
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.
Summary
git.digest(snapshot revision, source path)match so repository or revision collisions fail closedBehavior
Commit provenance notes now carry sorted, deduplicated
changed_pathsderived from Git's rawNUL-delimited output. The parser accepts both observed one- and two-NUL commit boundaries, preserves
delimiter-bearing and non-UTF-8 pathnames through deterministic lossy normalization, represents
empty commits, and uses first-parent diffs for merges. Credential-shaped path fragments are masked
before persistence.
When code-ingest data is present, module annotations are resolved against the source snapshot's
exact HEAD revision and source path. A unique match produces the commit-to-module link; duplicate,
cross-repository, or otherwise ambiguous candidates are skipped instead of fabricating provenance.
These facts make churn and co-change analysis derivable from the stored graph.
This is a stacked draft on #1619 because its exact snapshot-revision binding consumes the code-ingest
provenance contract introduced there. Issues #1600, #1603, and #1605 remain scoped exclusively to
the parent draft.
Validation
khive-pack-gitunit, acceptance, and documentation testscargo test --manifest-path crates/Cargo.toml --workspacecargo check --manifest-path crates/Cargo.toml --workspacecargo clippy --manifest-path crates/Cargo.toml --workspace --all-targets -- -D warningscargo fmt --manifest-path crates/Cargo.toml --all -- --checkRUSTDOCFLAGS=-Dwarnings cargo doc --manifest-path crates/Cargo.toml --workspace --no-depsCloses #1604