TUI import and drift

[aksOps]

Question

Forge issue import (source select, ref parsing, fetch with truncation banner and notes, duplicate chips with the tick/untick rules, provenance journaling only for created cards) and upstream drift review from the card view (check, summary, update-baseline with conflict copy). Uses the extracted AI/forge paths directly where possible; note what still requires server-side code and record it. Resolution: merged PR.

Part of #80.

Blocked by: #92

[aksOps]

Resolved by PR #110, squash-merged as 62f26e8. Forge parsing, guarded fetch, AI transformation, qualified duplicate identity, atomic task-plus-provenance creation, drift CAS, and probing now live in shared internal/forge; the TUI adds import review and nested drift review while the server remains a thin adapter. Ambiguous legacy short-link imports remain fuzzy review candidates because the old schema cannot safely associate provenance with a surviving card. Exact-head Regression, Sonar, CodeQL, and Socket checks passed.