`retaildevcrews` org retirement - decision needed by Thursday, Jun 11

The `retaildevcrews` GitHub organization is being retired and deleted on
Tuesday, 2026-06-30. This repo needs a decision before then.

cc admins: @kev-ms
cc heavy contributors: @AAkindele @kev-ms

Repo at a glance:

* Last push: 2024-03-20
* Open PRs: 0 / 26
* Open issues: 0 / 0
* Visibility: public
* Size: 821 KB

Default action if no one responds by Thursday, Jun 11: archive.
Rationale: Rule 2, stale for more than 12 months with no open PRs and no open
issues.

Your options:

1. Transfer to another org if these labs are still needed. GitHub's transfer
flow preserves history, issues, PRs, stars, and URL redirects.
2. Archive in place. History stays read-only until the org is deleted Tuesday, Jun 30.
Cloning and forking still work. New commits, PRs, and Actions stop.
3. Accept the default. No comment needed. We will proceed with archive on
Thursday, Jun 25 after a final notice posted on Thursday, Jun 18.

Destination guidance:

| Scenario | Destination |
|----------|-------------|
| Internal reusable asset or IP | `mcaps-microsoft` EMU |
| Public asset, partner/customer sharing | `microsoft` or `azure` |
| MS Learn code samples | `Azure-Samples` |
| Transitional, disposable, or hackathon | `gim-home` EMU |
| Confidential or customer-tented | Azure DevOps |

Timeline:

| Date | Milestone |
|------|-----------|
| Thursday, Jun 11 | Owner decision deadline |
| Thursday, Jun 18 | Default action posted here, with one final week to override |
| Thursday, Jun 25 | Transfers and archives executed; final sweep completed |
| Tuesday, Jun 30 | `retaildevcrews` org deleted |

Comment here with the decision or questions. I can help with the transfer if
archiving is not the right outcome.