Skip to content

De-jargon user-facing output; align CLI/CI naming with the deploy grammar - #910

Merged
efizzybot merged 1 commit into
t3/improve-deploy-output-clarityfrom
t3/output-grammar-followups
Nov 19, 2026
Merged

efizzybot merged 1 commit into
t3/improve-deploy-output-clarityfrom
t3/output-grammar-followups

Conversation

@efizzybot

Copy link
Copy Markdown
Collaborator

Stacked on #908 — applies the remaining audit findings (#9, #10, #11, #13, #14) from the output-quality audit.

CLI

  • Jargon → concrete nouns in --help summaries and user-facing errors: no more "full train", "the lockfile + pointer ride the train", "image build/push leg"; partial publishes now name what failed ("the image push and boot gate failed", not "leg(s) failed"); bare "the registry" says FastKV where it meant one of three registries.
  • One label grammar: all publish/rollback/promote/plugin renderers use the lowercase label: value style the deploy summary introduced.
  • Explorer links everywhere: rollback and promote link their transaction on nearblocks (network-aware, carried on the wire result); bos deploy --status history links each block height.
  • "Pointer digest:" → "config fingerprint:" in every renderer that printed it.
  • Seed skips render with – (not a dim ✓) and carry their reason in a dedicated reason field — error means failure only.
  • bos login / bos logout print each warning on its own ⚠ line (login could previously concatenate up to four warnings into one breathless sentence).
  • Custody balance-skip names OutLayer, includes the real error, and states what still gates; the duplicate submit-time "Signing via" print is removed (preflight owns strategy announcements); remaining ! glyphs use the shared ⚠ grammar.

CI

  • The identical pnpm run build template command had three different step names (one above a comment denying the step exists) — now one name, comment rewritten.
  • Job display names self-describe: "Registry sentinel (cold-cache resolution)" → "Published-chain resolution check", "Process Changesets" → "Publish to npm / open version PR", "Start/Unit/Dev plane" → "… regression".
  • check-skills validate gate runs advisory until the Intent skill snippet hygiene: triage ~123 validate findings, then gate PRs on validate #298 triage clears the ~86 pre-existing findings — findings stay visible (grouped + warned + step summary) but a genuinely new regression is distinguishable from the baseline instead of the check being permanently red.

Deliberately not done (vetted during audit)

  • The framework-suite watchdog's inline tee is documented deliberate behavior (runner-death evidence must survive when the artifact upload is skipped) — left as-is.
  • Thrown error strings that chain cause-remedy with em-dashes (seed runner timeout, confirm rejections) are left: they now render inside the structured failure blocks from Redesign deploy output into phased, scannable, failure-aware blocks #908, so rewording them is low-value churn.

Also fixes the biome useTemplate lint failure from the previous run (now on #908, commit b266a34).

…mmar

CLI: --help summaries and error strings drop train/leg/pointer vocabulary
for concrete nouns; summary labels are uniformly lowercase across
publish/rollback/promote/plugin renderers; rollback and promote link their
transaction on nearblocks; publish history links each block height;
'Pointer digest:' reads as 'config fingerprint:'; seed skips render with a
dash and carry their reason in a dedicated field instead of the error
channel; login/logout print each warning on its own line instead of one
space-joined sentence; 'the registry' is named (FastKV) where it meant one
of three registries; the custody balance-skip warning names OutLayer and
says what still gates; the duplicate submit-time 'Signing via' print is
gone (preflight owns it); remaining '!' glyphs use the shared warning
grammar.

CI: one name for the identical 'build template' step across ci.yml and
regression-full.yml (and the stale comment denying the step's existence is
rewritten); job display names describe themselves (published-chain
resolution, publish-to-npm) instead of plane/leg/sentinel jargon; the
check-skills validate gate runs advisory with grouped findings until the
#298 triage clears the pre-existing baseline, so a genuinely new finding
is distinguishable from the known ~86.
@elliotBraem
elliotBraem added this pull request to stack #911 November 19, 2026 23:37
@efizzybot
efizzybot merged commit e67f955 into main Nov 19, 2026
19 of 22 checks passed
An error occurred while trying to automatically change base from t3/improve-deploy-output-clarity to main November 20, 2026 13:45
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.

2 participants