创作提示词：按合同 Goal 动态生成与组合内容

Structure、Paragraph、ElementSet 只实现合同声明的 goal_ids，Compare 按 Goal 并集比较，Compose 不得伪造 Host 派生覆盖，Portfolio 要求全部 Goal 闭合。

统一把 constraints 视为硬标准、preferences 视为可说明的权衡，并移除固定 4–5 段和 internal E2E 描述。

script_build_host/src/script_build_host/agents/prompts/comparison_worker.md

@@ -6,3 +6,5 @@ pinned artifact_ref exactly once with a concrete reason. recommendation must
 be the immutable artifact URI selected by the comparison. Do not rewrite,
 merge, rank by completion time, or fetch a latest candidate. The Planner alone
 decides which result is adopted, replaced, held, or rejected.
+Compare the union in `goal_ids`, reject constraint violations, and report
+preference trade-offs without treating every unmet preference as a hard failure.

script_build_host/src/script_build_host/agents/prompts/compose_worker.md

@@ -5,6 +5,8 @@ complete script in this Attempt workspace, close Paragraph/Element/Link
 references, freeze one StructuredScriptArtifactV1, and submit it. If a real
 gap remains, report it through validation; never insert a placeholder or read
 a superseded or unadopted URI.
+Cover every Direction Goal in the contract. GoalCoverage is derived by the Host
+from adopted creative artifacts; never submit or invent it.
 
 Call `read_active_frontier` once, verify it matches the contract closure and
 order, then call `save_structured_script_candidate` with bounded acceptance

script_build_host/src/script_build_host/agents/prompts/element_set_worker.md

@@ -3,3 +3,5 @@ scope. Elements may be explored before Paragraphs, but every adopted Element
 must eventually map to an adopted Paragraph or scope; leave unplaced items for
 Planner disposition. Use only accepted inputs and this Attempt workspace.
 Freeze one Artifact and submit it without reading or mutating another branch.
+Implement only the contract's `goal_ids`; constraints are hard and preferences
+are optional trade-offs.

script_build_host/src/script_build_host/agents/prompts/paragraph_worker.md

@@ -3,6 +3,8 @@ scope in this Task contract. A Paragraph may be explored before a Structure,
 but it is not formally adopted until an accepted Structure covers or absorbs
 its scope. Use only accepted inputs and the current Attempt workspace. Freeze
 one Artifact and submit it; never read or overwrite another Attempt branch.
+Implement only the contract's `goal_ids`. Constraints are mandatory;
+preferences guide choices but are not automatic rejection conditions.
 
 Call `load_frozen_strategy` only with an exact `script-build://strategies/...`
 reference copied from `read_input_snapshot.strategies` where `mode` is

script_build_host/src/script_build_host/agents/prompts/portfolio_worker.md

@@ -4,6 +4,8 @@ StructuredScript and explicitly classify every candidate and Decision as
 adopted, superseded, held, or rejected. Freeze one CandidatePortfolioArtifactV1.
 Do not rewrite script content, retain hard or critical unresolved defects, or
 publish a final script.
+Require exact all-Goal coverage in the adopted StructuredScript. Constraints
+block acceptance; preferences are recorded as trade-offs.
 
 Call `read_pinned_candidates` once, then `save_candidate_portfolio` using the
 exact adopted, held/rejected, and compose-order Decision IDs frozen in the

script_build_host/src/script_build_host/agents/prompts/structure_worker.md

@@ -9,11 +9,12 @@ reference copied from `read_input_snapshot.strategies` where `mode` is
 `on_demand`. If no such exact reference is present, do not call the tool; never
 derive a strategy reference from a name, description, or the Task objective.
 
-For the full-script Structure used by the internal E2E, call
-`read_accepted_input_bundle` once, then call `create_script_paragraphs` once for all
-parent-linked Paragraph shells. Use `client_key` and `parent_client_key`; use
-`create_script_paragraph` only for a later isolated repair. Create each
-structural paragraph (normally 4-5) with consecutive
+Implement only the contract's `goal_ids`; treat Direction constraints as hard
+requirements and preferences as trade-offs. Call `read_accepted_input_bundle`
+once, then prefer one `create_script_paragraphs` call for all parent-linked
+Paragraph shells. Use `client_key` and `parent_client_key`; use
+`create_script_paragraph` only for a later isolated repair. Create each needed
+structural paragraph with consecutive
 `paragraph_index`, a stable name, a concrete `content_range`, and bounded
 theme/form/function/feeling element arrays. Every `client_key` must be nonblank;
 inside each one of those four arrays, every `维度` value must be unique;