Show each review round's failure-class chains, churn and cost in status

Abierto
  • ¿Algo no está bien?
#458 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
cli, observability

Línea de trabajo

Start with the status output and the per-round run-log record, and read execution.json to see where the Claude-reported cost is stored. The churn figures must come from the controller's own git reads of each FIX commit (--shortstat, cumulative since the first FIX), not from agent output. This issue depends on #452 and #453, which supply chain ids and lengths, so check those first. Done means a fixture history renders each round's findings, chains, churn and cost, showing "unknown" or "not reported" where data is absent.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Problem

Nothing in status or the run log shows whether a REVIEW/FIX loop is converging. An operator watching Lychee-Technology/forma#801 saw finding counts of 1, 1, 1… and could not tell, without reading every review comment, that each round was the same unresolved problem and that each FIX was adding hundreds of lines to one module.

Evidence

From #451:

  • Churn was large but invisible. Rounds 3–11 of Lychee-Technology/forma#801 added +2,128 / −473 lines, about 95% of them in the scanner and lexer files.
  • Cost is only partly recorded. The Claude-reported cost is in execution.json ($24.42 for the run), but OpenCode's provider_summary holds no cost at all, so the total cost of the incident is unknown.

Desired outcome

status, and a run-log record per review round, show:

  • the finding count;
  • each finding's chain id and chain length (from #452);
  • the FIX commit's --shortstat and the cumulative change since the first FIX, computed by the controller from git, never taken from agent claims;
  • the provider-reported cost where there is one, and "not reported" where there is not.

Acceptance criteria

  • status renders these from a fixture history. A history without links or costs renders "unknown" or "not reported", never zero.
  • The churn numbers come from the controller's own git reads of the reported commits.
  • No new GitHub read or write.

Trade-offs and unknowns

Whether OpenCode can report cost at all in this mode is unknown; if it cannot, the field stays "not reported".

Depends on #452 and #453.

Lenguaje dominante
Python
Estrellas
0
Forks
0
Merge medio
5 h 43 min
PR fusionados (30 d)
108

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 iceboundrock/AutoForge

Todos los issues de iceboundrock/AutoForge

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.