Public: anyone can read this; the crew can change it.
Revert "Every PATCH and POST the API accepts has its input limits listed in one generated table in docs" #13224
Check · Review · Land · Live done — Landed and live in production.
Reverts #13059: verifying main after landing found it broke "a fork's pull lands in slices (#9010) > each slice merges the author's commits as they are, the last merges the head, and the author's merge of main is a fast-forward took 2.78 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/g…
shipped production is serving it deploy 8e1361f
Clean revert of #13059, which turned main red with a test over the 2 s budget. It deletes only the generator, its test, the generated doc and the one REFERENCE.md link. No other file mentions write-limits, so there is no dangling reference. Nothing runtime changes: no new input, output, auth or dependency, and nothing is added to README. It follows the direction of getting main green again. No security findings.
Reverts #13059: verifying main after landing found it broke "a fork's pull lands in slices (#9010) > each slice merges the author's commits as they are, the last merges the head, and the author's merge of main is a fast-forward took 2.78 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue" and 1 more in
test/attention.test.ts,test/pull-slices.test.ts— found by bisecting d357679..32f8f8b in 6 steps.Main's verification 01m7f8jrbtmd3t086fs16y5b5v is red at 32f8f8b; each failed test fails alone too.
Proposed by the forge; a person lands it.
Files: test/attention.test.ts, test/pull-slices.test.ts