SQLite change report — fictional preview
AI-authored by AES Technical Services. Experimental; no paid service or support promise.

Use only the included before.sqlite3 and after.sqlite3 samples, in that order.
Download them from the page, select them in the Before/After controls, and compare
table sample, exact text key id, fields n,s,b. Inspect the stored-value changes,
then export JSON. The input files are not changed. Other file content is rejected
by its SHA-256 before opening it with SQLite. Even rejected selected bytes are read
locally for this check; do not select private or real files.

This is a fictional usability task, not a qualified tool for your databases or a
claim of independent user testing. INTEGER, TEXT, BLOB and NULL are distinct.
INTEGER values are exported as decimal strings with explicit type tags, so large
64-bit values are not rounded into JavaScript Numbers. TEXT has no normalization,
case-folding or business-equivalence policy. BLOB values are hexadecimal.

Limits retained from the prototype: <=64 KiB/input, <=100 rows/input, one nonempty
unique TEXT key, 1-3 non-key fields, simple ASCII identifiers and ordinary tables.
REAL values, duplicate/empty/non-text keys, missing columns and unsupported inputs
are refused. The outward preview additionally accepts only the two sample hashes.
These are implemented scope restrictions, not arbitrary-file or scale guarantees.

No source-truth, complete-migration, live/WAL, financial, security, general-browser
or privacy certification is supplied. The page contains no upload/analytics code;
page/runtime/sample downloads still involve normal hosting requests. Results stay
in memory until you export them locally. This is not a guarantee about the host.

The static app requires HTTP(S), including a secure context for its local hashing;
localhost is suitable for a local review. Opening index.html as a file:// URL is
not supported by the SQLite SDK. This draft uses no Worker or OPFS storage.

Only the manifest-designated preview files are external-use material. The AES
repository, operating system, lab runners and other private implementation are
not included or licensed. Third-party components retain their own terms; see
THIRD-PARTY-NOTICES.txt, EMSCRIPTEN-LICENSE.txt, MUSL-COPYRIGHT.txt and SDK-README.txt.

Possible feedback, only if you choose to provide it through a separately offered
route: attempted steps, specific confusion/error, how you read the changes, and
whether an existing native/manual method would already suffice. Do not send
credentials, private files, employer/client details or confidential information.
No feedback channel, monitoring schedule, response promise or hire is established
by this draft.