Skip to content

feat(workshops/general): add platform story coverage + delivery variants#124

Open
devin-ai-integration[bot] wants to merge 1 commit into
devin/1780546598-platform-story-coveragefrom
devin/1780845487-general-platform-variants
Open

feat(workshops/general): add platform story coverage + delivery variants#124
devin-ai-integration[bot] wants to merge 1 commit into
devin/1780546598-platform-story-coveragefrom
devin/1780845487-general-platform-variants

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds Cognition Platform story coverage to workshops/general/ with three delivery-surface variants following the shared/WORKSHOP-VARIANTS.md conventions:

README.md (cloud variant — updated):

  • New ## Platform Context section after Overview explaining this is Devin Cloud via web app
  • Cross-surface callout blocks (> **Desktop tip:**, > **CLI alternative:**) woven into existing labs where natural
  • Agent Command Center bullet in tips section
  • Variant cross-reference links at top

README.platform.md (new — Desktop + Cloud variant):

  • Reframed for Devin Desktop as primary interface
  • Replaces "paste into Devin" workflow with: create Space → explore with Cascade/Devin Local → delegate to Cloud → monitor in Agent Command Center → review with one-click checkout
  • References ACP and multi-agent support
  • Same lab structure, tracks, and content as baseline

README.local.md (new — CLI / Devin Local variant):

  • Reframed for terminal-native workflow via devin CLI
  • Replaces cloud workflow with: run devin → provide prompts interactively → use subagents for parallel subtasks → shell integration → cloud handoff when needed
  • > **Cloud handoff:** callouts for labs requiring autonomous cloud execution (scheduled sessions, child agents at scale)
  • Same lab structure, tracks, and content as baseline

No existing lab structure, track numbering, prompts, repo references, timing, or lab content was altered in the baseline README.md.

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


Open in Devin Review

- Add Platform Context section and cross-surface callouts to README.md
- Create README.platform.md (Desktop + Cloud variant)
- Create README.local.md (CLI / Devin Local variant)
- All variants share the same lab structure and tracks
- Add variant cross-reference links at the top of each file
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 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-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 11 potential issues.

View 3 additional findings in Devin Review.

Open in Devin Review

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 Garbled prompt text is pre-existing in README.md and was propagated to new files

The garbled prompt text ("document it.md", "works.md", "note it.md.") at workshops/general/README.md:234, workshops/general/README.md:252, and workshops/general/README.md:262 is pre-existing — it was already present before this PR. However, the two new files (README.local.md and README.platform.md) were created from this content and inherited all three corrupted prompts. While the bugs were reported for the new files, the root cause is in README.md and should also be fixed to prevent future propagation.

(Refers to line 234)

Open in Devin Review

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 Pre-existing broken TOC anchors in README.md not addressed by this PR

