Fix a Dangerous Database Instruction

Goal

Replace a dangerous database instruction with guidance that protects production data.

Repository Context

This application uses PostgreSQL.

billing-service/
├── src/
├── migrations/
├── scripts/
├── package.json
└── AGENTS.md

Developers use local and test databases during normal development.

Production database operations require an explicit deployment or operational process outside routine coding tasks.

Agents should never reset, truncate, or destructively modify a production database as part of normal development or testing.

Current AGENTS.md

# Project Instructions

## Development

- Use `pnpm`.
- Store database migrations in `migrations/`.

## Database

- If database state causes tests to fail, reset the database before trying again.
- It is acceptable to reset the production database when necessary to get a clean state.

## Validation

- Run `pnpm test` after database-related changes.

Your Task

Remove the dangerous production database instruction.

Clarify that destructive database operations must be limited to explicitly safe development or test environments and must not be performed against production during routine development.