Stabilize backend adapter contracts and filter Tauri events by job

[blackopsrepl]

Summary

Define and normalize backend-facing contracts, with special attention to schedule creation and Tauri event handling.

Problem

createSolver() appears to assume schedule creation returns a raw job ID, and the Tauri event stream does not reliably filter against the requested job. Those assumptions create correctness risks in real integrations.

Scope

• Document the expected backend adapter contract shape
• Normalize schedule creation responses instead of relying on implicit raw values
• Filter Tauri events by the active job identifier
• Add tests for mismatched jobs, missing IDs, and malformed backend responses

Acceptance Criteria

• Backend adapter inputs and outputs are explicitly defined in code and docs
• Schedule creation handles structured responses predictably
• Tauri event listeners ignore events for unrelated jobs
• Integration tests cover happy path and contract mismatch scenarios

Notes

This issue should be resolved before promoting the adapter surface as stable.

[blackopsrepl]

Resolved by merged PR #22: https://github.com/SolverForge/solverforge-ui/pull/22\n\nWhat shipped:\n- responses are normalized to a stable string job-id contract\n- the Tauri event stream now filters by active job id without dropping id-less single-run updates\n- and related id fields are handled correctly\n- backend contract regression tests were added\n\nClosing this issue because the backend contract stabilization is merged on .

[blackopsrepl]

Resolved by merged PR #22: #22

What shipped:

• createSchedule responses are normalized to a stable string job-id contract
• the Tauri event stream now filters by active job id without dropping id-less single-run updates
• payload.data.id and related id fields are handled correctly
• backend contract regression tests were added

Closing this issue because the backend contract stabilization is merged on main.