Align instability documentation with current runtime (#74)

docs/PORTING.md

@@ -5,6 +5,22 @@ The world-generation, dimension, registry, networking, and rendering APIs have
 changed substantially, so the work is divided into independently testable
 milestones.
 
+## Porting principles
+
+The primary goal is to reproduce verified Mystcraft Legacy behavior as closely
+as practical. Legacy source and the supplied 0.13.7.06 build are the behavioral
+reference for grammar, probabilities, ordering, defaults, visuals, and gameplay
+effects. A difference should be deliberate and documented rather than inferred
+from modern implementation convenience.
+
+Minecraft 1.21.1 has different world heights, registries, threading, networking,
+data-pack APIs, and server protection expectations. Where an exact port would be
+unsafe, technically impossible, or incompatible with current Minecraft,
+Rivencraft preserves the player-visible intent while using bounded modern
+mechanics. New features may extend Legacy when they fit Age writing and linking,
+but extensions must be identified separately from compatibility behavior and
+must not silently change existing saved Ages.
+
 ## Project tracking
 
 Gitea is the source of truth for project status:
@@ -42,7 +58,8 @@ acceptance issue and all required implementation issues are complete.
    TerraBlender and Serene Seasons integration. **Complete for the supported
    subset.** See the [acceptance record](MILESTONE_5_ACCEPTANCE.md) and
    [Legacy grammar audit](LEGACY_AGE_GRAMMAR_AUDIT.md).
-6. **Instability** — deterministic validation and server-safe effects. Start with the
+6. **Instability** — deterministic validation and server-safe effects. **In
+   progress.** Start with the
    [Legacy instability audit](LEGACY_INSTABILITY_AUDIT.md), which separates
    source behavior from proposed 1.21.1 safety limits.
 7. **Structures and polish** — libraries, crystals, portals, recipes, models,