Restore source-neutral LibreBible catalog

CONVENTIONS.md

@@ -107,16 +107,6 @@ Attachment metadata should identify:
 - Markdown docs are a human-readable projection of the same metadata. They must not become a separate truth source.
 - Public ChristIT.com pages and app/plugin package discovery should read machine catalogs first, then link to Markdown docs for explanation.
 
-## CrossWire/SWORD Intake
-
-- Treat CrossWire/SWORD as a source channel, not a blanket license approval.
-- SWORD modules must pass the local license approval registry before generated content is committed under `packages/json/`.
-- Preserve original SWORD `.conf` metadata, rawzip URL, rawzip checksum, module version, module date, driver, source type, and license text in audit output or source manifests.
-- Use `scripts/sword-audit.js` to classify candidate modules before import.
-- Use `scripts/import-sword.js` for approved pilot modules. It downloads CrossWire rawzip packages, extracts them into `cache/sword/library`, exports content through containerized SWORD utilities, then normalizes the result into JSONL packages.
-- If Docker or SWORD utilities are unavailable, keep the module in audit/review status and do not hand-parse compressed SWORD binary data.
-- Duplicate Bible texts from SWORD should not be published when the same edition is already sourced from a better upstream package. SWORD may still be used for comparison, commentaries, dictionaries, lexicons, and study aids.
-
 ## Update Workflow
 
 - Update checks must be mechanical and repeatable.
@@ -145,7 +135,6 @@ Initial package targets:
 
 Future package targets may include:
 
-- SWORD-compatible exports.
 - OSIS/USFM normalized exports.
 - Search indexes.
 - Static web catalogs.