fix(selfhost): validate private config repo names

[JSONbored]

Motivation

• Close a path-traversal security hole in the self-host private-config reader where crafted repo full names like owner/.. could cause reads outside GITTENSORY_REPO_CONFIG_DIR.
• Ensure per-repo candidate generation only accepts GitHub-safe owner/repo segments and does not allow ./.. or extra slashes.

Description

• Validate repo full names by rejecting multiple slashes, enforcing an owner regex and a safe repo-segment regex, and rejecting ./.. segments before building candidates in localConfigCandidates (src/selfhost/private-config.ts).
• Normalize and resolve the configured base directory and candidate file paths with resolve() so reads are always performed against resolved paths; keep the existing lookup priority (owner-qualified folder → bare repo folder → flat file → global fallback).
• Added a regression unit test covering invalid names and the reported traversal case (test/unit/private-config.test.ts).
• Kept error-swallowing candidate iteration behavior (continue on ENOENT/unreadable) and preserved back-compat filename order (.yml, .yaml, .json).

Testing

• Ran the targeted unit suite vitest run test/unit/private-config.test.ts, all tests passed (12 tests).
• Attempted coverage remapping with npm run test:coverage -- --run test/unit/private-config.test.ts, the targeted tests ran but coverage remapping failed with TypeError: jsTokens is not a function during report generation.
• Ran npm run typecheck which reported unrelated local type resolution issues for @sentry/node in src/selfhost/sentry.ts and prevented a clean full typecheck run.
• Attempted the full gate via npm run test:ci, which was blocked by actionlint setup/network issues (WASM fallback flagged a custom self-host runner label); npm audit --audit-level=moderate returned a 403 from the npm audit endpoint.

---

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 (5d6428b).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1563   +/-   ##
=======================================
  Coverage   95.42%   95.42%           
=======================================
  Files         202      202           
  Lines       21674    21679    +5     
  Branches     7833     7835    +2     
=======================================
+ Hits        20683    20688    +5     
  Misses        416      416           
  Partials      575      575           

Files with missing lines	Coverage Δ
src/selfhost/private-config.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

2 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:S.
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 7 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