fix(movement): invalidate burden on enchantment changes

docs/plans/2026-04-11-roadmap.md

@@ -53,7 +53,11 @@ TS-8 are retired by focused and end-to-end packet tests. #269's
 capture-driven slope-slide residual is also closed and user-accepted:
 `CTransition::validate_transition` now performs retail's non-OK-only
 remembered-plane restore with the preceding `OBJECTINFO::kill_velocity`.
-Campaign P now continues with the unfinished live matrix rows.
+The matrix then exposed #272: burden was invalidated by base Strength but not
+by Strength enchantment add/purge. Runtime movement plus both retained burden
+surfaces now use effective Strength and the canonical enchantment-change edge;
+automated gates pass and the connected buff/death gate was user-accepted on
+2026-07-31. Campaign P then continues with the unfinished live matrix rows.
 
 ---
 

docs/plans/2026-07-29-physics-parity-campaign.md

@@ -400,6 +400,14 @@ root-caused, retail-ported, and user-accepted in the same session:
   and the complete Release suite passes 10,062 tests / 5 skips. The user
   accepted repeated uphill runs while pressing into the stair sides. Evidence:
   `docs/research/2026-07-31-271-stair-side-slide-capture.md`.
+- **#272 complete and user-accepted 2026-07-31** —
+  `CACQualities::InqLoad` consumes enchantment-adjusted Strength through
+  `InqAttribute`, but Runtime movement and both retained burden displays read
+  raw Strength and did not share the enchantment invalidation edge. They now
+  consume `GetEffectiveAttribute(Strength)` and
+  `Spellbook.EnchantmentsChanged`, so buff, dispel, expiration, and death
+  purge recompute the same burden state immediately. Focused and full
+  Runtime/App tests pass.
 
 Matrix rows accepted so far: speed parity, roof slide, downhill bounce,
 flat pop, uphill landing, and #269's slope-stop feel