JSQLite2 0.0.0-beta.6 — compiler ownership and maintainability

JSQLite2 0.0.0-beta.6

Sixth public beta: a bounded structural-maintainability milestone, retaining
beta.5's join/index/Bloom functionality while clarifying shared compiler ownership.
Independently accepted locally on2026-10-25 at
c59d3bb6205ade1a98d09c1c6665174118833934, tree
ec4ac7f56f91552994c39b1d0cffd87b699de4a0, under root review10.
Publication changes legal/package metadata and documentation, not engine behavior.
Later LIKE/GLOB prefix-range work and subsequent development are excluded.
Prior releases remain immutable; this is not whole-project completion.

Changes since beta.5

• Consolidate identical aggregate-subquery destination production behind the
  union of its original admission guards. Shared builder/destination, GROUP BY
  without aggregates, Once and IN evaluation order remain explicit.
• Share INDEX_INFO semantic row production while retaining direct PRAGMA versus
  module protocols, field typing, error/check order and cursor cleanup.
• Replace obsolete clone-return machinery in RIGHT target verification with
  read-only visitation: express the actual responsibility instead of allocating
  cloned operations that are discarded.
• Introduce cohesive SELECT result delivery via createSelectDelivery:
  DISTINCT, direct/sorted publication, sorter draining and OFFSET/LIMIT have an
  identifiable owner. WHERE/RIGHT positioning, snapshots, shared register/cursor/
  label allocation, enclosing compound stops and cleanup remain in their owners.
• Update source-sensitive tests to protect the relocated responsibilities, with
  negative mutations and actual public/native result checks rather than obsolete
  helper adjacency. Preserve explicit integration inventory and native enrollment.

Pinned local ESLint/typescript-eslint and jscpd findings guided contextual review.
The affected hotspot's same-config complexity changed455→432; total warnings
remain310. Metrics are supporting evidence, not acceptance quotas or proof of
correctness. Large source-shaped dispatch is retained where justified. SonarJS's
SSAL distribution was not adopted. See
maintainability research,
translation guidance and source map.

Accepted evidence and important qualifications

• The full532-file integration run on c90 completed with531 component exits0
  and one obsolete compound-owner observer failure:9174passes/1failure/5skips.
  That historical invocation remains failed, not retroactively green.
• On the accepted final test-only correction, fresh35/35 affected checks passed.
  Independent acceptance reconciled all5357 source inputs,40 native prerequisites,
  203 generated inputs and logs to permit unchanged531-component reuse. No
  newly executed monolithic532-green run is claimed.
• 39 companion files/829passes, explicit opt-in13files/28passes,13 package commands
  and actual built/offline-installed Chromium230/230 each are authenticated
  unchanged-input evidence, not newly rerun final-commit executions. Counts overlap
  and are not an additive compatibility denominator. Five full-suite skips remain.
• Fresh independent35/35 checks, actual installed HTTP native-query repetitions/
  reset/full metadata, six demo groups and error precedence, typecheck and package
  boundaries passed on the accepted applicability closure.
• Accepted local tarSHA
  15d73b321e3b2890f069f25501f97bf7f7b46e3ac2e9ccfede7d316aec4f237d
  contains57 runtime modules/114 emitted JS/declarations, authenticated across
  build/tar/extraction/installation and browser serving.

These are retained acceptance results, not publication-wide reruns. Publication
separately validates its versioned package, compares all emitted files with the
accepted artifact, and tests the actual playground/versioned installed demo.
Historical failures, partial runs and unmeasured limitations remain qualified.

Delivery and remaining boundaries

Download jsqlite2-0.0.0-beta.6.tgz and SHA256SUMS from the
GitHub prerelease.
Verify hashes before installing. No npm registry publication. Serve the complete
dist tree for unbundled browsers. GPL-3.0-or-later; LICENSE/NOTICE and corresponding
source accompany the release; Chinook retains its separate MIT notice.

