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

Abierto
  • ¿Algo no está bien?
#13,724 6 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@kyle-sexton ya está trabajando en esto.

Desde el 6/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
1 h 13 min
PR fusionados (30 d)
954

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.