feat(demos/data-engineering): reorganize into use-cases/ + add general talk track with variants

[devin-ai-integration]

Summary

Reorganizes demos/data-engineering/ and adds a source/target-agnostic general migration demo talk track with Cloud and Desktop+Cloud variants.

Structure change:

demos/data-engineering/
├── general.md              # NEW — Cloud variant talk track
├── general.platform.md     # NEW — Desktop + Cloud variant
└── use-cases/
    ├── sas-to-databricks-demo.md   # moved from parent dir
    └── sybase-to-sqlserver-demo.md # moved from parent dir

general.md — Coarse-grained Cloud-only demo covering the universal migration pattern (orient → convert → verify → catch divergences → fan out). Includes source-agnostic prompts in fenced code blocks, verification loop mechanics, scaling via playbooks/child sessions, and links to the specific use-case demos.

general.platform.md — Same arc reframed for Desktop as primary interface: explore legacy estate in a Space, delegate conversions to Cloud, monitor child sessions in Agent Command Center Kanban, review migration PRs via one-click checkout.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/d9d5fd2d61b347fca38589df2c633eb0
Requested by: @bsmitches

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[devin-ai-integration]

Devin Review found 5 potential issues.

View 1 additional finding in Devin Review.

[devin-ai-integration]

🚩 Prompt specificity uses template placeholders intentionally

The prompts in both files use generic placeholders like <source-repo>, <target-platform>, <object-name> rather than concrete repo names and file paths. The AGENTS.md rule says "Prompts must include repo names, file paths, and expected output format." However, these are general methodology documents that explicitly link to specific worked examples (use-cases/sas-to-databricks-demo.md, use-cases/sybase-to-sqlserver-demo.md) at the bottom. The placeholders are intentional template syntax for a cross-platform guide, not vague prompts. The specific worked examples are expected to contain concrete paths.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🚩 Substantial preamble before first actionable prompt may tension with demos/AGENTS.md guidance

The demos/AGENTS.md says "Lead straight into the guide with prompts and user instructions. Keep preamble minimal — no long orientation before the first step." In general.md, the first actionable prompt doesn't appear until line 100, after ~67 lines of pattern explanation and verification loop description. In general.platform.md, the first prompt is at line 87. These are general methodology/overview documents rather than step-by-step demo walkthroughs, and they link to specific worked examples for the actual hands-on path. Whether they need to follow the "minimal preamble" rule as strictly as a concrete demo is a judgment call for the reviewer.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 1 new potential issue.

⚠️ 1 issue in files not directly in the diff

⚠️ Broken relative link after file rename — resolves to non-existent path (demos/data-engineering/use-cases/sas-to-databricks-demo.md:397)

The file demos/data-engineering/sas-to-databricks-demo.md was moved one directory deeper to demos/data-engineering/use-cases/sas-to-databricks-demo.md, but the relative link at line 397 (../../modules/data-engineering/sas-migration-analysis.md) was not updated. From the new location, ../../ resolves to demos/ (not the repo root), so the link points to the non-existent path demos/modules/data-engineering/sas-migration-analysis.md. The correct relative path should be ../../../modules/data-engineering/sas-migration-analysis.md.

View 2 additional findings in Devin Review.

[devin-ai-integration]

Fixed in 700bf2f — updated the relative link from ../../ to ../../../ to account for the extra directory depth after the move to use-cases/. Also confirmed the Sybase demo has no relative links that need updating.