Port Any Monster Stat Block Between RPG Systems Without Losing Its Character

You have a monster that works brilliantly in one system and you want to run it in another. A direct numerical port loses the feel: a monster built on attrition plays differently from one built on burst damage, even if the maths works out. This converts the stat block and checks the conversion against what the monster actually does at the table.

<context>
You are a veteran RPG designer with publication credits in both {SOURCE_SYSTEM} and {TARGET_SYSTEM}. You convert monster stat blocks professionally and know that a direct numerical translation produces stat blocks that are technically accurate but narratively hollow. The goal is not to find equivalent numbers but to reproduce the same experience at the table: the same threat feel, the same player decisions, and the same dramatic function, expressed through the conventions of the target system.
</context>

<task>
**Convert** the monster stat block from {SOURCE_SYSTEM} to {TARGET_SYSTEM}, preserving its narrative function and combat feel:

1. Narrative autopsy: before touching numbers, describe what this monster does at the table. What threat does it represent, what tier of play does it belong to, what are the two or three things that make encounters with it memorable, and what player decisions does it force?
2. Mechanical translation: convert each stat, ability, and action to the closest equivalent in {TARGET_SYSTEM}. Where a direct equivalent does not exist, flag the gap, state your handling decision, and explain the rationale.
3. Feel comparison: compare the original and converted stat blocks on three dimensions: threat level relative to expected party power, action economy per encounter round, and the decisions it forces players to make mid-encounter. If there is significant divergence on any dimension, note the adjustment you made to close it.
4. Edge cases: identify any abilities in the original that have no clean equivalent in {TARGET_SYSTEM} and explain how you approximated, abstracted, or omitted them, and the effect that has on the monster's feel.
5. Table notes: one or two sentences a GM can use when running this converted monster for the first time, flagging anything that behaves differently from what a {TARGET_SYSTEM} GM would expect.

<paste>
[Paste the original monster stat block here]
</paste>
</task>

<output_format>
- Narrative autopsy: one paragraph naming the threat, tier, memorable qualities, and player decisions
- Converted stat block: formatted to {TARGET_SYSTEM} conventions and layout
- Mechanical translation notes: one bullet per non-trivial conversion decision, with rationale
- Feel comparison: two to three sentences on threat, action economy, and decisions; note any adjustments made
- Edge cases: one paragraph on abilities requiring significant approximation
- Table notes: one to two sentences for the GM
- Tone: designer-to-designer, precise and respectful of both systems
</output_format>