@tekyzinc/gsd-t 2.56.10 → 2.56.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -678,6 +678,14 @@ Rules:
|
|
|
678
678
|
7. **E2E Functional Gaps**: Review ALL Playwright specs. Do they test actual
|
|
679
679
|
behavior (state changes, data loaded, navigation works) or just check
|
|
680
680
|
that elements exist? Flag and rewrite any shallow/layout tests.
|
|
681
|
+
8. **Design Fidelity** (if .gsd-t/contracts/design-contract.md exists):
|
|
682
|
+
Open every implemented screen in a real browser. Screenshot at mobile
|
|
683
|
+
(375px), tablet (768px), desktop (1280px). Get Figma reference via
|
|
684
|
+
Figma MCP get_screenshot (or design contract images). Compare every
|
|
685
|
+
element: chart types, colors, typography, spacing, layout, component
|
|
686
|
+
states, data visualization style. Any visual deviation from the design
|
|
687
|
+
is a CRITICAL bug. 'Build shows vertical bars but design shows horizontal
|
|
688
|
+
stacked bars' is a real bug, not a style opinion.
|
|
681
689
|
|
|
682
690
|
## Exploratory Testing (if Playwright MCP available)
|
|
683
691
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tekyzinc/gsd-t",
|
|
3
|
-
"version": "2.56.
|
|
3
|
+
"version": "2.56.11",
|
|
4
4
|
"description": "GSD-T: Contract-Driven Development for Claude Code — 51 slash commands with headless CI/CD mode, graph-powered code analysis, real-time agent dashboard, execution intelligence, task telemetry, doc-ripple enforcement, backlog management, impact analysis, test sync, milestone archival, and PRD generation",
|
|
5
5
|
"author": "Tekyz, Inc.",
|
|
6
6
|
"license": "MIT",
|
|
@@ -322,7 +322,7 @@ After QA passes, every code-producing command spawns a **Red Team agent** — an
|
|
|
322
322
|
**Key Red Team rules:**
|
|
323
323
|
- **Inverted incentive**: More bugs found = more value. Zero bugs requires exhaustive proof of thoroughness.
|
|
324
324
|
- **False positive penalty**: Reporting non-bugs destroys credibility. Every bug must be reproduced with proof.
|
|
325
|
-
- **Exhaustive categories**: Contract violations, boundary inputs, state transitions, error paths, missing flows, regression, E2E functional gaps — all must be attempted.
|
|
325
|
+
- **Exhaustive categories**: Contract violations, boundary inputs, state transitions, error paths, missing flows, regression, E2E functional gaps, design fidelity (when design contract exists: render in browser, screenshot, compare pixel-by-pixel against Figma) — all must be attempted.
|
|
326
326
|
- **VERDICT**: `FAIL` (bugs found — blocks completion) or `GRUDGING PASS` (exhaustive search, nothing found).
|
|
327
327
|
- **Report**: Written to `.gsd-t/red-team-report.md`; bugs also appended to `.gsd-t/qa-issues.md`.
|
|
328
328
|
|