---
phase: 07-testing-polish
plan: 03
type: execute
depends_on: []
files_modified: [.planning/phases/07-testing-polish/DEPLOYMENT-CHECKLIST.md]
---

<objective>
Verify admin moderation workflow functions correctly and create comprehensive deployment checklist for production readiness.

Purpose: Ensure admin can effectively moderate job submissions, manage listings, and that the system is ready for production deployment with all necessary configurations documented.
Output: Verified admin workflow, deployment checklist document, system ready for production.
</objective>

<execution_context>
~/.claude/get-shit-done/workflows/execute-plan.md
~/.claude/get-shit-done/references/checkpoints.md
./summary.md
</execution_context>

<context>
@.planning/PROJECT.md
@.planning/ROADMAP.md
@.planning/STATE.md

# Prior work being tested:
@.planning/phases/03-job-management-core/03-03-SUMMARY.md
@.planning/phases/03-job-management-core/03-04-SUMMARY.md
@.planning/phases/04-job-deactivation-system/04-02-SUMMARY.md
@.planning/phases/06-email-notifications/06-03-SUMMARY.md

**Tech stack being tested:** WordPress admin UI enhancements, custom columns, email notifications, Action Scheduler, moderation workflow
**Expected flows:** Admin receives notifications, reviews pending jobs, approves/rejects via status changes, sees enhanced columns
**Established patterns:** German admin UI, custom columns (submission date, location, type), sortable columns, admin-only hooks
**Deployment considerations:** Email configuration (WP Mail SMTP on production, disabled in Local WP dev), Action Scheduler, ACF fields, Formidable forms
</context>

<tasks>

<task type="checkpoint:human-verify" gate="blocking">
  <what-built>Admin moderation workflow with enhanced UI (Phase 3)</what-built>
  <how-to-verify>
    **Prerequisites:**
    - Logged in as admin
    - At least one pending job exists (from provider flow test in Plan 07-01)

    **Test Admin Job List UI:**
    1. Visit: /wp-admin/edit.php?post_type=job_offer
    2. Confirm: Custom columns display:
       - Eingereicht am (submission date)
       - Standort (location)
       - Art (job type)
    3. Confirm: Default "Author" and "Date" columns removed (cleaner interface)
    4. Click column headers to test sorting
    5. Confirm: All columns are sortable (including ACF fields)
    6. Confirm: German labels display correctly

    **Test Moderation Actions:**
    1. Find pending job in list
    2. Click job title to edit
    3. Review job details:
       - Title, description, location, type, contact email, logo
    4. Change post status from "Pending Review" to "Published"
    5. Click "Update" to save
    6. Confirm: Job status changes to published
    7. Confirm: Job now appears on public archive (/jobangebote/)

    **Test Rejection (Set to Draft):**
    1. Find another pending job
    2. Change status to "Draft"
    3. Update
    4. Confirm: Job remains in admin list but not on public archive
    5. Confirm: Provider can still see it in their dashboard (as draft)

    **Test Admin Email Notifications:**
    1. Review inbox for submission notifications (from Plan 07-01)
    2. Confirm: Email includes direct edit link
    3. Click edit link in email
    4. Confirm: Taken directly to job edit screen
    5. Review deactivation notification (from Plan 07-01)
    6. Confirm: Email includes deactivation reason
  </how-to-verify>
  <resume-signal>Type "approved" when admin moderation workflow works correctly, or describe issues</resume-signal>
</task>

