perf(pr-verify): set the capture key proxy's token-cap from a full measured capture

未关闭
#13,724 6 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@kyle-sexton 已经在做这个了。

开始于 2026年11月6日。

评估

这个 Issue 还没有评估数据。

描述

host-run priority: medium status: confirmed work-class: scoped

Refs: #12232

Problem

PR capture's key proxy enforces merge.verify-capture.proxy.token-cap (docs/conventions/pr-pipeline.yaml), still the provisional judgment value set before any live run. The first live capture (run 42235412941, graded at issuecomment-6687618296) stopped at the key's credit wall ("Credit balance too low"; the proxy counted 27,876 driven tokens), so it measured no full capture.

Done when

  • One capture on PR_VERIFY_CLAUDE_API_KEY with refreshed promotional credit drives a UI-surface PR's hook and mod entry points without a credit stop.
  • token-cap is set above that run's proxy-reported token use (the "Report the key proxy's usage" notice) with a stated margin, in a PR that cites the run, and the yaml comment's "provisional" wording is replaced.
  • The trigger to start: the first capture run after the credit refresh whose "Report the key proxy's usage" notice shows no 400 credit-stop answers.

Remaining

  • Every item needs a full CI key capture and waits on PR_VERIFY_CLAUDE_API_KEY's credit reset (the key is burnt, run 42323030495; owner Q8: no rotation; hub H149). A local capture runs on the building session's subscription, behind no key proxy, so it cannot measure the proxy's caps.
  • Progress: PR 13868 split the cap. token-cap: 1500000 bounds the driven session, and driver-token-cap: 6000000 bounds the driver legs, both provisional. The fullest run so far, 42313414930, used 3,656,992 loopback and 33,234 driven tokens, but its typed entry points were refused (since fixed by PR 13877), so it is not the measurement. Rule: cap = measured × 1.5, rounded up to the next 100,000.
主要语言
Shell
星标
22
派生
2
平均合并
1 小时 13 分钟
30 天内合并 PR
954

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。