- 已装运
- 2026年9月23日 14:33 UTC
- 作者
- Kamo
- 提交
- 75a41bc
An organization whose security model fixes every Compliance answer (no product a member may switch, one age range for each member type) was still counted against nine steps. It had to "save" an empty ninth step before its wizard latched as finished (reported 2026-09-21, Gnosia). OrgSetupStepApplicability decides which steps apply, from the applied model. Today only Compliance can drop out. The summary's steps, stepsCompleted and totalSteps, the completedAt latch and lastStep all run over that list. A step recorded before it stopped applying stays stored but isn't counted, so it comes back ticked if the model ever offers a choice there again. If the model can't be read, the step is shown: a shown step can be skipped, a hidden one can't be reached. The rule mirrors kamo-internal's getComplianceStepUi (what the step draws); both are pinned by the same case table. AppliedModelController now reads product policies and age ranges through the same helpers, so the endpoint and the rule can't drift apart.