⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

Grove账户删除指南：使用Wrangler CLI安全删除租户及关联数据

grove-account-deletion by autumnsgrove/groveengine

62 周安装量

2 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/autumnsgrove/groveengine --skill grove-account-deletion

云服务开发运维数据处理

🇨🇳中文介绍

Grove 账户删除

使用 wrangler CLI 命令安全地从 Grove 平台删除租户账户及其所有关联数据。

何时激活

用户提及类似"删除 Alice 的账户"或"Alice 已完成"的内容
用户提到想要移除测试账户
用户要求在演练或演示后进行清理
用户显式调用 /grove-account-deletion
用户说"清除那个账户"或"擦除他们的数据"

操作流程

识别 → 验证 → 快照 → 删除租户 → 清理孤立数据 → 清除 R2 → 验证

步骤 1: 识别租户

用户将提供用户名（子域名）、电子邮件或显示名称。请查找他们：

# 通过用户名/子域名（最常见）
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain, display_name, email, plan, created_at FROM tenants WHERE subdomain = 'USERNAME';"

# 通过电子邮件（如果用户名未知）
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain, display_name, email, plan, created_at FROM tenants WHERE email = 'EMAIL';"

# 通过显示名称（模糊匹配）
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain, display_name, email, plan, created_at FROM tenants WHERE display_name LIKE '%NAME%';"

()。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

步骤 2: 与用户确认

在删除任何内容之前，向用户展示您找到的信息并要求明确确认：

Found tenant:
  ID:       abc-123-def
  Username: alice
  Name:     Alice Wonderland
  Email:    alice@example.com
  Plan:     seedling
  Created:  2026-01-24

This will permanently delete:
  - All blog posts and pages
  - All media files (R2 storage)
  - All sessions and settings
  - Commerce data (orders, products, customers)
  - Curio configurations (timeline, journey, gallery)
  - Onboarding and billing records

Proceed with deletion?

切勿跳过此确认步骤。 即使是测试账户。

步骤 3: 删除前快照（可选但推荐）

对于非测试账户，快速捕获即将删除内容的计数：

npx wrangler d1 execute grove-engine-db --remote --command="
  SELECT
    (SELECT COUNT(*) FROM posts WHERE tenant_id = 'TENANT_ID') as posts,
    (SELECT COUNT(*) FROM pages WHERE tenant_id = 'TENANT_ID') as pages,
    (SELECT COUNT(*) FROM media WHERE tenant_id = 'TENANT_ID') as media_files,
    (SELECT COUNT(*) FROM sessions WHERE tenant_id = 'TENANT_ID') as sessions;
"

步骤 4: 删除租户（级联处理 29 张表）

此单次 DELETE 操作将级联删除：posts, pages, media records, tenant_settings, sessions, products, product_variants, customers, orders, order_line_items, subscriptions, connect_accounts, platform_billing, refunds, discount_codes, post_views, timeline_curio_config, timeline_summaries, timeline_activity, timeline_ai_usage, journey_curio_config, journey_snapshots, journey_summaries, journey_jobs, gallery_curio_config, gallery_images, gallery_tags, gallery_collections, git_dashboard_config。

npx wrangler d1 execute grove-engine-db --remote --command="DELETE FROM tenants WHERE id = 'TENANT_ID';"

步骤 5: 清理孤立记录

这些表不会从租户表级联删除，需要手动清理：

# 移除 onboarding 记录（通过用户名链接，非外键）
npx wrangler d1 execute grove-engine-db --remote --command="DELETE FROM user_onboarding WHERE username = 'USERNAME';"

# 移除该用户的电子邮件验证码（通过外键从 user_onboarding 级联删除，但请验证）
npx wrangler d1 execute grove-engine-db --remote --command="DELETE FROM email_verification_codes WHERE user_id IN (SELECT id FROM user_onboarding WHERE username = 'USERNAME');"

如果用户通过 Heartwood 注册且没有其他租户：

# 检查用户是否拥有其他租户
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain FROM tenants WHERE email = 'USER_EMAIL';"

