Add Resolved/Unresolved toggle button for Concept Manager Worklists

[filiperochalopes]

User story

As a CIEL curator working through a Worklist, I want to explicitly mark whether an edited item has been resolved so that saving a concept can also update its Worklist status.

Use case

When a concept is opened from an Internal Data/Worklist item, add a Resolved / Unresolved toggle button between Cancel and Save Concept.

The component should follow the checkbox-button pattern shown in the reference, using the primary button style when Resolved and the secondary button style when Unresolved.

Requirements

• Create a reusable checkbox-button toggle component.
• Add the component between Cancel and Save Concept when Concept Manager is opened from an Internal Data/Worklist item.
• Do not display it when Concept Manager is opened outside a Worklist context.
• Support two states:
  • Unresolved: unchecked and secondary button style.
  • Resolved: checked and primary/blue button style.
• When the concept form becomes dirty, automatically change the state to Resolved.
• Allow the curator to manually change it back to Unresolved after editing.
• Do not automatically switch it back to Resolved unless another form change occurs.
• When saving with Resolved, save the concept changes and move/update the Worklist item to the Resolved state/list.
• When saving with Unresolved, save the concept changes without resolving the Worklist item.

Acceptance criteria

• The toggle is displayed only when editing a concept associated with a Worklist item.
• Changing the form automatically selects Resolved.
• The curator can manually select Unresolved even when the form is dirty.
• Saving as Resolved marks the corresponding Worklist item as resolved.
• Saving as Unresolved keeps the corresponding Worklist item unresolved.
• The Worklist status is updated only when Save Concept is executed successfully.

[ocl-automation]

Automated Triage — 2026-09-07

Dimension	Score
Complexity	2
Scope	2
Clarity	3
Dependency	1
Risk	2

Decision: decision/human-review
Type: type/feature
Signals: signal/low-risk, signal/small-scope

Straightforward UI component addition with clear user story and specific placement requirements. Affects concept editor and worklist components but follows existing patterns. Missing some implementation details like state management and API integration.

---

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-4 (openrouter).

[filiperochalopes]

/uat @askanter