v1.0.0 qualification

The owner authorized release in v1.0.0 released and accepted the pending remediation/presentation in Round 14: Owner acceptance for v1.0.0. The canceled earlier candidate remains historical. This candidate is based on 9d3b793928eef76c0043185d0ee2aff3968b5fb5 plus the recorded worktree/source identity.

Actual executed scope

  • 122 Python cases and 36 JavaScript cases passed; zero failures, errors or skips. These are one full candidate run, not combined development passes. 111 canonical procedures have new execution records.

  • Windows, Python 3.13.17, Firefox/geckodriver and Node identities are retained in candidate.json (retained in the engineering checkout). File and static HTTP transports, offline resource restrictions, Windows nested paths/retry, persistent details, classified rows and stable navigation are included.

  • A fresh 30,000-Need/90,000-edge capacity fixture built in 263.80 seconds. Each browser transport was measured three times; raw timings and process-tree memory observations are retained. No numeric performance budget is claimed because none is agreed.

  • The exact wheel passed isolated offline installation/Sphinx usage under the main test environment and independently on Python 3.10.9. Python 3.10 version, installed-package identity and dependency consistency passed.

  • Wheel and sdist come from the normal build frontend; the wheel is built from the sdist. Both exact archives, their SHA-256 checksums and member inventories are retained. All 17 wheel runtime members match checkout inputs byte-for-byte. Source-level suites are not misrepresented as installed-wheel tests.

  • Strict executable mapping, initial warnings-as-errors documentation, graph validation with required test coverage and source/published diagram links passed. Final staged documentation and evidence validation are recorded separately after consolidating these records.

Owner-accepted release deferrals

Release-runner improvements, hosted CI confirmation, cryptographic attestation and branch protections are deferred by the owner. Limited automated validatio... (STV_PR_012) remains analyzed/partially verified, and its unrelated draft designs are unchanged. These are owner-accepted nonblocking deferrals for v1.0.0. Repository visibility is a separate setting and is not changed by this work. Occurrence mode, touch and additional platform/browser qualification remain later scope. Widget JavaScript parity is outside the static-detail contract.

The underlying runtime evidence is fresh. Criterion review closes the five prior Windows-path partial dispositions: Deliver a self-contained do... (STV_SYS_003) (self-contained file/HTTP use), Provide original-object ins... (STV_SYS_006) (cross-page, metadata/body/local media, external fallback and original anchors), Publish full rendered details (STV_SWR_015) (rendered details and remote-resource fallback), Avoid runtime network loading (STV_SWR_017) (offline classic assets), and Use portable output URLs (STV_SWR_018) (nested file/HTTP-prefix portable paths). The full set combines the nested Windows/retry procedure, offline exploration, alternate-model rich content/original navigation, transport-marker, persistent-details and component URL/media checks. These five fields change to passed on actual full-run evidence; acceptance and stakeholder verification remain independent. The initial runner documentation build is a development build. The separate final staged build supplies the prescribed publication tree without modifying the runner.

Retained supplementary evidence

  • Exact archive checksums (retained in the engineering checkout)

  • Source archive member inventory (retained in the engineering checkout)

  • Wheel member inventory (retained in the engineering checkout)

  • Checkout/wheel equivalence (retained in the engineering checkout)

  • Supplement commands and times (retained in the engineering checkout)

  • Minimum-runtime installed identity (retained in the engineering checkout)

  • Minimum-runtime Sphinx/dependency check (retained in the engineering checkout)

  • Preparation commit message (retained in the engineering checkout)

  • Conditional tag template (retained in the engineering checkout)

  • GitHub release notes (retained in the engineering checkout)