Author: Expansion

[paulsonder]

Priority: 3
Quarter: Q2 2026
Bucket: CIEL Implementer

Overview

Implement Collection Versions and Expansions management UI in TBv3. The API and backend are complete; TBv3 needs the frontend interface.

Spec

• Surface: `ocl-kb/tbv3/04_surfaces/versions-expansions-tab.md`
• Capability: `ocl-kb/tbv3/02_capabilities/manage-versions-and-expansions.md`
• Objects: `ocl-kb/tbv3/01_objects/version.md`, `ocl-kb/tbv3/01_objects/expansion.md`

Current State

• oclweb2 has a working Versions + Expansions tab (`src/components/collections/Versions.jsx`, `ExpansionForm.jsx`). Use as V2 baseline where applicable, adapting to TBv3 design patterns.
• oclweb3 has a `VersionForm.jsx` component and a route for the Versions + Expansions tab, but the tab is not yet reachable in `RepoHome`.

Scope (M42)

Make the tab reachable

• Wire "Versions + Expansions" tab in `RepoHome` so it renders for Collections
• Wire "Versions" tab in `RepoHome` for Sources (versions only, no right panel)

Versions + Expansions Tab — two-panel layout

Full layout spec in `04_surfaces/versions-expansions-tab.md`:

• Left panel: version list (HEAD + released versions), status badges, default expansion summary chip, stale indicator
• Right panel: expansions for selected version (ID, default badge, status, stale badge, concept/mapping counts, last built timestamp)
• Default selection: most recently released version on tab open
• Responsive stacking below 900px

Version CTAs (from left panel)

• New Version — opens Create Version dialog (`VersionForm.jsx` already exists in oclweb3; wire it in)
• Release (draft versions) — one-click with confirmation
• Edit description — inline edit of version description/external_id
• Delete (draft versions with no expansions)

Expansion CTAs (from right panel) — individual tickets

Each expansion CTA is tracked separately:

• CTA / Expansion / Create ($expand) #1984 Create ($expand)
• CTA / Expansion / Set as default #1985 Set as default
• CTA / Expansion / Delete #1986 Delete
• CTA / Expansion / Update metadata #1987 Update metadata
• CTA / Expansion / Rebuild expansion #1988 Rebuild

Dependency notification entry point

• When user arrives via dependency notification link: pre-select the relevant version, scroll stale expansion into view, show highlighted banner above right panel (spec in `versions-expansions-tab.md` § Dependency Notification Entry Point)

Out of Scope (M42)

• Restore HEAD to version (Restore/Revert Collection HEAD to Previous Version #2284 — separate ticket, cut from M42)
• Version comparison UI (post-M42)
• Export/download actions (post-M42)