Adom Wiki

@@ -381,6 +381,25 @@ answer carries its own back-off hint, so slow down when one appears rather than pre-tuning. 300 parts at ~5s spacing is under half an hour. Every failure names its fix in the hint; trust the hints over memory. +## Bulk visibility, and a component page's body layout++**Flip many pages' visibility in ONE call** instead of a throttled loop: `POST+/api/pages/batch/visibility { refs: ["<owner>/<slug>", ...], visibility: "public" |+"private" }` returns a per-ref `results` array. Each ref is manage-checked (you only+flip pages you own), it has its own rate bucket so it does NOT hit the per-page+~10/window limit, and it is capped at 100 refs. This is the right tool for making a+freshly-published batch of parts public at once.++**`sections` controls a component page's body** (a `page.json` array of `hero,+viewers, install, deps, readme, breadcrumbs, info`). It is BOTH an allowlist (only+listed blocks render) AND, on a component/molecule page, the ORDER of the main+column (`readme` / `viewers` / `breadcrumbs`). So `"sections": ["viewers", "readme"]`+puts Symbol & Footprint above the README; omit it for the kind default+(component/molecule lead with the README). `hero` and `info` have their own areas+(the 3D headline, the metadata sidebar), so their tokens don't affect main-column+order. Pushing a `page.json` with `sections` returns a `SECTIONS_DECLARED` hint+echoing what was kept vs dropped.+ ## Decision table  | You want to | Do this |