fix: correct local query and curate messaging

[strasserwm]

Summary

Fixes two local ByteRover query/curate UX issues:

1. Non-ByteRover provider 401 / Unauthorized failures were shown as cloud-sync login failures, telling users to run brv login even when local query/curate only needed provider credentials.
2. brv curate could print Context curated successfully for blocked/no-op curation responses where no context-tree operations were applied.

Changes

• Keep brv login guidance for true ByteRover cloud auth / NOT_AUTHENTICATED cases.
• For non-ByteRover provider auth failures, show provider credential/base URL guidance and avoid echoing raw error text.
• Add curate outcome classification for blocked/no-op responses.
• Treat blocked curate responses as errors instead of successful completions.
• Record blocked zero-op curation logs as error.
• Print No context changes applied for genuine successful no-op curation.
• Add/update focused tests for auth-message and curate-outcome behavior.

Verification

Performed locally:

• git apply --check for Phase 1 patch
• git apply --check for Phase 2 patch
• git apply --check for combined patch
• git diff --check
• Phase 1 focused tests previously reported passing: 9 passing

Could not fully verify locally because this checkout lacks private/incomplete dependencies:

• mocha is missing locally
• npm install / full dependency repair is blocked by private github.com/campfirein/byterover-packages
• tsc --noEmit reports repo-wide missing dependency/type errors unrelated to this patch set

Recommended maintainer verification with private deps available:

npm ci
npx mocha --forbid-only \
  "test/unit/oclif/lib/daemon-client-error.test.ts" \
  "test/commands/curate.test.ts" \
  "test/unit/infra/executor/curate-executor.test.ts" \
  "test/unit/infra/process/curate-log-handler.test.ts"
npm run typecheck
npm test

Risk notes

• Provider auth-message change is low risk; main watch item is whether provider context is always available where the CLI formats daemon errors.
• Curate outcome change is medium risk; main watch items are blocked-text false positives and any downstream assumptions that task completion always means curation success.

[bao-byterover]

Hey @strasserwm could you merge main into this branch when you get a chance? There've been a few updates upstream, and syncing will keep CI green and make review easier. Thanks!

[strasserwm]

Merged latest main and pushed fixes for the post-merge CI regressions. The latest commit is 8418a82. Validation is currently skipped because safe-to-test was removed after the push. Could you please re-add safe-to-test when you get a chance?

…

On Wed, May 20, 2026 at 12:30 AM bao-byterover ***@***.***> wrote: *bao-byterover* left a comment (campfirein/byterover-cli#668) <#668 (comment)> Hey @strasserwm <https://github.com/strasserwm> could you merge main into this branch when you get a chance? There've been a few updates upstream, and syncing will keep CI green and make review easier. Thanks! — Reply to this email directly, view it on GitHub <#668 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI2JSSZZEYSVIF424322XBD43UYGDAVCNFSM6AAAAACZBVYKKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOJUGUZDIMJQGY> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>