[Multica] Migrate Mark's Linear content to Multica (contingent on evaluation)

[dnovick]

Goal

If the Multica evaluation (#584) produces a go decision, migrate Mark's existing Linear issues and project structure to Multica. This is a contingent issue — do not start until #584 is resolved.

Background

Mark uses Linear for tracking work on BTP projects (bedrock-chat, law-hipaa-deployment, trellis-vault). As of August 2026 he has active projects in Linear including BAL-* (bedrock-chat issues), PHR-* (paused medical venture), and SKIP-* (consulting engagement). See ~/gitrepos/projects/btp/foundry/standards/issue-triage-standard.md for the triage vocabulary used in Linear.

See #582 for the full conversation context.

Action Items (contingent on #584 go decision)

• Export all active Linear issues (BAL-, SKIP-) to CSV/JSON
• Map Linear fields to Multica fields (priority, timing, status, labels, cycle)
• Write or configure import script using Multica API
• Import BAL-* issues; validate that priority, timing, and status map correctly
• Import SKIP-* issues (consulting engagement; may need separate project/team)
• Archive PHR-* issues with P4/Someday status (venture on hold)
• Validate with Mark that Linear content is correctly represented in Multica
• Update BTP project workflows (CI/CD, foundry references) to point to Multica
• Close Mark's Linear workspace (or archive it) after successful migration

Dependencies

• [Multica] Evaluate Multica as issue tracker and agent orchestration platform #584 (Multica evaluation — do not start until go decision)
• [Multica] Configure Multica project structure based on Mark's Linear setup #585 (Multica project configuration must be complete first)