source-plan-authoringlisted

# Retired: Source Plan Authoring `source-plan-authoring` no longer defines a separate handoff between the initial proposal and Long-Task execution. For an explicit long delivery, select `$long-task-workflow` in Codex (or use the host's Skill selector) with the initial/revised proposal, selected immutable design resources and other attachments. They enter the same `delivery-contract.yaml` Draft immediately; input inventory, Source-quality synthesis/refinement, stable semantic keys, Product Control-level UI meaning, acceptance scenarios, research/delegation traceability, real Source marking, repository binding and Contract mapping converge in one Goal before Preflight/Compile. Product Control projection does not cap selected design-resource granularity: the active workflow separately preserves every supported complete observable design fact through the handoff and Contract. Likewise, a paragraph/Requirement/current-code shape does not cap non-UI granularity: the active workflow inventories all material inputs, expands the standard plus custom product/business/backend/architecture domain families into exact subjects/relations/populations, conditions, atomic properties, semantic Facts and Fact×method obligations, persists one Source `semantic-fact-manifest-v1`, and requires exact Contract/current-Final-Gate closure without aggregate or sampled substitution. For non-long work, give the proposal and selected resources directly to the current native Goal under the default Workflo