# Next Session Prompt

Continue Conductor Slice 2: Visual Configuration from the latest `main` branch.

First read `CODEX.md`, `TASKS.md`, `MVP_SCOPE.md`, `SLICE2.md`, and `BASELINE.md`. Verify the current branch, working tree, recent commits, and relevant diffs before changing anything.

Completed and pushed work includes:

- Visual anonymous REST action creation, editing, duplication, and reference-aware deletion.
- Visual Button `onClick` action assignment with add/change/clear, no-action state, diagnostics, canonical synchronization, automated Preview execution coverage, and manual acceptance.
- Visual request-input authoring from existing component and variable values into executed REST URL, header, query, and body templates.
- `ComponentEvent.inputMap` is compatibility-only and must not be used by new UI.

Begin the next coherent vertical increment: visual response bindings and variable authoring.

Requirements:

- Create, edit, and delete canonical top-level `project.bindings` visually.
- Default new action-response bindings to `trigger: "onSuccess"`.
- Select an existing REST action response source and supported component or variable target.
- Preserve compatibility with legacy `onClick` response bindings without creating new ones.
- Do not use deprecated `action.responseMapping`.
- Add variable declaration/default-value editing with reference-aware diagnostics.
- Keep runtime values, loading state, responses, and errors ephemeral.
- Preserve anonymous-only REST configuration; authentication/secrets remain Slice 3.
- Leave page-load actions for the following Slice 2 increment unless a minimal supporting change is unavoidable.
- Add focused tests, update representative fixtures and durable state documents, and run the Node 20/npm 10 focused/full frontend tests, frontend build, backend build, schema matrix, and proportional manual workflow.
- Report the standalone TypeScript 4.9 / `@types/node` incompatibility separately from the passing CRA production compile.

Before implementing the next increment, complete or coordinate manual acceptance of the most recently completed request-input step:

1. Start Docker Desktop and run Conductor with Docker Compose; verify both services and the health endpoint.
2. Open or create a project containing a Text Input or Dropdown, a Button, and an anonymous REST action.
3. Edit the REST action in Actions & Bindings and add a query parameter named `item`.
4. In Request value reference, select the input component, select `Query: item`, and click Insert reference.
5. Inspect canonical JSON and confirm the query value immediately becomes `{{components.<componentName>.value}}`.
6. Confirm no `ComponentEvent.inputMap` data was added and path parameters are not offered as destinations.
7. Assign the action to the Button, enter or select a runtime value in Preview, and execute the Button.
8. Confirm the outgoing request contains the runtime component value and runtime loading, response, and error state do not leak into canonical JSON.
9. Confirm raw URL/header/query/body template editing still works after guided insertion.
10. If the project already declares a variable through JSON, repeat insertion with it and verify `{{variables.<name>}}` resolution.

Record manual acceptance separately from automated coverage in `CODEX.md`, `SLICE2.md`, and `BASELINE.md`. Do not mark it accepted without user confirmation.

Do not commit or push unless explicitly requested.