Contact CSV Review v1.1.1 — verification scope (English)
Documentation revision 1; the tool itself is unchanged.

This is an English explanation of the historical verification record
검증범위.txt, recorded on 2026-10-09 at 18:48:16 KST.
The new document does not report a new customer, browser or income test.

Checked for the v1.1.1 repair:
- Ten file-lifecycle cases exercised the real bundled script in a synthetic
  DOM: pending reads, Clear everything, the fictional demo, encoding changes,
  failed reads, input limits, an empty selection and language changes.
- All ten cases passed after the repair. A late read from file A cannot
  replace file B's selected input, report or original-byte download source.
- Four Blob-created outputs and their correspondence to the original bytes
  were checked in that synthetic environment, not by actual browser downloads.
- Eleven core checks and sixteen Korean/English checks were regression tests.
  These 27 checks do not represent 27 newly added features.
- The approved core and the limits remain unchanged: 2,000 records, 80 columns,
  2 MiB, no inferred country codes, original rows and columns preserved and
  formula-like strings protected as text in generated report CSVs.
- No network, AI, analytics or persistent-storage API was added. The existing
  content security policy keeps connections and frames disabled.

Historical browser evidence:
- The earlier v1.1 version was exercised in desktop Edge over local HTTP,
  including language switching, a fictional 12-row example and four actual
  CSV downloads. Those results belong to that earlier version and environment.

Not verified for v1.1.1:
- Directly opening the HTML file via file:, the current actual browser/OS file
  picker and downloads, customer files, native Excel/CRM imports, mobile or
  older browsers, or the effect of extensions.
- Physically cancelling a pending read or securely erasing OS memory. The
  repair ignores obsolete results and clears application references.
- Actual customer identity, email delivery, CRM compatibility or migration.
- A purchaser's downloaded ZIP, a remote ZIP hash, customer acceptance,
  paid orders, sales, settlement or bank deposits.

The historical record's pre-upload sentence describes its recording time;
it is not a current seller-status statement. ZIP integrity, seller settings,
buyer delivery and income must be verified separately. A successful report
does not prove two records belong to the same person. Review candidates and
your destination's import requirements manually before using them.