ci: add timeout-minutes to devcontainer job

[devsy-app]

Problem

The build job in .github/workflows/devcontainer.yml had no timeout-minutes set. A hung devcontainer build (e.g. a stalled devcontainer build/image pull) would run indefinitely against the GitHub Actions default 6-hour ceiling, wasting CI minutes and blocking the workflow until it is manually cancelled.

Change

Add an explicit timeout-minutes: 15 to the build job:

jobs:
  build:
    name: Build and Run Devcontainer
    runs-on: ubuntu-latest
    timeout-minutes: 15

This is a safety guard only - successful runs complete well within the limit, so there is no behavior change for the normal path.

Runs inspected

Recent devcontainer.yml workflow runs were surveyed via gh run list --repo devsy-org/devsy. No individual run id is cited because the fix is a preventive guard for the absent-timeout-minutes class of issue rather than a response to one specific failure.

Validation

• python3 -c "import yaml; yaml.safe_load(open('.github/workflows/devcontainer.yml'))" -> YAML OK
• act / docker unavailable in this sandbox, so local act --list validation was skipped (the change is a single top-level job key, validated by YAML parse).
• Open PRs reviewed (ci: add timeout-minutes to release jobs #1070, ci: add timeout-minutes to desktop-ci jobs #1054, fix: remove orphaned non-compliant feature fixture #1047, ci: bump act.yml artifact actions v5 to v7/v8 #1022) - none address this.

This PR was created by an AI agent as part of an automated daily CI optimization job.

[netlify]

✅ Deploy Preview for devsydev canceled.

Name	Link
🔨 Latest commit	eef7419
🔍 Latest deploy log	https://app.netlify.com/projects/devsydev/deploys/6a82d4aa6a5a1800086838a2

[netlify]

✅ Deploy Preview for images-devsy-sh canceled.

Name	Link
🔨 Latest commit	eef7419
🔍 Latest deploy log	https://app.netlify.com/projects/images-devsy-sh/deploys/6a82d4aa9dd7c00008942821

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}