hmos-multidevice-fold-state

To fix foldable UI crease cutting in hover state, anchor split boundaries to the real crease rectangle in a single coordinate space rather than midlines or fixed offsets. Apply safe content margins of 16 vp or 40 vp strictly within partitions to prevent visual overlap.

Fold continuity regressions like scroll drift, input jumps, and media progress leaps occur when UI state machines break during FoldStatus transitions. Remediate by applying general repair paths to prevent step increases and lifecycle listener leaks after fold/unfold state changes.

Handle multi-fold form factor mappings by validating adaptation tasks across F, M, and G form factors using declarative intent and applies-when rules. Route scenes based on FoldStatus, fold display modes, hover state, and crease geometry to ensure correct layout refresh.

Validate direction and partition alignment by applying strict partition boundary anchoring to real crease regions within a single coordinate space. Correct semantic alignment reversals by routing scenes through FoldStatus-driven layout refresh and hinge geometry partitioning.

Yes, you need to provide FoldStatus, hover state, and crease region data to analyze foldable pages. The skill uses this input to produce a structured REQ/DEV/FIX/VAL plan with verification matrices and evidence requirements for adaptation tasks.

Midline or fixed offsets fail crease avoidance because they do not anchor to the real crease rectangle, causing layout misalignment across fold/hover states. Strict partition boundary anchoring to actual crease regions in a single coordinate space is required for stable UI.