Browse, author, and save workflows in one editor #25

Parent

#3

What to build

Deliver the workflow plugin's library and one editor as a complete authoring feature: find saved/packaged workflows, create a reported agent sequence, save/reopen it safely, and exchange canonical YAML. Make the narrow host/API changes this feature requires within the same ticket, prefactoring those seams first rather than creating separate infrastructure tickets.

Acceptance criteria

• Workflows appears in normal navigation with explicit environment/project context. Project selection/discovery is target-bound. The library provides search and paging across the entire catalog, name/available description, step/review summary, saved revision, and packaged/read-only status. Invalid/duplicate entries retain their authoritative reason and source, with repair/import replacement actions.
• New workflow asks for a name and opens one palette/flow/inspector with Add a step and an always-available Route list. Create, select, connect, reorder, and remove reported Agent and End steps without dragging. End outcome, entry, whole-run visit bound, and At limit use the canonical schema. Desktop and labeled narrow-width sheets share the same definition and accessible reading order.
• Agent inspection covers label, provider/model/custom options, runtime/interaction mode, actual installed skill, instructions, deadlines, explicit typed upstream bindings, declared report fields, next and unresolved routes. Boolean/string/finite-number/enum reports support required/optional fields. Own the narrow public provider/model/skill discovery access needed; use the selected environment's reporting capability matrix, never free-text installation claims or core-store imports.
• Existing definitions preserve all node types and meanings; controls delivered by later tickets are visibly read-only until available. Packaged examples clone under a new identity. Unsupported skills/providers have actionable, control-linked reasons and block runnable publication according to authoritative validation.
• Own an authorized canonical authoring read/save/export path. Redacted display snapshots cannot overwrite instructions, enums, predicates, or check commands; protected values use an explicit backend-supported preservation mechanism. YAML import stages a candidate draft and preserves current edits on failure. Export/import round-trips graph semantics, or clearly explains a protected value that prevents lossless export.
• Repair an invalid catalog entry through an authorized replacement tied to its exact server-selected source and observed content fingerprint/revision. Validate before commit; a concurrent external edit conflicts without overwriting unrelated entries or discarding the draft.
• Show Unsaved changes/Saving/Saved revision. Bounded local drafts persist across reload, keyed by environment/project/workflow identity; Keep editing/Discard protects navigation. Expected-revision conflicts and request failures retain edits and offer reload/compare. Layout preferences cannot change semantics.
• Own structured server validation locations and blocking/warning severity while preserving original reasons. Problems to fix focuses the node/route/control; local invalid drafts remain recoverable. Preserve canonical blocking rules: nodes without an End/human path block publication; an End unreachable from entry is an authoritative warning.
• Prefactor only required generic host facilities: shared bounded/validated page-link state for server/client links, persistent draft storage/navigation guard, and supported design/discovery interfaces. Verify them with the existing fixture. Core navigation/stores contain no workflow branches; links to feature pages not yet contributed remain unavailable. Begin with code-native flow presentation; defer any canvas-library choice until the repeat-direction human check.
• Loading/empty/Retry, authorization, missing/incompatible plugin/client module, discovery failure, and disconnect states are useful. Drafts and last snapshots remain visibly stale offline; cached mutations stay unavailable until the intended environment reconnects and reconciles. All controls have keyboard access, semantic labels, textual status, and touch-friendly targets.
• Focused real-host/client behavior tests demonstrate a saved reported-agent sequence, keyboard authoring, YAML/clone/invalid-file repair, protected-value preservation, failed saves/conflicts/imports, paging beyond the catalog cap, two similarly named environments, and authenticated remote authoring. Use existing services and public boundaries; do not introduce another graph or execution engine.

Blocked by

None (can start immediately; plugin host and canonical backend prerequisites are already implemented).

Ticket specification reviewed and agreed by Codex and Claude Opus 5.5.