[Feature] 支持将 SkillHub 部署到路径

[z1645444]

Problem

SkillHub 目前假设自身部署在域名根路径下。子域名（以 https://skillhub.example.com 为例）部署
已通过 runtime.sh --public-url、compose.release.yml 和 Helm ingress 得到良好支持，但没有官方支持的方式
将 SkillHub 作为子站点托管，例如部署到 https://example.com/tools。

Proposed Solution

引入 base path 概念，支持配置类似 SKILLHUB_PUBLIC_BASE_URL=https://example.com/tools

Alternatives Considered

No response

Impact

No response

Contract Or SDK Impact

No response

[github-actions]

Issue Triage

• Route: triage/deferred
• Priority: priority/p2 (2.6/5)
• Effort: effort/l (4/5)
• Confidence: 4/5
• Risk: low
• Analysis Mode: rules-only

Why

• Open for 9 days; entering the 2-week closure warm-up window.

Next Action

• Keep the issue in the deferred queue and let the 6-hour rescore keep lifting it; it is forced into an active lane by day 10. If it is still open on day 14, treat it as a P0 escalation target under the SLA and prioritize it in the next triage pass.

---

问题分流结果

• 路由: triage/deferred
• 优先级: priority/p2 (2.6/5)
• 修复投入: effort/l (4/5)
• 信息完整度: 4/5
• 风险: 低
• 分析模式: rules-only

原因

• 已打开 9 天，开始进入 2 周闭环预热窗口

下一步

• 将 issue 保留在 deferred 队列，并由 6 小时一次的 rescore 持续抬升；最晚在第 10 天强制进入 active lane。若第 14 天仍未闭环，应按 SLA 视为 P0 升级目标，并在下一次 triage 中重点处理