Complete runtime backend and JavaScript demo assembly #21

New Issue

2026-09-27T09:24:04Z

KofTwentyTwo commented

2026-09-27 09:24:04 +00:00

(Migrated from github.com)

The approved design promises every backend wired, a table per backend, and a fully runnable reference app. Read-only audit of e1625d2000 and its packaged JAR confirms that the API backend and JavaScript language module are absent; these are not explicit design deferrals. The core memory backend is packaged but has no demo table. The PostgreSQL demo currently uses an app-local strategy rather than the existing first-party module.

Complete the reference-app assembly under epic #1:

Include existing BOM-managed API and JavaScript modules at runtime, including the engine service registration in the shaded JAR.
Wire a seeded API-backed catalog table against an owned local JSON endpoint, with working query/get/pagination and normal permissions.
Wire a permission-protected JavaScript order-calculation process through ExecuteCodeAction with deterministic input/output.
Add a small explicitly transient memory-backed demo table to satisfy the backend demonstration contract.
Inspect the existing PostgreSQL module against the app-local strategy and use the first-party module if it preserves the established native full-profile behavior; report any incompatibility before changing semantics.
Extend core/full and packaged-app tests and smoke assertions to exercise actual data/process behavior, not merely dependency presence. Document startup, demo actions and transient data behavior.

Use existing framework modules and dependencies. Preserve all eight included qbits, explicit qbit deferrals, broker profiles, permissions, and normal quality gates. No Next UI changes, stored-script editor, Test-mode policy change, or held authentication work. Public release remains gated on the final QQQ/Next/qbit artifacts and native profile verification.

The approved design promises every backend wired, a table per backend, and a fully runnable reference app. Read-only audit of e1625d20001c25097ece0403958b1a7d055cf474 and its packaged JAR confirms that the API backend and JavaScript language module are absent; these are not explicit design deferrals. The core memory backend is packaged but has no demo table. The PostgreSQL demo currently uses an app-local strategy rather than the existing first-party module. Complete the reference-app assembly under epic #1: - Include existing BOM-managed API and JavaScript modules at runtime, including the engine service registration in the shaded JAR. - Wire a seeded API-backed catalog table against an owned local JSON endpoint, with working query/get/pagination and normal permissions. - Wire a permission-protected JavaScript order-calculation process through ExecuteCodeAction with deterministic input/output. - Add a small explicitly transient memory-backed demo table to satisfy the backend demonstration contract. - Inspect the existing PostgreSQL module against the app-local strategy and use the first-party module if it preserves the established native full-profile behavior; report any incompatibility before changing semantics. - Extend core/full and packaged-app tests and smoke assertions to exercise actual data/process behavior, not merely dependency presence. Document startup, demo actions and transient data behavior. Use existing framework modules and dependencies. Preserve all eight included qbits, explicit qbit deferrals, broker profiles, permissions, and normal quality gates. No Next UI changes, stored-script editor, Test-mode policy change, or held authentication work. Public release remains gated on the final QQQ/Next/qbit artifacts and native profile verification.

KofTwentyTwo commented

2026-09-30 16:11:30 +00:00

(Migrated from github.com)

Delivered by #22 and integrated into develop through #19 at signed 4c6794065c. The reference app now demonstrates the existing API and JavaScript modules, API-backed catalog query/get/pagination, scoped JavaScript order calculation, transient memory notes, and the official PostgreSQL backend. Core/full metadata, packaged runtime tests, permission checks, listener regression tests and README instructions were included and independently reviewed.

Exact develop Smoke run 36741556295 passed both profiles, with actual API/memory/JavaScript permission assertions and full backend queries. CircleCI job 26 passed. Existing opt-in Maven skips remain explicit; the separate full Compose job exercises real PostgreSQL and brokers. No Next UI changes were made. Final public release and released dependency pins remain tracked by #10.

Delivered by #22 and integrated into develop through #19 at signed 4c6794065c59daec18011c435f23f28ba3f4a45a. The reference app now demonstrates the existing API and JavaScript modules, API-backed catalog query/get/pagination, scoped JavaScript order calculation, transient memory notes, and the official PostgreSQL backend. Core/full metadata, packaged runtime tests, permission checks, listener regression tests and README instructions were included and independently reviewed. Exact develop [Smoke run 36741556295](https://github.com/QRun-IO/qqq-all/actions/runs/36741556295) passed both profiles, with actual API/memory/JavaScript permission assertions and full backend queries. [CircleCI job 26](https://circleci.com/gh/QRun-IO/qqq-all/26) passed. Existing opt-in Maven skips remain explicit; the separate full Compose job exercises real PostgreSQL and brokers. No Next UI changes were made. Final public release and released dependency pins remain tracked by #10.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qqq-all#21