feat(cli): the board reads what actually ran

Abierto
#651 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Check dependency #620 first, then trace the board's existing frontmatter reader and inspect the run journal and task identity file formats it must read. Verify the board preserves run order and repeated steps, resolves originating tickets, handles unattached work and missing journals, and remains read-only without telemetry or cross-project aggregation.

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

Descripción

As a developer returning to a project
I want the board to show what actually ran, not only what was declared
So that I recover the thread without opening folders or paying an agent to summarise state that is already written down

Acceptance

  • A feature shows its steps in the order they ran, with the duration of each.
  • A step that ran several times appears several times, not merged.
  • The originating ticket is shown, resolved through the identity file's upward link.
  • Work with no task attachment is reachable, not hidden.
  • The board keeps working on a project that has no run journal at all, degrading to what it shows today.
  • No token or cost figure appears: they are not on disk, and the board reads only the repository.
  • The board still writes nothing and launches nothing.

What it reads, and what it must not

It reads the run journal and the task identity file, next to the frontmatter it already reads. It must not read telemetry: the board is offline, unauthenticated, and local by design. Cost belongs to the skill that can reach the sink, and to the dashboard.

Its own product brief already names these two as missing — "journal des exécutions" and "tokens par phase" — and answers the second: the board is not where tokens belong.

Out of scope

  • Any figure requiring the telemetry sink.
  • Aggregation across projects.

Relations

Field Value
depends_on #620
Lenguaje dominante
TypeScript
Estrellas
481
Forks
45
Merge medio
14 h 36 min
PR fusionados (30 d)
110

Guía de contribución

Abrir la guía de contribución

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 ai-driven-dev/framework

Todos los issues de ai-driven-dev/framework

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.