chore: release v3.4.1

[carlos-alm]

Summary

• Bump version to 3.4.1 (patch — no user-facing features)
• Add CHANGELOG entry for all commits since v3.4.0
• Update ROADMAP progress

Replaces #639 — corrected from v3.5.0 to v3.4.1. The feat(titan) commit is internal developer tooling, not a user-facing feature, so it does not trigger a minor bump.

Test plan

• npm install succeeds with updated lock file
• CHANGELOG renders correctly on GitHub
• ROADMAP checklist items match actual codebase state

[claude]

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

---

Code Review Complete ✅

Todo List:

• Phase 1: Root cause analysis - understand the release justification
• Phase 2: Configuration change detection - check for rule relaxations
• Phase 3: Test integrity - look for test weakening
• Phase 4: Code quality review
• Phase 5: Backlog compliance grading
• Final Assessment: Provide rating and recommendation

Phase 1: Root Cause Analysis ✅

Problem Being Solved: This is a legitimate patch release (v3.4.1) correcting the content of changelog entries and doing post-migration stabilization. The PR corrects a previous mistaken attempt at v3.5.0 by recognizing that the feat(titan) commit is internal tooling, not user-facing functionality.

Why This Approach: Standard release process using commit-and-tag-version. The titan commit is indeed internal tooling (line 36 in CHANGELOG.md shows it as a "chore" entry: "titan: first full Titan Paradigm pipeline run — audit report generation and skill improvements"). This correctly should not trigger a minor version bump.

Risk Assessment: Low risk - this is purely versioning/documentation updates with no code changes.

Phase 2: Configuration Change Detection ✅

No concerning configuration changes detected. The only configuration-adjacent changes are:

• Version bumps in package.json and Cargo.toml (standard)
• package-lock.json version updates (automatic from version script)
• No biome rule changes, no test timeout modifications, no linting rule relaxations

Phase 3: Test Integrity ✅

No test integrity issues. No test files were modified in this release PR. Existing skip patterns in the codebase are legitimate:

• describe.skipIf(!hasNative) - standard pattern for skipping native-engine tests when native engine unavailable
• it.skip() calls are all for incomplete/WIP features, not weakening existing tests

Phase 4: Code Quality ✅

Clean release with no code changes. Only documentation and version metadata updated:

• CHANGELOG.md: Proper v3.4.1 entry with comprehensive release notes
• Version files: Standard version sync across package.json and Cargo.toml
• ROADMAP.md: Progress updates reflecting completed work (roles optimization, DB indexes)
• BACKLOG.md: Date stamp update only

The libc fields mentioned in PR description are indeed present in package-lock.json for Linux entries - this appears to be standard npm behavior for platform-specific packages.

Phase 5: Backlog Compliance ✅

Zero-dep: ✓ — No new dependencies added
Foundation-aligned: ✓ — Release process preserves all core principles
Problem-fit: N/A — This is a release process, not a feature
Breaking: No — Purely additive version/documentation changes
Tier: N/A — Release maintenance

Root Cause Analysis

Problem Being Solved: Correct a mistaken version bump from v3.5.0 to v3.4.1, recognizing that feat(titan) commit is internal developer tooling, not user-facing functionality.
Why This Approach: Standard semantic versioning correction using commit-and-tag-version. The titan feature is correctly categorized as "chore" in the changelog.
Risk Assessment: Minimal - documentation and version metadata only, no code changes.

Backlog Compliance

• Zero-dep: ✓ — no new runtime dependencies
• Foundation-aligned: ✓ — pure release process, no principle violations
• Problem-fit: N/A — release maintenance
• Breaking: No — version and docs only
• Tier: N/A

Critical Concerns

None. This is a clean, standard release PR.

Final Recommendation

• Rating: ⭐⭐⭐⭐☆ (4/5)
• Action: APPROVE
• Reasoning: This is a well-executed patch release correction. The reasoning for treating feat(titan) as internal tooling is sound based on the changelog content. All version files are properly synchronized, changelog is comprehensive, and no risky configuration changes are present. The only reason this isn't 5 stars is that it's routine release maintenance rather than exceptional work.

