Skip to content

Rename stale industrial dashboard and workflow wording#218

Open
ProfRandom92 wants to merge 1 commit into
mainfrom
repo/rename-stale-industrial-actions-wording
Open

Rename stale industrial dashboard and workflow wording#218
ProfRandom92 wants to merge 1 commit into
mainfrom
repo/rename-stale-industrial-actions-wording

Conversation

@ProfRandom92
Copy link
Copy Markdown
Owner

Summary

  • Rename the stale GitHub Actions workflow display name from Industrial Validation to Replay Validation
  • Update dashboard-facing Industrial / Enterprise / Showcase copy to replay-validation and review wording
  • Rename dashboard package metadata only, without dependency or behavior changes

Validation

  • npm run layout
  • npm run typecheck
  • npm run validate
  • npm run build
  • pytest -q

Scope

Wording and metadata cleanup only. No validation logic, Python behavior, fixtures, artifacts, generated dist output, scripts, or dependencies changed.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 diagnosticsfocused 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>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
<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 diagnosticsfocused on retained anchors, validation evidence, CI artifacts, and explicit scope boundaries.</p>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant