chore: remove ~118MB build artifacts from git

[carlos-alm]

Summary

• Remove artifacts/ and pkg/ directories from git tracking (~118MB of native .node binaries)
• Add both to .gitignore

These directories are created by the publish workflow during CI (download-artifact → pkg assembly → npm publish). They were accidentally committed to the repo.

[claude]

Claude finished @carlos-alm's task —— View job

---

PR Review Complete

Root Cause Analysis

Problem Being Solved: The publish CI workflow (publish.yml:178-181, publish.yml:218-219) downloads build artifacts to artifacts/ and assembles platform packages in pkg/, but these ~118MB directories containing native .node binaries were accidentally committed to git instead of being treated as temporary CI artifacts.

Why This Approach: The solution is correct and minimal — removing the committed artifacts and gitignoring both directories prevents future accidental commits. The workflow will recreate these directories during each publish run, so no functionality is lost.

Risk Assessment: LOW RISK — This is purely a repository hygiene fix with no impact on functionality, build process, or user experience.

Critical Concerns

None. This is a straightforward cleanup with proper prevention measures.

Detailed Review

✅ Changes Analysis

1. .gitignore:7-8: Added artifacts/ and pkg/ directories — perfectly aligned with their usage in publish.yml:178-181 (download artifacts) and publish.yml:218-219 (create platform packages)
2. File deletions: All 12 deleted files are legitimate CI artifacts that should never have been committed:
   • 8 native .node binaries (~15MB each)
   • 4 temporary package.json files for platform packages

✅ Process Validation

• Workflow recreates both directories on every publish run (lines 178-181, 218-236 in publish.yml)
• No build scripts or runtime code references these directories
• Platform packages are published from temporary pkg/ structure, not persistent files

✅ Configuration Safety

• No risky configuration changes — only .gitignore additions
• No disabled linting rules, relaxed timeouts, or weakened tests
• No module resolution or build configuration changes

✅ Repository Impact

• Immediate: 118MB reduction in repo size
• Future: Prevents accidental re-commit of CI artifacts
• Zero functional impact: Native binaries are distributed via npm platform packages (@optave/codegraph-{platform}-{arch} in package.json:64-67)

Final Recommendation

• Rating: ⭐⭐⭐⭐☆ (4/5)
• Action: APPROVE
• Reasoning: Clean, targeted fix that addresses the exact problem with appropriate prevention. Well-documented commit message explains the context. No functional or security risks. Only minor deduction for the original accident requiring this cleanup.

This PR exemplifies good repository hygiene — it fixes an accident, prevents recurrence, and makes no unnecessary changes.

[greptile-apps]

Greptile Summary

Removed ~118MB of build artifacts (artifacts/ and pkg/ directories containing native .node binaries) from git tracking and added both directories to .gitignore. These directories are dynamically generated during the CI publish workflow (lines 178-246 in publish.yml) and should never have been committed to the repository.

Confidence Score: 5/5

• Safe to merge — removes accidentally committed build artifacts and prevents future commits
• This is a straightforward cleanup that removes CI-generated build artifacts (~118MB of native binaries) that were accidentally committed. The .gitignore additions ensure these won't be committed again. The workflow at .github/workflows/publish.yml lines 178-246 shows these directories are created fresh during each publish run, so removing them from git has no negative impact.
• No files require special attention

Important Files Changed

Filename	Overview
.gitignore	Added artifacts/ and pkg/ to gitignore to prevent build artifacts from being tracked

_{Last reviewed commit: db17f98}

[greptile-apps]

_{13 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[claude]

Claude finished @carlos-alm's task —— View job

---

PR Review Complete

Todo List

• Phase 1: Root Cause Analysis
• Phase 2: Configuration Change Detection
• Phase 3: Test Integrity Check
• Phase 4: Code Quality Assessment
• Final Assessment and Rating

---

Phase 1: Root Cause Analysis ✅

Problem Being Solved: The publish CI workflow was downloading build artifacts to artifacts/ (line 181) and creating platform packages in pkg/ (line 213), but these ~118MB directories containing native .node binaries were accidentally committed to git instead of being treated as temporary CI artifacts.

Root Cause: The workflow originally downloaded artifacts to the repository root (artifacts/) and built packages in pkg/. These directories should have been in .gitignore from the start, but weren't. The fix properly moves them to ${{ runner.temp }}/ to prevent future accidents.

Why This Approach: The solution is correct and comprehensive:

• Removes the accidentally committed artifacts (~118MB cleanup)
• Updates workflow to use temp directories (${{ runner.temp }}/artifacts/ and ${{ runner.temp }}/pkg/)
• Adds .gitignore entries as defense-in-depth

Risk Assessment: VERY LOW RISK — This is purely repository hygiene with no functional impact.

Phase 2: Configuration Change Detection ✅

NO RISKY CONFIGURATION CHANGES DETECTED:

• Linting rules: biome.json:12-15 unchanged — still uses "recommended": true
• Test configuration: vitest.config.js:6 unchanged — timeout remains 30s, no coverage thresholds
• Build configuration: No module resolution or TypeScript config changes
• Workflow improvement: Publish workflow correctly moves artifacts to temp directories

Phase 3: Test Integrity Check ✅

NO TEST INTEGRITY CONCERNS:

• No test files modified — only .gitignore and publish workflow changed
• No test expectations lowered — no changes to assertions or validation logic
• No disabled rules — no eslint-disable or workaround comments
• Clean scope: Only 2 modified files, 12 deleted artifact files

Commit History Context: Recent commits show legitimate fixes (fix(ci), fix/call-resolution-accuracy) with no pattern of configuration shortcuts.

Phase 4: Code Quality Assessment ✅

WORKFLOW CHANGES ANALYSIS:

• Lines 181, 213: Correctly moves artifact handling from repo root to ${{ runner.temp }}/
• Lines 212-213: Introduces proper variable scoping (ARTIFACTS, PKG_DIR)
• Lines 222-223, 239: Updates all file paths to use temp directories consistently
• Security: No command injection risks — proper variable quoting maintained
• Idempotency: Preserves existing version check logic (lines 242-245)

GITIGNORE VALIDATION:

• Lines 7-8: Added artifacts/ and pkg/ — correctly prevents future accidents
• Alignment: Matches exact directory names used in workflow

VERIFICATION:

• ✅ Both artifacts/ and pkg/ directories properly removed from filesystem
• ✅ ~118MB of native binaries successfully cleaned from git history
• ✅ Platform packages will be recreated in temp dirs during next CI run

Critical Concerns

NONE. This is exemplary repository hygiene — fixes an accident, prevents recurrence, makes no unnecessary changes.

Final Recommendation

• Rating: ⭐⭐⭐⭐☆ (4/5)
• Action: APPROVE
• Reasoning: Clean, targeted fix with proper prevention measures. Well-structured 2-commit approach (remove artifacts → fix workflow). Zero functional or security risks. Only minor deduction for the original oversight requiring cleanup.

This PR demonstrates excellent engineering discipline — it addresses the exact problem, implements appropriate safeguards, and maintains full CI functionality.