Open Questions

Open Questions [OPEN]

The original architecture questions are resolved: instanced duel (Q1), FFA + PvE with hidden monsters (Q2), AI-resolved combat (Q3), generate-on-empty then ~90% reuse (Q4), Railway hosting (Q5), anonymous+nickname→OAuth (Q6), no status taxonomy (Q7), partial energy reset (Q8), vault-on-defeat (Q9). What's still open (blocks the next features — see docs/REQUIREMENTS.md §4):

1. Q10 — Run-loss penalty. Death currently loses the active team (vault safe); confirm or change.
2. Q11 — PvP design [RESOLVED]: interactive turns; AI-resolved with a deterministic engine fallback; triggered on contact and by landing a spirit chain (thrower gets first-turn initiative); winner loots the loser's active team. Live by default (PVP_ENABLED=false to disable). Open tuning: contact-trigger may be too forced vs chain-only — see design note.
3. Q12 — Disconnect/reconnect (blocks reconnection): grace period to resume a round, and whether abandoning counts as a death (anti-rage-quit).
4. Persistence is coded but inert until a Railway Postgres is provisioned + DATABASE_URL set; until then profiles reset on redeploy.