The harness page's setup terminal targets the Kit agent profiles, so the two pages were two halves of one flow split across routes: with no Kit profile the harness page dead-ended in a disabled 'No profiles configured' select while the place to create one sat on another page. /settings/agent-profiles now carries the profiles editor and a 'Harness sign-in' section (setup terminal plus the credential-bindings sign-in table), and /settings/harness redirects to it. The bindings re-read when a terminal session ends so a fresh capture shows immediately, and a null-seeded agent-profiles document now renders the empty state instead of a bare add form. The gateway page registry names the merged page.