STV 1.2.0 release qualification

Candidate: 1.2.0-candidate-1, based on Git revision 0e7cc3c2243e851f79b19a1aa60a062a907048f8 plus the retained worktree/source identity. The owner authorized 1.2.0 workspace preparation and full release qualification on 2026-11-01. No commit, tag, push, publication or deployment is performed.

Observed qualification

  • One complete main selection: 244 passed, 196 Python / 48 JavaScript, no failures, errors or skips. The Python reset wrapper also executes two Node command-sequence checks; those nested checks are not counted again.

  • Six separate final CR019 browser supplements passed on file and HTTP. The earlier four-case supplement is retained; its repeated cases are not added to the final six-case supplement total.

  • All 122 delivered canonical procedures have fresh mapped observations. Four occurrence-mode procedures remain explicitly deferred. Acceptance statuses and ADR lifecycle are unchanged; only assessed verification fields and latest case/execution links advance.

  • Windows 11, Python 3.13.17, installed Firefox 159.0, geckodriver 0.37.1, Node 24.21.0; direct-file and static HTTP browser workflows.

  • A fresh offline Python 3.10.9 consumer passes installation, dependency checks, installed-runtime import and clean host builds against this exact wheel.

  • Fresh 30,000-Need / 90,000-link host generation and current browser capacity measurements passed. Timings are observed measurements, with no invented performance threshold. No older fixture/result was substituted.

  • Four maximum-size SVG exports passed: 200 visible nodes, ten open cards, 1600/900px, file/HTTP. Real visible-hover exports reopened successfully on both transports. Representative source/reopened/narrow screenshots were visually inspected; raw SVGs are preserved losslessly with hash manifests.

  • The owner confirmed native automatic/prompted saving, cancellation and browser zoom behavior; see Owner native browser observations.

  • Fresh retained-archive inspection verified 47 archive identities and the complete licensing supplement. Original archives and Git history are unchanged.

CR019 criterion assessment

Pure snapshot tests cover schema/context validation, current-graph authority, hidden/removed IDs, seeded/project state, page memories, card age/order, 200/201-node bounds, independent storage keys, quota/getter/removal errors and geometry reuse. Real browser checks cover keyboard opt-in/out, reload/restart, expansion and stable placement, FIFO/card closing, independent saved views and pages, last-save-wins tabs, safe untrusted content, reduced card capacity, blocked storage, pending/stale/failed layouts, back/forward navigation and changed/narrow viewport behavior without startup focus theft. Current source contracts and requirement-to-case assertions were reviewed against these observations. No stored HTML is used as content authority.

Retained attempts and corrections

The initial runner records a Windows permission error during final HTML promotion, after strict Sphinx and publication audits passed. The fresh documentation retry succeeded without product changes. The original failed runner/log remains intact; final consolidated documentation/evidence checks are recorded separately.

The first consolidated documentation build rejected a short heading underline; it was corrected before the strict retest. Its failed log and final-validation-1 record remain retained, with no product or test-input changes.

The first Python 3.10 install lacked its Python-version-specific tomli wheel. That provisioning failure is retained; a fresh environment with the completed offline wheelhouse passed. The historical helper initially omitted retained development archives and the compressed cleanup evidence archive from its known checksums. Prior preservation-manifest checksums reconcile those inputs; the audited ELK fingerprint and complete supplement checks remain enforced.

The release runner now reports individual Node checks with process isolation disabled and runs local/published method-package gates. These are runner corrections, with no new product behavior beyond the already merged CR019.

Disposition and boundaries

Local executable qualification passed; final consolidated gates are retained in final-validation.json. Release approval and successful hosted checks remain required before publication. Do not infer an existing release/tag from these local observations. The final release commit does not exist yet.

Qualified scope remains Windows/Firefox on file and HTTP. Other operating systems/browsers, mobile/touch optimization, occurrence mode and universal SVG-editor support remain deferred. The existing owner-authorized PR012 branch-protection/provenance hardening disposition is unchanged.

All distributions, including older versions, remain in dist/. The owner approved only the concrete cleanup list in Workspace cleanup review after testing. Post-release workspace review remains due when publication completes.

Evidence

  • Canonical observations (retained in the engineering checkout)

  • Verification assessment (retained in the engineering checkout)

  • Exact distribution checksums (retained in the engineering checkout)

  • Final CR019 supplemental report (retained in the engineering checkout)

  • Fresh minimum-runtime commands (retained in the engineering checkout)

  • Historical licensing assessment (retained in the engineering checkout)

  • Supplemental commands and attempts (retained in the engineering checkout)

  • Maximum-size export results (retained in the engineering checkout)

  • Visible-hover export results (retained in the engineering checkout)

  • Raw SVG observations (retained in the engineering checkout)

  • SVG preservation manifest (retained in the engineering checkout)

  • Final local gates (retained in the engineering checkout)

  • Proposed commit message (retained in the engineering checkout)

  • Tagging template (retained in the engineering checkout)

  • GitHub release note draft (retained in the engineering checkout)