You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Complete sequence diagrams across the canonical pipeline #280
Complete sequence-diagram support across Sketchi's canonical diagram pipeline and use it as the reference path for future explicitly supported diagram families.
Current baseline
diagram-core currently registers flowchart and mindmap as typed families.
Sequence diagrams now have an explicit Code Mode contract, native renderer, Excalidraw output, and public build endpoint.
Natural-language generation, CLI dispatch, maintained scenarios, and Storybook do not yet treat sequence as a canonical family.
Unsupported families fail explicitly; there is no generic fallback to preserve.
Scope
Establish one typed sequence contract and validation boundary shared by the relevant entry points.
Integrate sequence with diagram-core, generation, CLI dispatch, scenarios/evals, and Storybook where those surfaces advertise diagram families.
Preserve sequence-specific participant, message-ordering, and lifeline semantics rather than mapping it to a flowchart.
Update the diagram-type generator or extension guidance so a future family cannot omit required pipeline stages silently.
Non-goals
Creating speculative issues for organization, ER, Gantt, swimlane, or other unselected families.
Reintroducing the retired generic diagram-type fallback.
Acceptance criteria
Sequence is represented by one canonical typed contract rather than parallel surface-specific shapes.
Supported generation and CLI entry points can request sequence diagrams explicitly.
Deterministic renderer, Excalidraw validation, scenario/eval, API, CLI, and Storybook coverage is present where applicable.
Unsupported families continue to fail explicitly and are not advertised.
The documented extension path identifies every required integration point for the next selected family.
This replaces the still-actionable part of #69 after native Code Mode sequence support landed in #277. Add other families only when product demand or eval evidence selects them.
Done and verified in production. Sequence is a canonical family: one Effect Schema contract in diagram-core shared by generation, Code Mode, renderer, and CLI, with the duplicate shapes deleted (#374, #375); derived activation bars with lane assignment (#376); Studio chat sequence tool with shared turn budget and explicit-type routing (#377); maintained sequence evals scored on model output (#378); a family-pipeline test, generator update, docs/diagram-families.md, and CLI --type listing only supported families, with the generate API, wizard, and prompt derived from the registry (#379); participant logos through the shared icon contract (#380). Production check: /api/v1/generate sequence placed GitHub, Cloudflare, and PostgreSQL logos, drew 2 activation bars, and rendered correctly to PNG.
Activity
feat(scenarios): maintained sequence scenarios and evals
feat(sequence): participant logos through the shared icon contract
feat(sequence): participant logos through the shared icon contract
fix(sequence): name participants in logo diagnostics and eval messages
feat(sequence): participant logos through the shared icon contract
fix(sequence): name participants in logo diagnostics and eval messages
feat(diagram-core): canonical sequence diagram contract and family re…
refactor(diagram): one sequence contract across generation and Code M…
feat(sequence): derive and draw activation bars (#376)
feat(playground): Studio chat builds sequence diagrams (#377)
feat(scenarios): maintained sequence scenarios and evals (#378)
feat(diagram): enforce the diagram family pipeline and stop advertisi…
feat(sequence): participant logos through the shared icon contract (#380
feat(playground): Studio chat builds sequence diagrams (#377)
feat(scenarios): maintained sequence scenarios and evals (#378)
feat(diagram): enforce the diagram family pipeline and stop advertisi…
feat(sequence): participant logos through the shared icon contract (#380
feat(sequence): participant logos through the shared icon contract (#380
anandpant commentedon Oct 11, 2026
Done and verified in production. Sequence is a canonical family: one Effect Schema contract in diagram-core shared by generation, Code Mode, renderer, and CLI, with the duplicate shapes deleted (#374, #375); derived activation bars with lane assignment (#376); Studio chat sequence tool with shared turn budget and explicit-type routing (#377); maintained sequence evals scored on model output (#378); a family-pipeline test, generator update, docs/diagram-families.md, and CLI --type listing only supported families, with the generate API, wizard, and prompt derived from the registry (#379); participant logos through the shared icon contract (#380). Production check: /api/v1/generate sequence placed GitHub, Cloudflare, and PostgreSQL logos, drew 2 activation bars, and rendered correctly to PNG.