#8173 set the budget to 82,000 against 81,378 bytes measured, about 0.8%
over. The budget file's own rule is 5% above measured, so the next small
change would trip it again: ceil(81,378 × 1.05) = 85,447.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The bench's openStudio now waits in the page for Studio's own word that the
composition loaded (studio_look reports a duration) under the one 90 s boot
budget, instead of a separate 30 s poll that failed a case Studio was still
loading after a reload under load. A boot that never loads names Studio's last
report, and seekBound names the condition it was still waiting on.
hiddenTarget no longer throws on a preview frame detached mid-scan: puppeteer
throws that synchronously, so the per-frame .catch never ran.
* revert(producer): a render that fails on a missing file stops naming what was gone, for now
This reverts commit cfea8cfff5 (#7955). The detail comes back in a follow-up that only looks inside the folders the render owns.
* revert(producer): name the files the #7955 revert removes in the deletion guard
* fix(aws-lambda): match the shell to its own pin, ship only hashed files, refuse the shell ZIP in CDK and SAM
Review follow-ups to the pinned shell route:
- build-zip --source=chrome-headless-shell accepts the folder only when its
digest is pinned for this version, not for any pinned build.
- It leaves out the files the digest skips (debug.log and chrome_debug.log,
which Chrome writes as it runs), so nothing unhashed ships.
- The CDK construct throws on chromeSource "chrome-headless-shell" and the
SAM template allows only sparticuz, as lambda deploy already refused it:
a shell ZIP cannot fit a function. The CHROME_PATH wiring for that ZIP is
gone with it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(aws-lambda): raise the packed size budget to 82,000 bytes
The shipped build-zip script now checks the shell against its own
version's pin and skips the files the digest leaves out. That takes the
tarball to 81,378 bytes in CI, over the 80,500 budget's 1% tolerance;
main was already within about 200 bytes of it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
- build-zip --source=chrome-headless-shell stages only the repo's pinned
build (managedChromeVersion) and only when its folder matches the pinned
digest (isPinnedHeadlessShell), instead of the newest folder in the cache.
The folder cannot fit a ZIP function, so lambda deploy refuses
--chrome-source chrome-headless-shell up front on either arch, and the
docs say the arm64 video image is where the shell runs.
- build-zip prints the headroom under the unzipped gate, and a new
"Lambda handler ZIP" workflow builds the ZIP on PRs that touch the code
it bundles, so growth fails before merge rather than in the release job.
- The arm64 image keeps @sparticuz/chromium's fonts and fonts.conf from the
handler ZIP (FONTCONFIG_PATH=/var/task/fonts) instead of liberation-fonts,
so text falls back to the same fonts as on x86. The image workflow renders
a mixed-script page on both arches and fails when any line resolves to
different platform fonts.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* test(studio): property panel edits in a sealed preview reach the frame's element
* fix(studio): property panel style and attribute edits show in a sealed preview
* fix(studio): keep live property saves synchronous and use the runtime's realm-safe element check
* fix(studio): a sealed edit's put-back never replaces a newer edit
* refactor(studio): keep the sealed save wait private
* fix(studio): check a sealed edit's put-back reply without the helper main removed
* test(studio): share one sealed preview frame that delivers messages like a browser
* test(studio): name the sealed frame's port wrapper instead of commenting it
* fix(ci): the capture check treats .test-helpers files as tests, like the rest of the repo
* test(studio): keep the sealed frame's delivery helper private
* fix(studio): keep test helpers out of Studio's typecheck, like core does
* test(producer): a deep or query-stretched composition folder stays within the size limit
* fix(compiler): rebase composition asset paths from the file read and charge what they add
A mount's references now rebase from the project file the render read for
it, so a query or fragment in data-composition-src no longer lengthens every
rebased path. Every byte a rebased reference adds, including the entry file's
own rebase, is charged to the render's expansion budget as it is produced.
* test(producer): close the font embedding block after the rebase
* fix(cli): figma commands print manifest and folder text with visible escapes
figma asset prints a manifest row's id, path and description, and the <img> snippet built
from them. These lines, the index.md regeneration warning and the tokens 'wrote' line now go
through terminalText, so control characters show as visible escapes. The manifest file and the
returned records are unchanged.
* test(cli): run the figma escape fixtures where file names may hold control characters
* fix(cli): project folder names print control characters as visible escapes
check, info, compositions, benchmark, play, present and preview printed the
project folder name, and in places the project path, straight to the
terminal. A folder name can hold escape bytes on Linux and macOS, so a
received project could move the cursor, rewrite earlier lines, set the
window title or write the clipboard. Those lines now go through
terminalText(), as validate, snapshot, layout and lint already do. This
covers the preview summary, --status, --stop, --list and --kill-all lines,
and the check report path. The CLI's own colours stay, and --json output is
unchanged.
The play page also HTML-escapes the name in its title and footer, as the
present page does.
* fix(cli): preview --selection and --context print Studio text as visible escapes
The human output of preview --selection and --context printed the selected
element's label, source file, target and thumbnail URL, and the preview
server's project name, straight to the terminal. These come from the
composition or from whichever preview server answers, so control characters
in them could move the cursor, rewrite earlier lines, set the window title
or write the clipboard. They now go through terminalText(), as do the
failure messages these commands print. The CLI's own colours stay, and
--json output is unchanged.
* fix(cli): cloud get, list and delete print server fields as visible escapes
The human output of cloud get printed render fields from the server, such
as the failure message, title, composition and URLs, straight to the
terminal. A failure message can quote text from the rendered project, so
control characters in it could move the cursor, rewrite earlier lines, set
the window title or write the clipboard. cloud get, cloud list (rows and
the next-page token) and cloud delete now pass those fields through
terminalText(). The CLI's own colours stay, and --json output is unchanged.
* fix(inspector): the live inspection stamp gives the page only the generation id
prepareLiveInspection wrote the project's absolute path into the preview
page as window.__hfLiveInspection.project. Nothing in the page reads it, but
any composition script on that page could, which told it the account name
and folder layout. The page now gets only the generation id; the project
path stays with the host that prepared the page.
* fix(skills): locate.mjs keeps its grid font in a private per-run folder
locate.mjs drew its grid labels with a font at the fixed shared path
/tmp/locate-font.ttf. It used whatever file was already there and copied a
system font onto that path otherwise, following any link in its place. On a
machine shared with other accounts, someone else could plant that file
first, so the grid showed wrong numbers, a file appeared where they chose,
or every run failed.
The font is now copied into a folder made with mkdtemp (mode 0700) for each
run and removed when the run ends, so no file another account can create is
read or written. The skills manifest hash is regenerated.
* fix: escape the check report path and lint warnings, and harden locate.mjs font cleanup
check's report path notice and its not-recorded warning, and preview's
"Lint did not finish" warning, now print control characters as visible
escapes, like the other lines that carry the project path.
locate.mjs escapes the font path for ffmpeg's filter syntax, so a temp
folder with ':', ',', quotes or brackets in its name still works, and it
removes its font folder when the run is stopped by SIGINT or SIGTERM before
re-raising the signal.
play and present share one HTML escape helper.
* refactor(cli): keep the shared HTML escape helper within the comment budget
* fix: one HTML escape helper for the CLI, and locate.mjs escapes its font path in one pass
The sign-in callback page uses the shared escapeHtml helper, which now also
escapes single quotes.
locate.mjs escapes the font path for ffmpeg's option list and filtergraph
in a single replacement with the same result as before, and removes its
font folder on SIGHUP as well as SIGINT and SIGTERM.
* fix(cli): escape render output paths and cloud upload names
A finished render printed its output path and the desktop app hint raw.
The default output path sits under the project folder and is named after
it, so the folder name reached the terminal on every render. Batch renders
printed row output paths and the manifest path raw, and cloud render
printed the archive name in its upload progress lines and walked file
names in its left-out warnings raw. These lines now go through
terminalText() or terminalLines(). --json output is unchanged.
* fix(skills): the launcher's floor is 0.9.65, the oldest release Desktop ships
The skill launcher now refuses any HyperFrames release older than 0.9.65, the oldest release
the HyperFrames Desktop app ships. This applies to --cli-version, to
HYPERFRAMES_STANDALONE_CLI_VERSION, to a helper started with --script and to a plugin manifest
pin. A standalone install's default npx range starts at 0.9.65. Every plugin manifest in this
repo already pins 0.9.65.
The skills guide and the plugin installation reference name the current floor, and a test
keeps them in step with the launcher. Desktop's release checks read the floor from the
published launcher, so a comment asks that it stay a string literal.
* test(skills): a helper started with --script forwards a release at the launcher's floor
The accept loop now also starts a --script helper, so all four paths are shown accepting 0.9.65.
* fix(aws-lambda): run chrome-headless-shell 158 in the arm64 video image
The arm64 video image now installs Chrome for Testing's linux-arm64 chrome-headless-shell
158.0.8127.36, pinned by sha256 and fetched with curl -f, as the whole shell folder. The Lambda
Node 22 base has none of the shared libraries the shell links and no fonts, so the image installs
them from the base's repository at the same pinned release. The image sets
HYPERFRAMES_LAMBDA_CHROME_SOURCE and HYPERFRAMES_LAMBDA_CHROME_PATH itself, and the nested video
function no longer passes ChromeSource, which would override them. stage-arm64-image.ts stops
fetching the sparticuz arm64 pack and drops the ZIP's x86 sparticuz Chrome instead.
The x86 handler ZIP stays on @sparticuz/chromium, bumped from 148.0.0 to 153.0.0. It builds at
258,502,222 bytes unzipped, under Lambda's 262,144,000-byte limit and the 248 MiB in-house gate.
Two fixes for --source=chrome-headless-shell:
- build-zip.ts staged only the executable, which exits at launch without its ICU data and .pak
files. It now stages the whole shell folder at chrome-headless-shell-linux64/.
- Nothing set HYPERFRAMES_LAMBDA_CHROME_PATH, which src/chromium.ts requires for that source.
The SAM template and the CDK stack now set it to the bundled shell when ChromeSource asks for it.
Drops the unused @types/aws-lambda devDependency, which the dead-code audit reports whenever this
package's manifest changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* ci(publish): build the Lambda arm64 video image on an ARM runner
The video stage now installs Chrome's system libraries with microdnf, so it runs code for arm64.
The pack job built that image on ubuntu-latest with no emulation, which it could do only while the
stage copied files. A new lambda-video-image job builds it natively on ubuntu-24.04-arm, from the
handler zip whose sha256 the zip job reported, and reports the OCI tarball's sha256. Pack downloads
that tarball, checks the sha256 against the job's, and pins it as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(aws-lambda): fit the comment ratchet and the package size budget
chromium.ts loses the two doc lines on BUNDLED_SHELL_DIR and BUNDLED_SHELL_PATH; the names and the
SAM template's comment already say what they are.
@hyperframes/aws-lambda's unpacked budget goes from 290,508 to 298,000 bytes. The package unpacks to
295,324 bytes, up from the shared chrome-headless-shell staging module the ZIP and image scripts now
import and from the README and docs that describe the two Chrome sources.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): a font many rules name stays within the page's size limit
* fix(producer): inline a local font only while the page stays within its size limit
Only url() sources inside @font-face rules are replaced, and every inlined
copy is charged to the render's expansion budget. Once the budget is spent,
the remaining references keep loading the font from its file.
* fix(producer): keep the font anchoring test and name the fit-or-skip charge
* fix(studio): a sealed preview's element reads are bounded, and a frame with no agent answers at once
* fix(studio): a sealed preview's sources and style names are bounded too, never cut
* test(core): two editing clients of one preview frame each get their replies
* fix(core): each editing client takes its own port, so a sealed preview answers Studio again
* test(core): SVG id renaming shares its table, looks up only named ids, caps and charges what it adds
* fix(core): SVG id renaming shares one table, caps id prefixes and charges the bytes it adds
* test(core): a long namespace is hashed once per mount
* fix(core): sanitize and hash each mount's namespace once, before minting its ids
* test(core): page goldens carry the regenerated selector alias bundle
A folder move or delete in Studio checked each file inside only by its
name. A script that package.json runs from a subfolder could be moved
aside or deleted with its folder. A move could also land a file on a
path a direct write refuses, such as a script package.json runs or
mise/config.toml, by moving a folder onto the right name.
Now each entry in the folder is checked at its current path with the
same rules a direct delete or rename uses, including the package.json
scripts. For a move, it is also checked at the path where it would
arrive. Ordinary folder moves still work.
The engine ceiling moves from Beta 152.0.7977.30 to stable 158.0.8127.36, with its Chrome for
Testing digests. The places that installed `@stable` or an older pin follow it: the CI test
workspace, the regression test image, the k8s and Cloud Run examples, the CLI render image
(amd64) and the Lambda build hint. The motion-blur nightly keeps its pinned-versus-stable
comparison: the pin leg now uses the workspace's pinned shell, and a stable leg fetches stable.
The chat regression golden is regenerated on 158. Chrome 157 renders it pixel-identically to
158, so the previous golden recorded Chrome 152's paint of a background-clip:text phrase whose
word spans start at opacity 0.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio): a sealed preview takes its film's size from the player
A sealed preview frame refuses Studio's reads, so the size reader found no
document and Studio kept a 16:9 stage and no size for anything placed on
the picture. For a sealed frame it now reads the size its player got from
the runtime, once the player is ready, and the preview reads it again when
the player reports it.
* fix(studio): a sealed preview's size reader keeps its files' comment share
* refactor(studio): the player's size callback reaches its newest owner through one stable call
* fix(studio): a sealed preview reads its size once its film is ready to show, with no new player prop
* test(studio): the preview's mock player loads once, as a frame does
* test(core): a composition id with $ patterns scopes as text, not as a replace pattern
* fix(core): scoping writes a composition id's $ as text, at compile time and in the runtime script
* fix(compiler): bound composition variable styles and variable media sources
Charge every compile-time composition-variable rule against a size budget
and stop emitting once it is exceeded. The render compiler shares one
CompositionExpansionBudget between mounts, variable styles and variable
media sources; other callers get a 32 MiB core default. Host
data-variable-values are now parsed once per host instead of once per
declarer. Bound media sources over 8 KiB or holding control characters are
refused, and every src written is charged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(producer): trim bound media sources and name the variable budgets in errors
Bind the trimmed value, as a browser does, so a trailing newline no longer
makes compile-time probing disagree with the runtime; refuse only interior
control characters or values over 8 KiB, and log the refusal as a warning.
The generated-bytes error now says which of variable styles or variable
media sources overran. Adds a with-mount test for the after-inline budget.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(producer): trim comments added to htmlCompiler to keep its comment share down
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(producer): a render that fails on a missing file says what was gone
* fix(producer): a failed look at what was missing never hides the render's own error
The missing-path probe now returns nothing when it throws, reads through at most four links and only
links that point into the temp root or the cache folder, names a removed folder by its own name, treats
a custom cache folder as the cache, and skips programs that could not start.
* refactor(producer): split the missing-path link walk into its own step
* fix(core): a clip that stops downloading no longer holds the preview in Buffering forever
* fix(core): the stuck-clip bound also holds in a hidden tab
Clicking or dragging the scrubber while a film played left it paused at
the new spot, and `paused` turned true without a `pause` event. The
controls now hold a playing film during the press and play on from where
it is released, like a <video>'s own controls; a paused film stays
paused. A touch scrub no longer replays as mouse events.
seek() gains an opt-in { keepPlaying: true } for hosts (keyboard seeks,
chapter jumps). A plain seek(t), and setting currentTime, still land
paused, so existing callers keep their behavior.
The packed player tarball grows 339 bytes (158705 to 159044, packed with
pnpm 10.17.1 as CI does). main sat 11 bytes under the 1% gate, so the
packed budget moves to 159100; the unpacked size stays within budget.
Co-authored-by: robinebers <16515780+robinebers@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A tag name went into new RegExp unescaped, so a page could hang or crash
the linter (#8028). This test reads every RegExp the lint package builds
and fails when a template input is not escapeRegExp(...), an escaped*
name or an ALL_CAPS constant. Three inputs that cannot carry page text
are listed with the reason.
#8013 escaped resolve's results, recipes, stats and error lines, and
#8087 the adopt skip line. A few resolve lines still printed their
values raw: argument errors that repeat --type, --provider, --from,
--reuse and the --for path, the measured-grade note and the
similar-asset hint that repeats the intent. cube-validate's error can
quote a value from the LUT file. They now go through the same
terminalText copy, so a control character shows as \xNN. --json output
is unchanged.
A page that embeds <hyperframes-player> can now give it its own play,
pause and volume icons and its own loading logo, by putting elements with
a slot attribute inside the player. Anything the page leaves out keeps
today's HyperFrames look.
Co-authored-by: robinebers <16515780+robinebers@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
The .media/index.md generators (figma's mediaIndex.ts and media-use's
index-gen.mjs) turned only CR and LF in a record into a space. Vertical
tab, form feed, NEL, U+2028 and U+2029 still ended a row early for
readers that treat them as line breaks, and other control characters
(NUL, ESC, BEL, C1) reached the file as raw bytes.
- Every line-ending character now becomes a space.
- Other control characters are written as visible \xNN escapes through
the existing terminalText helper; tabs stay as they are.
- Both generators and the skill copy change together, so their output
stays byte-identical.
* fix(cli): tests read opencv.js from a CI cache, never a CDN mid-test
* chore(ci): re-pin the cli test job after its opencv cache step
* chore(cli): one-line note on the opencv cache copy
* test(studio): sealed preview crop and scale resize read the frame's values
* fix(studio): crop and scale resize work in a sealed preview
* test(studio): a sealed preview's crop lift and resize box survive lost or bad frame replies
* fix(studio): a sealed preview's crop lift and resize box survive lost or bad frame replies
* refactor(studio): the crop's stylesheet clip under a lift is read in its own step
* test(studio): the frame crop-lift helper answers the lift it just sent
npm, pnpm, yarn and bun run `node-gyp rebuild` on install when a binding.gyp
is present and package.json has no install script, and a .gyp file can include
any .gyp or .gypi. npm, pnpm and yarn run `node server.js` for start when
package.json has no start script. A project from `hyperframes init` has
neither script, so both defaults apply.
toolTrustedFileKind now classifies .gyp/.gypi files and server.js, in every
spelling projectPathSegments folds, so Studio's file routes and the registry
installer refuse to write them. Rename and duplicate refusals now report
why: protected_path when the destination is inside the project, as POST and
PUT already do.
The skill launcher raises its floor to 0.9.64, the oldest release with every
protection for projects received from someone else. The floor applies to a
plugin pin, to --cli-version and to HYPERFRAMES_STANDALONE_CLI_VERSION. A
release below it is refused with a message that names the floor.
The skill lifecycle reference no longer sends the agent back to the project's
pinned release after a failed check. The agent stops and reports, and runs
the old release only when the person asks for it. The CLI notice for a
project that pins a newer release now says the pin is the person's choice.
When the 30 s limit stops a guarded ffprobe or ffmpeg run, the line check prints for the
skipped source now ends "stopped after 30 s" instead of a generic read failure. Every
other message is unchanged.
A new test decodes a text-art file through readSamples's guarded path and expects
ffmpeg to refuse it, so dropping the demuxer list from that run fails the suite.
The media-use copy of the received-files rule now reads the host app's kept
copy of an expected project's record, as the CLI does. It adds back each kept
entry whose path still holds something, checks the folder identity for a
project found only by dev and ino, and counts every file as received when the
copy has no list, is doubted, a link, oversized, unparsable or another
project's.
In both the CLI and the copy:
- a kept copy whose identity names another folder counts every file as
received instead of being ignored;
- a kept copy that fails its first read, for example because the app replaced
it mid-read, is read once more before every file counts as received;
- a kept copy named both by path and by dev and ino is read once.
The docs no longer suggest that the app's next read restores a kept entry
whose file is gone.
* fix(studio): slideshow scenes, block stacking, drill-down and shortcuts work in a sealed preview
* fix(studio): sealed preview keys act only with the preview focused; frame replies are validated
* fix(cli): a rename keeps the received-files record listing the moved file
On a disk that tells letter case or Unicode forms apart, a Studio rename to a
name differing only in case or form followed the old spelling, so the record
dropped the file's only line while the file moved to the new name.
- onDiskPath folds a requested name onto an existing entry only when the disk
opens the same file under both spellings, so the record follows the exact
path the rename creates, spelled as the move spells it.
- After a move, an old non-media line goes only when the file left its old
path, sits at the planned path (same identity or content), and another line
lists that path. Otherwise the line stays, as it does for a delete.
- A refused move keeps a new line for a file another move already put there.
* docs(cli): word a rename helper comment as what it checks now
* test(cli): build the rename test folder by its native real path
On Windows the temp folder can carry an 8.3 short name, which onDiskPath
spells in full, as the native real path does.
* fix(producer): charge generated mount scripts and scoped styles to the expansion budget
The expansion budget charged only the source bytes of each mounted file.
The inliner wraps every inline script in kilobytes of scoping code and
prefixes every style rule with the host's scope, so tiny scripts or a long
composition id over many rules assembled a page hundreds of times larger
than its source.
The inliner now reports what it generates through a chargeEmitted option.
Each wrapped script is charged once built. Each style rule reserves an upper
bound before it is scoped and settles to its real size after, so no rule is
built past the limit. Generated output has its own 32 MB allowance.
* fix(core): reserve the separator postcss re-joins scoped selectors with
The per-rule reservation summed a bound per selector but left out the
separator. postcss's selectors setter re-joins the list with the first
separator in the authored selector, so a wide first separator over many
selectors grew the rule past its reservation before it was charged.
* test(core): give the scoper bound test the same time limit as its neighbour
* fix(studio): error events send a class, a shape and Studio's own frames, not the error's words
Error messages from the browser, a server or the project now leave as an unsalted shape of the cut first line (numbers, quotes and paths removed) plus any HTTP status, beside the error class each sender now passes. Stacks keep only frames in Studio's own scripts as fn@file:line:col; any other frame, its name included, is ?. Component stacks keep component names. A script filename is sent only when it is one of Studio's own. The resolver shadow's mismatch list no longer carries the error's words or the selector-built animation id.
* fix(studio): error shapes match across projects and bare paths are never Studio frames
Only an absolute http(s) frame on Studio's origin is kept; the message shape cuts URLs and selector ids and uses the install salt.
* feat(studio-server): let a host count the requests the API refuses with 403
* fix(studio-server): a refusal names the endpoint asked for, not the middleware that refused it
* style(studio-server): refusal reports carry their meaning in names, not comments
* fix(studio-server): a refusal the API sends through itself again is counted once
* fix(studio-server): a request sent through the API again is known before a middleware swaps it
* test(studio): Add keyframe on a sealed preview seeds from a moved layer's translate
* fix(studio): Add keyframe on a sealed preview keeps a moved layer in place
* fix(studio): a sealed keyframe seed reads the translate the frame renders, a stylesheet's too
The text-over-face pass now treats a page-named source as missing when it
is a private project file, by its name or through a link, or is not a
regular file. Before any ffprobe or ffmpeg run, it refuses a document,
pipe or playlist that names files outside its folder or private in it.
Every probe and decode then uses render's demuxer list and a 30 s limit.
measure reads files named on the command line as before.
* test(studio): a sealed preview moves and saves a layer its animation moves
* fix(studio): a sealed preview moves and saves a layer its animation moves
* test(studio): a sealed drag of a moving layer saves nothing when the preview's tweens can't be read
* fix(studio): a sealed drag of a moving layer saves nothing without the preview's tweens
* refactor(studio): keep the drag stamp's writer beside its reader
* style(studio): keep the drag stamp reader's comment on the reader
* fix(studio): analytics send path and selector facts, not the paths and selectors
Both Studio transports now shape every event's values in one place before they leave the machine: a file path becomes its extension, kind, depth and a per-install salted hash; a selector becomes its kind and the same hash; any other value that reads as a path or selector is dropped and named in dropped_fields. Save failures send the error class, a fixed error key and the server's fixed refusal code instead of the error's words. Session fields can no longer be overwritten by a caller.
* fix(studio): save failures keep their dedupe and no selector leaves in shadow mismatches
The editor's failure dedupe keys on the error's own text again, locally. The resolver shadow's animation_not_found no longer repeats the animation id inside mismatches. Error keys and path kinds read from tables; the server's full refusal list is known.
* fix(studio): a paused save queue reports codes, not the save error's words
save_queue_paused spreads the save failure's fixed codes again; its handler lives outside the persistence hook.