test

test header

The cause: reset never cleared the content. It only flipped taxonomy_pipeline status fields, leaving every generated_content and stat_sections row still is_active: true. So when you reset and reopened the generate page, my rehydration effect (which reads active=1 content) faithfully reloaded Stage 5's output — reset and rehydration were fighting, and rehydration won.

Deploy api_taxonomy_reset_route.ts → app/api/taxonomy/reset/route.ts. Now reset also deactivates both generated_content and stat_sections for the pipeline. After that, the rehydration query finds nothing active and correctly starts fresh — the two now work together instead of against each other.

On "can't delete generated content from the UI": the DELETE handler and UI button do real deletes, so it works at the DB level — what you were seeing was the same rehydration pulling content back because reset hadn't deactivated it. With this fix, reset gives you the clean slate. If you still see a specific row that won't delete after deploying this, tell me which delete button (there are a few — single content row, brief, full reset) and I'll trace that exact one, but the reset path is the one your description points at.

One note since it matters for testing: this fix is forward-acting. The content currently stuck active from before won't clear until you either run the new reset once, or manually deactivate the existing rows: