fix(selfhost): probe Qdrant /readyz for readiness

[JSONbored]

Motivation

• The self-host /ready probe queried the raw QDRANT_URL without the configured QDRANT_API_KEY and without using Qdrant's documented unauthenticated /readyz endpoint, causing healthy API-key-protected Qdrant deployments to make the instance report 503.
• Readiness should avoid re-probing the authenticated root and instead use the unauthenticated readiness endpoint (or authenticate) so load balancers don't evict otherwise healthy instances.

Description

• Added qdrantReadyzUrl(url: string) in src/selfhost/qdrant-vectorize.ts to normalize a configured Qdrant base URL and produce the unauthenticated /readyz URL.
• Updated the self-host readiness probe in src/server.ts to call qdrantReadyzUrl(qdrantUrl) instead of fetching the raw base URL, while leaving authenticated collection initialization via initQdrantCollection() unchanged.
• Added a regression unit test in test/unit/selfhost-qdrant-vectorize.test.ts to assert /readyz is chosen for both plain and trailing-slash base URLs.

Testing

• Ran the Qdrant unit suite with npx vitest run test/unit/selfhost-qdrant-vectorize.test.ts, and the tests passed successfully.
• Ran npm run typecheck, which failed in this environment due to missing @sentry/node type declarations unrelated to the change.
• Attempted coverage with npx vitest run --coverage test/unit/selfhost-qdrant-vectorize.test.ts, which exercised tests but coverage remapping failed here with TypeError: jsTokens is not a function (environmental tooling issue).
• Attempted the full local gate npm run test:ci and npm audit --audit-level=moderate, both of which failed in this environment due to external tool/registry issues (actionlint/runner-label DNS fallback and npm audit 403) and not because of the PR logic or behaviour.

---

Codex Task

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.42%. Comparing base (14dc3f1) to head (9ed8b8a).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1565   +/-   ##
=======================================
  Coverage   95.42%   95.42%           
=======================================
  Files         202      202           
  Lines       21674    21675    +1     
  Branches     7833     7833           
=======================================
+ Hits        20683    20684    +1     
  Misses        416      416           
  Partials      575      575           

Files with missing lines	Coverage Δ
src/selfhost/qdrant-vectorize.ts	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gittensory-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ Gittensory review — safe to merge

3 files · 1 AI reviewers · no blockers · readiness 48/100 · CI green · blocked

✅ Approved — safe to merge

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewers, synthesized
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Review load	❌ 8/20	Readiness component derived from cached public PR metadata and labels; size label size:XS.
Validation evidence	❌ 5/25	Cached preflight status is hold.
Open PR queue	❌ 3/10	48 open PR(s), 9 likely reviewable, 39 unlinked.
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 81 PR(s), 261 issue(s).
Gate result	✅ Passing	No configured blocker found.

Nits — 2 non-blocking

• Repository config was not parsed
• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 81 PR(s), 261 issue(s).
• Related work: Titles/paths share 6 meaningful terms. (PR #1392)
• Related work: Titles/paths share 6 meaningful terms. (PR #1553)
• Related work: Titles/paths share 6 meaningful terms. (PR #1558)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Review top overlaps.
• Add scope summary.
• Fix blocker.
• Expect slower review.
• Refresh registry data or choose a registered active repo.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• Check active issues and PRs before submitting.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Review load = cached public PR metadata such as size labels, changed paths, and preflight status.
• Open PR queue = repo-wide review pressure; it is not a PR quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review