Take over two docs gaps from the marko backlog

[DylanPiercey]

Both were found while working in marko-js/marko and recorded there; the deliverable is documentation, so they move here.

native-tag.md says a style= declaration is dropped for false/null/undefined/empty string, but marko's stringifyStyleObject uses value || value === 0, so NaN and 0n drop too. And core-tag.md's <script> section doesn't say that a <script> reading a tag variable first runs at dependency-init rather than in source order.

Removed from marko in marko-js/marko#3714; the optional MARKO_DEBUG warning stays there.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 203d533

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.

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: ecc4c610-9bc9-4d6f-9159-0c7574f20a28

📥 Commits

Reviewing files that changed from the base of the PR and between 4c5bb12 and 203d533.

📒 Files selected for processing (2)

• agent-feedback/bugs.md
• agent-feedback/unclear.md

---

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

[github-actions]

PR Preview Deployed

Your changes are live at markojs.com/previews/pr-268.

commit 203d533