Run one dependency-free source file against the accepted and candidate Unity revisions. It writes bounded `pib-repository-snapshot-v0.1` JSON locally, so path/meta, GUID, package, and changed-path Git LFS evidence can reach the existing browser evaluator without uploading a repository.
The kit exposes the minimum structural evidence needed for a real comparison. It is deliberately narrower than the private-pilot extractor and makes its sensitive fields explicit.
The tarball has no dependencies or lifecycle scripts. Extract it, inspect the CLI source, then generate the accepted and candidate snapshots under the same declared contract.
Verify the SHA-256, list the archive, and read `bin/pib-snapshot.mjs`. No package installation is required.
Run baseline mode in the clean accepted checkout with the real serialization and path-case labels.
Run candidate mode in the clean candidate checkout and name the accepted base ref used for changed paths.
Inspect both JSON files, paste them into the browser evaluator, and keep bounded coverage visible.
The comparison ID and every repository-contract label must match. Only the revision label and revision-owned evidence should move.
--modeChanges per checkoutbaseline or candidate; candidate requires one accepted base ref--comparison-idMust matchA short, non-secret pull-request or comparison label--revision-labelChanges per checkoutThe accepted or candidate revision label shown in the result--serialization-modeMust matchForceText, Mixed, or ForceBinary as verified in Unity--path-case-modeMust matchcase-sensitive or case-insensitive for the checkout filesystem--base-refCandidate onlyThe accepted comparison point used only to enumerate changed paths--outputLocal destinationA JSON path outside Assets, Packages, and ProjectSettings--expected-changeOptional / repeatableA stable finding ID that should remain visible as expected--project-rootOptionalThe clean Unity Git checkout; defaults to the current repository--overwriteOptional / explicitAllow replacement of the exact requested output filenode package/bin/pib-snapshot.mjs \ --mode baseline \ --comparison-id "pr-931" \ --revision-label "main@accepted" \ --serialization-mode "ForceText" \ --path-case-mode "case-sensitive" \ --output "../reference.json"
node package/bin/pib-snapshot.mjs \ --mode candidate \ --base-ref "origin/main" \ --comparison-id "pr-931" \ --revision-label "pr-931" \ --serialization-mode "ForceText" \ --path-case-mode "case-sensitive" \ --output "../candidate.json"
The generator writes nothing when the checkout is dirty or sparse, a required project file is missing, a relevant path is a symbolic link, metadata or package state is malformed, an inventory exceeds its ceiling, or the output location is unsafe.
It reads `.meta`, project-version, package JSON, Git path/attribute metadata, and at most 1 KiB of a current changed Git object when pointer-form detection requires it. File bodies, URLs, object IDs, absolute paths, and the project root are not serialized.
Compare two reviewed snapshots →