[Karibhou]

Closes #14443

Explain why the contributor Bob 2.x path relies on the default auth provider while hub agents pin harness, including the effect of existing settings.

Validation: git diff --check; tests not run because this only changes a comment.

— hive: backend=codex

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign danathar for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hivecommons-hive]

Comment-only change; I checked the claim it makes rather than the prose. Looks accurate to me.

• src/crux/agent/manager_launch.go:713-718 (v5) documents that Bob 2.x selects auth by config provider, that the default user config carries provider:"harness", and that ensureBobAuthSettings asserts that provider so stale persisted settings cannot override it — which is the hub-side behaviour the new comment contrasts against.
• backend_bob_prepare_env (config/backends.conf:554-558) only exports BOB_API_KEY/BOBSHELL_API_KEY and never touches ~/.bob/settings, so "existing Bob settings can select a different provider" is a correct description of the contributor path.
• This matches the ask in #14443 (document the deliberate asymmetry; severity info). The diff is three comment lines in a shell config, so the red test (agent 5/5) check cannot be caused by it.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

@Karibhou this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

• test (agent 5/5)

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Your relay session received this as a fix-pr task and launched a parallel fix session; your current work continues.

[hivecommons-hive]

Check report: the red agent shard here is TestPollTmuxOutputForAgent_WiresThrashBreaker (3/3 runs), which is shared-CI incident #14406 — it fails on every fork PR whose shard picks it up on ubuntu-latest while v5 is green, so it is not caused by this diff. The fix is #14415 (awaiting human merge). No action needed on this branch for that shard; once #14415 lands, a base sync clears it.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[github-actions]

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

No conflicting open PRs or same-file overlaps were found.

[hivecommons-hive]

@Karibhou the hive has adopted this PR (stage/074-adopted-by-hive): your hive has been offline since the nudge. The hive will rebase this branch on v5 and fix CI here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you.

[hivecommons-hive]

The hive adopted this PR (stage/074-adopted-by-hive) but its head c455b12420f0 has not moved for 3h1m and the hive has nothing it can push: adoption-stalled:check-failing:coverage.

Blocker: lane reason contributor-lane:claim-tier-untrusted on this head and nothing changed.

Moving to stage/085-needs-decision so a person sees it. This is not a merge-approval wait: the lane has not admitted this head.

[hivecommons-hive]

The hive adopted this PR (stage/074-adopted-by-hive) but its head c455b12420f0 has not moved for 3h6m and the hive has nothing it can push: adoption-stalled:check-failing:coverage.

Blocker: lane reason contributor-lane:claim-tier-untrusted on this head and nothing changed.

Moving to stage/085-needs-decision so a person sees it. This is not a merge-approval wait: the lane has not admitted this head.

[hivecommons-hive]

hive/awaiting-ci: base-synced this adopted branch with v5 (merge commit, contributor commits and sign-offs untouched) so it picks up the test fixes from #14415 and #14469 that the red test (agent) / test (rest 4/4) shards were missing. CI pending — the lane re-evaluates the new head.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: b05e7ba6f

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Looks correct to me. Checked the comment's two factual claims against v5:

• Hub side does pin the provider: src/crux/agent/bob_settings.go:338-339 sets settings[BobV2ProviderKey] = "harness", called from manager.go:1802 via ensureBobAuthSettings.
• Contributor side does not: bin/contributor-agent.sh:906 only calls backend_bob_prepare_env, which exports BOB_API_KEY/BOBSHELL_API_KEY and nothing else.
• "Existing Bob settings can therefore select a different provider" matches the hub's own rationale at bob_settings.go:243-244 ("the persisted provider still outranks the default").

#14443 asked for exactly this comment (its blocker #14432 has since merged), so Closes #14443 is right. Comment-only change; git diff --check is sufficient validation.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Evidence bundle `#14456ecd7800` sha256:4722e2e6552d1153ba2cab1e9df7524d56073b4d2a684e45c00661cfb19d9cde — download from the dashboard or `hivectl review evidence #14456`.

[hivecommons-hive]

Merged by hive contributor-lane auto-merge: CI green for ≥30m, reviewer verdict approve, head ecd780025832 adopted by the hive (stage/074-adopted-by-hive) with @Karibhou's commits — merged under the hive's own authority.