JSQLite2 0.0.0-alpha.7

JSQLite2 0.0.0-alpha.7 (experimental prerelease)

Source: 57b498c
Tree: db1443ec2f1517ce12d99fa1155ef57b16c766c4

Corrected physical/module name resolution, positioned child readiness, linked
compound outer contexts and shared LIMIT/OFFSET ownership in the admitted subset.
Runtime is browser-only JavaScript translated from SQLite read-only internals.
The development source/oracle remains deliberately pinned to SQLite 3.53.4;
this is not a latest-upstream or full SQLite compatibility release.

Finite local checks: 7033 passed, 0 failed, 5 skipped; focused 948 passed.
Actual independently installed Chromium Fetch 48 and separate resource 2 pass;
demo lifecycle and original Chinook query (three executions/two resets) pass.
Reused native snapshots remain reused; skipped checks are not passes.
No all-browser, universal termination, statistical latency or beta claim.
Publication and actual served assets are separately verified by the external operator.

Tarball SHA256: 0e1da3bf5ccb385e182e37429cc8aa3ed7301aca6bf876cd14079d114d07a0fd
No npm publication. Prior alpha assets remain immutable.

Known wrong-result limitation

Metadata-table aggregation is unreliable in this release. For example,
SELECT name,count(*) FROM pragma_table_info('t') GROUP BY name ORDER BY name
can return source cid/name rows instead of grouped names/counts, across all three
encodings. Avoid metadata-table aggregation in alpha.7. This was discovered after
the selected candidate checks; the ongoing repair is NOT in this immutable package.
Passing metadata checks or the earlier test totals do not override this limitation.