# 如果没有其他租户存在，清理孤立的用户记录（如果适用）
# 注意：'users' 表可能存在也可能不存在，具体取决于使用的身份验证方法

步骤 6: 清除 R2 媒体文件（如果存在媒体文件）

R2 键遵循模式 {tenant_id}/{filename}。D1 的 media 表记录已删除（级联），但实际的 R2 对象仍然存在。

# 列出具有租户前缀的对象
npx wrangler r2 object list grove-media --prefix="TENANT_ID/" --remote

# 删除每个对象（wrangler 不支持批量删除，因此需要迭代）
# 对于少量文件：
npx wrangler r2 object delete grove-media --remote "TENANT_ID/filename1.webp"
npx wrangler r2 object delete grove-media --remote "TENANT_ID/filename2.webp"

对于大量文件，生成删除脚本：

# 列出所有键，然后在循环中删除
npx wrangler r2 object list grove-media --prefix="TENANT_ID/" --remote 2>/dev/null | jq -r '.[] .key' | while read key; do
  echo "Deleting: $key"
  npx wrangler r2 object delete grove-media --remote "$key"
done

如果删除前快照显示有 0 个媒体文件，请跳过此步骤。

步骤 7: 删除后验证

确认租户已完全删除：

# 验证租户已删除
npx wrangler d1 execute grove-engine-db --remote --command="SELECT COUNT(*) as remaining FROM tenants WHERE subdomain = 'USERNAME';"

# 验证级联是否生效（抽查几张表）
npx wrangler d1 execute grove-engine-db --remote --command="
  SELECT
    (SELECT COUNT(*) FROM posts WHERE tenant_id = 'TENANT_ID') as posts,
    (SELECT COUNT(*) FROM media WHERE tenant_id = 'TENANT_ID') as media,
    (SELECT COUNT(*) FROM sessions WHERE tenant_id = 'TENANT_ID') as sessions;
"

# 验证 onboarding 已清理
npx wrangler d1 execute grove-engine-db --remote --command="SELECT COUNT(*) as remaining FROM user_onboarding WHERE username = 'USERNAME';"

向用户提供清晰的摘要：

Tenant "alice" (Alice Wonderland) has been fully deleted.

Cleaned up:
  - Tenant record + 29 cascaded tables
  - Onboarding record
  - 3 R2 media files
  - Email verification codes

The subdomain "alice.grove.place" is now available for reuse.

删除前始终确认 - 即使用户似乎很确定，也要先向他们展示租户详情
切勿仅通过 ID 删除 - 始终解析为人类可读的标识符（子域名/电子邮件）以进行确认
检查是否有活跃订阅 - 如果 platform_billing.status = 'active' 或存在 LemonSqueezy 订阅，请发出警告
测试账户也是账户 - 相同流程，相同确认，相同验证
R2 是永久性的 - R2 对象一旦删除，即永久消失。D1 媒体记录（保存键值）已级联删除，因此在丢失存储内容记录之前进行 R2 清理

快速模式（测试账户）

对于用户明确称为"测试账户"或在当前会话中创建的账户：

仍然确认用户名/电子邮件
跳过删除前快照
如果未上传媒体文件，则跳过 R2 清理
仍然验证删除是否完成

用户拥有多个租户

一个电子邮件可以拥有多个子域名。仅删除指定的租户。不要触碰其他租户。

如果子域名/电子邮件与任何租户都不匹配，请告知用户。不要猜测。

Heartwood 会话清理

Heartwood 会话存储在 KV 中，而非 D1。D1 的 sessions 表用于遗留/本地会话。Heartwood 会话将自然过期（24 小时 TTL）。除非指定了紧急性，否则无需手动清理。

LemonSqueezy 订阅处于活跃状态

如果设置了 user_onboarding.lemonsqueezy_subscription_id，请警告用户他们可能需要在 LemonSqueezy 仪表板中单独取消订阅。D1 删除不会取消外部计费。

所有命令从项目根目录运行：/Users/mini/Documents/Projects/Lattice

数据库是：grove-engine-db (D1) 媒体存储桶是：grove-media (R2)

