Add the Paratext 9 import service, storage, provenance, and commands

[jasonleenaylor]

The backend half of the PT9 import, stacked on #272. Supersedes #268.

• InterlinearProject gains optional pt9Import provenance (per-file hashes and
  the import timestamp). A project carrying it is frozen: storage rejects
  every user write and only the import's own save path replaces its content;
  deleting stays allowed.
• projectStorage gains savePt9Import (create the source's single import
  project or replace it wholesale), getPt9ImportForSource, and
  createEditableCopy (clone an import's analysis into a new editable project
  with no provenance).
• pt9ImportService.importPt9Project fetches the parsed payload through the
  platformScripture.Pt9Interlinear projectInterface, rebuilds each referenced
  book's text layer from USJ, converts, and persists - created on first run,
  replaced wholesale on later runs, and kept untouched (staleKept) when the
  source files have vanished.
• Commands, localized strings for the import project's fixed name and
  description, and the type guards the wire surface needs.

---

This change is 

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 78760bdf-afbb-4abe-8387-a9f669877821

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[jasonleenaylor]

❓ Nothing in the stack passes a resolver: pt9ImportService calls convertPt9Project({ data, books, importedAt }), so every import persists zero lexicon refs. Fine for the import project, which a later run replaces wholesale, but createEditableCopy keeps sourceProjectId and drops pt9Import, so a re-import never touches a copy already taken. PT9 lexeme identity is permanently gone for that copy.

Is dropping PT9 identity at import decided? (#269 makes a foreign paratext9 ref expressible, which would render identically today and survive into copies.)

--drafted by Claude; reviewed and edited by me--

Resolver implementation is deferred, but that needs tracking, created #280 as a reminder.