This release does not add the later selected LIKE/GLOB prefix-range implementation.
Wider/repeated/module/USING join layouts, broader automatic-index/Bloom and virtual
planner compositions, specialized range/minmax/DISTINCT/BIGNULL/order/statistics
paths and broader SELECT combinations remain progressive work, not exclusions.
Correct scan fallback is not index-use credit; no exhaustive compatibility,
native work/allocator parity, guaranteed speedup or hard latency/fairness claim.

Development policy100s/file/serial≤80/600s independent batch is distinct from the
playground's unchanged60-second watchdog/1000-row cap. Public API memory/work/
cancellation/deadline guarantees are unchanged. Runtime remains browser-safe
read-only TypeScript/JavaScript without native SQLite, WebAssembly or query backend.

JSQLite2 0.0.0-beta.5 — joins, automatic indexes and Bloom filters

JSQLite2 0.0.0-beta.5

Fifth public beta: broader join-aware index execution and real runtime automatic
indexes/Bloom filters, with source-owned packed private storage and required
correctness/resource fixes. Independently accepted locally on2026-10-25 at
942e6135ab5c212cf02d46d51171cfb94ce807ab, tree
24944e9ed6e19bd5ba19d612bc28fc492c013a8b.
Publication changes version, legal packaging and documentation, not engine
behavior. Ongoing beta.6 maintainability work is excluded; prior releases remain
immutable. This is a bounded milestone, not whole-project completion.

Changes since beta.4

• Broader RIGHT/FULL matched index access for represented two/three-rowid and
  rowid-left/WITHOUT ROWID-right joins. Complete primary-key identity, ON hit
  before WHERE, exact physical positioning and independent unmatched drain are
  preserved. Selected drain access does not masquerade as matched-pass credit.
• Native-costed automatic packed-index construction, Once build/probe/covering
  for ordinary two-physical-rowid INNER/LEFT joins, plus persistent-index Bloom
  production. Live affinity precedes Filter/seek; collisions still require the
  authoritative comparison. No host hash join, decoded-array evaluator or fake
  persistent schema index is introduced.
• Shared packed private Delete and application cursor operations now back
  represented window extrema instead of sorted-array search/splice. Window
  result ownership, typed ties, EXCLUDE and primary-error cleanup are corrected.
• Comparison-affinity, predicate NULL/error short-circuit and ordering repairs;
  explicit Mem input/output overlap, reserve-before-copy, rollback/sequence and
  zero-tail sizing corrections. Resource limits retain real live ownership,
  rather than discounting it to preserve obsolete test thresholds.
• Test orchestration now enrolls required pinned native fixture producers and
  detects generated-input drift. Long RIGHT/FULL tests run separately by encoding
  with the full original workloads and assertions.

See translation guidance, source map
and conformance evidence for exact scope and mappings.

Accepted local evidence

• Fresh full 528/528 component exits0;9,161 passes,zero failures/cancellations,
  five opt-in skips,36 successful native prerequisites,201 generated inputs,
  no timeout/unrun/source or generated-input drift.
• 829/829 companion checks across39 files, no skips/failures/drift.
• All five skipped production skipscan units separately exercised through the
  existing closure:6 prerequisites,13 files,28/28 units,zero skips. These overlap
  full coverage and are not added to9,161; the full manifest retains its skips.
• Build/type/package checks passed. Actual built and offline-installed
  Chromium148/Playwright1.60 each passed 230/230 all-lane checks, with
  build/tar/install/served module equality. Independent installed HTTP six demo
  groups and the original native-typed query three executions/two resets passed.
• Native/public checks cover all three database text encodings, typed results,
  all five metadata fields, errors, reset/rebind and cleanup at the represented
  boundaries. Execution claims remain revision-qualified, not a compatibility
  percentage or exhaustive fault-schedule guarantee.