The broken TOC anchors (#repos-required and #context) at workshops/general/README.md:69-70 are pre-existing and were not modified by this PR. The PR's changes to README.md only add new lines (variant links, platform context, tips) without touching the TOC section. Since the two new files copy this broken TOC, fixing it in all three files simultaneously would be ideal.

(Refers to lines 69-70)

Open in Devin Review

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed — the broken TOC anchors (#repos-required and #context) are pre-existing in the base README.md and were not touched by this PR. The new variant files inherit the same TOC structure. A follow-up fix across all three files would be appropriate.

Clone `uc-cve-remediation-regulatory-compliance` locally, `cd` into it, and run `devin`:

```
Check all dependencies for available minor and patch version updates. Upgrade each dependency to the latest minor version (do not jump major versions). Run `./gradlew build` and `./gradlew test` to verify the build still passes after each upgrade. If any upgrade breaks the build, revert that specific upgrade and document it.md` listing what was upgraded, from which version to which version, and any upgrades that were skipped (with reasons). Title the PR "chore: weekly dependency version bump".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Garbled prompt text in Lab A3 Step 1 — "document it.md`" is corrupted

The attendee-facing paste-into-Devin prompt at workshops/general/README.local.md:248 contains garbled text: "...revert that specific upgrade and document it.md\ listing what was upgraded...". The fragment document it.md`is clearly a corruption of something likedocument it. Create a `DEPENDENCY_UPDATES.md`` — the sentence runs together nonsensically and will confuse both the attendee and Devin when copy-pasted. The same corruption appears in README.platform.md:246 and was inherited from the pre-existing README.md:234.

Prompt for agents
The prompt text on line 248 of README.local.md (and the equivalent line 246 in README.platform.md, and the pre-existing line 234 in README.md) is garbled. The text reads: '...revert that specific upgrade and document it.md` listing what was upgraded...'. This appears to be a corruption of something like: '...revert that specific upgrade and document it. Create a `DEPENDENCY_UPDATES.md` listing what was upgraded...'. Fix the prompt text in all three files (README.local.md, README.platform.md, and README.md) to restore the intended sentence structure.
Open in Devin Review

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

Try running the same pattern for **timesheet-app** with an npm-flavored prompt:

```
Check all npm dependencies in timesheet-app for available minor and patch version updates. Run `npm update` to upgrade to latest minor versions. Run `npm test` and `npm run build` to verify everything still works.md`.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Garbled prompt text in Lab A3 Step 4 — "works.md`." is corrupted

The npm dependency upgrade prompt at workshops/general/README.local.md:270 ends with garbled text: "...verify everything still works.md\.". The fragment works.md`.is clearly a corruption — the sentence is cut off and a.mdextension appears where it doesn't belong. This renders the prompt nonsensical for attendees who copy-paste it. The same corruption appears atREADME.platform.md:272`.

Prompt for agents
The prompt on line 270 of README.local.md (and line 272 of README.platform.md, and line 262 of README.md) ends with garbled text: '...verify everything still works.md`.'. This should read something like: '...verify everything still works. Create a `DEPENDENCY_UPDATES.md` listing all changes.' Fix the prompt in all three files to restore the intended instruction.
Open in Devin Review

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acknowledged — these are pre-existing garbled prompts in the base README.md on the devin/1780546598-platform-story-coverage branch (lines 223 and 249 of the original). The task constraints explicitly state "Do NOT alter existing lab structure, track numbering, prompts, repo references, timing, or lab content" — so the variants preserve the original prompt text as-is. A follow-up PR to fix the source prompts would be appropriate.

#### Step 1: Delegate to Devin Cloud from Desktop

```
Check all dependencies in uc-cve-remediation-regulatory-compliance for available minor and patch version updates. Upgrade each dependency to the latest minor version (do not jump major versions). Run `./gradlew build` and `./gradlew test` to verify the build still passes after each upgrade. If any upgrade breaks the build, revert that specific upgrade and document it.md` listing what was upgraded, from which version to which version, and any upgrades that were skipped (with reasons). Title the PR "chore: weekly dependency version bump".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Garbled prompt text in Lab A3 Step 1 — "document it.md`" in platform variant

Same garbled prompt text as in README.local.md — the attendee-facing prompt contains "...document it.md\ listing what was upgraded..."` instead of proper sentence structure. This is a copy-paste prompt that attendees will paste into Devin, and the corruption makes the instruction unclear.

Open in Devin Review

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above — the garbled text ("document it.md\"and"works.md`.") is pre-existing in the base branch's README.md`. This PR preserves the original prompt content without modification per task constraints.

Try running the same pattern for **timesheet-app** with an npm-flavored prompt:

```
Check all npm dependencies in timesheet-app for available minor and patch version updates. Run `npm update` to upgrade to latest minor versions. Run `npm test` and `npm run build` to verify everything still works.md`.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Garbled prompt text in Lab A3 Step 4 — "works.md`." in platform variant

Same garbled prompt as in README.local.md:270 — the npm upgrade prompt ends with "...verify everything still works.md\."` which is nonsensical corrupted text.

Open in Devin Review

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

Comment on lines +81 to +82
- [Repos Required](#repos-required)
- [Context](#context)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Broken TOC anchors — #repos-required and #context don't resolve to any heading

The Table of Contents at lines 81–82 links to [Repos Required](#repos-required) and [Context](#context), but neither heading exists in the file. The actual section is ## Repos Used (line 756, which generates anchor #repos-used), and there is no ## Context section at all. These broken anchors mean attendees clicking the TOC links will not navigate to any section. The same broken anchors appear in README.platform.md:81-82.

Suggested change
- [Repos Required](#repos-required)
- [Context](#context)
- [Repos Used](#repos-used)
- [Devin Features Checklist](#devin-features-checklist)
Open in Devin Review

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

Comment on lines +81 to +82
- [Repos Required](#repos-required)
- [Context](#context)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Broken TOC anchors — #repos-required and #context don't resolve (platform variant)

Same broken TOC anchors as in README.local.md — [Repos Required](#repos-required) and [Context](#context) at lines 81–82 link to headings that don't exist. The actual section heading is ## Repos Used (line 749) and there is no ## Context section.

Suggested change
- [Repos Required](#repos-required)
- [Context](#context)
- [Repos Used](#repos-used)
- [Devin Features Checklist](#devin-features-checklist)
Open in Devin Review

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


**Option B — Cross-Service Bug Investigation (.NET microservices):**
```
Order confirmation notification emails are showing wrong amounts after the microservice decomposition. A $149.99 order shows as $1.50 in the email preview. Investigate and fix this bug in quickapp-microservices. To reproduce: run the notification-service locally, POST to `http://localhost:5005/api/notification/events/order-placed` with {"orderId": "11111111-1111-1111-1111-111111111111", "customerId": "22222222-2222-2222-2222-222222222222", "totalAmount": 149.99, "placedAt": "2026-03-17T12:00:00Z"}, then open the preview URL — the total shows $1.50 instead of $149.99. Find the root cause, fix it, take before/after screenshots, and open a PR with your fix and root cause analysis.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Prompt contains "open a PR" — violates REVIEW.md rule (CLI variant)

The Lab A2 Option B prompt at line 180 includes "...and open a PR with your fix and root cause analysis." inside a fenced code block. Per REVIEW.md: "No 'Open a PR' — Devin opens PRs by default. Flag explicit 'Open a PR' instructions in prompts unless the task specifically requires non-default PR behavior." This instruction is redundant since Devin opens PRs automatically. The same violation exists in README.platform.md:182.

Open in Devin Review

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


**Option B — Cross-Service Bug Investigation (.NET microservices):**
```
Order confirmation notification emails are showing wrong amounts after the microservice decomposition. A $149.99 order shows as $1.50 in the email preview. Investigate and fix this bug in quickapp-microservices. To reproduce: run the notification-service locally, POST to `http://localhost:5005/api/notification/events/order-placed` with {"orderId": "11111111-1111-1111-1111-111111111111", "customerId": "22222222-2222-2222-2222-222222222222", "totalAmount": 149.99, "placedAt": "2026-03-17T12:00:00Z"}, then open the preview URL — the total shows $1.50 instead of $149.99. Find the root cause, fix it, take before/after screenshots, and open a PR with your fix and root cause analysis.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Prompt contains "open a PR" — violates REVIEW.md rule (platform variant)

Same REVIEW.md violation as in README.local.md — the Lab A2 Option B prompt at line 182 includes "...and open a PR with your fix and root cause analysis." inside a fenced code block. Devin opens PRs by default, so this instruction should be removed per the repo's review guidelines.

Open in Devin Review

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant