[Multica] Replicate existing GitHub issues into Multica

[dnovick]

Goal

Import existing open GitHub issues from berean-bible-bots into Multica so the backlog is available in the new platform from day one.

Background

As of August 2026, berean-bible-bots has ~580 GitHub issues. Of these, roughly 10 are open. After Multica is configured (#585) and the integration strategy is settled (#586), this issue covers the mechanical work of importing the open backlog.

See #582 for the full conversation context. Do not start until #584 (evaluation) and #585 (configuration) are complete.

Action Items

• Export all open GitHub issues to JSON using gh issue list --state open --json number,title,body,labels,assignees,createdAt
• Map GitHub labels to Multica labels/priority/timing fields using the configuration from [Multica] Configure Multica project structure based on Mark's Linear setup #585
• Write an import script using the Multica API that creates one Multica issue per GitHub issue
• Validate: spot-check 5 imported issues for accuracy
• Decide whether to close or archive the originating GitHub issues (per [Multica] GitHub ↔ Multica integration for external issue reporting #586 integration decision)
• Document the import process for future use

Current Open Issues (as of August 2026)

#	Title	Status
571	Fixes for BBH ch3 exercises	Open
554	Ch33 exercises: dropdown selects + answer-row alignment fixes	Open
528	א as a Matres Lectiones	Open
425	Refactor Studies section to be YAML-driven	Open
388	Fix issues with BBH 29 Hiphil exercise	Open
373	Add Biblical Hebrew Syntax Course	Open
357	bbh-2024.1: scaffold past sessions	Open
227	Fix collapsed answer rows in BBG and BBA HTML exercises	Open
223	Migrate all flashcard decks to YAML-driven approach	Open
221	Make research MCP server capabilities available on website	Open

And the BTP/Foundry initiative issues: #582–#590 (created August 2026).

Dependencies

• [Multica] Evaluate Multica as issue tracker and agent orchestration platform #584 (Multica evaluation — confirm go decision)
• [Multica] Configure Multica project structure based on Mark's Linear setup #585 (Multica configuration — must be set up first)
• [Multica] GitHub ↔ Multica integration for external issue reporting #586 (Integration strategy — determines what happens to GitHub issues after import)