Add agents file

[tomusdrw]

No description provided.

[netlify]

✅ Deploy Preview for pvm-debugger ready!

Name	Link
🔨 Latest commit	5904401
🔍 Latest deploy log	https://app.netlify.com/projects/pvm-debugger/deploys/692197a60d00040009024c4c
😎 Deploy Preview	https://deploy-preview-450--pvm-debugger.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change adds AGENTS.md, a new documentation file establishing repository guidelines. It covers project structure, build/test/dev commands, coding style, testing guidelines, and commit/PR practices for a React/TypeScript project. No functional code changes are introduced.

Changes

Cohort / File(s)	Summary
Documentation AGENTS.md	Adds repository guidelines document covering project structure, build/test/dev commands, coding style, testing guidelines, and commit/PR practices

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess relevance to the changeset.	Add a description explaining the purpose of the AGENTS.md file and how it benefits the project or team.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add agents file' directly and accurately describes the main change: adding the AGENTS.md documentation file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch td-agents

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

AGENTS.md (2)

4-4: Consider breaking down the dense Project Structure section for readability.

Line 4 packs multiple topics (directories, WASM workers, RPC alignment, asset locations, test placement, tsconfig updates) into a single paragraph. While accurate, restructuring this as a bulleted list or separate subsections could improve clarity for new contributors scanning the guidelines.

## Project Structure & Module Organization

- **React app**: `src/` holds reusable UI in `components/`, feature views in `pages/`, Redux logic in `store/`, and shared helpers in `hooks/` and `lib/`.
- **Web workers**: WASM-facing workers live in `src/packages/web-worker`; keep their RPC shapes aligned with the integrations listed in `README.md`.
- **Static assets & build outputs**: `public/` for static files, `dist/` for build outputs.
- **Testing**: Browser specs and fixtures belong in `tests/`; unit specs stay beside their modules using the `*.spec.ts(x)` suffix.
- **Configuration**: Add any new top-level folder to the `@/` alias in `tsconfig.json`.

---

7-7: Node version specification could become stale; ensure it's kept in sync with tooling requirements.

The reference to "Node 22.1.0 expected" is specific and helpful for reproducibility, but pinned versions can quickly become outdated as dependencies update. Consider verifying this matches what's specified in package.json (engines field) or .nvmrc, and document a process for keeping this guideline synchronized during tool upgrades.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 786d9ec and 5904401.

📒 Files selected for processing (1)

• AGENTS.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test