Add db_content_updates directory for production sync

- Create db_content_updates/ for documenting database changes
- Add README with required document format and template
- Update CLAUDE.md with mandatory documentation requirement
- All content changes must be documented for production team

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CLAUDE.md

@@ -37,12 +37,24 @@ npm run build
 Access via `homeproz_get_option('key')`:
 - `phone`, `email`, `address`, `facebook`, `tiktok`
 
-## Custom Post Types
+## Database Content Changes (MANDATORY)
 
-### Property (`/properties/`)
-- ACF: price, address, beds/baths/sqft, gallery, documents, listing_agent
-- Taxonomies: `property_status` (Active/Pending/Sold), `property_type`, `property_location`
-- Location dropdown only shows communities with active/pending properties
+This site has a production fork. All database changes must be documented for production sync.
+
+**Schema changes** (new tables, columns, indexes): Use migration files in the MLS plugin (`wp-content/plugins/mls-by-hansonxyz/`).
+
+**Content changes** (options, ACF fields, posts, menus, terms): Create a timestamped document in `db_content_updates/` with:
+- Filename: `YYYY-MM-DD_HH-MM_description.md`
+- What was changed (exact field names, option keys, post IDs)
+- The exact values set (copy/paste the WP-CLI commands or SQL)
+- Why it was changed
+- Any dependencies or order of operations
+
+Example: `2026-01-04_19-30_add-footer-menu.md`
+
+**DO NOT** make database content changes without creating the corresponding document. The production team relies on these files to sync changes.
+
+## Custom Post Types
 
 ### Agent (`/agents/`)
 - ACF: phone, email, bio, gallery, social links, order, disabled toggle