Skip to content

fix(cli): disclose incomplete search coverage and pin beta setup - #165

Draft
PatrickSys wants to merge 2 commits into
masterfrom
fix/stranger-frictions-20261107
Draft

PatrickSys wants to merge 2 commits into
masterfrom
fix/stranger-frictions-20261107

Conversation

@PatrickSys

Copy link
Copy Markdown
Owner

Human search output hid when source inspection stopped early, and Codex setup help could select the stable package instead of the beta. This change shows checked and skipped file counts with early-stop guidance, and makes the README, --help and init --help use codebase-context@2.3.1-beta.0 explicitly.

Validation: all 61 CLI tests pass. The build, changed-source ESLint, source formatting check and replay of a recorded search response pass. npm currently lists beta 2.3.1-beta.0 and stable 2.2.0.

The seven original freshness-test timeouts did not reproduce: all seven pass on both this patch and the unchanged base at the original 15-second limit, and in separate 60-second diagnostic runs, all serial. The pre-push full suite then reported 1,449 passes, 13 timeouts and two skips. All 13 failed cases pass in a single isolated serial check at their unchanged original limits. The timeout cause remains unproven. These checks do not establish a green full-suite result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant