docs(slice5): record SLICE-5 bulk edit shipped in SPEC §22.4a status

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ben Stull
2026-06-07 20:52:48 -07:00
parent a2b55f94ce
commit 8eee907893
+8 -2
View File
@@ -5160,8 +5160,14 @@ never used for routing or lookup. New entries are never assigned one.
> `POST …/rfcs/{slug}/meta` editor (contributor+, validated at the write > `POST …/rfcs/{slug}/meta` editor (contributor+, validated at the write
> boundary), the schema-driven detail panel, all entry **write paths made > boundary), the schema-driven detail panel, all entry **write paths made
> sidecar-aware** (a migrated body-only `.md` never re-grows frontmatter), and > sidecar-aware** (a migrated body-only `.md` never re-grows frontmatter), and
> the Owner-gated `POST …/collections/{cid}/migrate` endpoint. Bulk edit > the Owner-gated `POST …/collections/{cid}/migrate` endpoint. **Bulk
> (SLICE-5) follows. See §9.5 for the edit-metadata write-through this reuses. > tag/untag (SLICE-5, v0.51.0)** completes the design: the
> `POST …/collections/{cid}/meta/bulk` endpoint (`{slugs, op: set|add|remove,
> field, value}`) applies one field change to many entries' sidecars in a
> **single commit** (D7), validated per entry at the write boundary with
> partial-rejection reporting (`{applied, rejected}`), plus the catalog's
> row multi-select + sticky bulk action bar. See §9.5 for the edit-metadata
> write-through this reuses.
Every collection declares a `type` in its `.collection.yaml` manifest Every collection declares a `type` in its `.collection.yaml` manifest
(§22.2), chosen at creation and **immutable**: one of `document`, (§22.2), chosen at creation and **immutable**: one of `document`,