fix(tessl): emit per-step dashboard progress during Modal scans - #119
Merged
Conversation
Supersedes the standalone slice 54 stub so dashboard ≥80 vs Rest triage stays one Wave J contract with GWT-42.11–42.16 and updated trackers.
Bulk running placeholders made all five Tessl rows look frozen for the whole group run even while Lint and Review were completing. Tessl rows now update step-by-step via on_scanner_progress; dashboard labels blocked/stale states.
code-review-graph reviewOverall risk: 0.55 (MEDIUM) — 3 changed function(s)/class(es), 9 affected flow(s), 1 test gap(s) Risk-scored changes
Affected execution flows
Test gaps
Token savings: this graph-backed report used ~75,829 fewer tokens (~89%) than reading every changed file in full (estimated, chars/4 approximation). Powered by code-review-graph — local-first analysis; no code leaves the CI runner. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fix(tessl): Tessl rows no longer bulk-insert asrunningat group start; Lint and Review (Quality) persist step-by-step viaon_scanner_progress; dashboard adds pills forblocked,stale,interrupted,timed_outdocs(changelog): merge duplicate### Fixedheading under[Unreleased]docs(plan): blend quality tabs into slice 42 as A14–A15 (plan-only delta; supersedes standalone slice 54 stub — implementation is a follow-up onslice/42-quality-score-tabs)Test Results
pytest)prototypes/dc-dashboard)cli/)Quality Gates
./scripts/quality-gates.sh— passed (ruff, mypy, xenon, vulture, bandit, gitleaks, markdownlint, shellcheck)Test plan
modal deploy sandbox/scan_app.pytripwire scan <skill-path> --forceand confirm Tessl rows appear sequentially (only active step shows Running)blockedpill for Eval when Scenario Generation has not populatedevals/Checklist
./scripts/quality-gates.shpasses locallyMade with Cursor
Complexity
Automatically refreshed by CI for product-code changes.
sandbox/)cli/)Functions above the JavaScript threshold