[Feat] Add DCG support for macOS x86_64

[zoomote]

Opened on behalf of Naved Merchant. View the task or mention @roomote for follow-up asks.

Related GitHub Issue

Closes: #N/A — internal request (DCG macOS x86_64 support gap)

Description

Adds Destructive Command Guard (DCG) support for macOS on Intel (x86_64). Previously getDcgArchiveInfo("darwin", "x64") returned undefined, so DCG was treated as an unsupported platform on Intel Macs and command guarding could not run there.

The change uses the existing DCG_ARCHIVES platform-mapping construct in src/services/destructive-command-guard/constants.ts:

• New darwin-x64 entry pointing at the upstream dcg-x86_64-apple-darwin.tar.xz asset from the pinned v0.7.7 release, with its SHA-256 checksum (15b42fbbbeab47123899e6328d90cd593e14999f3d275f71294815ad8ed9479c). The checksum was verified against the actual downloaded release archive.
• No logic changes: manager.ts resolves DCG_ARCHIVES[${platform}-${arch}], so darwin/x64 now resolves automatically through the existing download, checksum-verification, and extraction path.
• Updated the platform-mapping test in __tests__/manager.spec.ts to include darwin-x64 and assert the archive name mapping.

Test Procedure

• Updated src/services/destructive-command-guard/__tests__/manager.spec.ts platform-mapping test now covers darwin-x64 (getDcgArchiveInfo("darwin", "x64") → dcg-x86_64-apple-darwin.tar.xz).
• vitest run services/destructive-command-guard/__tests__/manager.spec.ts: 17 passed, 1 skipped.
• Full pnpm test (turbo, all 10 packages): all tasks successful.
• eslint --max-warnings=0 clean on changed files; pre-commit lint-staged + full turbo lint passed.
• The SHA-256 in the new entry was verified by downloading dcg-x86_64-apple-darwin.tar.xz from the pinned v0.7.7 GitHub release and running shasum -a 256.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Visual Snapshot (UI changes only): Not applicable — no UI change.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Visual Snapshots

Not applicable — no user-visible UI change.

Videos (interaction / animation only)

Not applicable.

Documentation Updates

• No documentation updates are required. The docs repository does not currently document DCG platform support, so there is nothing to update in Zoo-Code-Docs.
• Yes, documentation updates are required.

Additional Notes

None.

Get in Touch

Available via @roomote mentions on this PR for follow-up questions.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!