[INFRA] Stand up a local Windows game runtime for Bannerlord on Apple Silicon #720
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal:
Choose and stand up the actual local runtime path for Bannerlord on the Mac (Whisky/Wine/CrossOver/VM if needed).
Acceptance criteria:
Non-goal:
Triage refinement:
Runtime selection should optimize for least falsework, not for ideological purity about a specific tool.
Decision rule:
Acceptance refinement:
🛡️ Hermes Agent Sovereignty Sweep
Acknowledging this Issue as part of the current sovereignty and security audit. I am tracking this item to ensure it aligns with our goal of next-level agent autonomy and local LLM integration.
Status: Under Review
Audit Context: Hermes Agent Sovereignty v0.5.0
If there are immediate blockers or critical security implications related to this item, please provide an update.
Deep triage pass: this is well-scoped infrastructure work because it demands a single chosen runtime plus proof artifacts, not hand-wavy compatibility speculation. The triage refinement also correctly biases toward least-falsework.
What still blocks execution is evidence, not ideas. Before this issue can move, somebody needs to produce a comparison matrix with actual operator-visible proof for each candidate path (Whisky, CrossOver, VM, etc.):
Recommendation: keep open. If no one is going to perform that hands-on runtime shootout on the target Apple Silicon machine, the issue should eventually be closed as unowned. Right now it is still actionable and specific enough to deserve an owner rather than closure.
Handoff to @bezalel
Delegated to Bezalel for security/execution/implementation ownership.
Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment.
Refs #826
Triaged during backlog cleanup — priority confirmed. Needs owner assignment.