You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Coverage result: 91% function coverage, 105/116 functions
42
+
43
+
## Manual Validation Steps
44
+
1. Open `/toolbox/input-mapping-v2/index.html`.
45
+
2. Confirm the Inspector column shows Devices and Status, with no Mapping JSON accordion.
46
+
3. Confirm Controls > Actions lists Cancel through Thrust alphabetically.
47
+
4. Confirm each action has a short creator-facing description beside it.
48
+
5. Add a mapping, capture a keyboard input, save, reload, and confirm the mapping remains.
49
+
6. Edit the mapping and confirm device-specific capture controls still appear for the selected device.
50
+
51
+
## Skipped Lanes
52
+
- Full samples validation was skipped as required by the PR instructions; this change is scoped to Controls/Input Mapping UI and targeted behavior tests.
53
+
- Full workspace contract lane was skipped because no Workspace V2 contract/runtime files changed; workspace return remains covered by targeted Controls Playwright.
54
+
55
+
## Runtime Scope Confirmation
56
+
- Controls remains Wireframe.
57
+
- Controls mapping and controller profile data remain persisted through the shared DB/mock adapter.
58
+
- No sample JSON alignment, auth behavior, production DB behavior, engine runtime behavior, or unrelated rewrites were added.
awaitexpect(page.locator("[data-input-state-explanation]")).toHaveText("State: Active means the mapping is available to the game. Disabled means the mapping is saved but ignored by the game until re-enabled.");
0 commit comments