一次干净的删除是一次友好的告别。不留任何孤儿。

🇺🇸English

Grove Account Deletion

Safely delete a tenant account and all associated data from the Grove platform using wrangler CLI commands.

When to Activate

User says something like "delete Alice's account" or "Alice is done"
User mentions wanting to remove a test account
User asks to clean up after a walkthrough or demo
User explicitly calls /grove-account-deletion
User says "nuke that account" or "wipe their data"

The Pipeline

Identify → Verify → Snapshot → Delete Tenant → Clean Orphans → Purge R2 → Verify

Step 1: Identify the Tenant

The user will provide a username (subdomain), email, or display name. Look them up:

# By username/subdomain (most common)
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain, display_name, email, plan, created_at FROM tenants WHERE subdomain = 'USERNAME';"

# By email (if username unknown)
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain, display_name, email, plan, created_at FROM tenants WHERE email = 'EMAIL';"

# By display name (fuzzy match)
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain, display_name, email, plan, created_at FROM tenants WHERE display_name LIKE '%NAME%';"

Run these from the project root (/Users/mini/Documents/Projects/Lattice).

Step 2: Confirm with the User

Before deleting ANYTHING, show the user what you found and ask for explicit confirmation:

Found tenant:
  ID:       abc-123-def
  Username: alice
  Name:     Alice Wonderland
  Email:    alice@example.com
  Plan:     seedling
  Created:  2026-01-24

This will permanently delete:
  - All blog posts and pages
  - All media files (R2 storage)
  - All sessions and settings
  - Commerce data (orders, products, customers)
  - Curio configurations (timeline, journey, gallery)
  - Onboarding and billing records

Proceed with deletion?

NEVER skip this confirmation step. Even for test accounts.

Step 3: Pre-Deletion Snapshot (Optional but Recommended)

For non-test accounts, capture a quick count of what's being deleted:

npx wrangler d1 execute grove-engine-db --remote --command="
  SELECT
    (SELECT COUNT(*) FROM posts WHERE tenant_id = 'TENANT_ID') as posts,
    (SELECT COUNT(*) FROM pages WHERE tenant_id = 'TENANT_ID') as pages,
    (SELECT COUNT(*) FROM media WHERE tenant_id = 'TENANT_ID') as media_files,
    (SELECT COUNT(*) FROM sessions WHERE tenant_id = 'TENANT_ID') as sessions;
"

Step 4: Delete the Tenant (CASCADE Handles 29 Tables)

This single DELETE cascades to: posts, pages, media records, tenant_settings, sessions, products, product_variants, customers, orders, order_line_items, subscriptions, connect_accounts, platform_billing, refunds, discount_codes, post_views, timeline_curio_config, timeline_summaries, timeline_activity, timeline_ai_usage, journey_curio_config, journey_snapshots, journey_summaries, journey_jobs, gallery_curio_config, gallery_images, gallery_tags, gallery_collections, git_dashboard_config.

npx wrangler d1 execute grove-engine-db --remote --command="DELETE FROM tenants WHERE id = 'TENANT_ID';"

Step 5: Clean Up Orphaned Records

These tables don't CASCADE from tenants and need manual cleanup:

# Remove onboarding record (linked by username, not FK)
npx wrangler d1 execute grove-engine-db --remote --command="DELETE FROM user_onboarding WHERE username = 'USERNAME';"

# Remove email verification codes for that user (cascades from user_onboarding via FK, but verify)
npx wrangler d1 execute grove-engine-db --remote --command="DELETE FROM email_verification_codes WHERE user_id IN (SELECT id FROM user_onboarding WHERE username = 'USERNAME');"

If the user signed up via Heartwood and has no other tenants:

# Check if user has other tenants
npx wrangler d1 execute grove-engine-db --remote --command="SELECT id, subdomain FROM tenants WHERE email = 'USER_EMAIL';"

# If no other tenants exist, clean orphaned user record (if applicable)
# NOTE: The 'users' table may or may not exist depending on auth approach used

Step 6: Purge R2 Media (If Media Existed)

