feat(component-family): Spatial objects & durable views — object card, edges, groups, ports

[bntvllnt]

Goal

Create the spatial object and durable view family for the infinite canvas.

Minimum serious v0 ownership

• ObjectCard
• ConnectorEdge
• EdgeLabel
• GroupHull
• AnchorPort
• ObjectHandle

Why

The canvas should be built around durable AI/runtime objects, not anonymous dashboard widgets. This family turns runs, artifacts, agents, tasks, and outputs into first-class spatial objects.

Design direction

These components should emphasize:

• durable object views
• visible relationships
• compact but rich object state
• calm density instead of dashboard clutter

Explicit non-duplicates

This family must not duplicate or merely re-skin:

• existing Card variants (Card, StatCard, ProgressCard, SubscriptionCard, WalletCard, TutorialCard)
• FlowDiagram — generic flow primitive; this family is product-object-first, not node-editor-first
• timeline family issues (#32, #33, #34, #35, #63, #64) — time structures, not object relationships
• AI Artifact / Canvas issue #56 — artifact viewer remains its own component/problem; this family must compose with it rather than absorb it

Acceptance criteria

• define a product-object contract for cards, edges, handles, and groups
• define how objects expose live state, metadata, and action affordances
• define grouping and connection semantics for runs, artifacts, tasks, agents, and outputs
• keep the primitives reusable across AI, ops, analytics, and collaboration surfaces
• bias toward durable object views rather than generic canvas decorations