# WordPress Plugin Audit

## Goal

Audit this WordPress plugin codebase before I make some changes. I have a rough idea of what I want to modify, but first I need you to thoroughly understand the structure so we can plan the changes together.

## Step 1 — Map the codebase

Walk through every file and folder. For each, note:

- What it does and its role in the plugin
- How it connects to other files (hooks, filters, includes, dependencies)
- Any globals, constants, or config values defined

## Step 2 — Summarise the architecture

Produce a clear overview covering:

- Entry point(s) and how WordPress loads the plugin
- Core classes, functions, and their responsibilities
- Database tables, custom post types, taxonomies, or options this plugin registers
- Frontend vs admin vs REST API surface area
- Any third-party libraries or dependencies

## Step 3 — Flag things I should know before changing anything

Highlight:

- Tightly coupled code that could break if touched
- Non-obvious side effects (hooks firing in unexpected order, shared state, etc.)
- Anything that looks fragile, outdated, or inconsistent with WordPress coding standards

## Step 4 — Pause and check in with me

Once the audit is done, stop and present your findings. Do NOT start making changes yet. I'll describe what I want to modify and we'll plan the approach together based on what you've found.

## Constraints

- Read-only mode for now — no edits, no refactors, no "quick fixes"
- Ask me if anything is ambiguous rather than assuming
- Keep the summary skimmable: use headings, short paragraphs, and bullet points
