[Q4] Hive sharing model

[radical]

Decision needed.

~/.aspire/hives/ is shared across all 5 routes. PR installs add hives/pr-N/; release installs use the default ~/.aspire/hives/release/ (or equivalent).

Question

When winget binary runs aspire add while a PR script's hives/pr-12345/ exists from a previous PR install:

• Should winget see / use that hive? (today: yes, via shared NuGet.config; this is W35)
• Should the hive be route-scoped? Or just config-scoped (Q3 covers that part)?
• Who garbage-collects orphaned PR hives?

Options

1. Keep hives shared, fix only the channel/config layer (Q3 covers it).
2. Hives are route-scoped: hives/<route>/<id>/.
3. Hives stay shared but PR uninstall sweeps hives/pr-N/.

Lean

Option 1 + option 3 hybrid: hives stay shared (they're large and reusable), PR uninstall sweeps its own hive, and we rely on Q3 to fix the contamination at the config layer. This is the smallest delta. But validate against scenarios S4.1, S4.2 once Q3 is decided.

Connects to

• B4 — aspire uninstall surface
• S4.* in user-scenarios.md

---

Part of: #29

[radical]

Consolidated team-review post for Q3/Q4/Q6/Q7 with side-by-side trade-offs and recommended leans: #49