Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
HTML agent-skillsai-agentsarchitecture-diagramclaude-codeclaude-skillscodexcoding-agentsdeepseek-harnessdeveloper-toolsdiagramsdiagrams-as-codedsh-pluginflowchartllmmermaidopencodesequence-diagramsoftware-architecturesystem-designvisualization
fix(skill): prioritize first-draft composition guidance
tt-a1i1ddb102bef05
diff --git a/archify.zip b/archify.zipindex 70049d81..9c1fa2d0 100644Binary files a/archify.zip and b/archify.zip differdiff --git a/archify/references/authoring-defaults.md b/archify/references/authoring-defaults.mdindex 56b39be0..78657c89 100644--- a/archify/references/authoring-defaults.md+++ b/archify/references/authoring-defaults.md@@ -2,6 +2,26 @@Read this file once before writing a fresh candidate. A frozen existing candidate that is going straight to `finalize` does not need it unless a failed gate requires repair.+## Composition and meaning++- For Architecture, default to a system overview unless the user requests a narrower mechanism, module map, or deployment topology. Lead with the main user journey and keep necessary branches close. Group cooperating implementation roles into accurately named subsystems; a group may contain multiple processes without implying they are one process. Expose a separate role or interaction when combining it would hide a requested mechanism or an important boundary. Retain secondary and opt-in capabilities as concise sourced notes by default; draw their path when needed to understand the main journey or a requested boundary. Preserve their role and trust conditions in either form. Name a deliberately narrower scope in the title rather than silently omitting it.+- Choose abstraction by the reader's question: would combining these responsibilities mislead the reader about the requested behavior, control ownership, trust, lifecycle, or persistence? If so, keep them separate; otherwise use an accurately named overview node with supporting labels and source references. Keep a behavior-changing condition visible on its affected node or relationship: an approval, authorization, or state-transition gate must not look unconditional while its qualifier appears only in a card. Separate source files, classes, protocols, or internal services do not by themselves require separate nodes. For example, an overview may show one local HTTP / WebSocket service; a transport-mechanism diagram may expand it. A cloud relay and a local decrypting bridge stay distinct when the remote trust boundary matters.+- Cover the requested meaning, with evidence for every claim. An overview need not enumerate every implementation role discovered during source reading. Put useful supporting facts in sublabels or concise cards; expand a subsystem in a focused diagram when its mechanism is requested. Guided views focus existing topology and do not collapse a crowded default overview. Add `meta.views` or cards only for a real reader question, with no quota.+- Let the requested question and source facts determine node and relationship counts; never target a number. Choose scope and abstraction before routing. Once authoring or repairing an agreed detailed graph, preserve its required roles, relationships, meaningful labels, and evidence; geometry failures do not authorize silently reducing that scope.+- When correcting an authored overview's abstraction, map every affected role, relationship direction, protocol, boundary, and source reference to its surviving node or relationship before regrouping. Carry the inspected references for each retained claim onto the relevant surviving component; a citation proving process startup does not also prove its message protocol. Check that requested meaning and evidence still have a home. User-supplied or agreed topology stays fixed; fewer routes alone do not justify merging.+- A boundary is evidence, not decoration. Use it when it communicates a real trust, runtime, process, ownership, or persistence boundary; a boundary around one node needs an explicit isolation fact. Do not box every concern or duplicate the node label as a boundary title.+- Relationship labels are semantic data. When one collides, move the label, adjust the route or spacing, then shorten the wording while preserving meaning. Omit only wording that is already fully implied by both endpoints and contains no protocol, action, direction, synchronous/asynchronous behavior, or cross-boundary mechanism. Preserve every meaningful label; deleting it is not a geometry repair. If a relationship starts unlabeled because its endpoints fully imply it, explain why the wording is redundant; this is a semantic authoring choice, not a geometry repair.++## Layout and routing++- Place Architecture nodes from connectivity before assigning coordinates: lay the main interaction path in order, place a branch beside the node it actually connects to, and place a shared store beside its main readers/writers. A category row (all runtimes, then all workers, then all stores) is useful only when the actual edges also follow it. Keep each tightly connected neighborhood together; give real return paths a clear outside corridor. Mentally trace every relationship across the proposed boxes before writing: if an unrelated node or another neighborhood blocks it, move the connected neighborhood now. The router chooses paths around fixed boxes; it does not rearrange a poor node layout. Choose the main path by the reader’s task, not by component category or the longest graph path. Keep a second data-processing chain in its own consistent reading order; place its scheduler beside the stage it drives. Do not move the main actor to a distant row to make room for a background worker. This is part of writing the first JSON, not an extra planning document or tool pass.+- Treat the standalone desktop viewer as a first-screen artifact by default, not a shallow strip. Generate one responsive artifact for laptops and external displays, preserving the authored SVG/viewBox, proportions, semantic geometry, and normal document flow. Start the first meaningful row near the canvas origin and use real content rows to create vertical rhythm; empty leading rows only enlarge the canvas and shrink the drawing. Keep the diagram panel and necessary conclusion cards balanced across wide and tall desktops. For a fresh Architecture, omit `meta.viewBox` by default so the renderer measures the real content and declares intrinsic-height Reader behavior. Author a fixed viewBox only when the user supplied fixed geometry or measured evidence shows it is necessary and the resulting text remains comfortably readable.+- For a medium Architecture, encode one obvious main path, but let it step across multiple rows when one horizontal rail would create a shallow strip, long empty corridors, or force semantic compression. Put short branches above or below their nearest hub. Start with automatic routes. Leave main-path `fromSide` / `toSide` unset so the router can align endpoints across different node heights. Pin a side only for a necessary branch or return constraint, such as a return edge on the outer side of a hub. Reserve `via`, `channelX`, `channelY`, and label-position controls for measured geometry. Never make unrelated orthogonal segments share the same axis for 8px or more; keep nonzero segments at least 8px and interior turns at least 16px.+- Before writing, apply `6.5px × ASCII units + 21px`, counting each CJK character as two units, to every labeled connection on the main path. Treat the result as that edge's minimum clear gap, never as one fixed gap shared across the row. Increase the gap or choose a clear segment when the budget does not fit; do not wait for a predictable label-route collision.+- Spacing means clear gap, not center distance. For a relationship label, clear gap must exceed its measured mask width; follow the label-preserving repair order.+- Architecture sublabels render at a preferred 9px before responsive projection. Size each component for that preferred size (`5.4px × text units + 8px`, counting each CJK character as two units) instead of relying on shrink-to-fit. If a supporting phrase would make the node disproportionately wide, keep the node's exact role or protocol concise and preserve the supplementary fact in a guided-view note or conclusion card. Never remove a responsibility, protocol, or boundary fact just to shorten text.+- Never accept an edge crossing an unrelated opaque node, an ambiguous shared corridor, or a relationship label masking another route.+## Repository-backed first draftWhen the diagram reflects a real repository, finish the evidence shape while inspecting source, not after validation fails. Copy the credential-free origin returned by `git remote get-url origin` without converting its transport or path, and record the full 40-character commit, add `meta.repository`, and attach at least one inspected `sources` entry to every key semantic node. Use only real repository-relative files and line numbers; source references are evidence, never decoration. The minimum shape is:@@ -13,27 +33,20 @@ When the diagram reflects a real repository, finish the evidence shape while insFor an SSH origin, an unsupported forge, or intentionally local-only source links, set `meta.repository.link_mode` to `"local-only"` and retain `url` and `revision`. Web links require a supported GitHub/Gitee HTTPS origin. Local-only disables web hyperlinks while preserving local identity and source verification.-Keep `<repo-root>` from source inspection and pass it to the first `finalize` call. Choose the diagram's abstraction using Composition and meaning below; retain required facts and evidence at that level.+Keep `<repo-root>` from source inspection and pass it to the first `finalize` call. Choose the diagram's abstraction using Composition and meaning; retain required facts and evidence at that level.A source reference proves only the implementation visible at that location. When separate files or locations establish materially different relationships, protocols, lifecycle transitions, persistence behavior, or conclusion-card claims, attach those inspected locations to the relevant semantic node. Let the real claims determine the references; never target a total reference count or reuse one citation as a proxy for evidence it does not contain.## Field constraints before writing-Examples demonstrate valid field shape. Before choosing a different boundary kind or writing a guided-view note, inspect `properties.boundaries.items` in `schemas/architecture.schema.json` and `$defs.guidedViews` in `schemas/common.schema.json`. Use their actual enums and length limits. Keep longer evidence in a conclusion card; do not remove the underlying fact to fit a note. Finished showcase examples may contain measured route repairs; transfer their semantic shape, then follow the automatic-routing first-draft rule below.+Examples demonstrate valid field shape. Before choosing a different boundary kind or writing a guided-view note, inspect `properties.boundaries.items` in `schemas/architecture.schema.json` and `$defs.guidedViews` in `schemas/common.schema.json`. Use their actual enums and length limits. Keep longer evidence in a conclusion card; do not remove the underlying fact to fit a note. Finished showcase examples may contain measured route repairs; transfer their semantic shape, then follow the automatic-routing first-draft rule in Layout and routing.-## Composition and meaning+## Presentation defaults-- For Architecture, default to a system overview unless the user requests a narrower mechanism, module map, or deployment topology. Lead with the main user journey and keep necessary branches close. Group cooperating implementation roles into accurately named subsystems; a group may contain multiple processes without implying they are one process. Expose a separate role or interaction when combining it would hide a requested mechanism or an important boundary. Retain secondary and opt-in capabilities as concise sourced notes by default; draw their path when needed to understand the main journey or a requested boundary. Preserve their role and trust conditions in either form. Name a deliberately narrower scope in the title rather than silently omitting it.-- Choose abstraction by the reader's question: would combining these responsibilities mislead the reader about the requested behavior, control ownership, trust, lifecycle, or persistence? If so, keep them separate; otherwise use an accurately named overview node with supporting labels and source references. Keep a behavior-changing condition visible on its affected node or relationship: an approval, authorization, or state-transition gate must not look unconditional while its qualifier appears only in a card. Separate source files, classes, protocols, or internal services do not by themselves require separate nodes. For example, an overview may show one local HTTP / WebSocket service; a transport-mechanism diagram may expand it. A cloud relay and a local decrypting bridge stay distinct when the remote trust boundary matters.-- Cover the requested meaning, with evidence for every claim. An overview need not enumerate every implementation role discovered during source reading. Put useful supporting facts in sublabels or concise cards; expand a subsystem in a focused diagram when its mechanism is requested. Guided views focus existing topology and do not collapse a crowded default overview. Add `meta.views` or cards only for a real reader question, with no quota.-- Let the requested question and source facts determine node and relationship counts; never target a number. Choose scope and abstraction before routing. Once authoring or repairing an agreed detailed graph, preserve its required roles, relationships, meaningful labels, and evidence; geometry failures do not authorize silently reducing that scope.-- When correcting an authored overview's abstraction, map every affected role, relationship direction, protocol, boundary, and source reference to its surviving node or relationship before regrouping. Carry the inspected references for each retained claim onto the relevant surviving component; a citation proving process startup does not also prove its message protocol. Check that requested meaning and evidence still have a home. User-supplied or agreed topology stays fixed; fewer routes alone do not justify merging.-- A boundary is evidence, not decoration. Use it when it communicates a real trust, runtime, process, ownership, or persistence boundary; a boundary around one node needs an explicit isolation fact. Do not box every concern or duplicate the node label as a boundary title.- Omit `meta.visual_preset` by default so every diagram opens in `classic`, regardless of whether its resolved color mode is light or dark. Switching Light / Dark preserves the current preset. Set `signal-flow`, `blueprint`, or `editorial` only when the user explicitly requests that visual style.- Omit `meta.subtitle` by default. Never invent a subtitle that restates the title, nodes, or cards; include one short supporting line only when the user explicitly asks for it.- Omit `meta.legend` for the truthful `auto` default. When needed, use only `mode: auto|all|hidden` and renderer-supported `entries.<kind>.label|visible`; labels never change semantics.- Component types are `frontend`, `backend`, `database`, `cloud`, `security`, `messagebus`, and `external`. Components do not accept a `variant` field. Relationship variants are `default`, `emphasis`, `security`, and `dashed`; when an optional component must be visible, mark it in the component label and use a dashed relationship instead.-- Relationship labels are semantic data. When one collides, move the label, adjust the route or spacing, then shorten the wording while preserving meaning. Omit only wording that is already fully implied by both endpoints and contains no protocol, action, direction, synchronous/asynchronous behavior, or cross-boundary mechanism. Preserve every meaningful label; deleting it is not a geometry repair. If a relationship starts unlabeled because its endpoints fully imply it, explain why the wording is redundant; this is a semantic authoring choice, not a geometry repair.- Omit `meta.engineering_profile` by default. Region, cluster, and security boundary wording do not by themselves enable it. Enable `deployment-ownership` only when the user explicitly asks for a production deployment topology, ownership handoff, or fail-closed deployment review and the source facts are known. Once enabled, must not remove the engineering profile merely to pass validation; repair the facts or report the diagnostics truthfully.## Language and identity@@ -47,21 +60,14 @@ Examples demonstrate valid field shape. Before choosing a different boundary kinSet required `meta.output` to a portable POSIX-relative `.html` path, such as `reports/diagram.html`. It resolves from the working directory and must remain inside it. An explicit native CLI output may be elsewhere but does not replace this authored contract. See [Output path contracts](delivery-contract.md#output-path-contracts) for native Windows paths, aliases, and long filenames.-## Layout and routing+## Reader and routing reference-- Treat the standalone desktop viewer as a first-screen artifact by default, not a shallow strip. Generate one responsive artifact for laptops and external displays, preserving the authored SVG/viewBox, proportions, semantic geometry, and normal document flow. Start the first meaningful row near the canvas origin and use real content rows to create vertical rhythm; empty leading rows only enlarge the canvas and shrink the drawing. Keep the diagram panel and necessary conclusion cards balanced across wide and tall desktops. For a fresh Architecture, omit `meta.viewBox` by default so the renderer measures the real content and declares intrinsic-height Reader behavior. Author a fixed viewBox only when the user supplied fixed geometry or measured evidence shows it is necessary and the resulting text remains comfortably readable.- Let `finalize` run the real browser check at 1440×900, 1600×1000, 1920×1080, and 2048×1320. Require zero horizontal overflow. Prefer full first-screen containment only when the complete diagram stays comfortably readable. The 6px projected-text check is a hard failure floor, not a layout target; at 1440px, aim for ordinary context text around 7.5px or larger. If semantic completeness needs more room, add meaningful vertical rows and use Reader-declared vertical page scroll with an intrinsic-height diagram instead of merging responsibilities, dropping evidence, or squeezing typography. Repair every other overflow by removing genuinely redundant content or compacting spacing before shrinking nodes, labels, or the main panel. Never counterfeit a pass with `overflow: hidden`, clipped content, an internal diagram scroller, stretched SVG height, or smaller typography. See [Automated browser evidence](delivery-contract.md#automated-browser-evidence) for the authoritative rule.-- Architecture sublabels render at a preferred 9px before responsive projection. Size each component for that preferred size (`5.4px × text units + 8px`, counting each CJK character as two units) instead of relying on shrink-to-fit. If a supporting phrase would make the node disproportionately wide, keep the node's exact role or protocol concise and preserve the supplementary fact in a guided-view note or conclusion card. Never remove a responsibility, protocol, or boundary fact just to shorten text.- If the largest viewport still has a conspicuous empty lower band at the viewer's width cap, redistribute authored Y positions and increase the viewBox height proportionally; do not add filler copy or decorative cards.-- Spacing means clear gap, not center distance. For a relationship label, clear gap must exceed its measured mask width; follow the label-preserving repair order.-- Place Architecture nodes from connectivity before assigning coordinates: lay the main interaction path in order, place a branch beside the node it actually connects to, and place a shared store beside its main readers/writers. A category row (all runtimes, then all workers, then all stores) is useful only when the actual edges also follow it. Keep each tightly connected neighborhood together; give real return paths a clear outside corridor. Mentally trace every relationship across the proposed boxes before writing: if an unrelated node or another neighborhood blocks it, move the connected neighborhood now. The router chooses paths around fixed boxes; it does not rearrange a poor node layout. Choose the main path by the reader’s task, not by component category or the longest graph path. Keep a second data-processing chain in its own consistent reading order; place its scheduler beside the stage it drives. Do not move the main actor to a distant row to make room for a background worker. This is part of writing the first JSON, not an extra planning document or tool pass.-- For a medium Architecture, encode one obvious main path, but let it step across multiple rows when one horizontal rail would create a shallow strip, long empty corridors, or force semantic compression. Put short branches above or below their nearest hub. Start with automatic routes. Leave main-path `fromSide` / `toSide` unset so the router can align endpoints across different node heights. Pin a side only for a necessary branch or return constraint, such as a return edge on the outer side of a hub. Reserve `via`, `channelX`, `channelY`, and label-position controls for measured geometry. Never make unrelated orthogonal segments share the same axis for 8px or more; keep nonzero segments at least 8px and interior turns at least 16px.-- Before writing, apply `6.5px × ASCII units + 21px`, counting each CJK character as two units, to every labeled connection on the main path. Treat the result as that edge's minimum clear gap, never as one fixed gap shared across the row. Increase the gap or choose a clear segment when the budget does not fit; do not wait for a predictable label-route collision.- Automatic routes own their endpoint sides. A relationship does not accept a `side` field; use `fromSide` or `toSide` when a deliberate branch or return direction is needed. Each endpoint side is a direction contract: the first and final segment must leave/enter perpendicular to that side.- Estimate the resolved Architecture content width before the first write. At 1440px, legacy, unknown, and authored-viewBox artifacts use the conservative 930px diagram budget. A fresh automatic wide Architecture with the recognized Reader contract instead reports its declared budget and cap in `composition.desktopReadability`; use that evidence before changing a semantic node or relationship label. Keep ordinary context text comfortably above the 6px hard floor by adding meaningful rows or using intrinsic-height layout, not by dropping meaning or designing to a fixed viewBox width.- Automatic Port Spread is a default renderer behavior for architecture, workflow, data-flow, and lifecycle. It skips single relationships and explicit `via`, `channelX`, `channelY`, `labelAt`, or non-`auto` routes. Near parallel ports use an outside bridge so automatic routing cannot create a sub-8px segment or sub-16px interior turn. Architecture separately keeps unobstructed facing automatic ports (`left`/`right` or `top`/`bottom`) on one shared axis when their offset is under 16px and both ports retain corner clearance. If exactly one endpoint was spread, only the unshared endpoint may move onto that axis; if both endpoints were spread, keep the outside bridge so competing ports remain distinct.- In showcase Architecture, an explicit route must stay proportionate to the shortest legal orthogonal route. `composition/excessive-route-detour` reports the actual length, obstacle-aware shortest length, ratio, and empty-space excursion. Remove an unnecessary `via` or move the diagnosed corridor inward; do not enlarge the canvas to legitimize the detour. Related edges may share one deliberate outer bus.-- Never accept an edge crossing an unrelated opaque node, an ambiguous shared corridor, or a relationship label masking another route.## Type-specific defaultsdiff --git a/docs/gallery.html b/docs/gallery.htmlindex ab889865..ac44b17c 100644--- a/docs/gallery.html+++ b/docs/gallery.html@@ -771,6 +771,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -897,6 +901,16 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": true,+ "emptyTopPx": 85,+ "emptyTopRatio": 0.117,+ "occupiedTop": 85,+ "viewBoxTop": 0,+ "canvasHeight": 728,+ "typicalNodeHeight": 62,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "recognized-declared-wide","readerContract": "declared-wide-v1",@@ -1028,6 +1042,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1154,6 +1172,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1344,6 +1366,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1501,6 +1527,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1627,6 +1657,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1783,6 +1817,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1976,6 +2014,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -2102,6 +2144,10 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -2259,6 +2305,16 @@ receipt 99 checks / 11 artifacts / deterministic hashes</pre>}]},+ "leadingSpace": {+ "measured": true,+ "emptyTopPx": 110,+ "emptyTopRatio": 0.187,+ "occupiedTop": 110,+ "viewBoxTop": 0,+ "canvasHeight": 588,+ "typicalNodeHeight": 60,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "recognized-declared-wide","readerContract": "declared-wide-v1",diff --git a/docs/gallery/manifest.json b/docs/gallery/manifest.jsonindex 8ad259ee..4c310db6 100644--- a/docs/gallery/manifest.json+++ b/docs/gallery/manifest.json@@ -123,6 +123,10 @@}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -249,6 +253,16 @@"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": true,+ "emptyTopPx": 85,+ "emptyTopRatio": 0.117,+ "occupiedTop": 85,+ "viewBoxTop": 0,+ "canvasHeight": 728,+ "typicalNodeHeight": 62,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "recognized-declared-wide","readerContract": "declared-wide-v1",@@ -380,6 +394,10 @@"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -506,6 +524,10 @@"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -696,6 +718,10 @@}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -853,6 +879,10 @@}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -979,6 +1009,10 @@"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1135,6 +1169,10 @@}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1328,6 +1366,10 @@}]},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1454,6 +1496,10 @@"crossings": [],"detours": []},+ "leadingSpace": {+ "measured": false,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "legacy-930","readerContract": "declared-wide-v1",@@ -1611,6 +1657,16 @@}]},+ "leadingSpace": {+ "measured": true,+ "emptyTopPx": 110,+ "emptyTopRatio": 0.187,+ "occupiedTop": 110,+ "viewBoxTop": 0,+ "canvasHeight": 588,+ "typicalNodeHeight": 60,+ "reviewSuggested": false+ },"desktopReadability": {"budgetBasis": "recognized-declared-wide","readerContract": "declared-wide-v1",