The PR correctly applies semantic versioning - internal tooling improvements should not trigger minor version bumps, making v3.4.1 the appropriate choice.

---

[greptile-apps]

Greptile Summary

This is a clean patch release PR bumping @optave/codegraph from v3.4.0 to v3.4.1. It synchronizes the version across all four version-bearing files (package.json, package-lock.json, crates/codegraph-core/Cargo.toml, docs/roadmap/ROADMAP.md), adds a comprehensive CHANGELOG entry for the 13 PRs merged since v3.4.0, and updates the ROADMAP to reflect the compound-index work from PR #632.

• Version consistency: All four version fields are updated in lockstep to 3.4.1 — no drift between JS and Rust manifests.
• CHANGELOG accuracy: All merged PRs since v3.4.0 are accounted for under the correct sections (Bug Fixes, Performance, Refactors, Chores); the feat(titan) commit (PR feat(titan): first full pipeline run — audit report + skill improvements #623) is deliberately placed under "Chores" rather than "Features" and treated as a patch bump, which is explicitly justified in the PR description as internal developer tooling.
• ROADMAP update: Section 6.8 correctly adds PR perf(db): add compound indexes to fix query regression from TS migration #632 (compound DB indexes) to the "Done" list and "Key PRs" reference.
• Prior concern resolved: The stale libc bullet from the replaced PR chore: release v3.5.0 #639 has been removed from the description.

Confidence Score: 5/5

Safe to merge — purely a version-bump and documentation release with no logic changes.

All version fields are consistent, the CHANGELOG is accurate and complete, the ROADMAP reflects the correct state, and the prior stale-description concern from the previous review has been addressed. No code logic is touched.

No files require special attention.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds well-structured 3.4.1 release entry covering bug fixes, performance improvements, refactors, and chores; all PR references and section headings are accurate
crates/codegraph-core/Cargo.toml	Single-line version bump from 3.4.0 to 3.4.1; correct and consistent with the rest of the release
package.json	Version bumped from 3.4.0 to 3.4.1; straightforward and correct
package-lock.json	Both version fields updated from 3.4.0 to 3.4.1; lockfile structure is otherwise unchanged
docs/roadmap/ROADMAP.md	Version header and date updated to 3.4.1 / 2026-03-26; section 6.8 accurately adds compound-index work from PR #632 to the Done list and Key PRs reference
docs/roadmap/BACKLOG.md	Date-stamp updated from 2026-03-25 to 2026-03-26; trivial and correct

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[v3.4.0 tag] -->|13 merged PRs| B[v3.4.1 release PR]
    B --> C[package.json\n3.4.0 → 3.4.1]
    B --> D[package-lock.json\n3.4.0 → 3.4.1]
    B --> E[Cargo.toml\n3.4.0 → 3.4.1]
    B --> F[CHANGELOG.md\nAdd 3.4.1 entry]
    B --> G[ROADMAP.md\nVersion + PR #632 notes]
    B --> H[BACKLOG.md\nDate stamp update]
    F --> F1[Bug Fixes × 9]
    F --> F2[Performance × 2]
    F --> F3[Refactors × 4]
    F --> F4[Chores × 1]

Loading

_{Reviews (2): Last reviewed commit: "fix: resolve merge conflicts with main" | Re-trigger Greptile}

[greptile-apps]

PR description mentions libc restoration not present in diff

The PR description states: "Restore libc fields in package-lock.json for Linux entries", but the actual diff for package-lock.json contains only the two version-number bumps (3.4.0 → 3.4.1). No libc field additions are visible in the changeset.

This is either:

• Copy-paste carry-over from the replaced PR chore: release v3.5.0 #639 that doesn't apply to this diff, or
• The libc fields were already present in main before this PR and the description is stale.

Either way, the description inaccurately describes what this PR changes. Consider updating the description to remove or clarify that bullet point so the release record stays accurate.

[carlos-alm]

Good catch. The libc bullet was a stale carry-over from the replaced PR #639. Removed it from the PR description.

[carlos-alm]

@greptileai