Add agent-feedback setup and take over the streaming render gap

[DylanPiercey]

Sets up agent-feedback/ the way the other marko-js repos have it, plus a minimal AGENTS.md pointing at it (this repo had none).

The first entry was found while working in marko-js/marko: render() does String(await template.render(input)), which drains the Marko 6 stream to completion, so a server test can never observe an <await>/<try> placeholder and an unsettled load() hangs until timeout. Nothing is needed from marko — pipe(), toReadable() and [Symbol.asyncIterator]() already exist there.

Removed from marko in marko-js/marko#3714.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c79486d

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]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9e22b4bf-df79-4d07-a5b9-863c8bd0e081

📥 Commits

Reviewing files that changed from the base of the PR and between ce33921 and c79486d.

📒 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

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.42%. Comparing base (ce33921) to head (c79486d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage   65.42%   65.42%           
=======================================
  Files           3        3           
  Lines         188      188           
  Branches       50       50           
=======================================
  Hits          123      123           
  Misses         44       44           
  Partials       21       21           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.