Resolve Root vs Nested Conflict

Goal

Make the web instructions consistent with the repository-wide package-manager policy while keeping Next.js-specific guidance scoped to the web application.

Repository Context

This repository contains separate web and API applications.

Code exampleMarkdown

platform/
├── AGENTS.md
├── apps/
│   ├── web/
│   │   ├── AGENTS.md
│   │   └── src/
│   └── api/
│       └── src/
└── package.json

The repository uses pnpm.

The root AGENTS.md contains:

Code exampleMarkdown

# Project Instructions

## Development

- Use `pnpm` throughout the repository.

The root instruction applies across the repository.

The web application has its own nested AGENTS.md for frontend-specific guidance.

Current AGENTS.md

The current apps/web/AGENTS.md contains:

Code exampleMarkdown

# Web Instructions

## Development

- Use `npm` for frontend dependencies.
- Follow the existing Next.js App Router structure.

## Validation

- Run `npm test` before completion.

Your Task

Fix apps/web/AGENTS.md so it no longer conflicts with the repository-wide package-manager instruction.

Keep the Next.js-specific guidance scoped to the web application and avoid unnecessarily duplicating instructions already provided by the root AGENTS.md.