Rename stale industrial dashboard and workflow wording#218
Conversation
There was a problem hiding this comment.
Code Review
This pull request rebrands the application from "CompText Industrial Ops Console" to "CompText Replay Validation Console" by updating text in the README, package configuration, UI components, and backend templates. The feedback identifies a grammatical ambiguity in the hero section's copy where an em-dash was replaced by a comma, suggesting its restoration to maintain clarity.
| <h2 id="showcase-title">CompText V7 turns repetitive diagnostics into auditable KVTC frames.</h2> | ||
| <p className="hero-copy">A premium reviewer dashboard for deterministic, lossy token reduction over structured synthetic diagnostics—focused on retained anchors, validation evidence, CI artifacts, and clear enterprise boundaries.</p> | ||
| <div className="hero-actions" aria-label="Showcase highlights"> | ||
| <p className="hero-copy">A reviewer dashboard for deterministic, lossy token reduction over structured synthetic diagnostics, focused on retained anchors, validation evidence, CI artifacts, and explicit scope boundaries.</p> |
There was a problem hiding this comment.
The replacement of the em-dash (—) with a comma (,) in the hero copy introduces a slight grammatical ambiguity. In the original version, the em-dash clearly separated the dashboard's primary function from its list of focus areas. With a comma, the phrase 'focused on...' could be misread as modifying 'structured synthetic diagnostics' rather than the 'reviewer dashboard'. Consider using a semicolon or restoring the em-dash to maintain clarity while applying the wording changes.
| <p className="hero-copy">A reviewer dashboard for deterministic, lossy token reduction over structured synthetic diagnostics, focused on retained anchors, validation evidence, CI artifacts, and explicit scope boundaries.</p> | |
| <p className="hero-copy">A reviewer dashboard for deterministic, lossy token reduction over structured synthetic diagnostics—focused on retained anchors, validation evidence, CI artifacts, and explicit scope boundaries.</p> |
Summary
Validation
Scope
Wording and metadata cleanup only. No validation logic, Python behavior, fixtures, artifacts, generated dist output, scripts, or dependencies changed.