Version Consistency Warning UI (collection update mismatch pathway)

[jamlung-ri]

Overview

UI design for communicating canonical source version locking behavior to users during collection updates — so that version mismatches don't feel like bugs.

Related Issues

• Implement repo version locking in expansions #2236
• MVP Version locking UI workflow: Verify versions/params and rebuild/recreate as needed #2312

Spec

KB: ocl-kb/tbv3/02_capabilities/manage-references.md (version consistency rules)
KB: ocl-kb/tbv3/TODO.md — SESSION item: Version Consistency / Collection Update Workflows

Scope (needs design session first)

• How the UI tells the user what it's doing when it locks to a canonical source version
• The pathways offered when a version mismatch is encountered during a collection update
• Whether HEAD-resolution during updates applies only to owned sources or also to CIEL

Status

Backend version locking is deployed and stable. UI communication is unspecified. Requires a dedicated design session before this ticket can be built.

[ocl-automation]

Automated Triage — 2026-04-06

Dimension	Score
Complexity	4
Scope	3
Clarity	2
Dependency	4
Risk	3

Decision: decision/blocked
Type: type/feature
Signals: signal/needs-spec, signal/has-dependencies

This is a UI design task for version consistency warnings that requires design decisions and coordination with existing specs, but lacks concrete implementation details. The existing type/feature label correctly identifies this as new UI functionality.

---

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-4 (openrouter).