[adrianwebb]

Outcome

Qualify reusable React, browser, server and terminal providers against the exact combined capacity/provider SDK archive. Retain mobile-first rendering, Keycloak boundaries and the historical UI .16 replacement fixture byte-for-byte.

Work authority

• Work item / Issue: Part of chore: qualify SDK Agent contract candidate for reusable presentation #101; portfolio feat: deliver seed-driven Agent Capacity Provider infrastructure platform#773; Agent feat: implement extensible Agent manager worker and warm capacity agent#525.
• Proposal / decision: Approved Task 3D consumes one exact SDK/public presentation closure.
• Assignment / checkpoint: Independent UI compatibility candidate; no Agent, seed, domain or identity runtime moves into UI.
• Actor: OpenAI Codex desktop agent.
• Human authority: @adrianwebb.
• Agent / capacity provider: OpenAI Codex desktop; Work/models remain Task 10.
• Exact base ref: cordis at dbaf0eebac197be81bef84921715ac141bb28a9e.
• Exact head ref: feature/101-capacity-compat at 42053cf1649ea1e2537fcdb15f2f1202c4d1224a.

Contributor mode:

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Owner documentation → public program/fixture and exact-peer specifications → archive adoption and touched fixture refactoring → owner and genuine consumer verification. Exactly ten files. SDK #486 and UI #103 retain the independent shared policy changes; this candidate does not silently bundle those PRs.

Changes and commits

Select SDK .22 from c4f7849d402fc60bd1ee8274f647dac71a45b76e, archive SHA-256 dc9a91c26b12180a6dd003a8f7b56e1bc76c19c48fde42feaa0026765dd6583f. UI .20 carries its own metadata/provider identity and new archive. Earlier UI .16/.18/.19 artifacts remain unchanged. Frozen replacement-fixture compilation resolves its original exact SDK bytes from Git, rather than adopting ambient SDK metadata. The changed fixture methods are small and preserve assertions, inputs, timeout and registration. A built default server/terminal capacity-view program verifies escaping, content and native disposal without moving domain policy into UI.

Verification

• Exact SDK/installed-peer assertions failed before archive adoption in the preserved owner candidate.
• Full owner check/build/all tiers passed: 8 acceptance, 10 regression, 12 integration and 6 unit cases (36 total).
• Real browser mobile-to-widescreen, Astro/React hydration, frozen replacement archive and default server/browser/terminal construction remain qualified by the owner suite.
• Actual .20 archive and exact SDK .22 installed scripts-disabled into an independent consumer; public Node presentation passed and strict TypeScript checked emitted declarations.
• Shared canonical method checker passed against the unchanged verified origin baseline: zero new debt or exceptions.
• Whitespace and ten-file scope checks passed.
• Both exact-head hosted owner verification jobs passed. CI.
• Maintainer review.

Risk and rollback

No visual component, identity authority, domain policy or productive Agent behavior is added. Exact peer compatibility requires consumers to select one SDK closure. Revert the isolated candidate if necessary. Existing archives, licenses and owner boundaries stay intact. No production publication, legacy mutation, merge or issue closure.

Review checkpoint: synchronized with accepted readability policy; exact-head owner CI is being rerun before integration. Current maintainer instruction authorizes eligible Cordis merges; issues stay open.

Completion summary

Local owner and genuine packed-consumer gates passed. UI .20 archive SHA-256: 32f06cdc97e029ba48fc46d7bdf9d25b632d28d59518c74581f66175afa9a193. All current-head hosted checks passed. All issues remain open; this is a compatibility boundary, not complete Task 3D activation.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.