Those are retained exact-input acceptance results, not newly rerun
publication-wide tests. Publication separately checks its versioned package and
all114 emitted JS/declarations against accepted local tarSHA
dfbd0b653310e4b191669423c69ae4277c0af395f14055dd0414228becac8c6f,
and validates the actual public playground. Historical failed/partial runs remain
failed/partial on their original inputs.

Delivery and remaining boundaries

Download jsqlite2-0.0.0-beta.5.tgz and SHA256SUMS from the
GitHub prerelease,
verify the hash, then install the local tarball. No npm registry publication.
Unbundled browsers must serve the complete dist tree and import dist/index.js.
GPL-3.0-or-later; LICENSE/NOTICE and corresponding source accompany this release.
Chinook retains its separate MIT notice.

Wider/repeated/module/USING matched layouts, broader automatic/Bloom and
virtual-table/planner/Filter compositions, specialized LIKE/GLOB ranges,
minmax/DISTINCT/BIGNULL, wider multisource ordering and statistics-sensitive paths
remain progressive work, not permanent exclusions. Correct scan fallback earns
no index-use credit. No all-query guarantee, native cost/work/allocator parity,
stable speedup or hard latency/fairness claim follows.

Development validation uses100s/file, serial batches<=80 and an independent600s
batch ceiling; performance is not this stage's acceptance objective. These test
settings do not weaken public API memory/work/cancellation/deadline semantics.
The public playground keeps its separate60-second watchdog and1,000-row cap.
Runtime remains browser-safe read-only TypeScript/JavaScript with no native
SQLite, WebAssembly or SQL-query backend. SPEC scope is unchanged; beta.6 quality
work and continued development follow without automatic publication authority.

JSQLite2 0.0.0-beta.4 — broad index-supported SELECT milestone

JSQLite2 0.0.0-beta.4

Fourth public beta: materially broader index-supported SELECT planning and
execution, independently accepted locally on 2026-10-23 at
f6ae8c3dfc9963b1a8f0aa02c60b8dee7784734d, over runtime
7d9a7822620adc8559f003b63cf7cd730b3effdc. Publication changes version, legal
packaging and documentation, not engine behavior. Later RIGHT/FULL matched-pass
development is deliberately excluded. Existing public releases remain immutable.

Changes since beta.3

• Scalar/vector/correlated selected IN now uses eligible persistent ROWID/UNIQUE
  indexes or translated private B-tree set destinations, including projection,
  physical direction, affinity/collation, NULL and repeated-field handling.
• Index paths feed ordinary, joined, recursive OR, derived, retained LIMIT and
  GROUP/aggregate consumers through shared SELECT and VDBE owners.
• Resolved-source flattening, retained coroutine eligibility, ORDER reference
  projection and explicit COLLATE comparison repairs preserve real callers,
  full-tuple residuals, typed results and lifecycle semantics.
• The twelve-family admission ledger distinguishes actual selected access from
  correct scan fallbacks, partial support and missing optimizations. It covers
  equality/IPK/prefix/range/composite, IN/OR, skipscan, covering/WITHOUT ROWID,
  bounded ORDER/GROUP/DISTINCT/LIMIT and joined/correlated consumers,
  statistics/parameters, expression/partial indexes and enrolled modules.

See family-level scope and evidence.
This is a MOST-major-family milestone, not a compatibility percentage, all-query
guarantee, universal optimizer parity or native cost/work equivalence.

Accepted local evidence

• 509/509 test files completed successfully, 8,806 passes and five existing
  skips, 16 successful prerequisites, no input drift or unrun tail.
• 812 companion passes across 39 files; focused counts overlap and are not
  additive compatibility coverage. The five existing skips receive no credit.
• Original 20k/20-outer/20-RHS selected-versus-scan workloads complete around
  21.6–21.8 seconds across encodings under unchanged serial/file60s/batch600s
  limits. WR87 is the authenticated 85+2 partition with unchanged assertions,
  not a newly run obsolete unpartitioned file or a universal speed claim.
