feat(workshops/otterworks): add platform story coverage + delivery variants

[devin-ai-integration]

Summary

Adds Cognition Platform story coverage to the OtterWorks workshop with two delivery variants.

README.md (cloud-agent baseline) — augmented with:

• ## Platform Context section after Overview explaining this is a Devin Cloud workshop via app.devin.ai, with a > **Tip:** callout pointing to Desktop and CLI alternatives
• Cross-surface callout blocks at natural points: Desktop tips for PR review (after A1, C1) and Agent Command Center (Track B intro, tips section), CLI alternative for the Getting Oriented exploration step
• Variant link at top: **Other variants:** [Desktop + Cloud](README.platform.md)

README.platform.md (Desktop + Cloud variant) — new file reframing the entire workshop for participants using Devin Desktop as primary interface:

• ## Desktop Workflow section replacing the web-app paste-prompt model with: create Space → explore locally with Cascade/Devin Local → delegate to Cloud → monitor in Agent Command Center → review with one-click checkout
• Each lab gains a **Desktop workflow:** block showing the local-explore → cloud-delegate → review-in-editor pattern
• ACP and multi-agent references where relevant
• Same lab structure, tracks, numbering, and content preserved throughout

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/f5563ca4953946b4bc9fd7ea8ee13032
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 1 new potential issue.

View 3 additional findings in Devin Review.

[devin-ai-integration]

🚩 Blockquote prompts in README.md Getting Oriented section remain inconsistent with new variant

The README.md "Getting Oriented" section (lines 107-119) uses blockquote format (> **"..."**) for paste-into-Devin prompts, while the new README.platform.md (lines 122-150) correctly uses fenced code blocks for the same prompts. The REVIEW.md rule states: "All paste-into-Devin prompts must use triple-backtick fenced code blocks so GitHub renders the copy button. Flag prompts in blockquote format." These violating lines are pre-existing and not within the diff hunks of this PR, so they can't be flagged as PR bugs. However, since the PR modifies this section (adds line 125) and creates a parallel variant that does it correctly, this creates an inconsistency between the two files that should ideally be fixed.

(Refers to lines 107-119)

---

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

[devin-ai-integration]

Acknowledged — this is a pre-existing format in README.md. The task constraints for this PR explicitly require not altering existing lab content ("Do NOT alter existing lab structure, track numbering, prompts, repo references, timing, or lab content"). The new README.platform.md uses fenced code blocks correctly. The README.md blockquote-to-fenced-code-block conversion could be addressed in a follow-up consistency pass.

[devin-ai-integration]

Based on review feedback from PR #128 (security demos), the following change is needed:

Replace "Devin API sessions" with Devin Automations

We now support Devin Automations as the trigger mechanism. In README.md line ~185 and README.platform.md line ~234:

• "Grafana alerts → webhook → auto-created incidents → Devin API sessions" → should reference Devin Automations as the trigger mechanism. The pattern is: you define what fires the automation (a webhook, a GitHub event, a schedule), and the automation kicks off a Devin session.

Example: "Grafana alerts → webhook → Devin Automation triggers a remediation session" or similar phrasing that uses Automations rather than raw API calls.

See the final state of PR #128 for reference on how these patterns were resolved.