What is built: Debugging and review
Which parts of Debugging and review are built, and what the rest waits on
| Feature | Status |
|---|---|
jadpo calls, calls show and calls script |
Built. |
Each step a request's action reached, as a trace line in jadpo dev |
Built. Until the timelines are built, each step is a line under its request's line in jadpo dev, and a delivery whose action reached steps gets a line of its own (design notes for jobs and events). |
jadpo why <schedule> |
Built: it answers why a schedule didn't run (Watching schedules). |
Mapped .jadpo stacks, jadpo incident, the other forms of why, timelines, test new --from, call and the approval report |
Not built yet: these come first (the roadmap). Until jadpo approval is built, jadpo translations missing lists wording not yet accepted. |
| The developer console, MCP and the review web view | Not built yet: they come after those, as product work. |
jadpo traces, metrics, logs and watch; path coverage, production counts in review, replay and query cost |
Not built yet. |
Markdown for agents: /docs/debugging-and-review-built.md.Built from Jadpo main at a707efb.