Development environment setup

[jon-bell]

Add AGENTS.md to document cloud-specific setup and jest.setup.ts to fix test configuration.

---

  

Summary by CodeRabbit

• Documentation

  • Added a comprehensive setup guide covering local service startup, environment configuration, database seeding, development and build commands, key ports, and troubleshooting notes for running the project locally.

• Tests

  • Enhanced the test environment to include extended DOM matchers, improving reliability and expressiveness of UI tests.

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[coderabbitai]

Walkthrough

Adds AGENTS.md, a new developer-facing doc detailing local setup, service startup, seeding, and dev/test commands for the Cursor Cloud / Pawtograder stack; and adds jest.setup.ts to import @testing-library/jest-dom for extended Jest DOM matchers.

Changes

Cohort / File(s)	Summary
Documentation & Setup AGENTS.md	New developer documentation describing stack (Next.js + Supabase + Docker), starting services, environment config, DB seeding, pre-commit hooks, lint/test/build commands, key ports, and operational notes/caveats.
Test Configuration jest.setup.ts	New Jest setup file that imports @testing-library/jest-dom to enable extended DOM matchers in the test environment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A fresh guide lands to light the way,
Commands and ports to shape the day,
Tests grow clearer, matchers in tow,
Developers stride, the workflows flow,
Small changes, steady progress on display.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Development environment setup' accurately reflects the main changes: adding AGENTS.md for setup documentation and jest.setup.ts for test configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch cursor/development-environment-setup-3146

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@AGENTS.md`:
- Line 1: Prettier formatting is failing CI for AGENTS.md; run the formatter and
commit the changes to fix it—execute `npm run format` or `prettier --write
AGENTS.md`, review the updated formatting in AGENTS.md, then add and commit the
formatted file so the pipeline passes.
- Line 3: The heading "Cursor Cloud specific instructions" needs a hyphenated
compound adjective; rename it to "Cursor-Cloud-specific instructions" (update
the heading text in AGENTS.md) so the multi-word modifier is correctly
hyphenated before the noun.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e28b40a and af4fd73.

📒 Files selected for processing (2)

• AGENTS.md
• jest.setup.ts

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	⚠️ Changes detected (Review)	53 changed, 12 removed, 1 failure	Mar 1, 2026, 8:09 PM

[coderabbitai]

Actionable comments posted: 1

♻️ Duplicate comments (1)

AGENTS.md (1)

3-3: ⚠️ Potential issue | 🟡 Minor

Hyphenate the compound modifier in the heading.

Line 3 should use a hyphenated compound adjective for readability/grammar consistency (e.g., Cursor-Cloud-specific).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@AGENTS.md` at line 3, Change the heading "Cursor Cloud specific instructions"
to use a hyphenated compound adjective; locate the heading string "Cursor Cloud
specific instructions" in AGENTS.md and replace it with "Cursor-Cloud-specific
instructions" so the compound modifier is hyphenated for correct grammar and
consistency.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@AGENTS.md`:
- Line 13: The documented workaround contains an invalid shell redirection in
the command that references the migration file for migration
`20260217000000_binary_submission_files.sql`; replace the broken token `... <
<migration_file>` with a valid invocation that supplies a real filename or
variable (for example use a single input redirection with the actual migration
filename or pipe the file contents into docker exec), and update the command
text so it shows a concrete filename or a clear variable like MIGRATION_FILE
rather than the literal `<migration_file>` placeholder.

---

Duplicate comments:
In `@AGENTS.md`:
- Line 3: Change the heading "Cursor Cloud specific instructions" to use a
hyphenated compound adjective; locate the heading string "Cursor Cloud specific
instructions" in AGENTS.md and replace it with "Cursor-Cloud-specific
instructions" so the compound modifier is hyphenated for correct grammar and
consistency.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between af4fd73 and 7fb1326.

📒 Files selected for processing (1)

• AGENTS.md