• Native/public common45, leads45 and six-family18 compare typed rows, all five
  metadata fields and repeated execution/reset across UTF-8/UTF-16le/UTF-16be.
• Package/offline strict-consumer checks, actual Chromium48 plus two separate
  gap controls, independent installed HTTP six demo groups and original
  native-typed query three executions/two resets passed.

These are retained accepted exact-input results, not newly rerun publication-wide
tests. Historical failures/timeouts remain failures on their original inputs;
unknown causes remain unknown. Publication separately validates its versioned
tarball, equality of all 112 emitted JS/declaration files with the accepted local
artifact and the actual public playground. Gap controls do not implement gaps.

Delivery and limitations

Download jsqlite2-0.0.0-beta.4.tgz and SHA256SUMS from the
GitHub prerelease.
Verify its hash and install the local tarball; no npm registry publication.
For unbundled browsers serve the complete dist tree and import dist/index.js.
GPL-3.0-or-later; LICENSE/NOTICE and corresponding source accompany the release.
Chinook retains its separate MIT notice.

At this accepted milestone RIGHT/FULL main matched-pass planning still falls
back; a selected unmatched drain does not earn matched-pass credit. Runtime
automatic-index/Bloom construction, general LIKE/GLOB range synthesis,
specialized minmax/DISTINCT/BIGNULL, wider multisource ordering and broader
STAT4 vector/function/subquery proofs remain incomplete. Immutable PK/UNIQUE
indexes are not runtime automatic indexes. Broader SQL compositions and finite
resource/interruption schedules remain progressive work, not scope exclusions.

The runtime remains read-only browser-safe TypeScript/JavaScript: no native
SQLite, WebAssembly or SQL-query backend. Cooperative controls do not establish
hard preemption, native heap parity or all-browser certification. See the
versioned API, guide, SPEC and
conformance. The public playground retains its 60-second
watchdog and 1,000-row cap. Beta.4 is not whole-project completion.

JSQLite 0.0.0-beta.3

JSQLite2 0.0.0-beta.3

Third public beta: a useful bounded index-planning improvement, independently
accepted locally at 14d15a3f1d6d69ea9ed88d7a44a01ca412acbd96. Publication adds
version/license/documentation and legal-notice package checks, not engine edits.
Unfinished beta.4 work is excluded; previous releases remain immutable.

Changes since beta.2

• STAT4-informed scalar range estimates for invalid-prefix skip-scans now feed
  actual candidate costing and selected index execution, translating SQLite's
  whereRangeSkipScanEst and scalar sample extraction. Known-prefix KeyStats
  and fallback behavior remain distinct.
• Schema-owned sample records are borrowed by internal readers without an
  unnecessary full-record copy before resource checks; public copies stay defensive.
• Numeric separator tokens publish the normalized owning semantic production
  consistently for planner probes and ordinary execution.
• Meaningful sample-loop interruption, cleanup, reset/retry and actual elapsed
  deadline-control checks accompany the translated production paths.

The representative native-backed20k-row fixture demonstrates useful index
selection and reduced JSQLite cursor work against a forced alternative. These
are fixture-specific access observations, not universal speedups, native VM-step
equivalence or full optimizer parity. Broader index-supported SELECT coverage is
the separate beta.4 workstream, not a claim of this release.

Accepted evidence

Exact local-beta source: 485/485 files completed,8,707 passes,five existing
skips,zero failures/cancellations/timeouts,16 prerequisites successful, and
809/809 companion tests across39 files. No input drift or unrun files.
Five skipscan-copy compiled/concurrent/corruption/memory/recovery cases receive
no coverage credit. Counts overlap and are not a compatibility percentage.

Fresh native/public common45,leads45 and six-family18 observations match typed
rows/full metadata/two executions across all three encodings. Original unreduced
20k6/6 and unpartitioned WR87/87 complete; WR58.302s is close to the60s ceiling,
not evidence of performance headroom. Historical failed/drifted/masked runs and
timeouts remain historical failures, not retroactively green.

