Skip to content

fix(cli): published readableArtifacts links point to deleted staging paths #397

Description

@Fancy0uth

Reproduction

Current main 63b6463, locally compiled native 0.7.2-beta.6 on Windows x64. Run code-intel <committed-temp-repo> --mode lite --json successfully. JSON reports outcome completed and publication.path, plus readableArtifacts.agentCodeSliceRanking pointing inside the run at evidence.native-code/code-evidence/merged/agent/ranking.json. That path does not exist. The publication contains content-addressed objects; the reported path is a staging artifact path incorrectly joined to the committed publication root.

Bounded repair

Resolve the existing primary-result readableArtifacts fields against committed content-addressed references, preserving field names and schema. Prove reported files exist, parse as the expected artifacts, and match committed refs; cover completed and non-clean runs without suggesting a failed run is clean. Do not create parallel report copies or change artifact authority.

Evidence

C:/Users/asus/AppData/Local/Temp/code-intel-ux-source-python-s9gi2cho/evidence.json (successful run); code-intel-ux-source-56gz2ug6/evidence.json (domain-failed run); pi-unified-exec-25-c7ab398a.log (each advertised path existence=False). Local source binary SHA256 5e9cf13045cc391ef6de2831fd6b307e24041870ab3d604d740285e6c1e306ed. Native pre-edit gate passed without rebaseline. No overlap with PR #392.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions