chore: release v3.1.5

[carlos-alm]

Summary

• Bump version to 3.1.5
• Add CHANGELOG entry for all commits since v3.1.4
• Update ROADMAP: Phase 3 marked Complete (14/14 tasks), 3.15 and 3.16 marked done with PR links
• Update README: Phase 3 roadmap line updated, --table/--csv options documented
• Remove generated/architecture.md — all 20 audit items addressed by Phase 3 (15 resolved, 5 deferred to Phase 6)
• Restore libc fields in package-lock.json for Linux native packages (dropped by npm install --package-lock-only on Windows)

Test plan

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

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[greptile-apps]

Greptile Summary

This is a chore release PR that bumps the package version from 3.1.4 to 3.1.5, adds a CHANGELOG entry documenting all Phase 3 completion work, updates the README and ROADMAP to reflect Phase 3 as fully complete (14/14 tasks), and removes the now-stale generated/architecture.md audit document.

Key changes:

• package.json / package-lock.json: version → 3.1.5
• CHANGELOG.md: new v3.1.5 section covering 1 feature (openGraph() + universal output formatter), 5 bug fixes, 4 refactors, and 1 test addition
• README.md: Phase 4 roadmap row updated to Complete (v3.1.5); --table and --csv output options added to the options reference table
• ROADMAP.md: version header, Phase 3 summary table, and section header all updated to Complete; tasks 3.15 and 3.16 rewritten with completion notes and PR links; stale architecture.md reference removed
• generated/architecture.md: deleted — all 20 audit items addressed or deferred to Phase 6

One item worth verifying: the bug fix attributed to PR #446 (LIKE wildcard escaping) is numbered considerably earlier than all other PRs in this release (#456–#475), and may have already been included in v3.1.4.

Confidence Score: 4/5

• Safe to merge — purely documentation and version bump changes with no runtime code modifications.
• All changes are confined to documentation files, the CHANGELOG, and version fields in package manifests. No source code, tests, or build configuration was modified. The only item worth verifying before merging is whether PR fix: escape LIKE wildcards in NodeQuery.fileFilter and nameLike #446 was already included in a prior release and is being double-counted in the CHANGELOG.
• CHANGELOG.md — confirm PR fix: escape LIKE wildcards in NodeQuery.fileFilter and nameLike #446 (LIKE wildcard fix) was not already shipped in v3.1.4

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds v3.1.5 CHANGELOG section documenting 1 feature, 5 bug fixes, 4 refactors, and 1 test entry; PR #446 (LIKE wildcard escape) appears out of sequence relative to the other PRs in this release (#456–#475), which may indicate it was already included in v3.1.4.
README.md	Phase 4 roadmap line updated from "In Progress (v3.1.4)" to "Complete (v3.1.5)", and --table/--csv output options added to the options table; changes are accurate and well-placed.
docs/roadmap/ROADMAP.md	Version header updated to 3.1.5, Phase 3 table entry and section header marked Complete, stale architecture.md reference removed, tasks 3.15 and 3.16 rewritten from pending to completed with PR links.
generated/architecture.md	457-line architectural audit document deleted; all 20 audit items it tracked have been resolved or deferred to Phase 6, making the file stale. The ROADMAP reference to it is also cleaned up.
package.json	Version field bumped from 3.1.4 to 3.1.5; no other changes.
package-lock.json	Lock file version fields updated from 3.1.4 to 3.1.5 at root and packages[""] entries; no dependency changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([v3.1.4 tag]) --> B[Phase 3 remaining work]

    B --> C["3.15 Domain Directory Grouping\n#456, #458, #459, #466, #469"]
    B --> D["3.16 CLI Composability\n#461"]

    C --> E{Phase 3\n14/14 ✅}
    D --> E

    E --> F["Bump version → 3.1.5\npackage.json / package-lock.json"]
    E --> G["CHANGELOG.md\nv3.1.5 entry added"]
    E --> H["README.md\nPhase 4 row → Complete"]
    E --> I["ROADMAP.md\nPhase 3 → Complete\n3.15 & 3.16 → ✅"]
    E --> J["generated/architecture.md\nDeleted — all 20 items resolved/deferred"]

    F & G & H & I & J --> K([v3.1.5 release PR #477])

Loading

Comments Outside Diff (1)

1. CHANGELOG.md, line 23 (link)

   PR fix: escape LIKE wildcards in NodeQuery.fileFilter and nameLike #446 may be misattributed to this release

   All other PRs listed in the v3.1.5 changelog entry are numbered refactor: reorganize src/ into domain/, features/, presentation/ layers #456–test: add findRepoRoot and findDbPath ceiling boundary tests #475. PR fix: escape LIKE wildcards in NodeQuery.fileFilter and nameLike #446 is notably earlier in sequence, which suggests it may have already shipped in v3.1.4 (or an earlier release) and is being double-counted here.

   If this fix was genuinely merged after the v3.1.4 tag, this is fine — but it's worth confirming that git log v3.1.4..HEAD actually includes the merge commit for fix: escape LIKE wildcards in NodeQuery.fileFilter and nameLike #446. If git log shows it landed before the v3.1.4 tag, this entry should be removed from the v3.1.5 section to avoid misleading the changelog.

_{Last reviewed commit: 58ca942}

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[carlos-alm]

Addressing both P2 comments from Greptile's review:

P2: Native optional dependency versions not synced to 3.1.5
Confirmed — this is by design. The release skill explicitly says "Do NOT bump optionalDependencies versions — synced automatically by scripts/sync-native-versions.js" during the publish workflow. The publish.yml workflow (lines 389–390) calls the script and raises a follow-up PR. Since no Rust code changed in this release, the 3.1.4 binaries are ABI-compatible with the 3.1.5 JS package.

P2: libc field removed from Linux optional native package entries
Fixed in 58ca942. The 3.1.4 packages on npm do expose libc in their metadata (verified via npm view @optave/codegraph-linux-x64-gnu@3.1.4), but npm install --package-lock-only on Windows drops platform-specific libc constraints from optional dependencies it can't install locally. Restored glibc on the two -gnu entries and musl on the -musl entry to match registry metadata.

@greptileai