Actual rebuilt package/offline strict consumer checks, HTTP Chromium148 /
Playwright1.60 current48 plus separate gap2, authenticated52 served runtime
modules, independent installed six demo groups and original native-typed Chinook
query three executions/two resets passed. Publication separately validates its
versioned tar, identical accepted emitted bytes and actual public playground.
Accepted full-suite results are not claimed as newly rerun publication tests.

Delivery and remaining boundaries

Download jsqlite2-0.0.0-beta.3.tgz and SHA256SUMS from the
GitHub prerelease,
verify the tarball hash, then install the local tarball with npm. For unbundled
browsers serve its complete dist/ tree and import dist/index.js. No npm
registry publication. GPL-3.0-or-later; LICENSE/NOTICE and corresponding source
accompany the release. Chinook retains its separate MIT notice.

This is bounded read-only support, not all SQLite query/optimizer combinations.
General parameter-sensitive reprepare-plan parity, vector/function/subquery
probes, broader selected index/composition paths and exhaustive resource/error
schedules remain work. Cooperative controls are not hard preemption, native heap
parity or all-browser certification. Native SQLite is development-only: no
native/WASM/query-server evaluator is shipped. See exact-version API,
guide, conformance and SPEC.

The public playground keeps its60-second watchdog and1000-row cap. Publication
receipts retain exact artifact hashes, commands, outcomes and applicability.
Beta.3 is an accepted milestone, not whole-project completion.

Reproducible development evidence

With explicit owner authorization, nine unpublished development commits were
rewritten to remove oversized, duplicated research output. Original accepted
source14d15a3f maps to494ace2f5a48b3ebee160b9d3b1712e65bea03b9. Runtime/API/build
and all other source inputs are unchanged; the package reproduces the original
accepted artifact byte-for-byte. Published history/releases were not rewritten.

The native regression fixture losslessly shares ten repeated typed rowsets;
all102 query/profile/encoding captures reconstruct identically with hash checks.
The exploratory search retains all29 plan differences, setup/work counters,
row counts and typed-result hashes. Pinned generators freshly reproduced both
committed compact outputs, writing full raw captures only to disposable card
work. See capture policy and regeneration.
Original captures/Git state remain in the verified operator backup; historical
accepted evidence retains original source-era hash identities. This is evidence
storage repair, not new engine behavior or a claim that old tests ran on new hashes.

JSQLite 0.0.0-beta.2

JSQLite2 0.0.0-beta.2

Second public beta: SQL functionality and composition improvements. Accepted
local source: e48e22f56240f321deda9e51d1ea71baebf390b2. Release packaging adds
version metadata, GPL notices and publication documentation; no beta.3 index work
or engine edits are included. Earlier releases remain immutable.

Changes since beta.1

• Generated outer-column metadata Filter arguments in supported scalar and
  aggregate queries use the existing resolved WHERE and positioned-row owners.
• Joined metadata window queries use the shared producer/coroutine path.
• Corrected cumulative window peer-result publication.
• Representative physical LEFT metadata aggregates, correlated count+sum,
  derived JOIN count, Window JOIN, UNION ALL aggregate and LEFT ON versus
  WHERE-null compositions match pinned SQLite across all three text encodings.

Validation

Independent root review accepts the bounded local beta.2 product milestone.
Exact accepted source: 482 files completed, 8,684 test passes, five unchanged
skips, zero failures/cancellations, 16 prerequisites successful, and all
809 companion tests across 39 files passed; no input drift or unrun files.
Native/public common45, leads45 and six-family18 observations match typed rows,
all five metadata fields and two reset executions. Counts overlap and are not
a SQLite compatibility percentage. Five skipscan compiled/concurrent/corruption/
memory/recovery-copy cases receive no pass credit.

