fix(cloud): JA-16 keep Agent accounts in AI capabilities; Orca account leads the Orca Cloud group

This commit is contained in:
Neil
2026-11-10 21:10:13 -08:00
parent 7ce2885149
commit 0335884b8a
2 changed files with 6 additions and 5 deletions
@@ -79,12 +79,12 @@ describe('one Orca Cloud group (JA-16)', () => {
nav('automations', 'workflows')
]
it('leads the Orca Cloud group with Agent accounts and the Orca account', () => {
it('leads the Orca Cloud group with the Orca account; Agent accounts stays in AI capabilities', () => {
const out = gatherOrcaCloudSettingsGroup(all, options({}))
expect(out.map((section) => `${section.group}:${section.id}`)).toEqual([
'capabilities:agents',
'capabilities:accounts',
'setup:general',
'orca-cloud:accounts',
'orca-cloud:orca-account',
'orca-cloud:cloud-billing',
'orca-cloud:cloud-team',
@@ -106,8 +106,9 @@ export function buildOrcaCloudSettingsSections(
}
/**
* JA-16: in Orca Cloud builds every cloud entry sits in one group, led by Agent accounts and the
* Orca account, instead of being split across AI capabilities, Set up and Orca Cloud.
* JA-16: in Orca Cloud builds the Orca account leads the one Orca Cloud group instead of sitting in
* Set up. Agent accounts stays in AI capabilities: it covers this computer and hosts as much as
* Orca Cloud, and its Orca Cloud part is deep-linked from every cloud entry point.
*/
export function gatherOrcaCloudSettingsGroup(
sections: readonly SettingsNavSection[],
@@ -116,7 +117,7 @@ export function gatherOrcaCloudSettingsGroup(
if (isWebClient || !isOrcaCloudApiAvailable) {
return [...sections]
}
const leadIds = ['accounts', 'orca-account']
const leadIds = ['orca-account']
const leads = leadIds
.map((id) => sections.find((section) => section.id === id))
.filter((section): section is SettingsNavSection => section !== undefined)