M007 S03: Gambit auto-activation when behind on resources not implemented #9

New issue

Closed

opened 2026-05-15 19:19:51 +00:00 by Mark · 1 comment

Mark commented

2026-05-15 19:19:51 +00:00

Owner

Severity: LOW
File: src/pages/CasualDuel.tsx

Problem

Gambits are defined with costs and rewards, and players can browse and manually activate them. However, the spec requires that gambits can optionally auto-activate or prompt when the player is behind on resources (e.g. vitality below 30). This auto-prompt behavior is not implemented.

Fix

Add a hook in CasualDuel that checks after each turn: if the player has saved gambits and vitality is below a threshold (e.g. 30), show a non-blocking prompt: "Critical health — Gambit available: [name]" with a single-tap to activate. Do not force activation.

**Severity:** LOW **File:** src/pages/CasualDuel.tsx ## Problem Gambits are defined with costs and rewards, and players can browse and manually activate them. However, the spec requires that gambits can optionally auto-activate or prompt when the player is behind on resources (e.g. vitality below 30). This auto-prompt behavior is not implemented. ## Fix Add a hook in CasualDuel that checks after each turn: if the player has saved gambits and vitality is below a threshold (e.g. 30), show a non-blocking prompt: "Critical health — Gambit available: [name]" with a single-tap to activate. Do not force activation.

Mark added the

blocked:needs-decision

label

2026-05-15 19:20:11 +00:00

Mark commented

2026-05-15 22:06:58 +00:00

Author

Owner

GSD RESEARCH could not determine a clear fix.

STATUS: UNCLEAR

EVIDENCE:
After reading CasualDuel.tsx (1350 lines) and src/data/openings.ts in full:

The Opening type (openings.ts) defines gambitCost and gambitReward fields but has NO autoActivate, autoPrompt, or threshold field of any kind. There is no way to express "this gambit should auto-activate when the player is behind on resources."
The current gambit activation flow in CasualDuel.tsx is purely manual:
- handleActivateOpening (line 464): shows a confirmation o

GSD RESEARCH could not determine a clear fix. STATUS: UNCLEAR EVIDENCE: After reading CasualDuel.tsx (1350 lines) and src/data/openings.ts in full: 1. The `Opening` type (openings.ts) defines `gambitCost` and `gambitReward` fields but has NO `autoActivate`, `autoPrompt`, or threshold field of any kind. There is no way to express "this gambit should auto-activate when the player is behind on resources." 2. The current gambit activation flow in CasualDuel.tsx is purely manual: - `handleActivateOpening` (line 464): shows a confirmation o

Mark referenced this issue from a commit

2026-05-16 16:01:24 +00:00

fix: resolve all open M007 issues

Mark closed this issue

2026-05-16 17:23:30 +00:00