Build production Scripture library through Phase 3 - #1
Merged
Conversation
Llewellynvdm
marked this pull request as ready for review
July 26, 2026 13:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Build the
GetBible\\Scripture\\Composer package as the production Bible application layer abovegetbible/sword, while preserving the exactgetbiblesword.ndjson/v1extraction contract and keeping remote module mutation explicit.Commit structure
Translation → Book → Chapter → Verseobjects.initialize(),refresh(),refreshIfDue(), durable success/failure state, whole-run locking, per-module failure isolation, Joomla Console commands, a Joomla Scheduled Tasks bridge, health output, and cron/systemd operations guidance.Production properties
Native boundary
getbible/sword0.1.0 / getBibleSword 0.3.0 ABI v1 can list and export installed modules but cannot safely download, update, or remove them. The default adapter reports those capabilities as unavailable instead of implementing unsafe direct archive downloads. The public provisioning API is dependency-injected so a future additive native installer can be substituted without changing consumers.Validation
Final GitHub Actions run: CI #5
git diff --check: pass.Review status
Phases 0–3 are complete and all required checks are green. Ready for review.