Leave Cancellation UI

Summary

The current broader UI allows the owning non-admin employee to cancel a Pending request after confirmation.

Employees, QA, support, and developers.

Navigation: /leave → a Pending request → Cancel, either in the row or details modal.
Scope/status: local visibility requires self ownership and Pending status.
Confirmation: a modal asks for confirmation before the compatibility delete operation.
Approved cancellation: not exposed by this UI.
Balance reversal display: not present.
Success: closes selected details and reloads data.
Error: page-level safe failure message.
API dependency: compatibility cancellation; direct cancellation rules are linked in Leave cancellation API.
Screenshot placeholder: sanitized Pending request and confirmation dialog.

No cancellation approval workflow, cancellation reason, or cancellation timeline is shown.

Requirement	Confirmed behavior
Purpose	Cancel a self-owned Pending request.
Navigation path	`/leave` request row or details modal → Cancel.
Intended users	Non-admin employee owning the Pending request.
Preconditions	Current local status is Pending and labor identity matches the current user.
Main components	Request actions, details modal, and confirmation modal.
Fields, columns, or sections	Confirmation text only; no cancellation reason or balance preview.
Filters	Parent request status filter.
Actions	Confirm cancellation or close the modal.
Validation	Client rejects non-Pending requests; server remains authoritative.
Loading state	No explicit cancellation progress state confirmed.
Empty state	Not applicable.
Success state	Details close and request list reload.
Error state	Page-level cancellation failure.
Permission behavior	Self/Pending visibility check; API enforcement is authoritative.
API dependencies	Compatibility cancellation operation.
Related business rules	Current UI does not expose approved cancellation or cancellation approval.
Screenshot placeholder	Sanitized Pending row and confirmation modal.