Context
Follow-up to #13491 (the Accounts keeper-view extraction, delivered by PR #13516). The extraction PR shipped the identity-setup form + the Brain-side credential boundary + the shared AgentDefinitions roster singleton (the Accounts view exists, writes redacted identities, fails closed on the bridge). Per the close-target reconciliation on #13491 (cross-family review caught the over-claim), three of #13491's original ACs are not in the extraction and are deferred here so they have a durable home rather than being silently closed.
The Problem
#13491 was scoped broadly ("set up the cross-family fleet's agent identities (provider login + GitHub identity)"). The extraction delivers the view + form + credential boundary, but three enhancement ACs are genuinely additional scope and were deferred:
The Fix — the deferred ACs (from #13491)
- AiConfig provider-login integration (ADR 0019). The extracted form submits credentials through the Brain-side
FleetRegistryService bridge. Wire the provider-login config (model/provider selection, endpoints) through the AiConfig provider SSOT (ai/ConfigProvider.mjs) — read/write leaves, no service-local shadow.
- Basic NL-MCP entry (v13.1 external-harness entry). Include the basic Neural-Link MCP entry path an external harness uses to register/connect, in the Accounts surface. Extended multi-agent NL coordination (
#13056 / H3) stays fenced (scope guard #3 — do not pull forward).
- v14
IdentityState forward-compat slot. Verify the v13.1 Accounts identity slot (the AgentDefinition shape) is a subset/prefix of the v14 IdentityState schema (#13444) — zero-migration; no field contradicting the v14 shape.
Decision Record impact
aligned-with ADR 0019 (AiConfig provider SSOT) + aligned-with ADR 0020 (entry modes). Forward-compat target: #13444 (v14 IdentityState).
Acceptance Criteria
Out of Scope
- The Accounts view extraction itself (delivered by #13491 / PR #13516).
- Extended multi-agent NL coordination (
#13056, H3).
- The full v14
IdentityState schema / COP (#13444).
Related
- Follows: #13491 (the extraction) + PR #13516.
- Parent: #13448 (harness-UI cockpit epic) — linked via
SUB_ISSUE.
- Forward-compat: #13444. Fences:
#13056.
Release classification: v13.1 harness cockpit (not v13-release-blocking) — boardless.
Origin Session ID: a200ff3b-5ea5-4fc0-b288-cd5fe2c917e0
Authored by Claude Opus 4.8 (Claude Code), @neo-opus-vega (Vega).
Context
Follow-up to #13491 (the Accounts keeper-view extraction, delivered by PR #13516). The extraction PR shipped the identity-setup form + the Brain-side credential boundary + the shared
AgentDefinitionsroster singleton (the Accounts view exists, writes redacted identities, fails closed on the bridge). Per the close-target reconciliation on #13491 (cross-family review caught the over-claim), three of #13491's original ACs are not in the extraction and are deferred here so they have a durable home rather than being silently closed.The Problem
#13491 was scoped broadly ("set up the cross-family fleet's agent identities (provider login + GitHub identity)"). The extraction delivers the view + form + credential boundary, but three enhancement ACs are genuinely additional scope and were deferred:
The Fix — the deferred ACs (from #13491)
FleetRegistryServicebridge. Wire the provider-login config (model/provider selection, endpoints) through the AiConfig provider SSOT (ai/ConfigProvider.mjs) — read/write leaves, no service-local shadow.#13056/ H3) stays fenced (scope guard #3 — do not pull forward).IdentityStateforward-compat slot. Verify the v13.1 Accounts identity slot (theAgentDefinitionshape) is a subset/prefix of the v14IdentityStateschema (#13444) — zero-migration; no field contradicting the v14 shape.Decision Record impact
aligned-with ADR 0019(AiConfig provider SSOT) +aligned-with ADR 0020(entry modes). Forward-compat target: #13444 (v14IdentityState).Acceptance Criteria
ai/ConfigProvider.mjs) — read/write leaves, no shadow.#13056/H3 remains fenced.IdentityStateschema (#13444) — zero-migration.Out of Scope
#13056, H3).IdentityStateschema / COP (#13444).Related
SUB_ISSUE.#13056.Release classification: v13.1 harness cockpit (not v13-release-blocking) — boardless.
Origin Session ID: a200ff3b-5ea5-4fc0-b288-cd5fe2c917e0
Authored by Claude Opus 4.8 (Claude Code), @neo-opus-vega (Vega).