Reproduction
Studio combined proof for https://zeeworks.art/ on 2026-09-29. The Blocks Engine import-report.json form fallback has presentation_graph.controls[2].control.styles for a textarea (font_family=Source Sans Pro, font_size=16px base with responsive variants, line_height=1.75, padding 16px), but the graph is marked truncated:true. The first 32 diagnostics are unrelated unsupported selectors; the actual truncation reason is not visible due MAX_DIAGNOSTICS. ArtifactCompiler::runtimeDeclarationsFromFallbacks excludes the entire graph when truncated (line 1081). The generic/forms/v1 runtime entity therefore has NO presentation_graph despite complete sourced control facts in the diagnostic. SSI sees only rows=6 and paints font-family:revert; line-height:revert, producing a 142px Jetpack textarea instead of the 223px source textarea. The form loses 158px, moving the article image from y=1882 to y=1724 at 1600px. SSI tracker Automattic/static-site-importer#1903 records the consumer symptom.
Acceptance
Preserve bounded, proven per-control presentation facts in the runtime entity when an unrelated global selector/budget makes the whole graph incomplete, with explicit status and provenance for omitted facts. Do not silently claim a complete graph. A neutral CSS fixture with >32 unrelated unsupported rules plus a form textarea yields a valid runtime form declaration carrying its reliable font/line-height/padding facts; fresh ZeeWorks paired import restores the desktop textarea and contact-section geometry without hardcoded values. State the precise truncation cause even when diagnostics are capped.
AI disclosure: GPT-6 Sol via OpenCode traced compiler fallback graph, runtime declaration omission and SSI provider CSS from the fresh combined import at Chris Huber’s direction.
Reproduction
Studio combined proof for https://zeeworks.art/ on 2026-09-29. The Blocks Engine
import-report.jsonform fallback haspresentation_graph.controls[2].control.stylesfor a textarea (font_family=Source Sans Pro,font_size=16pxbase with responsive variants,line_height=1.75, padding 16px), but the graph is markedtruncated:true. The first 32 diagnostics are unrelated unsupported selectors; the actual truncation reason is not visible dueMAX_DIAGNOSTICS.ArtifactCompiler::runtimeDeclarationsFromFallbacksexcludes the entire graph when truncated (line 1081). Thegeneric/forms/v1runtime entity therefore has NOpresentation_graphdespite complete sourced control facts in the diagnostic. SSI sees only rows=6 and paintsfont-family:revert; line-height:revert, producing a 142px Jetpack textarea instead of the 223px source textarea. The form loses 158px, moving the article image from y=1882 to y=1724 at 1600px. SSI tracker Automattic/static-site-importer#1903 records the consumer symptom.Acceptance
Preserve bounded, proven per-control presentation facts in the runtime entity when an unrelated global selector/budget makes the whole graph incomplete, with explicit status and provenance for omitted facts. Do not silently claim a complete graph. A neutral CSS fixture with >32 unrelated unsupported rules plus a form textarea yields a valid runtime form declaration carrying its reliable font/line-height/padding facts; fresh ZeeWorks paired import restores the desktop textarea and contact-section geometry without hardcoded values. State the precise truncation cause even when diagnostics are capped.
AI disclosure: GPT-6 Sol via OpenCode traced compiler fallback graph, runtime declaration omission and SSI provider CSS from the fresh combined import at Chris Huber’s direction.