docs(23-04): complete admin phishing-automation page plan

- Adds 23-04-SUMMARY.md documenting Task 1 (page) and Task 2 (index tile)
- Records that Task 1's human-verify checkpoint was approved via a
  temporary production container rebuild rather than local npm run dev
This commit is contained in:
lorentz 2026-07-16 21:02:00 -04:00
parent 160fe88253
commit 7e33a8568b

View file

@ -0,0 +1,101 @@
---
phase: 23-classification-disposition-per-client-automation-gate
plan: 04
subsystem: ui
tags: [nextjs, react, shadcn, admin-page, phishing-automation]
# Dependency graph
requires:
- phase: 23-classification-disposition-per-client-automation-gate
provides: "Plan 03's phishing_automation_gate migration + admin GET/PATCH/DELETE API"
provides:
- /admin/phishing-automation page with searchable/filterable company table and three per-row Switch toggles (auto-parse, auto-classify, auto-report)
- /admin index tile linking to the new page
affects: [23-05-gated-webhook-chain]
# Tech tracking
tech-stack:
added: []
patterns: [per-stage toggle(company, stage, next) sending all three current flags on every PATCH, cloned from client-scope's single-toggle pattern]
key-files:
created:
- app/admin/phishing-automation/page.tsx
modified:
- app/admin/page.tsx
key-decisions:
- "Used the Bot lucide icon for the Phishing Automation tile (ShieldCheck was already claimed by the Roles tile) to keep icons visually distinct within the Tools & Data section"
- "Task 1's human-verify checkpoint was approved against a temporary rebuild of the production container rather than local `npm run dev`, per the user's own testing preference in this session — functionally equivalent verification of the same committed code"
patterns-established:
- "Per-stage toggle(company, stage, next) helper: PATCHes all three current boolean flags (two unchanged + one toggled) rather than supporting partial-field updates, matching the Plan 03 API's all-fields-required PATCH contract"
requirements-completed: [AUTOGATE-02]
# Metrics
duration: ~25min (across two sessions; Task 2 continuation session ~5min)
completed: 2026-07-16
---
# Phase 23 Plan 04: Admin Phishing-Automation Page + Index Tile Summary
**New `/admin/phishing-automation` page with a per-company table exposing three independent Switch toggles (auto-parse, auto-classify, auto-report), cloned from the `/admin/client-scope` structure, plus a discoverable tile on the `/admin` index.**
## Performance
- **Duration:** ~25 min total (Task 1 in prior session, Task 2 completed in this continuation session in ~5 min)
- **Completed:** 2026-07-16
- **Tasks:** 2 completed
- **Files modified:** 2 (1 created, 1 modified)
## Accomplishments
- `/admin/phishing-automation` page renders a searchable/filterable company table with three per-row `Switch` toggles wired to the Plan 03 API (GET on load, PATCH on toggle, all three flags sent together)
- Helper caption clarifies stage dependency (report meaningfully requires classify; classify requires parse) as informational guidance only — not enforced in the UI
- `/admin` index now has a "Phishing Automation" tile in the Tools & Data section, next to Client Scope, linking to the new page
- Human verification (Task 1 checkpoint) confirmed: table loads with three toggle columns all OFF by default, a toggle persists across reload via PATCH, and search/type filters work — tested against a temporary production container rebuild
## Task Commits
Each task was committed atomically:
1. **Task 1: Build /admin/phishing-automation page (3-toggle company table)** - `5dabaad` (feat) — completed in prior session; checkpoint approved
2. **Task 2: Add admin index tile for Phishing Automation** - `160fe88` (feat) — completed in this continuation session
_No TDD tasks in this plan — all tasks are `type="checkpoint:human-verify"` (Task 1) and `type="auto"` (Task 2)._
## Files Created/Modified
- `app/admin/phishing-automation/page.tsx` (266 lines) - `'use client'` page with `Company` interface (`autoParse`/`autoClassify`/`autoReport` booleans), `load()` GET fetch, per-stage `toggle(company, stage, next)` PATCH, search + company-type filter chrome, three `<Switch>` cells per row with `aria-label`s, `PageHeader` describing the opt-in gate and acknowledge_user auto-post behavior
- `app/admin/page.tsx` - Added `Bot` to the `lucide-react` import block; added a "Phishing Automation" tile object to the Tools & Data section's `tiles[]` array, immediately after "Client Scope"
## Decisions Made
- Chose the `Bot` icon (not `ShieldCheck`, already used by the Roles tile) for visual distinction within the same admin section
- Task 1's checkpoint verification was performed by the user against a temporary production container rebuild rather than `npm run dev` locally — same committed code, equivalent verification path; documented here since it deviates from the plan's literal `npm run dev` instruction
## Deviations from Plan
None - plan executed exactly as written (Task 1's checkpoint verification method was a user-driven substitution of environment, not a code deviation).
## Issues Encountered
None.
## User Setup Required
None - no external service configuration required.
## Next Phase Readiness
- The admin control surface for the per-company automation gate (D-08) is complete and reachable from `/admin`
- Plan 05 (gated webhook auto-pipeline) can now rely on admins having a UI to opt individual companies into auto-parse/auto-classify/auto-report
- `npx tsc --noEmit --pretty` exits 0
---
*Phase: 23-classification-disposition-per-client-automation-gate*
*Completed: 2026-07-16*
## Self-Check: PASSED
- FOUND: app/admin/phishing-automation/page.tsx
- FOUND: app/admin/page.tsx
- FOUND: commit 5dabaad (Task 1)
- FOUND: commit 160fe88 (Task 2)