feat(cli): the board reads what actually ran

Open
#651 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
67/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

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.

Written by the indexing model from the issue text.

Description

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
Dominant language
TypeScript
Stars
481
Forks
45
Avg merge
14h 36m
Merged PRs (30d)
110

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ai-driven-dev/framework

All issues in ai-driven-dev/framework

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.