* M9: page.setOpening sets the page a shared file opens on, for everyone who joins (#1817)
A file on a figcraft-server opened on the page current at publish time, with no way to change it:
`DocProp::CurrentPage` was synced but nothing wrote it (`page.select` is each viewer's own page,
only a local save stamps the document). `page.setOpening {id?}` writes `doc.current_page` as a
document edit: one undo step, a synced change in a live session, so every later join opens on it;
the current page when none is named; a divider or a layer refused; nobody's own page moves. The
pages list's context menu gets "Set as opening page". Docs: mcp.md, collaboration-parity.md.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* M9: the pages menu's new string is in the English catalog (#1817)
The gate's i18n test wants every tr() key in locales/en.toml.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: the parity doc states the default when no opening page is set (#1972 issue)
With none set, a file opens on its saved current page, not the first page, and a link cannot name a page, so the row is partial.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: one sharing row, and the spotlight exception on the opening-page row (#1972 issue)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: the parity row states where the joiner's page comes from (#1972 issue)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: a no-op set adds no step, deleting the opening page falls back, and the tests cover junk ids, refusals, undo and the menu item (#1817)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* M5: the chosen opening page is saved with the file and opens it for everyone (#1817)
The opening-page flag now lives on the page node (NodeKind::Page opening), so it syncs
through the existing node kind. Saving writes the flagged page as current_page instead of
the page the saver was viewing. A duplicated page does not copy the flag, and deleting the
page removes it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* M8: Duplicate repeats the copy's rotation as well as its move, and forgets the step on a deselect (#2293)
Duplicate remembered only the shift of the copies' bounds corner, so a turned copy repeated an arbitrary offset and no rotation. The step is now the move of the copies' centre in the page frame plus the turn each copy has over its source, applied to the new copies about their own centre (one layer) or their shared centre (several). Size is not stepped; a resized copy repeats its move, not its growth. Measured in Figma's web app on 2026-11-12. The step was already dropped when the selection changes to anything but the copies (clean_selection), and a test now pins that.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Fable 5.2 queued; Opus 5.5 briefed; Sonnet 5.5 measured and wrote at medium
* M8: the duplicate step ignores turns in place, size changes and flips (#2293)
The move of the step is now measured per pair, as each copy's own centre minus its source's, less the shift a size change gives that centre (taken in the source's frame), averaged over the pairs. A turn about a layer's own centre, uneven layers and a widened-then-turned copy no longer record a move. A copy whose flip state differs from its source's repeats no turn, since flips were not measured.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Fable 5.2 queued; Opus 5.5 briefed; Sonnet 5.5 measured and wrote at medium
* M8: a turn of several copies together is not counted as a move in the duplicate step (#2293)
Duplicated::step took the mean of the per-pair centre moves, so a Rotate on several uneven layers (turned together about the selection centre) read as an extra move and the next Duplicate applied it. The step now also tries the reading where the copies were turned together about the sources' bounds centre, and uses it when every copy fits it and the in-place reading does not fit. Two tests cover a turn together and a move plus turn together.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
* M8: the duplicate step reads a turn about the rotation handle's centre, and a resize after a turn, as no move (#2293)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
* M8: the duplicate step turns several layers about their handle box's centre, with no pivot inferred (#2293)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Fable 5.2 briefed; Sonnet 5.5 wrote at medium
* Docs: repair a row the earlier merges garbled (Alt-drag duplicate)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Renaming a group in the Local variables window replaced every slash in the
typed name with a hyphen, so "Palette/Orange" gave a flat Palette-Orange
group and there was no way to move a group under a new parent.
The typed path now replaces the group's last part, so a slash nests the
group as in Figma: Orange/100 becomes Palette/Orange/100 and the sidebar
shows Orange under Palette. Each part is trimmed and empty parts are
dropped; a name that comes out empty or unchanged does nothing. The
renames go deepest name first, so a group moved into its own new subgroup
(Orange to Orange/Warm) never collides with a variable that is still to
move. A rename onto a variable name that stays is refused by
variable.update and the batch rolls back; it stays one undo step.