docs: standardize AgentV brand casing#1624
Merged
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
c67b337
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://94169992.agentv.pages.dev |
| Branch Preview URL: | https://av-g3wn-brand-casing.agentv.pages.dev |
christso
force-pushed
the
av-g3wn-brand-casing
branch
from
a75baeb to
c67b337
Compare
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
1 participant
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.
Summary
Public brand copy now consistently renders as
AgentVacross the landing page wordmark, Dashboard shell/default app name, generated results report chrome, public docs, and example-facing prose.Guardrail: this intentionally leaves identifiers/routes/env vars/package names/import paths/CSS classes/test IDs/config keys/CLI commands unchanged. The only code-string changes are user-facing display defaults and the test expectations for those strings.
Verification
git fetch origin && git merge-base --is-ancestor origin/main HEAD->ancestor:0bun installbun test apps/cli/test/commands/results/studio-config.test.ts-> 23 pass, 0 failbun run lintbun --filter @agentv/core build && bun --filter @agentv/sdk build && bun --filter agentv buildbun --filter @agentv/web buildafter rebasebun --filter @agentv/dashboard test && bun --filter @agentv/dashboard build-> 147 pass, 0 fail; build passedagent-browseragainst local previews: landing page, Dashboard shell, Enterprise Governance docs, Coding Agents docs, and Workspace Architecture docs renderedAgentVcasing as expected.Residual Risk
The Dashboard browser smoke used the standalone Vite preview, so it validated shell rendering but not live CLI API-backed Dashboard flows; the preview logs expected API proxy
ECONNREFUSEDmessages without the CLI backend. Dashboard unit tests and production build passed cleanly after the rebase.Post-Deploy Monitoring & Validation
No additional operational monitoring required. This is a casing-only user-facing copy/docs/UI text update with no runtime contract, route, config, or API behavior change.