Skip to content

Render Manifest State Summaries #183

Description

@csfh

Parent

#178

What to build

Update Manifest and Workspace summaries to use the same canonical RuntimeStatus codes as rows, ordered by operational severity and omitting zero-count states.

Acceptance criteria

  • Manifest summary counts visible runtimeStatus values, not raw lifecycle states.\n- [ ] Summary order is Err, Rty, Blk, Str, Stp, Off, Pau, Unk, Run.\n- [ ] Zero-count statuses are omitted.\n- [ ] Retrying processes count as Rty, not Err.\n- [ ] Summary text uses code labels such as 1 Err · 1 Rty · 2 Run.\n- [ ] External Runtime summary uses the same canonical status vocabulary where shown.

Blocked by

#181

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions