docs: update token badge to 10T+

[nabinchha]

📋 Summary

Updates the processed-token badge from 2.6T+ to 10T+ so the README reflects Data Designer's latest usage milestone.

🔗 Related Issue

N/A

🔄 Changes

• Update the README token badge to display 10T+ Tokens Processed.

🧪 Testing

• git diff --check passes
• Confirmed the README contains the 10T+ badge URL and no longer contains the 2.6T+ badge URL
• make test — not run (README-only change with no executable logic)
• Unit tests: N/A — no testable logic
• E2E tests: N/A — no testable logic

✅ Checklist

• Follows commit message conventions
• Commits are signed off (DCO)
• Architecture docs: N/A — no architecture changes

[greptile-apps]

Greptile Summary

This PR updates a single shields.io badge in README.md, bumping the displayed processed-token count from 2.6T+ to 10T+ to reflect a new usage milestone.

• The badge URL in line 5 of README.md is the only change; all other badges, links, and content are untouched.
• No executable code, tests, or configuration is affected.

Confidence Score: 5/5

This is a documentation-only change updating a single shields.io badge label; there is nothing here that could affect runtime behavior or correctness.

The change touches exactly one line in README.md, replacing the badge text from 2.6T+ to 10T+. The URL structure, color, logo, and surrounding content are all preserved correctly, and no code or configuration is modified.

No files require special attention.

Important Files Changed

Filename	Overview
README.md	Single-line update to the shields.io token badge, changing the label from 2.6T+ to 10T+ Tokens Processed; no other content modified.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[README.md badge line] --> B{Token count badge}
    B -->|Before| C["2.6T+ Tokens Processed"]
    B -->|After| D["10T+ Tokens Processed"]
    D --> E[shields.io renders updated badge]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[README.md badge line] --> B{Token count badge}
    B -->|Before| C["2.6T+ Tokens Processed"]
    B -->|After| D["10T+ Tokens Processed"]
    D --> E[shields.io renders updated badge]

Loading

_{Reviews (1): Last reviewed commit: "docs: update token badge to 10T+" | Re-trigger Greptile}

[github-actions]

Code Review: PR #811 — docs: update token badge to 10T+

Summary

This PR updates a single shields.io badge in README.md, changing the processed-token milestone from 2.6T+ to 10T+. It touches 1 file, +1/−1 line, and contains no executable logic.

Verified against the repository:

• origin/main still displays 2.6T+ in the README badge (line 5), so this is a genuine, non-duplicate change.
• The PR branch (codex/update-token-badge-10t) correctly changes only the badge label; the rest of the badge URL — scheme, Tokens_Processed label, 76b900 (NVIDIA green) color, and logo=nvidia&logoColor=white query params — is preserved intact.

Findings

Correctness

• ✅ The edit is surgical and correct: only the 2.6T+ → 10T+ substring changes within the badge URL. The badge URL remains well-formed (https://img.shields.io/badge/10T+-Tokens_Processed-76b900.svg?...).
• ✅ No stray 2.6T+ references remain in the README (grep confirms 0 occurrences on the branch, 1 occurrence of 10T).

Style & Conventions

• ✅ Commit message follows the project's docs: conventional-commit prefix and is DCO signed-off.
• ✅ No trailing-whitespace or diff issues (git diff --check passes per PR description).

Testing

• ✅ Appropriately skips make test — this is a documentation-only change with no executable logic, and the testing checklist correctly marks unit/E2E as N/A. Consistent with the CI policy of not linting docs-only changes.

Performance / Security

• N/A — no code, dependencies, or runtime behavior affected.

Suggestions (non-blocking, optional)

• Verify the underlying claim. The badge asserts a marketing/usage figure (10T+ tokens processed). A reviewer with visibility into the source metric should confirm 10T+ is the intended, accurate current figure before merge, since the badge is purely a hardcoded label with no automated source of truth.
• Note on maintainability: this figure is manually maintained and will drift over time. Not actionable for this PR, but if these updates recur frequently, a dynamic/endpoint-backed shields.io badge could remove the need for repeated manual edits. Out of scope here.

Structural Impact

No structural impact analysis file (/tmp/structural-impact-811.md) was present for this PR. Given the change is a single-line README badge edit with zero impact on the data_designer namespace, import direction, package layering, or any code path, structural risk is none.

Verdict

Approve (LGTM). This is a clean, correct, minimal documentation change that does exactly what it describes. No code-quality, correctness, performance, security, or test-coverage concerns. The only pre-merge action worth taking is an out-of-band confirmation that 10T+ is the accurate intended figure.

Note: Per CI reviewer constraints, this review does not post an approval or change-request on the PR itself; it is advisory only.