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
46
+
47
+
## Manual Validation Steps
48
+
1. Open `/toolbox/input-mapping-v2/index.html`.
49
+
2. Confirm Controls > Actions shows only the Action Name / Description catalog.
50
+
3. Confirm the Mappings footer shows Action and Object dropdowns next to Add Mapping and Reset Mappings.
51
+
4. Add or seed an Object record and confirm it appears in the footer Object dropdown.
52
+
5. Choose an Action and Object in the footer, click Add Mapping, and confirm the edit row uses those defaults.
53
+
6. Capture an input, save, reload, and confirm the mapping persists.
54
+
55
+
## Skipped Lanes
56
+
- Full samples validation was skipped as required by the PR instructions; this change is scoped to Controls/Input Mapping UI and targeted behavior tests.
57
+
- Full workspace contract lane was skipped because no Workspace V2 contract/runtime files changed; workspace return remains covered by targeted Controls Playwright.
58
+
59
+
## Runtime Scope Confirmation
60
+
- Controls remains Wireframe.
61
+
- Controls mapping and controller profile data remain persisted through the shared DB/mock adapter.
62
+
- No sample JSON alignment, auth behavior, production DB behavior, engine runtime behavior, or unrelated rewrites were added.
0 commit comments