feat(web): Improve web run preview workflows

[machado144]

Summary

• add structured run result summaries for dry-run, generate, and export jobs
• add a full-screen tabbed output modal with overview, table-role, and SQL/output views
• redesign Workspace run controls and the Generate / AI Enrich / Export utility pages
• add graph edge routing controls for Straight, Smooth/bezier, and Step/orthogonal views
• improve Smooth/Step readability with deterministic route lanes and relationship colors while preserving neutral Straight mode

Verification

• node --check internal/web/static/app.js
• go test ./...
• make build

Security

• no dependency changes in go.mod or go.sum on this branch
• govulncheck reports existing findings from the current Go toolchain go1.24.6 and existing golang.org/x/net v0.25.0; these are not introduced by this PR, but should be fixed by upgrading the Go toolchain and x/net

Packaging

• UI remains embedded via Go embed and still builds into the single bin/seedstorm binary

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

StructLint — All checks passed

157 rules validated against .structlint.yaml. No violations found.

_{View full run · Powered by StructLint}

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change

[github-actions]

⚠️ Invalid PR Title

PR title must follow the Conventional Commits format since we use squash merge:

<type>[optional scope][!]: <description>

Allowed types: feat, fix, docs, style, refactor, test, chore, build, ci, perf, revert

Examples:

• feat: add new feature
• fix(seed): handle null FK gracefully
• feat!: breaking change