Migrate task history and config reuse

[quinCode]

Migrate task history and config reuse

Parent

#2

What to build

Migrate task history, hide, restore, and reuse-config behavior into backend capability modules and React feature modules. The persistence shape should be owned by backend services, while React consumes typed UI application model responses.

This slice preserves existing task management behavior while improving module ownership.

Acceptance criteria

• UI backend exposes typed routes for task listing, hiding, restoring, and reuse-config retrieval.
• Backend services own task persistence and snapshot loading behavior.
• Running snapshots after server restart are handled consistently with existing behavior.
• React task history feature displays tasks and supports hide, restore, and reuse actions.
• Reuse-config responses omit or mark missing sensitive fields.
• Backend tests cover task snapshot loading, hide/restore rules, reuse availability, and sensitive field filtering.
• Frontend tests cover task list rendering, hidden/restored state, and reuse-config application.

Blocked by

• Migrate task progress, events, and cancellation #9