T-KX4V-agent-manager-rename

State: planning/proposed · Impact: high · Complexity: small

Goal

The agent-pants experience reads “Components” everywhere a user looks — nav label, pane titles, tree header, manual — while the milestone renames the product surface to Agent Manager. This task does the rename in every user-facing spot so the rest of the milestone (editor layout, preview pane, palette) lands under the name it will ship with, instead of drifting one screen at a time.

Today

Location	Role today
`solutions/determined/experiences/agent-pants/app/plugins/register.ts#defineExperience`	Sets `title: 'Agent Pants'` (the experience identity, kept) and the rail nav `label: 'Components'` (renamed); a comment calls the note screen “the Components screen”
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/index.vue`	`PaneContent region="secondary" title="Components"` labels the tree pane
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/build.vue`	Same `PaneContent region="secondary" title="Components"`
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/notes/[...path].vue`	Same `PaneContent region="secondary" title="Components"`
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/plugins/[...path].vue`	Same `PaneContent region="secondary" title="Components"`
`solutions/determined/experiences/agent-pants/app/components/ApComponentTree.vue`	`NodeTreePane label="Components"`; search input `aria-label="Search components"` and `placeholder="Search components…"`
`solutions/determined/experiences/agent-pants/docs/*.md`	Six manual chapters (`getting-started`, `vault-layout`, `frontmatter-reference`, `authoring`, `publishing`, `current-limits`) describe “the Components rail” and “components” as the user-facing noun
`solutions/determined/products/agent-pants/tests/e2e/authoring.e2e.ts`	A comment reads “the Components header carries a Rescan of its own”

Proposed

Every user-facing string in the experience says “Agent Manager” (or a tree-header-sized form of it, e.g. a shorter rail label where “Agent Manager” would not fit) instead of “Components”: the rail nav entry, the four PaneContent titles, the tree’s accessible label, the search placeholder, and the six manual chapters. defineExperience.title stays 'Agent Pants' — the experience identity is unchanged; only the human-facing name of what it does changes. Comments that named the old screen are corrected, not left stale. grep -ri components in the experience directory afterward matches only code identifiers (component/composable/type names, filenames) and inline code spans quoting those identifiers — no remaining prose or label uses the word.

Approach

register.ts: change the rail label from 'Components' to the chosen Agent Manager label; fix the stale “Components screen” comment. Exact label wording (full “Agent Manager” vs. a shortened rail form) is decided here, then reused verbatim everywhere else.
index.vue, build.vue, notes/[...path].vue, plugins/[...path].vue: change each PaneContent title="Components" to the same label from step 1.
ApComponentTree.vue: change NodeTreePane label, the search aria-label and placeholder to match (e.g. “Search Agent Manager…”, or a shorter “Search skills…” if that reads better — decide alongside step 1).
Rewrite the six docs/*.md chapters in place, replacing “Components rail” / “components” as the product noun with “Agent Manager” wording, without narrating the rename (“used to be called”).
Fix the stale comment in authoring.e2e.ts; check the other e2e specs under solutions/determined/products/agent-pants/tests/e2e/ for any user-facing string assertion that targeted the old label (none found in the initial sweep; re-check when this task is picked up).
Verify: grep -rni components solutions/determined/experiences/agent-pants and confirm every remaining hit is a code identifier, filename, or inline-code reference to one; run moon run product-agent-pants:check and the product’s Playwright projects.

Areas

Area	Note
`solutions/determined/experiences/agent-pants/app/plugins/register.ts`	Rail nav label; fix stale comment
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/index.vue`	`PaneContent` title
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/build.vue`	`PaneContent` title
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/notes/[...path].vue`	`PaneContent` title
`solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/plugins/[...path].vue`	`PaneContent` title
`solutions/determined/experiences/agent-pants/app/components/ApComponentTree.vue`	Tree label, search `aria-label`/`placeholder`
`solutions/determined/experiences/agent-pants/docs/*.md`	Rewrite “Components” prose to Agent Manager wording
`solutions/determined/products/agent-pants/tests/e2e/authoring.e2e.ts`	Fix stale “Components header” comment

Acceptance criteria

AC-1: The rail nav entry and all four PaneContent titles show the same new label; none reads “Components”.
AC-2: ApComponentTree.vue’s tree label, search aria-label and placeholder no longer say “components”.
AC-3: grep -rni components solutions/determined/experiences/agent-pants returns only code identifiers, filenames, or inline-code references to them — no prose or UI copy.
AC-4: defineExperience.title in register.ts is still exactly 'Agent Pants'.
AC-5: None of the six docs/*.md chapters says “Components” as the product name.
AC-6: moon run product-agent-pants:check and the agent-pants Playwright projects pass.

Out of scope

The tree’s structural behavior (folder icons, filters, add affordance) — T-0XMP-tree-typed-folders-filter-add.
Storybook mocks of the renamed workbench — T-I71M-stories-agent-manager-workbench.
Any change to defineExperience.id or the route segment apps/agent-pants — the URL and experience id are not part of this rename.

Dependencies

none

Discovery context

From the user’s Agent Manager planning request of 2026-09-07 and the assessment solutions/agent-pants/docs/vault/design/workflow-and-ux-assessment.md, whose naming-and-tree- navigation section starts from the same observation: the experience is called “Components” everywhere while the milestone’s own goal names it Agent Manager. Member of M-BMFD.

← Back to Tasks