Make the buttons groups, each with its own place

[nstarman]

Changing code or schema

What and why: the stars button should be separable from the rest — e.g. the buttons on the left and the stars on the right — and so should any other button. The buttons are individual elements, grouped by the name: buttons:… may now be given again. The first part is the card's own; each part after it is another group with its own keys, count to a row, area and place.

buttons:code,docs:left-buttons:stars:right        code and docs in a left rail, stars in a right one
buttons:all:fit-buttons:stars:bottom:right        everything as ever, the stars in the bottom row's right
buttons:code,docs-buttons:stars:top:right         the stars in a strip at the top right
buttons:code:left-buttons:stars:left:bottom       the stars at the foot of the same left rail

• Each key is in one group (all in one, empty in any); a key two groups list, a group of none, and paperbutton/year/position/context outside the first group are refused.
• Where a group sits: in the buttons' own area → a slot of their box at its v/h (the mechanism year/position/context already use); top → a strip of the card's padding; any other area (left, center, right, bottom) → a box of its own, .c-xfoot, set as the buttons' box is (column in a side, row under the words or at the bottom), figure stacking included.
• No change for a card with one group: every new rule keys off an attribute only a group adds (data-xg, data-gper, data-xfeet, .c-xfoot); cardFace for one group is what it was (all existing tests unchanged and green).
• Rendering: Card.astro for the first group and ButtonList.astro for the others; the embed page builds the same lists and boxes from the query. Both read cardFace.
• Card Builder: carries other groups through its controls and back as the name has them (so editing something else keeps them); its own controls for editing groups are a follow-up.

Checked in a browser on the embed page (seven arrangements: rail + rail, center + bottom row, same-rail slots, top strip, figure + groups, per-row groups) and on the Software page through a preset using groups.

• npm run test:schema passes; 596 unit tests (17 new: grammar, cardFace partition and placement, the embed's copy, CSS coverage, builder pass-through) and the build pass

Screenshots

unxt, drawn by the real card CSS on the embed page (/embed/unxt/?card=…).

buttons:all — one group, as before

buttons:code,docs:left-buttons:stars:right — code and docs in a left rail, stars in a right one

buttons:code,docs-buttons:stars:bottom:right — the usual row under the words, stars in a bottom row at the right

buttons:code,docs:left-buttons:stars:left:bottom — stars at the foot of the same left rail (a slot of its box)

buttons:code,docs-buttons:stars:top:right — stars in a strip of the card's padding at the top right

size:480 with a left figure, buttons:code,docs-buttons:stars:right:bottom — stars at the foot of the right side

buttons:code:2-buttons:docs,stars:2:right:bottom:right — each group's rows its own

the left/right arrangement in the dark theme

🤖 Generated with Claude Code

[github-actions]

Preview: https://9d33f783.nstarkman-space.pages.dev

Built from d98b5082742d20471675dd64dd0826cb471a4214, including the four CV PDFs.
Updated on every push to this pull request.