Optional authoring-dependency slice

A named next authoring use needs a stable dependency account. The selected FPF edition is available and relevant now, so its fpfEdition position has exact value and kind refs and no acquisition condition. The next-use boundary names the Core claims needed for that authoring use. The accepted architecture answer is cited through its E.9 DRR because this use needs that rationale; it is not a mandatory PFAD dependency position. A publication carrier is missing but retained for later use, so its position has no value refs, has an acquisition-condition description, and does not block current pattern drafting. A missing source pack marked currentForNextAuthoringUse blocks the next use and opens the stated return. Availability never stands for relevance.