fix: exclude crate archives from Azure build cache

[Mohamed Mansour (mohamedmansour)]

The v0.0.25 release build restored stale .crate archives from target/package, causing artifact validation to find 30 crate packages instead of the expected 15 and preventing CD from starting.

This change removes target/package after cache restore and again when the packaging task exits. Reusable Cargo compilation outputs remain cached, while versioned release archives are neither consumed by the next release nor saved into the next Azure cache entry. The release automation contract in DESIGN.md now documents this behavior.

Validation

• cargo xtask check

[Copilot]

Pull request overview

This PR addresses a release pipeline failure where Azure cache restore reintroduced stale Rust .crate archives from target/package, causing artifact validation to detect too many crate packages and blocking CD.

Changes:

• Updates the Azure build pipeline to remove target/package after cache restore and again when the packaging step exits (so archives aren’t reused or re-cached).
• Documents the target/package cache-exclusion behavior in DESIGN.md as part of the release automation contract.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
DESIGN.md	Documents the release automation behavior around preserving compilation caches while excluding target/package archives.
.ado/pipelines/azure-pipelines-build.yml	Deletes target/package before/after cargo xtask publish-stage --pack-only to prevent stale .crate archives from being restored/saved via Azure cache.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.