You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: scripts/design-conformance/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Design conformance check
2
2
3
-
Tool **3.3.0**, policy **design-conformance/1.3.0**. This is the maintained implementation of Sim's design guardrails.
3
+
Tool **3.3.1**, policy **design-conformance/1.3.0**. This is the maintained implementation of Sim's design guardrails.
4
4
5
5
From the repository root, using Bun **1.4.1** and the normal root installation:
6
6
@@ -16,7 +16,7 @@ Use the actual PR target for `--base`; it is required. The repository defaults t
16
16
17
17
-**Usage violations** identify newly introduced inputs that violate an explicit central design contract, the authoritative definition, and the permitted token/component mechanism. Fix confirmed violations through that mechanism.
18
18
-**System changes** identify edits to central definitions or this registry. Review them as changes to the design system; central authoring may introduce new styling.
19
-
-**Unchecked inputs** describe unresolved syntax or coverage limits. They do not create findings, and a clean result does not prove exhaustive conformance.
19
+
-**Unchecked inputs** describe unresolved syntax or coverage limits. They do not create findings, and a clean result does not prove exhaustive conformance. Text output identifies incomplete coverage and lists every diagnostic with its file, line, comparison side, context and reason. The CI summary includes an expandable list of the first 100 diagnostics, with long entries shortened; complete details remain in the check log and JSON report.
20
20
21
21
The ordinary command exits **0** for no findings, **1** for findings and **2** for operational failure. JSON retains `flagged: true` even during the warning-only rollout; failed reports have `flagged: null`.
`Showing ${notes.length} of ${report.unchecked.length} diagnostics. Long entries are truncated here. Full details are in the check log; these are not design violations.`,
112
+
'',
113
+
'<pre>',
114
+
...notes.map((note)=>{
115
+
consttext=uncheckedDescription(note)
116
+
constexcerpt=
117
+
text.length>1000 ? `${text.slice(0,1000)}… [truncated; see check log]` : text
118
+
/** Source text must not close the HTML block or introduce Markdown formatting. */
0 commit comments