v16->v17

packages/transform/STATUS-16-17.md

@@ -1 +1,47 @@
-not started — see previous status docs for format style.
+# PostgreSQL 16-to-17 AST Transformer Status
+
+## Current Status: 98.8% Complete (255/258 tests passing)
+
+### Test Results (Confirmed: June 28, 2025)
+- **Total tests**: 258
+- **Passing**: 255 (98.8%)
+- **Failing**: 3 (1.2%)
+
+### Progress Summary
+- ✅ **Core transformer implementation**: Complete
+- ✅ **Basic AST node transformations**: Complete  
+- ✅ **Domain creation contexts**: Fixed
+- ✅ **SELECT statement contexts**: Fixed
+- ⚠️ **Complex nested contexts**: 3 remaining failures
+
+### Remaining Test Failures
+1. **pretty-misc.test.ts**: JSON TypeCast prefix handling
+   - Issue: Transformer adding pg_catalog prefix when expected output has none
+   - Context: WITH clauses containing A_Expr with JSON TypeCasts
+   - Status: Logic needs to be reversed - remove prefixes instead of adding them
+
+2. **misc-quotes_etc.test.ts**: String escaping issue
+   - Issue: \v character handling difference between PG16/PG17
+   - Expected: `\v` → Received: `v`
+   - Status: Likely parser-level difference, not transformer issue
+
+3. **latest-postgres-create_am.test.ts**: CREATE ACCESS METHOD syntax
+   - Issue: `syntax error at or near "DEFAULT"`
+   - Status: PG16 parser limitation - syntax not supported in PG16
+
+### Key Insights
+- **JSON prefix logic**: Test failures show expected output does NOT want pg_catalog prefixes
+- **String escaping**: PG16/PG17 parser difference in escape sequence handling
+- **CREATE ACCESS METHOD**: PG16 parser doesn't support this PG17 syntax feature
+
+### Technical Details
+- **Branch**: pg16-pg17-transformer
+- **PR**: #177 (https://github.com/launchql/pgsql-parser/pull/177)
+- **Last test run**: June 28, 2025 20:47 UTC
+- **Current approach**: Context-aware transformation based on parent node types
+
+### Next Steps to Achieve 100%
+1. **Remove JSON pg_catalog prefix logic entirely** from TypeCast method
+2. **Investigate String method** for \v character handling
+3. **Document CREATE ACCESS METHOD limitation** as expected PG16 parser constraint
+4. **Final test run** to confirm 258/258 success rate