chore(master): release 1.10.0

[github-actions]

🤖 I have created a release beep boop

1.10.0 (2026-04-15)

Features

• add HTTP transport mode alongside stdio (8e97d0f)
• add HTTP transport mode and server config file support (3c8c273)
• add react and nextjs analyzers (1ac4671)
• add react and nextjs analyzers (3da89f9)
• add server config file support for pre-registering projects (08539c6)
• eval: add 5-comparator benchmark harness with timing and output flag (999faf7)
• freeze discovery benchmark contract (66824f9)
• freeze discovery benchmark contract (1c78171)
• HTTP transport mode (--http flag) (c9bf17f)
• implement DISC-01 compact/full search modes and SAFE-01 freshness-aware edit gating (059aa0c)
• map: promote codebase map as primary first-call surface (Phase 7) (328d03b)
• phase-6: add codebase-context init wizard (#90) (e52cf0d)
• support per-project analyzer hints (#83) (4441b41)
• tighten search contract (Phase 8 - DISC-01 + SAFE-01) (164ff14)
• v2.1: map structural skeleton + search metadata surface (#95) (8650c0a)

Bug Fixes

• address greptile P2 review comments (41c252a)
• align discovery protocol metrics (21c3e43)
• benchmarks: make all comparator lanes cross-platform on Windows (#97) (#97) (6c19628)
• ci: replace retired pnpm audit endpoint (b8c525d)
• clean up benchmark MCP sessions (ad5db8b)
• clean up benchmark MCP sessions (408c248)
• close Phase 8 review follow-ups (b549be4)
• config: reject empty roots and invalid ports (912e6f6)
• deps: patch picomatch audit path (c637bf5)
• finalize v2.1.0 token budget advisory (2df5399)
• format discovery benchmark sources (b4ab479)
• guard against unhandled rejections and resource leaks in HTTP transport (e031a56)
• harden managed MCP session cleanup (fcce4b6)
• metadata: prevent framework misclassification in codebase detection (#96) (ae649dd)
• patch vulnerable hono dependencies (fa79e90)
• prevent zombie MCP processes via handshake timeout + deferred init (#89) (37fd4b9)
• resolve PR #98 review blockers (396dd66)
• satisfy lint in index (e218859)
• search: finalize token budget advisory payload (2d08c89)
• search: query-aware bestExample, golden file threshold, ONNX thread limits (9cec82a)
• search: wire SearchResult imports/exports and stabilize map hub selection (#100) (922f9fc)
• test: update multi-project routing assertions for new map header (adfe8d5)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This is an automated Release Please PR bumping codebase-context from v1.9.0 to v1.10.0. It covers three mechanical changes — version in package.json, .release-please-manifest.json, and a new CHANGELOG.md section — to publish the HTTP transport mode (--http flag) that was already merged into master via PR #78.

Key observations:

• All three file changes are correct and consistent (1.9.0 → 1.10.0 everywhere).
• The CHANGELOG.md includes two feature entries for what is effectively one HTTP-transport feature; the second entry (c9bf17f) is the merge-commit of PR feat: HTTP transport mode (--http flag) #78 being picked up as a conventional commit, which is redundant.
• README.md and docs/capabilities.md have not been updated to document the new --http flag. The AGENTS.md release checklist explicitly requires both files to be updated before any version bump. This is the one actionable item before merging.

Confidence Score: 4/5

• Safe to merge after updating README.md and docs/capabilities.md with the new --http flag documentation.
• All version bumps are consistent and correct across the three changed files. The only blocker is a missing doc update required by the AGENTS.md release checklist — a targeted, low-risk fix that doesn't touch any logic.
• No files in the PR changeset need special attention; the gap is in README.md and docs/capabilities.md which are outside this PR's diff.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 1.9.0 to 1.10.0 — purely mechanical change by Release Please.
CHANGELOG.md	Adds the 1.10.0 section; two separate feature entries exist for what appears to be a single HTTP-transport feature (potentially duplicative), but no blocking issues.
package.json	Version bumped from 1.9.0 to 1.10.0; hono dependency and related pnpm overrides were already present from the feature branch merge.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please bot\ndetects feat/fix commits] --> B[Generates release PR\nchore: release 1.10.0]
    B --> C{PR merged?}
    C -- Yes --> D[package.json\nversion: 1.10.0]
    C -- Yes --> E[.release-please-manifest.json\n1.10.0]
    C -- Yes --> F[CHANGELOG.md\nadds 1.10.0 section]
    D & E & F --> G[npm publish\ncodebase-context@1.10.0]
    G --> H[New --http flag available\nHTTP transport mode\nalongside stdio]

Loading

_{Reviews (1): Last reviewed commit: "chore(master): release 1.10.0" | Re-trigger Greptile}

[greptile-apps]

Duplicate feature entries for HTTP transport

Two separate ### Features entries exist for what is effectively the same capability:

• add HTTP transport mode alongside stdio (8e97d0f)
• HTTP transport mode (--http flag) (c9bf17f — which is actually the merge commit of PR feat: HTTP transport mode (--http flag) #78, not a feature commit)

Release Please picked up the PR merge commit as a second entry. This is cosmetic, but it adds noise for users reading the changelog. Consider squashing these into one entry (or using a PR title that doesn't trigger a second conventional-commit parse) on future transport-related work.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[greptile-apps]

Release checklist: README.md and docs/capabilities.md not updated

AGENTS.md defines a non-negotiable release checklist:

Before any version bump: update CHANGELOG.md, README.md, docs/capabilities.md. Run full test suite.

Neither README.md nor docs/capabilities.md currently mention the new --http flag or the HTTP transport mode (verified by grepping both files). The feature commits (8e97d0f, e031a56) only touched src/ files — the docs were never updated.

Before merging this release PR, the HTTP transport mode should be documented in both README.md and docs/capabilities.md to satisfy the release checklist.

Context Used: AGENTS.md (source)

[PatrickSys]

Release note: the earlier docs blocker is stale; public docs were normalized in PR #102. This branch is rebased onto current master, the stale 2.1.0 changelog block was removed, package.json and .release-please-manifest.json are both 1.10.0, and npm view codebase-context@1.10.0 currently returns 404. Not merging in this pass because merge is the publish trigger.

[PatrickSys]

Release note: the remaining changelog noise noted by Greptile has now been cleaned up on this branch. The duplicate HTTP transport feature bullet was removed, so the 1.10.0 entry keeps a single user-facing HTTP transport line. The earlier docs blocker is also still stale: README and docs/capabilities.md were normalized on master in #102 before this release branch was rebased, so this PR remains release-only (.release-please-manifest.json, package.json, CHANGELOG.md).

[github-actions]

🤖 Created releases:

• v1.10.0

🌻