Fix Overly Broad Validation

Goal

Replace an unnecessarily expensive validation requirement with validation appropriate to the scope of the change.

Repository Context

This monorepo contains several independent applications and packages.

platform/
├── apps/
│   ├── web/
│   ├── admin/
│   └── api/
├── packages/
│   ├── ui/
│   ├── config/
│   └── database/
├── package.json
└── AGENTS.md

The repository supports targeted validation:

pnpm --filter web test
pnpm --filter admin test
pnpm --filter api test
pnpm --filter ui test

The full repository test suite is expensive and is reserved for changes that affect multiple packages or shared infrastructure.

Current AGENTS.md

# Project Instructions

## Development

- Use `pnpm`.
- Keep changes within the relevant application or package when possible.

## Validation

- Run the entire repository test suite after every code change.
- Use `pnpm test` for all validation, even when only one application changed.

Your Task

Rewrite the validation instructions so agents run tests relevant to the affected application or package.

Keep full-repository validation for changes that affect multiple packages or shared infrastructure.