1 files changed, 40 insertions, 0 deletions
diff --git a/js/scripting-lang/TABLE_ENHANCEMENTS_MYSTERY.md b/js/scripting-lang/TABLE_ENHANCEMENTS_MYSTERY.md
new file mode 100644
index 0000000..5bfbdad
--- /dev/null
+++ b/js/scripting-lang/TABLE_ENHANCEMENTS_MYSTERY.md
@@ -0,0 +1,40 @@
+# 🕵️ Table Enhancements Mystery - Investigation Log
+
+## 📊 **Status**: DEFERRED (Strategic Decision)
+- **Current Progress**: 29/34 tests (85%)
+- **Test Status**: FAIL on assertion around line 81
+- **Decision**: Focus on other 4 failing tests first
+
+## 🔍 **Investigation Summary**
+
+**Symptoms**: 
+- Assertion failure: `..assert person.age = 30; /* Original unchanged */`
+- Test fails around line 81 in `tests/unit/17_table_enhancements.txt`
+
+**Verified Working Operations** ✅:
+- **t.set immutability**: ✅ `person.age: 30` (unchanged after `t.set`)
+- **t.delete immutability**: ✅ `person.age: 30` (unchanged after `t.delete`)
+- **t.merge functionality**: ✅ Correct merging with precedence
+- **t.length, t.has, t.get**: ✅ All return correct values
+- **map, each combinators**: ✅ Proper immutability maintained
+- **Individual assertions**: ✅ All pass when tested separately
+
+**Ruled Out Hypotheses** ❌:
+- ❌ **map mutation**: map function IS properly immutable
+- ❌ **t.set mutation**: t.set IS properly immutable  
+- ❌ **t.delete mutation**: t.delete IS properly immutable
+- ❌ **Operation bugs**: All operations work correctly in isolation
+
+**Remaining Mystery** 🤔:
+- **Context dependency**: Something in the full test sequence causes failure
+- **Variable reuse**: `person` variable used multiple times throughout test
+- **Cumulative effect**: Unknown interaction between operations
+
+## 🎯 **Strategic Decision**
+
+**Action**: Deferred investigation in favor of:
+1. Implementing missing table operations (`t.shape`, `t.append`, `t.prepend`)
+2. Fixing other 4 failing tests for quicker wins
+3. Returning to this mystery after achieving higher test coverage
+
+**Rationale**: All core functionality works correctly, suggesting this is likely a test-specific issue rather than a fundamental implementation problem.
\ No newline at end of file