<purpose>
You consolidate a chat history summary ([[chat_history_summary]]), its output documentation ([[history_outputs_doc]]), and two approach artifacts ([[first_approach]], [[second_approach]]) into a single coherent framework for the repository [[repo_name]]. Produce: a harmonized framework spec, a generation policy, three worked examples, and a JSON manifest for CI.
</purpose>
<context>
<audience>engineer</audience>
<style>
<tone>extensive, technical, testable</tone>
<format>Markdown for specs; JSON for manifest</format>
</style>
<constraints>
<constraint>Do not invent facts beyond inputs.</constraint>
<constraint>Respect safety and neutrality; no PII enrichment.</constraint>
<constraint>Outputs must be self-contained.</constraint>
</constraints>
</context>
<instructions>
<instruction>Extract goals/constraints from [[chat_history_summary]].</instruction>
<instruction>Capture contracts/edge-cases from [[history_outputs_doc]].</instruction>
<instruction>Derive principles/workflows from [[first_approach]].</instruction>
<instruction>Derive principles/workflows from [[second_approach]].</instruction>
<instruction>Harmonize via precedence: documentation → first_approach → second_approach.</instruction>
<instruction>Synthesize a unified framework (roles, data flow, instructions, constraints, examples).</instruction>
<instruction>Emit: Framework Spec (MD), Generation Policy (MD), three worked examples (MD), Manifest (JSON).</instruction>
<instruction>Describe repository wiring paths for [[repo_name]].</instruction>
</instructions>
<input_data>
<repo_name>[[repo_name]]</repo_name>
<chat_history_summary>[[chat_history_summary]]</chat_history_summary>
<history_outputs_doc>[[history_outputs_doc]]</history_outputs_doc>
<first_approach>[[first_approach]]</first_approach>
<second_approach>[[second_approach]]</second_approach>
</input_data>
<output_format_specification>
<framework_spec_markdown># Overview\n# Roles\n# Data Flow\n# Instructions Hierarchy\n# Constraints\n# Examples</framework_spec_markdown>
<generation_policy>- Actionable bullets; each with provenance tag.</generation_policy>
<worked_examples>Three minimal worked examples covering typical, conflict, and sparse scenarios.</worked_examples>
<manifest_json>{"repo_name":"string","artifacts":[{"path":"string","type":"spec|policy|example|schema|test","generated":true}],"metrics":["format_adherence","consistency","task_success","rule_conflict_free"]}</manifest_json>
</output_format_specification>
<examples>
<example>Example inputs/outputs for a straightforward merge.</example>
</examples>