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

Aperta
  • Qualcosa non va?
#13,724 6 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@kyle-sexton ci sta già lavorando.

Dal 6/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.
Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
1h 13m
PR unite (30g)
954

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.