test(deploy): exercise external module packages #90

Merged

Zayin_Admin merged 4 commits from test/external-module-deploy-smoke into main 2026-10-10 16:32:32 +00:00

Conversation 1 Commits 4 Files Changed 9

+341 -89

ekklesia-bot commented 2026-10-10 03:18:27 +00:00

Member

Copy Link

Copy Source

Summary

• let the existing split-topology deployment smoke accept an exact external Module Package release pair and module ID while preserving the built-in template path
• verify invalid-package rejection, migration apply/idempotence, installed-module discovery, authenticated API probing, Dashboard UI loading, and display loading
• prove module and data persistence across an ordinary API restart and API container recreation
• exercise disable/re-enable, removal with retained migration history, and reinstall of the same verified package
• recognize contract-shaped ModuleStorageError values across separately bundled external-package copies
• keep the reference SeaweedFS deployment from stalling writes on modest disks by using the already-proven 32 MB volume allocation granularity

This is generic Core integration support only; it contains no Signage-specific registration or runtime behavior. Ekklesia_Signage PR #13 pins this exact head and supplies the real external package.

Validation

• pnpm ci:verify — passed at 40ef0ff802c124ae5a3a0b9aa51a1502a7b72644
• targeted deployment/CI suites — 32 tests passed
• all three reference Compose combinations — valid
• Core Actions run 252 — all 8 jobs passed, including both deployment topologies
• Ekklesia_Signage Actions run 253 / integration job 1189 — passed end to end with the real signage-0.1.2-linux-x64-glibc.tar.gz
• external browser validation covered split-origin Dashboard UI, authenticated API, three uploaded slides, kiosk pairing/playback, four resilience scenarios, process restart, container recreation, lifecycle disable/re-enable, removal, and reinstall

Scope

No production schema, migration history, verifier policy, authentication policy, package format, or Signage-specific behavior changed. The one reference deployment correction changes SeaweedFS allocation granularity, not individual-object or total storage capacity. Browser validation uses headless Chromium; no physical TV/device validation is claimed.

## Summary - let the existing split-topology deployment smoke accept an exact external Module Package release pair and module ID while preserving the built-in template path - verify invalid-package rejection, migration apply/idempotence, installed-module discovery, authenticated API probing, Dashboard UI loading, and display loading - prove module and data persistence across an ordinary API restart and API container recreation - exercise disable/re-enable, removal with retained migration history, and reinstall of the same verified package - recognize contract-shaped `ModuleStorageError` values across separately bundled external-package copies - keep the reference SeaweedFS deployment from stalling writes on modest disks by using the already-proven 32 MB volume allocation granularity This is generic Core integration support only; it contains no Signage-specific registration or runtime behavior. Ekklesia_Signage PR #13 pins this exact head and supplies the real external package. ## Validation - `pnpm ci:verify` — passed at `40ef0ff802c124ae5a3a0b9aa51a1502a7b72644` - targeted deployment/CI suites — 32 tests passed - all three reference Compose combinations — valid - Core Actions run 252 — all 8 jobs passed, including both deployment topologies - Ekklesia_Signage Actions run 253 / integration job 1189 — passed end to end with the real `signage-0.1.2-linux-x64-glibc.tar.gz` - external browser validation covered split-origin Dashboard UI, authenticated API, three uploaded slides, kiosk pairing/playback, four resilience scenarios, process restart, container recreation, lifecycle disable/re-enable, removal, and reinstall ## Scope No production schema, migration history, verifier policy, authentication policy, package format, or Signage-specific behavior changed. The one reference deployment correction changes SeaweedFS allocation granularity, not individual-object or total storage capacity. Browser validation uses headless Chromium; no physical TV/device validation is claimed.

ekklesia-bot added 1 commit 2026-10-10 03:18:28 +00:00

test(deploy): exercise external module packages fa27603133

ekklesia-bot referenced this pull request from Zayin/Signage 2026-10-10 03:31:26 +00:00

ci: restore external package integration #13

Zayin_Admin added 1 commit 2026-10-10 03:37:20 +00:00

test(deploy): allow slower display uploads 6e64b3c5f9

Zayin_Admin added 1 commit 2026-10-10 15:54:16 +00:00

fix(storage): recognize errors across module packages a0e9948820

Zayin_Admin added 1 commit 2026-10-10 16:07:58 +00:00

fix(deploy): bound object storage allocation size 40ef0ff802

Zayin_Admin approved these changes 2026-10-10 16:32:25 +00:00

Zayin_Admin merged commit 6dae29412f into main 2026-10-10 16:32:32 +00:00

Zayin_Admin deleted branch test/external-module-deploy-smoke 2026-10-10 16:32:32 +00:00

ekklesia-bot referenced this pull request 2026-10-10 16:55:26 +00:00

chore(release): prepare 0.2.4 #91

Sign in to join this conversation.

Reviewers

No Reviewers

Zayin_Admin

Labels

No items

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

Joey Zayin_Admin ekklesia-bot

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Zayin/Ekklesia#90