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/`)
+This site has a production fork. All database changes must be documented for production sync.
-- ACF: price, address, beds/baths/sqft, gallery, documents, listing_agent
+
-- Taxonomies: `property_status` (Active/Pending/Sold), `property_type`, `property_location`
+**Schema changes** (new tables, columns, indexes): Use migration files in the MLS plugin (`wp-content/plugins/mls-by-hansonxyz/`).
-- Location dropdown only shows communities with active/pending properties
+
+**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

db_content_updates/README.md

@@ -0,0 +1,67 @@
+# Database Content Updates
+
+This directory contains documentation for all database content changes made in development that need to be applied to production.
+
+## When to Create a Document
+
+Create a document here whenever you make changes to:
+- WordPress options (`wp_options` table)
+- ACF field values (Theme Options, page fields, etc.)
+- Posts, pages, or custom post type content
+- Menus and menu items
+- Taxonomy terms
+- User meta or other wp_usermeta changes
+
+## Document Format
+
+**Filename**: `YYYY-MM-DD_HH-MM_short-description.md`
+
+Example: `2026-01-04_19-30_add-properties-page.md`
+
+**Required Sections**:
+
+```markdown
+# [Brief Title]
+
+**Date**: YYYY-MM-DD HH:MM
+**Author**: [Your name or "Claude"]
+
+## Summary
+One sentence describing what changed and why.
+
+## Changes Made
+
+### [Change 1 Title]
+**Type**: [option | acf_field | post | menu | term | other]
+**Table**: [wp_options | wp_postmeta | etc.]
+
+**WP-CLI Command(s)**:
+wp --allow-root [exact command here]
+
+**Or SQL**:
+[exact SQL here]
+
+**Values Set**:
+- field_name: "value"
+- another_field: 123
+
+### [Change 2 Title]
+...
+
+## Dependencies
+- List any changes that must be applied first
+- Or note "None" if standalone
+
+## Verification
+How to verify the change was applied correctly:
+- Check URL: /some-page/
+- Verify in admin: Settings > Theme Options > Tab Name
+```
+
+## Important Notes
+
+1. Be EXACT - copy/paste actual commands and values
+2. Include post IDs, option names, field keys - no ambiguity
+3. If order matters, number the steps
+4. Test your commands before documenting them
+5. Production team will execute these verbatim