Actual Chromium/HTTP 50 checks and independently exercised installed demo/
original Chinook query passed on authenticated package bytes. The new joined
Window query has native/public and installed coverage, not invented additional
browser-inventory credit. Original unreduced20k and unpartitioned WR workloads
also completed under current ceilings; historical timeouts remain historical
failures, not retroactively green or causally explained.

Publication separately validates the versioned tarball, byte equality of every
emitted module/declaration to the accepted package, and the pinned public site.
Exact publication commands, hashes, failed attempts and remote outcomes are in
the external publication receipt. Accepted full-suite results are not claimed
as fresh publication reruns.

Installation and limits

Download jsqlite2-0.0.0-beta.2.tgz and SHA256SUMS from the
GitHub prerelease,
verify the tarball hash, then npm install --ignore-scripts ./jsqlite2-0.0.0-beta.2.tgz.
Alternatively serve the complete dist/ ESM tree and import dist/index.js.
No npm registry publication. GPL-3.0-or-later; LICENSE/NOTICE and corresponding
source accompany the release. Chinook retains its separate MIT notice.

This is bounded support, not all SQLite or arbitrary SQL combinations.
Broader generated/module Filter, joined/window/compound/planner compositions and
index-supported paths remain work. Exhaustive resource/interruption schedules,
native allocator parity, all-browser certification and hard-real-time guarantees
are not established. Tests-first chronology deviations and failed setup attempts
remain disclosed in accepted review evidence. Native SQLite is development-only;
there is no native/WASM/runtime server evaluator.

The playground retains its60-second watchdog and1000-row cap, not promises of
universal performance or hard preemption. See the exact-version API,
guide and SPEC. Beta.3 index work proceeds
separately; beta.2 is a milestone, not whole-project completion.

JSQLite 0.0.0-beta.1

JSQLite2 0.0.0-beta.1

First public beta, published with explicit owner authorization. The accepted
local-beta source is d2780fb63b20d560ed1f960c32b221b850e02573 (runtime
331128e5686362916373f3047431469bb3a8c42a). Release metadata, licensing and
publication documentation do not change its TypeScript engine. Post-beta
development is deliberately excluded from this release.

Delivery

Download the tarball, checksum list and corresponding source from the
GitHub prerelease.
Install the local tarball with npm, or serve its complete dist/ ESM tree and
import dist/index.js. No npm registry publication is involved.

The playground uses this pinned package.
Queries execute locally in a dedicated worker, with cancellation and a
60-second demo watchdog. The demo is capped at 1,000 rows. These are containment
limits, not promises about arbitrary SQL performance or engine preemption.

Changes since alpha.7

Bounded native-backed support now includes repeated recursive CTE readers,
recursive joined UNION/UNION ALL arms, recursive and WITHOUT ROWID RIGHT/FULL,
mixed physical/JSON USING/NATURAL and RIGHT/FULL, ordered-derived outer filters,
and multi-column joined/retained compound inputs. The original nine-item gap
inventory's representative cases all match the pinned oracle, including typed
rows, metadata and reset behavior across all three database encodings.
Metadata aggregation and correlated consumers received corrections after the
immutable alpha.7 release; alpha.7 itself retains its disclosed defect.

Evidence and limits

The accepted runtime's complete integration run finished 476 files, with
8,285 TAP passes, zero failures/cancellations, five existing skips, plus five
separately inspected non-TAP scripts. 39 companion files / 809 tests passed;
all 16 fixture prerequisites completed and there were no timeouts, unrun files
or input drift. Five skipped skipscan compiled/concurrent/corruption/memory/
recovery-copy cases receive no passing credit. Counts overlap and are not a
SQLite-compatibility percentage.

Independent installed-package evidence includes strict declarations/imports,
real Chromium Fetch checks (48 main plus two separate resource controls), six
demo groups and the original Chinook query with typed ordered rows/full
metadata/three executions/two resets. Release publication additionally checks
the actual versioned tarball and public playground. Fresh publication commands,
artifact hashes and outcomes are recorded in the publication receipt; earlier
accepted runs are not described as newly rerun.

