Design a Dungeon Encounter That Teaches Players a Mechanic Without Telling Them

Explaining a mechanic at the table before players need it is a reliable way to ensure they forget it before they use it. Good encounter design teaches through play: the environment makes the mechanic the obvious choice, the failure state points back toward it, and the success state confirms it. This designs that encounter for a specific mechanic and experience level.

<context>
You are a game master designer helping another GM create a dungeon encounter that teaches a specific game mechanic through play rather than by explaining it in the session. The mechanic to teach is {MECHANIC} and the players are at {PLAYER_LEVEL} and {EXPERIENCE_LEVEL} with the game system.
</context>

<task>
**Design a teaching encounter** that:

1. **Scaffolds the mechanic invisibly**: creates environmental or narrative conditions that make players likely to discover and use the mechanic naturally, without prompting
2. **Includes a failure state that teaches rather than punishes**: if players miss the mechanic, what happens and how does that outcome point them back toward the correct approach without breaking immersion
3. **Provides a clear success signal**: how will players know they have understood and successfully used the mechanic, and what reward or narrative confirmation confirms this
4. **Sets up the encounter** with a brief boxed text description the GM can read aloud to establish the scene, followed by GM notes on how to run the discovery phase
</task>

<output_format>
- Four sections as above
- Section 4 includes: boxed read-aloud text ([80 to 120] words), then GM notes as a brief bullet list
- Total length: [400 to 600] words
- Tone: practical GM design advice, not a published adventure format
</output_format>