<task type="checkpoint:human-verify" gate="blocking">
  <what-built>Action Scheduler and async email processing (Phase 6)</what-built>
  <how-to-verify>
    **Test Action Scheduler Status:**
    1. Visit: /wp-admin/tools.php?page=action-scheduler
    2. Confirm: Page loads without errors
    3. Review scheduled actions for group "email-notifications"
    4. Confirm: Mentor notification batches scheduled after job publish
    5. Check "Complete" tab
    6. Confirm: Email batch actions completed successfully
    7. Check "Failed" tab
    8. Confirm: No failed actions (or investigate failures if present)

    **Test Email Batch Logging:**
    1. Check error_log or debug.log for notification logs
    2. Search for "Scheduled X notification batches" (from job publish hook)
    3. Search for "Processed notification batch" (from batch processor)
    4. Confirm: Logs show expected behavior with counts
    5. Confirm: No PHP errors or warnings in logs

    **Test Rate Limiting:**
    1. If large mentor list exists (50+ opted-in users)
    2. Confirm: Batches processed in chunks of 50
    3. Confirm: No timeout errors
    4. If small list: Note that rate limiting works programmatically
  </how-to-verify>
  <resume-signal>Type "approved" when async processing works correctly, or describe issues</resume-signal>
</task>

<task type="auto">
  <name>Task 3: Create deployment readiness checklist</name>
  <files>.planning/phases/07-testing-polish/DEPLOYMENT-CHECKLIST.md</files>
  <action>Create comprehensive deployment checklist covering all system requirements for production. Include sections: (1) Server Requirements (PHP version, WordPress version, memory limit), (2) Required Plugins (ACF Pro, Formidable Forms + addons, Elementor Pro, WP Mail SMTP), (3) Plugin Configuration (ACF field groups, Formidable forms F1-F5, Elementor templates, notification opt-in), (4) Email Configuration (WP Mail SMTP setup for production, admin email verification, test notifications), (5) Access Control (verify /anbieter-login/ and /anbieter-dashboard/ pages exist, test redirects), (6) User Roles (ddhh_provider role exists, capabilities correct, test users), (7) Action Scheduler (verify cron running, check failed actions, monitor queue), (8) Testing Checklist (provider flow, mentor flow, admin flow - reference Phase 7 plans), (9) Security Checklist (HTTPS enabled, user enumeration blocked, file upload restrictions), (10) Performance (check query optimization, image optimization, caching if applicable), (11) Backup Strategy (pre-deployment backup, rollback plan), (12) Post-Deployment Verification (smoke tests, notification tests, form submissions). Use German labels where appropriate for consistency. Format as checklist with [ ] checkboxes for easy tracking.</action>
  <verify>cat .planning/phases/07-testing-polish/DEPLOYMENT-CHECKLIST.md shows comprehensive checklist with all sections and checkboxes</verify>
  <done>Deployment checklist created with all required sections, ready for production use</done>
</task>

</tasks>

<verification>
Before declaring plan complete:
- [ ] Admin can moderate jobs via status changes
- [ ] Enhanced admin columns display and sort correctly
- [ ] Admin receives all notification emails
- [ ] Action Scheduler processes email batches successfully
- [ ] No failed actions or errors in logs
- [ ] Deployment checklist created and comprehensive
</verification>

<success_criteria>

- Admin moderation workflow verified end-to-end
- All admin UI enhancements working correctly
- Email notification system functioning
- Action Scheduler stable and error-free
- Comprehensive deployment checklist created
- System ready for production deployment
- Phase 7 complete - all testing and polish work done
  </success_criteria>

<output>
After completion, create `.planning/phases/07-testing-polish/07-03-SUMMARY.md`:

# Phase 7 Plan 3: Admin Flow & Deployment Prep Summary

**[Substantive one-liner - what was tested and verified]**

## Test Results

- [Admin Moderation Workflow: PASS/FAIL with details]
- [Action Scheduler & Email Processing: PASS/FAIL with details]
- [Deployment Checklist: Created]

## Issues Found

[List any bugs, UX issues, or problems discovered, or "None"]

## Fixes Applied

[List any immediate fixes made during testing, or "None"]

## Deployment Readiness

- Server requirements documented
- Required plugins listed
- Configuration checklist created
- Security considerations noted
- Post-deployment verification plan ready

## Next Step

**Phase 7 complete.** All testing and polish work finished. System ready for production deployment following DEPLOYMENT-CHECKLIST.md. Project complete - all 7 phases done!
</output>