Skip to content

chore(dashboard): remove dead platform_type UI (closes #2811)#2831

Merged
bokelley merged 1 commit into
mainfrom
bokelley/remove-platform-type-ui
Apr 22, 2026
Merged

chore(dashboard): remove dead platform_type UI (closes #2811)#2831
bokelley merged 1 commit into
mainfrom
bokelley/remove-platform-type-ui

Conversation

@bokelley

Copy link
Copy Markdown
Contributor

Closes #2811.

Migration 409 dropped `platform_type` from `agent_registry_metadata` when `@adcp/client` 5.1.0 replaced the concept with specialisms. The dashboard still rendered three `` selects and POSTed `body.platform_type`; the server silently ignored the field. Dead UI shipping dead data. What's removed Three `Platform type<select …>` rows in `buildConnectForm` (bearer/basic, oauth, oauth_client_credentials variants). The 15-entry `platformTypes` array and its `platformTypeOptions` join in `renderAgentsSection`. `buildConnectForm`'s `platformTypeOptions` parameter; both call sites updated (post-change signature: `buildConnectForm(escapedUrl, agentContextId)`). `platformType` reads + `body.platform_type = …` in the bearer/basic save handler and the OAuth authorize flow. The OAuth authorize flow's dead second `PUT /connect` that was sent purely to "save platform type even if context already exists." Agent specialism discovery via `get_adcp_capabilities` replaces the classification the operator used to hand-set. Verification [x] All 16 isolated form tests still pass on the slimmer signature. [x] `npm run typecheck` clean. [x] HTML JS parse clean. [x] Grep confirms no remaining `platform_type` references outside historical migrations (331/342/409 — immutable, intentional). 🤖 Generated with Claude Code

Closes #2811.

Migration 409 dropped platform_type from agent_registry_metadata when
@adcp/client 5.1.0 replaced the concept with specialisms. The dashboard
buildConnectForm still rendered three <select name="platform_type*">
selects (one per auth-type field group) and the save handlers still
POSTed body.platform_type — the server silently ignored the field.

Deletions from server/public/dashboard-agents.html:
 - Three <label>Platform type<select ...> rows inside buildConnectForm
   (bearer/basic, oauth, oauth_client_credentials variants).
 - The 15-entry platformTypes array and its platformTypeOptions join in
   renderAgentsSection.
 - buildConnectForm's platformTypeOptions parameter. Both call sites
   updated.
 - platformType reads + body.platform_type assignments in the
   bearer/basic save handler and the OAuth authorize flow's
   "context already exists" branch.
 - The OAuth authorize flow's dead second PUT /connect that was sent to
   "save platform type even if context already exists".

Post-delete: buildConnectForm(escapedUrl, agentContextId) — cleaner
signature. Save handlers POST only fields the server actually reads.
Agent specialism discovery via get_adcp_capabilities replaces the
classification the operator used to hand-set.

All 16 isolated form tests still pass. Typecheck + HTML JS parse clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@bokelley bokelley force-pushed the bokelley/remove-platform-type-ui branch from 5bedfac to 3eb5ec0 Compare April 22, 2026 05:22
@bokelley bokelley merged commit c6e9786 into main Apr 22, 2026
17 checks passed
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.

Remove dead platform_type UI (superseded by specialisms in migration 409)

1 participant