CAI-8463: Fix copy text capitalization consistency on samples page

[mkesavan13]

COMPLETES CAI-8463

This pull request addresses

Copy text inconsistency on the samples page (widgets-samples/cc/samples-cc-react-app/src/App.tsx). Two UI strings used inconsistent capitalization that did not match the surrounding copy style.

by making the following changes

• Updated the page heading from "Contact Center Widgets in a React app" to "Contact Center Widgets in a React App" — "App" capitalized for consistency with surrounding Title Case labels.
• Updated the access token label from "Your access token: " to "Your Access Token: " — Title Case applied for consistency with adjacent fieldset legends and labels.

No data-testid, id, value, handler, or state was changed — only the two display text nodes.

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios were tested

• The testing is done with the amplify link
• Visual inspection: verified both strings now display with consistent Title Case capitalization on the samples page.
• No functional logic was changed; only display copy was updated.
• Source inspection of App.tsx diff confirms only the two planned text-node edits with zero functional identifier drift (AC-1).

External Validation Required

ID	Requirement	Scope	Status
AC-1	All pre-widget-init copy text in the samples CC React app (h1 heading, fieldset legends, select/checkbox/button labels) uses one consistent Title Case convention: the sentence-cased h1 tail 'in a React app' is normalized to 'in a React App' and the inline label 'Your access token:' to 'Your Access Token:' (trailing space preserved), with no data-testid, id, value, handler, or state changed.	both	External validation pending PR review

AC-1 details: The tsc compile gate (UT-1) only guards that the JSX text edits do not break the build and that no functional identifier drifted; it cannot assert copy casing. The core casing-consistency criterion is verified by config/source inspection of the App.tsx diff during PR review (package has no unit-test runner), confirming the h1 and access-token literals now match the surrounding Title Case labels.

Source reference: CAI-8463 summary/description: 'Samples page copy text consistency' — mixed case chars in labels on the samples page before widgets init must be fixed.

Verification limitations

Gate 1 compile: SKIPPED — skipped-missing-command — selected manifests do not declare commands.compile (missing .sdd/manifest.json).

Gate 2 unit tests: SKIPPED — skipped-missing-command — selected manifests do not declare commands.unit-test (missing .sdd/manifest.json). The samples package (widgets-samples/cc/samples-cc-react-app) exposes no unit-test runner (build via tsc/webpack/eslint only); no unit runner can validate copy casing programmatically.

Neither gate is described as passed. AC-1 unit validation is: Not validated — Gate 2 skipped.

Contract Discovery Warnings

• Manifest reference discovery capped at 100 strings.

The GAI Coding Policy And Copyright Annotation Best Practices

• GAI was not used (or, no additional notation is required)
• Code was generated entirely by GAI
• GAI was used to create a draft that was subsequently customized or modified
• Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
• Tool used for AI assistance (GitHub Copilot / Other - specify)
  • Github Copilot
  • Other - Claude Code (Anthropic)
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

Checklist before merging

• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the testing document
• I have tested the functionality with amplify link

---

Make sure to have followed the contributing guidelines before submitting.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-739.d1b38q61t1z947.amplifyapp.com

[bhabalan]

Closing to allow JiraToPr to open a fresh PR for CAI-8463.