docs: record four self-audit gaps in the parity ledger

[cardmagic]

Summary

• Add a Partial row for backpressure and payload caps (shared JSON nesting limit, optional maxBytes guard, 255-char reminder names), noting the missing distributed rate limits already tracked as an open Ruby roadmap item.
• Note under the wake-up table that neither runtime auto-selects an adapter — both poll until one is configured, and both warn once about it. Shared limitation, not a JS gap.
• Explain why the MySQL row tracks only mysql2: Ruby also tests trilogy, Node has no comparable second client.
• Record the operator dashboard's shared limits (single-ID dead-letter retry, no admin audit trail, pause sets a flag rather than interrupting a turn) — verified by reading dead_letter_manager.rb/dead-letters.ts and the pause implementation on both sides, not inferred from docs alone.

Found by a real run of the solid-objects-audit skill against this repo and solid_objects (Ruby), covering the 0.12.0–0.13.3 version range both changelogs share.

Test plan

• Docs-only change; no code paths affected
• Confirm table rendering in docs/parity.md on GitHub

[greptile-apps]

Greptile Summary

The parity ledger now documents shared runtime limitations and clarifies differences that are not JavaScript parity gaps.

• Adds backpressure and payload-cap behavior, including distinct InvalidPayload and PayloadTooLarge errors.
• Records shared operator-dashboard and wake-up adapter limitations.
• Explains why only the mysql2 client is tracked for Node.js.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
docs/parity.md	Expands the parity ledger with shared limitations and correctly distinguishes excessive-nesting errors from byte-limit errors.

_{Reviews (2): Last reviewed commit: "fix: correct payload error type and sati..." | Re-trigger Greptile}

[greptile-apps]

Distinguish payload error types

The new row says excessive nesting and an exceeded maxBytes limit both raise PayloadTooLarge, but nesting raises InvalidPayload; this gives callers incorrect error-handling guidance.

Suggested change

	| Backpressure and payload caps | Partial | Serialization enforces a shared maximum JSON nesting depth and an optional caller-supplied `maxBytes` limit, both raising `PayloadTooLarge`; reminder names are bounded to 255 characters. Distributed per-actor rate limits and global admission control do not exist yet, matching the open Ruby roadmap item. |
	| Backpressure and payload caps | Partial | Serialization enforces a shared maximum JSON nesting depth, raising `InvalidPayload`, and an optional caller-supplied `maxBytes` limit, raising `PayloadTooLarge`; reminder names are bounded to 255 characters. Distributed per-actor rate limits and global admission control do not exist yet, matching the open Ruby roadmap item. |

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/parity.md
Line: 41

Comment:
**Distinguish payload error types**

The new row says excessive nesting and an exceeded `maxBytes` limit both raise `PayloadTooLarge`, but nesting raises `InvalidPayload`; this gives callers incorrect error-handling guidance.

```suggestion
| Backpressure and payload caps                                                                                 | Partial | Serialization enforces a shared maximum JSON nesting depth, raising `InvalidPayload`, and an optional caller-supplied `maxBytes` limit, raising `PayloadTooLarge`; reminder names are bounded to 255 characters. Distributed per-actor rate limits and global admission control do not exist yet, matching the open Ruby roadmap item. |
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.