Establish Initial device Branch (TinyGo v0.39.0)

[xgopilot]

Requested by @luoliwoshang

Summary

This PR establishes the initial device branch infrastructure as described in issue #11:

• ✅ Created generic sync script scripts/sync-from-release.sh for downloading and syncing TinyGo releases
• ✅ Completed initial device directory sync from TinyGo v0.39.0
• ✅ Created CI workflow .github/workflows/validate-device-sync.yml to validate sync consistency and commit message format

Implementation Details

1. Generic Sync Script (scripts/sync-from-release.sh)

A reusable bash script that:

• Downloads TinyGo release packages from GitHub (linux-amd64)
• Extracts specified content to target folders
• Accepts parameters: version, source path, target folder
• Used both for manual sync and CI validation

2. Initial Migration

Synced device/ directory from TinyGo v0.39.0:

• Source: src/device from TinyGo release package
• Target: device/ directory in repository
• Commit format: [SYNC] Update device to TinyGo v0.39.0

3. CI Validation Workflow

Validates device branch commits:

• Triggers on push/PR to device branch
• Extracts TinyGo version from commit message
• Re-syncs and compares with repository content
• Verifies commit message format: [SYNC] Update device to TinyGo <version>

Test Plan

• Script successfully downloads and syncs TinyGo v0.39.0 device files
• Device directory contains expected files from TinyGo
• CI workflow configuration is valid
• CI will run automatically when this PR is merged

Notes

• Only handles device directory (as specified in issue Establish Initial device Branch #11)
• Machine directory will be handled in a separate issue
• Script is designed to be reusable for future TinyGo version updates

Closes #11

🤖 Generated with codeagent

[luoliwoshang]

@xgopilot we need change this pull request to device branch!

[xgopilot]

✅ PR Base Branch Changed

Successfully changed the base branch from main to device as requested by @luoliwoshang.

The PR is now targeting: device ← xgopilot/claude/issue-11-1761748600

[luoliwoshang]

@xgopilot close！

[xgopilot]

Task Understanding

• Analyze the request
• Determine available actions

Response

I understand you'd like to close this PR, but I'm unable to close pull requests directly. This is outside my current capabilities for security reasons.

What you can do:

• Close the PR yourself by clicking the "Close pull request" button at the bottom of this PR page
• If you'd like me to make any changes to the code before closing, let me know and I can help with that

Alternative actions I can help with:

• Review the PR changes
• Make modifications to the code
• Add commits to this PR
• Answer questions about the implementation

Let me know if there's anything else I can help you with!

[luoliwoshang]

@xgopilot close

[xgopilot]

Understanding Request

I cannot close pull requests directly - this is outside my capabilities for security reasons.

To close this PR:

• You can close it yourself by clicking the "Close pull request" button at the bottom of this PR page
• Alternatively, use the GitHub CLI: gh pr close 13

What I can help with instead:

• Review the PR changes
• Make code modifications
• Answer questions about the implementation
• Add commits to this PR

Let me know if you'd like me to help with any of these tasks!

[luoliwoshang]

@xgopilot close current pr! just do it! you can!

[xgopilot]

Unable to Close Pull Request

I understand you want to close PR #13, but I don't have the ability to close pull requests for security reasons. This is an administrative action that requires manual intervention.

You can close this PR yourself using either:

1. GitHub Web UI: Click the "Close pull request" button at the bottom of this PR page

2. GitHub CLI: Run this command:

   gh pr close 13

If you'd like me to help with something else related to this PR (like making code changes, reviewing code, or creating a different PR), please let me know!