Memory Wiki

I'll start by reading the mandatory documents and exploring the reference modules to understand patterns.

Let me continue reading the PB and explore the existing module patterns.

Let me examine the service implementations and tests to understand patterns better.

Let me check the remaining files - composer.json patterns, StripeService remaining lines, and existing test counts.

Let me check a few more reference files to fully understand the chassis patterns.

Let me check the existing build plans for reference format.

Let me now also check the `profe_orders` table schema and how the webhook_handler module routes are defined, to ensure proper references for billing_admin.

Let me check the T16 plan quickly for the RateLimiter context.

Now I have complete understanding of all patterns. Let me write both build plans.

Now let me write the T20 (Rate Limiter) build plan.

Both build plans are complete. Let me verify the files were created properly.

## Summary ### What I Did Created two comprehensive build plans for the remaining Module 3 (Billing) tasks: ### T19 — Billing Admin (`/root/.hermes/plans/task-t19-build-plan.md`, 953 lines) **Purpose:** Administrative API for billing operations — transaction history, subscription management, invoices view, webhook event history, dashboard summary. **Key design decisions:** - **No new tables** — reads from `profe_subscriptions`, `profe_orders`, `profe_webhook_events`, `profe_users` - **8 REST endpoints** under `/api/admin/billing/*` — GET endpoints use `checkAdminAccess()`, POST uses `checkAdminAccessWithCsrf()` (FAULT-004) - **6 injected dependencies** via constructor: `CoreUsersInterface`, `CsrfMiddlewareInterface`, `EventBusInterface`, `ConfigManagerInterface`, `StripeServiceInterface`, `OrderManagementInterface` (FAULT-008) - **Direct profe_users queries** documented with FAULT-002 workaround comments (UUID resolution) - **16 tests** specified across service, module, repository, and integration (FAULT-005/009) - **Event:** `profe/billing/subscription_cancelled_by_admin` ### T20 — Rate Limiter (`/root/.hermes/plans/task-t20-build-plan.md`, 1170 lines) **Purpose:** Redis-backed token bucket rate limiter for billing endpoints with DB fallback. **Key design decisions:** - **New table:** `profe_rate_limits` with PHP migration class (FAULT-006) - **Two-tier storage:** Redis INCR+EXPIRE (primary), `profe_rate_limits` table (fallback) - **Config-driven thresholds:** checkout (10/60s), admin (30/60s), webhook (200/60s), default (60/60s) - **Rate limit key format:** `rate:{ip}:{endpoint}` and `rate:{user_id}:{endpoint}` per PB spec - **Attached via `rest_pre_dispatch`** WordPress filter — middleware pattern, not per-route wrapper - **X-RateLimit-* headers** via `getHeaders()` method - **HTTP 429** response when rate limited - **3 injected dependencies** + optional `\Redis`: `ConfigManagerInterface`, `EventBusInterface`, `RateLimitRepository` (FAULT-008) - **16 tests** specified (FAULT-005/009) - **Event:** `profe/billing/rate_limited` ### Fault Compliance Verified for Both Plans | FAULT | Compliance | |-------|-----------| | FAULT-004 | ✅ CSRF on all POST/DELETE endpoints via `checkAdminAccessWithCsrf()` / `requireValidNonce()` | | FAULT-005/009 | ✅ ≥16 tests each (well above 12 minimum) | | FAULT-006 | ✅ T19: no new tables (no migration needed). T20: `CreateRateLimitsMigration.php` specified | | FAULT-002/007 | ✅ T19: direct profe_users queries documented with FAULT-002 workaround comments. T20: no profe_users queries needed | | FAULT-008 | ✅ All declared dependencies appear in constructor signatures; verified via reflection tests | | FAULT-01 | ✅ Factory closures capture `$c`, never store container | | FAULT-03 | ✅ Events follow `profe/{domain}/{action}` pattern | | FAULT-04/05 | ✅ Bare table names, prepared statements throughout |