docs: prepare release notes for v3.9.4

[carlos-alm]

Summary

• Add CHANGELOG entry for v3.9.4 (all commits since v3.9.3)
• Update ROADMAP: bump current version, note v3.9.4 progress on Phase 8.3 (callback resolution heuristic)
• Update BACKLOG last-updated date

Bump rationale: patch, not minor. Both feat: commits since v3.9.3 are internal improvements with no new CLI surface — feat(js-extractor) improves resolver accuracy (classified as Bug Fix, following the v3.9.1 precedent for similar consumption-tracking fixes), feat(native) ports structure computation to Rust (classified as Performance).

After merging: create a GitHub Release with tag `v3.9.4` to trigger the publish workflow, which handles version bumping, native binary builds, and npm publishing.

Test plan

• CHANGELOG renders correctly on GitHub
• ROADMAP checklist items match actual codebase state

[claude]

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

---

Reviewing PR: docs: prepare release notes for v3.9.4

Todo List:

• Read changed files to understand documentation updates
• Analyze changelog accuracy against actual commits since v3.9.3
• Review roadmap and backlog changes
• Assess version bump rationale (patch vs minor)
• Apply 5-phase review framework
• Provide final rating and recommendation

---

Root Cause Analysis

Problem Being Solved: Preparing comprehensive release documentation for v3.9.4, updating version references across documentation files, and providing clear rationale for the patch-level version bump.

Why This Approach: Pure documentation changes with no code impact - appropriate for a release preparation PR. The changes update version references and document completed work.

Risk Assessment: Minimal risk - documentation-only changes with no functional impact.

Backlog Compliance

• Zero-dep: ✅ - No runtime dependencies added (documentation only)
• Foundation-aligned: ✅ - No violation of core principles (pure documentation)
• Problem-fit: N/A - Documentation maintenance, not feature development
• Breaking: No - Purely additive documentation changes
• Tier: N/A - Documentation maintenance outside tier system

Critical Review Findings

✅ Changelog Accuracy

The v3.9.4 changelog entry accurately reflects all commits since v3.9.3:

• All 9 major commits properly categorized (Bug Fixes, Performance, Chores)
• PR references correctly linked (feat(js-extractor): resolve named function references passed as arguments #947, fix(ci): add resilience to Claude Code workflow for fork branch races #949, fix: include imports-type in fast-path fan_in/fan_out queries #948, fix(rust): fix test compilation errors and add verification rule #950, chore: disable adaptive thinking via env var #943, fix(structure): reconcile import_count semantics between fast path and full path #942, perf(native): defer NativeDatabase.openReadWrite until after change detection #939, fix(wasm): resolve incremental edge loss, unnecessary reparses, and V8 crash #938, feat(native): port full-build structure computation to Rust #937)
• Summary correctly emphasizes resolution accuracy and incremental build improvements

✅ Version Bump Rationale

The patch classification is justified:

• feat(js-extractor) (feat(js-extractor): resolve named function references passed as arguments #947): Internal resolver accuracy improvement, no new CLI surface
• feat(native) (feat(native): port full-build structure computation to Rust #937): Internal performance optimization, no new user-facing features
• Following established precedent from v3.9.1 for similar internal improvements

✅ Roadmap Updates

• Current version correctly updated: 3.9.3 → 3.9.4
• Phase 8.3 progress accurately marked: callback resolution heuristic now ✅ complete
• References the actual implemented feature from feat(js-extractor): resolve named function references passed as arguments #947

✅ Documentation Consistency

• BACKLOG.md last-updated date properly maintained (2026-04-17)
• All version references consistently updated
• No contradictory information across files

⚠️ Minor Observation

The changelog's performance section could more clearly distinguish between the feat(native) port (#937) and the pure performance optimizations (#939, #940) since feat: commits typically indicate new functionality, but this is classification preference rather than error.

Final Recommendation

• Rating: ⭐⭐⭐⭐☆ (4/5)
• Action: APPROVE
• Reasoning: Well-structured release documentation with accurate changelog, justified version bump rationale, and consistent version references. Minor stylistic preference noted but doesn't affect approval. Ready for merge to proceed with GitHub Release creation.

---

[greptile-apps]

Greptile Summary

Documentation-only release prep for v3.9.4: adds a CHANGELOG entry covering seven bug fixes, three performance improvements, and one chore; bumps the ROADMAP's current version and date; and adds Phase 8.3 progress notes reflecting the callback-resolution heuristic shipped in #947. No code changes are included.

Confidence Score: 5/5

Safe to merge — documentation-only, no code changes.

All three files are documentation (CHANGELOG, ROADMAP, BACKLOG). Content is internally consistent, PR-linked entries are plausible, dates match, and the patch-level rationale for the two feat: commits is explicitly documented. No P0/P1 findings.

No files require special attention.

Important Files Changed

Filename	Overview
CHANGELOG.md	New v3.9.4 entry added with accurate PR-linked bug fix, performance, and chore entries matching the described commits
docs/roadmap/ROADMAP.md	Current version bumped to 3.9.4, date updated, and Phase 8.3 progress block added with accurate scope notes
docs/roadmap/BACKLOG.md	Last-updated date bumped to 2026-04-17; no other changes

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Merge PR #952] --> B[Create GitHub Release\ntag v3.9.4]
    B --> C[publish.yml triggered]
    C --> D[commit-and-tag-version\nbumps package.json]
    D --> E[Native binary builds\nper platform and arch]
    E --> F[npm publish\n@optave/codegraph@3.9.4]
    F --> G[Optional packages published\nper platform and arch]

Loading

_{Reviews (1): Last reviewed commit: "docs: prepare release notes for v3.9.4" | Re-trigger Greptile}