Repository navigation
style(ui): console text follows official sub2api - #222
Merged
Merged
Conversation
The console theme's text now follows how official sub2api renders it, while keeping the console layout, surfaces, brand accent and stacked tables: - Font: the official system-ui stack (Microsoft YaHei UI on zh-CN Windows), no web fonts; Geist / Geist Mono files and the runtime MiSans stylesheet are removed. Mono only for identifiers and code (official stack + CJK fallbacks). - Sizes and weights: official text-sm 14/20, text-xs 12/16; headers 12/500 (usage tables) or 14/500 (TablePageLayout tables), uppercase only on headers and sidebar section titles; KPI values 20/700; no negative tracking. - Colour: class-driven official Tailwind greys (#111827 / #374151 / #4b5563 / meta #616977; dark #f3f4f6 / #d1d5db / #a4abb6), meta clamped to 4.5:1 on every neutral fill; official figure and tag colours return (cost, cache, account cost, latency, group / type / billing tags). The two-tone data text roles are deleted; dark selected rows lift their meta greys. - Layout: no horizontal overflow in Chinese at 1280-1920 (API key and user wrap recipes extended, accounts label gutter 50/56px, status header width); English TablePageLayout headers 12px and wrapping, recipes below 1680px. - Accounts name column measures names at 14px. Owner request 2026-10-01: text still hard to read, follow official sub2api. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
HTExplicit
force-pushed
the
ui/text-official
branch
from
October 7, 2026 08:12
7e46720 to
fae7072
Compare
HTExplicit
added a commit
that referenced
this pull request
Oct 7, 2026
The deployment path still carried retired acceptance, rollback, resource-request and plugin-era controls, while console typography needed to be brought up to date with the current upstream style. This integrates the remaining authorized takeover work after the reasoning repair in #252. - Integrates #253, #254, #255 and #222 while retaining their commit ancestry. Removes stale release scaffolding and deployment template settings; preserves every existing migration SQL file. - Production Deploy accepts only `release_tag` and `confirmation=DEPLOY`, sends `deploy <immutable-image>`, and retains standard OCI provenance and fixed SSH/environment controls. Both automation callers and historical-run deduplication match it. - Migration 274 deletes only validated, soft-deleted release-acceptance keys and their usage/dedup rows, removes the two acceptance columns, and leaves ordinary keys and diagnostic logs. The matching application no longer reads those columns. Older images cannot be deployed after 274; failures require a forward fix. - Uses upstream system fonts, sizes and readable semantic text colors without dropping table columns. Fixes the TLS empty-state color and whole-badge/word wrapping, and normalizes the audit helper's LF bytes without semantic changes. - Removes the image-side skill-registry directory after the host mount and retired runtime configuration were removed. Validation: reuse the component branches' directly affected tests and source-identical UI matrix; normal required checks run on this final integration tree. The only integration conflicts were the migration CI selector and retired documentation/notices; the resolved selector retains the new PostgreSQL migration fixture and live migration tests. All existing migration SQL is unchanged. Entry-point Bash syntax and diff checks pass. The simplified host tool has completed a successful unchanged-image `.12` redeploy, preserving environment/resources and other containers. Host config retirement also passed with a new complete backup retained. UI localhost fake-data validation sampled 7,728 normal text/input/placeholder elements across 36 after states, with no sample below 4.5:1; account tables fit at 1280/1440/1920 in both languages/themes. Before screenshots block external fonts and show their fallback stack. No real model call or live upstream ID-less-item acceptance test was performed.
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.
The console theme uses the official Sub2API system font stack and normal text scale, while keeping the current controls, layout, surfaces, accent and stacked account table.
The original owner-approved comparison on 2026-10-01 found that smaller Geist/MiSans type, mixed CJK/Latin stroke weights and widespread monospace were making dense pages harder to read. This update keeps that typography decision and rebases it onto the current main branch.
Validation on the final frontend tree:
This verification uses invented local fixtures. Production rollout and the required integration CI are coordinated separately.