Files
Agent-System/.doc/test-reports/assets/2026-09-26-full-system-browser-e2e/wipe-receipt.md
T

2.9 KiB
Raw Blame History

Wipe receipt — agent_system_dev → bootstrap-only

  • time: 2026-09-26T03:08Z–03:10Z (UTC+0 wall clock on host)
  • operator task: full-system-browser-e2e-wipe-2026-09-26 (env:dev)
    • Note: parent task full-system-browser-e2e-2026-09-26 only had docs:publish; same-id capability expansion is denied by agentctl, so wipe used a sibling wipe task.
  • scope: drop/create only agent_system_dev on localpg :5433. Did not touch regulations_kb_dev, data/dev/pg data directory, docker volumes, or test/main.

Before

field value
health status=ok env=dev schema_version=75 schema_ready=true database_ready=true kb_ready=true
stats users=424, projects=769, goose_version=75
evidence pre-wipe/health-before.json, pre-wipe/ready-before.json, pre-wipe/pre-wipe-stats.txt

Backup

field value
path .worktrees/full-system-browser-e2e-2026-09-26/.doc/test-reports/assets/2026-09-26-full-system-browser-e2e/pre-wipe/agent_system_dev.dump
format pg_dump -Fc (7.6M)
auth app user via CONTEXT_DB_* (password not written)

Procedure

  1. SIGTERM agent-server on :8080 (pid 1493262); port released.
  2. pg_dump -Fc → dump above.
  3. Via unix socket trust as postgres (/run/user/1000/as-pg-5433): DROP DATABASE agent_system_dev + CREATE DATABASE … OWNER app + extensions (vector, uuid-ossp, pg_trgm).
  4. Restart bin/agent-server with DATA_DIR=./data/dev, .env loaded, plus:
    • DISABLE_DEV_SEED_USERS=true
    • SEED_DEMO_USERS=false
    • LOCALPG_MODE=managed ENV=dev
  5. Wait /health + /ready ok.

After

field value
health status=ok env=dev schema_version=75 schema_ready=true database_ready=true kb_ready=true
agent-server pid 1585038, pgid=own session (detached)
seed env DISABLE_DEV_SEED_USERS=true, SEED_DEMO_USERS=false (confirmed in /proc/<pid>/environ)
users admin, seed-admin, seed-lizhuguan, seed-zhanggong (total 4)
demo BootstrapDevSeedUsers absent (zhanggong/lizhuguan/wangzong/guest count=0)
projects 10 (from goose 00011_…-seed-ten-projects.sql, not runtime demo seed)
goose 75
admin login POST /api/v1/auth/login → HTTP 200 (token redacted in admin-login-response.json)
regulations_kb_dev still present

Seed strategy (actual)

  • Runtime BootstrapDevSeedUsers / ReactivateDevSeedUsers: gated off by env → classic demo usernames not created.
  • Config admin: BootstrapAdminFromConfig → admin present; login OK.
  • Goose SQL seed (deploy/postgres/goose/00011_…): still inserts seed-* IAM rows + 10 projects on empty DB migrate. This is schema seed, not DISABLE_DEV_SEED_USERS.

Boundaries respected

  • No docker volume rm; no delete of data/dev/pg; no test/main; no regulations_kb_* drop; no push; no --force.