Add agent-feedback setup

[DylanPiercey]

Adds the agent-feedback/ directory (README + bugs/cleanup/dx/perf/unclear category files) and references it from AGENTS.md, matching the setup in the marko repo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5e7e0aa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Adds repository guidance for recording actionable out-of-scope observations in agent-feedback/. It links CLAUDE.md to AGENTS.md, documents entry categories, formatting rules, verification requirements, and resolution procedures, and initializes category files for bugs, cleanup, developer experience, performance, and unclear code or documentation.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the added agent-feedback setup and matches the main change.
Description check	✅ Passed	The description accurately describes the new agent-feedback directory and AGENTS.md reference.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dpiercey-ws-agents-feedback-i8bbdl

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@agent-feedback/README.md`:
- Around line 30-33: Update the feedback entry template in README.md to replace
the fixed 2026-07-02 value with a <YYYY-MM-DD> placeholder, while preserving the
existing entry format.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8d95a3e1-ad76-4071-9626-d99b73bf8106

📥 Commits

Reviewing files that changed from the base of the PR and between e9a79f3 and b4ac54c.

📒 Files selected for processing (8)

• AGENTS.md
• CLAUDE.md
• agent-feedback/README.md
• agent-feedback/bugs.md
• agent-feedback/cleanup.md
• agent-feedback/dx.md
• agent-feedback/perf.md
• agent-feedback/unclear.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use a date placeholder in the entry template.

2026-07-02 can be copied verbatim and make future feedback entries appear misdated. Replace it with <YYYY-MM-DD> or clearly label it as an example.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@agent-feedback/README.md` around lines 30 - 33, Update the feedback entry
template in README.md to replace the fixed 2026-07-02 value with a <YYYY-MM-DD>
placeholder, while preserving the existing entry format.