R2 keys follow the pattern {tenant_id}/{filename}. The D1 media table records are already gone (CASCADE), but the actual R2 objects remain.

# List objects with tenant prefix
npx wrangler r2 object list grove-media --prefix="TENANT_ID/" --remote

# Delete each object (wrangler doesn't support bulk delete, so iterate)
# For a small number of files:
npx wrangler r2 object delete grove-media --remote "TENANT_ID/filename1.webp"
npx wrangler r2 object delete grove-media --remote "TENANT_ID/filename2.webp"

For many files , generate a deletion script:

# List all keys, then delete in a loop
npx wrangler r2 object list grove-media --prefix="TENANT_ID/" --remote 2>/dev/null | jq -r '.[] .key' | while read key; do
  echo "Deleting: $key"
  npx wrangler r2 object delete grove-media --remote "$key"
done

Skip this step if the pre-deletion snapshot showed 0 media files.

Step 7: Post-Deletion Verification

Confirm the tenant is fully gone:

# Verify tenant deleted
npx wrangler d1 execute grove-engine-db --remote --command="SELECT COUNT(*) as remaining FROM tenants WHERE subdomain = 'USERNAME';"

# Verify cascade worked (spot-check a few tables)
npx wrangler d1 execute grove-engine-db --remote --command="
  SELECT
    (SELECT COUNT(*) FROM posts WHERE tenant_id = 'TENANT_ID') as posts,
    (SELECT COUNT(*) FROM media WHERE tenant_id = 'TENANT_ID') as media,
    (SELECT COUNT(*) FROM sessions WHERE tenant_id = 'TENANT_ID') as sessions;
"

# Verify onboarding cleaned
npx wrangler d1 execute grove-engine-db --remote --command="SELECT COUNT(*) as remaining FROM user_onboarding WHERE username = 'USERNAME';"

Step 8: Report

Give the user a clean summary:

Tenant "alice" (Alice Wonderland) has been fully deleted.

Cleaned up:
  - Tenant record + 29 cascaded tables
  - Onboarding record
  - 3 R2 media files
  - Email verification codes

The subdomain "alice.grove.place" is now available for reuse.

Safety Rules

Always confirm before deleting - Even if the user seems sure, show them the tenant details first
Never delete by ID alone - Always resolve to a human-readable identifier (subdomain/email) for confirmation
Check for active subscriptions - Warn if platform_billing.status = 'active' or LemonSqueezy subscription exists
Test accounts are still accounts - Same process, same confirmation, same verification
R2 is permanent - Once R2 objects are deleted, they're gone. The D1 media records (which held the keys) are already cascaded away, so do R2 cleanup BEFORE losing track of what was stored

Quick Mode (Test Accounts)

For accounts the user explicitly calls "test accounts" or accounts created in the current session:

Still confirm the username/email
Skip the pre-deletion snapshot
Skip R2 cleanup if no media was uploaded
Still verify deletion completed

Edge Cases

User has multiple tenants

One email can own multiple subdomains. Only delete the specified tenant. Don't touch others.

Tenant not found

If the subdomain/email doesn't match any tenant, tell the user. Don't guess.

Heartwood session cleanup

Heartwood sessions are stored in KV, not D1. The D1 sessions table is for legacy/local sessions. Heartwood sessions will expire naturally (24h TTL). No manual cleanup needed unless urgency is specified.

LemonSqueezy subscription active

If user_onboarding.lemonsqueezy_subscription_id is set, warn the user that they may need to cancel the subscription in the LemonSqueezy dashboard separately. D1 deletion doesn't cancel external billing.

Environment

All commands run from the project root: /Users/mini/Documents/Projects/Lattice

The database is: grove-engine-db (D1) The media bucket is: grove-media (R2)

A clean deletion is a kind goodbye. Leave no orphans behind.

Weekly Installs

Repository

autumnsgrove/groveengine

GitHub Stars

First Seen

Feb 5, 2026

Security Audits

Gen Agent Trust HubFail SocketFail SnykPass

Installed on

opencode50

codex50

gemini-cli50

continue49

cursor49

codebuddy49