This remains a bounded beta, not all of SQLite. Important remaining work:

• Legacy mixed metadata joins still reject some generated outer-column Filter
  arguments; post-beta repair is ongoing, not included here.
• Arbitrary joined aggregate/window/compound/nested and nondeterministic virtual
  Filter/planner combinations are not universally admitted or certified.
• Resource/cancellation checks are cooperative and finite; exact internal
  failure-phase coverage, native allocation/work parity, universal browser
  compatibility and hard-real-time guarantees are not established.
• Some recursive consumers eagerly materialize retained rows, with disclosed
  latency/memory costs; further faithful index-supported paths remain work.

See the exact-version API, translation guide,
conformance evidence and SPEC. Temporary gaps
remain obligations, not newly permanent exclusions. Writes, recovery of WAL or
journal sidecars, host extensions and native/WASM runtime backends stay excluded.

License and history

GNU GPL version 3 or later: LICENSE,
notices. Chinook has its own MIT notice. Corresponding source
is provided with the release and website. Previous alpha tags/assets are not
rewritten. Beta is a milestone; continued development is not project completion.

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.

JSQLite 0.0.0-alpha.6

Experimental browser-safe, read-only TypeScript ESM alpha. No native SQLite or WASM runtime backend; not beta or full SQLite compatibility.

This release includes represented trigger/generated/STRICT reads, ordered filtered compound SELECT via shared VM merge machinery, recursive CTE join/aggregate and JSON/metadata combinations, and the private B-tree bounded-copy performance repair. Exact admission boundaries are in the tagged docs/api.md; some deeper and RIGHT/FULL combinations remain unsupported.

• Accepted source: a572862f74876f8c29a7ab4697cfb5e9fc842840 (engine foundation 10f3d449).
• Unchanged accepted package: jsqlite2-0.0.0-alpha.6.tgz, 92 files, including 45 JS modules and 45 declarations.
• Package SHA256: 66dfc717f6b490b347f67064afea59a076d3c7ac462bde29e702c543949019d8.
• GPL-3.0-or-later: LICENSE and NOTICE.md accompany the unchanged package. Its private metadata/historical README describe the earlier local-only task, not this subsequently authorized public release.

Finite acceptance includes exact installed-package/type/security checks, Chromium current48 plus two separate gap probes, six demo groups, and the original Chinook query's ten native-matching rows across three executions/two resets. Prior source integration completed 348 files with 6,039 passing cases and five existing skips; counts overlap and are not a compatibility percentage. Fresh public-site browser checks passed before publication. Other browsers and universal performance are not certified.

Install the downloaded package locally with npm install --ignore-scripts ./jsqlite2-0.0.0-alpha.6.tgz. No npm registry publication.

Playground: https://salva.github.io/jsqlite/ (Pages deployment is separate from this release upload).
Release scope/build/evidence: https://github.com/salva/jsqlite/blob/public-site/docs/research/public-alpha-six-deployment.md

Alpha.5's tag and assets remain immutable. Ongoing beta workspace changes are not included. Historical local-only/publication-blocked notes at the source tag are superseded only for this owner-authorized publication, without changing prior acceptance or package bytes.

JSQLite 0.0.0-alpha.5

Accepted experimental read-only browser ESM alpha. Includes shared-WHERE aggregate planning, bounded task scheduling, stat1 skip-scan and parser-performance repairs. Not full SQLite compatibility; see the tagged source admission matrix. No native SQLite or WASM runtime backend. GPL-3.0-or-later (LICENSE and NOTICE.md supplied alongside the unchanged package). Source: a3eb296. Package SHA256: 075ba9862fde401d5223da940c7e6549fe0aadc935415326cce104239c320514. Alpha.4 remains immutable. Playground: https://salva.github.io/jsqlite/ . No npm registry publication.