Fix AGENTS.md prettier formatting (#691)

## Summary
- Fix markdown formatting in AGENTS.md to pass prettier checks
- Normalizes `*` list markers to `-` and double backticks to single

Made by AI

Author: ericholscher

AGENTS.md

@@ -6,6 +6,7 @@ Read the Docs is a documentation hosting platform that builds and hosts document
 It supports multiple documentation tools (Sphinx, MkDocs, etc.) and automatically builds documentation from Git repositories.
 
 **Technology Stack:**
+
 - Python 3.x
 - Django web framework
 - Docker and Docker Compose for development
@@ -15,16 +16,16 @@ It supports multiple documentation tools (Sphinx, MkDocs, etc.) and automaticall
 
 ## Commits
 
-* Use short descriptive commit messages
-* Only provide simple context, and don't be overly verbose
+- Use short descriptive commit messages
+- Only provide simple context, and don't be overly verbose
 
 ## Pull Requests
 
-* Put a footer note that this was generated by Copilot
-* Use feature branches for all changes
-* Don't include a "Changes" section, since the PR content is self-explanatory
-* Link related issues in the PR description, if there are any in the chat context
-* Prefix pull request titles with the part of the system being worked on, for example `api:`, `builds:`, or `docs:`.
+- Put a footer note that this was generated by Copilot
+- Use feature branches for all changes
+- Don't include a "Changes" section, since the PR content is self-explanatory
+- Link related issues in the PR description, if there are any in the chat context
+- Prefix pull request titles with the part of the system being worked on, for example `api:`, `builds:`, or `docs:`.
 
 ## Package Management
 
@@ -34,9 +35,9 @@ It supports multiple documentation tools (Sphinx, MkDocs, etc.) and automaticall
 
 ## Docs
 
-* Follow the style guide at https://github.com/readthedocs/readthedocs.org/blob/main/docs/dev/style-guide.rst.
-* Always use the marketing name used in the public-facing docs, and not the internal code names referenced in code.
-* The ``user`` directory is public docs, and ``dev`` is dev-focused. Most of what we do is focus on the user-facing docs.
+- Follow the style guide at https://github.com/readthedocs/readthedocs.org/blob/main/docs/dev/style-guide.rst.
+- Always use the marketing name used in the public-facing docs, and not the internal code names referenced in code.
+- The `user` directory is public docs, and `dev` is dev-focused. Most of what we do is focus on the user-facing docs.
 
 ## Testing
 
@@ -45,7 +46,7 @@ It supports multiple documentation tools (Sphinx, MkDocs, etc.) and automaticall
 - Write succinct, focused tests that test one thing at a time
 - Use descriptive test names that explain what is being tested
 - Place tests in appropriate test files following the project structure
-- Always keep the test db with ``pytest --reuse-db`` to speed up test runs
+- Always keep the test db with `pytest --reuse-db` to speed up test runs
 
 ## Code Quality