Files
WRNexusJS/docs/plans/2026-10-19-release-blocker-clearance.md

6.0 KiB

Release blocker clearance

Date: 2026-10-19. Scope: clear repository checks and reverify the local design release candidate. Publication is explicitly held at the user's request. No packages, access changes or deployments were published.

Corrections

  • The CLI now checks that the optional auth plugin configuration exists before reading it. Auth initialization behavior and the public app configuration remain unchanged.
  • Tests use the simulated browser's button types and explicit event constructors rather than mixing happy-dom and native DOM declarations. The Bun-specific WebSocket options are typed at their runtime boundary. The public mountHtml().window API remains unchanged.
  • The generated-type check resolves the example's real installed dependencies through an isolated scratch junction. Generated route types were refreshed for the existing file-preview/file-viewer routes.
  • Lint findings were corrected without disabling source rules: cleanup still preserves the original error, event callbacks have explicit signatures, conditional assignments are explicit, and unused locals/imports were removed. Files identified by the formatter were normalized. Local authoring output, isolated package stages and scratch tooling are excluded from source lint/format checks.
  • Package version audits now validate independent stable semantic versions. The framework and editor still retain their existing 0.8 release-line checks; independently versioned 0.1 packages are no longer rejected. Negative probes cover malformed versions. No package versions were bumped.
  • Reactive runtime repetition was factored into seven private native-DOM helpers and eleven shared literals, outside extracted controller sections. Production minified size fell from 56,617 to 54,958 bytes. The 55,000-byte budget was not increased, and controller/nav/realtime budgets remain unchanged. All 169 CSR tests pass.
  • The showcase generator was rerun for the actual 104-component reference. The old manifest covered only 102 entries; the regenerated catalog contains 86 component detail pages, 14 blocks and four deliberately excluded page templates. Generated WRN blank lines no longer introduce trailing whitespace.
  • Editor compiler, language-server and extension bundles were rebuilt from current sources and verified under Node.

API review

The baseline differences are additive: no previously recorded export name was removed. Existing package entry points remain available. The following groups were inspected against their source entry points before acceptance; full type checking and the package suites then exercised the current implementation.

Package Reviewed additions
auth Verification-session helpers, explicit runtime configuration and SQL store options
block-editor Editor state/runtime, canvas, kit, source editor and recovery helpers
blocks Schema, registry, documents, commands, clipboard, variables and rendering APIs
CLI Explicit production connection overrides
core Request-local control-template registry helpers
dnd Manager/lifecycle, locations, announcements and reorder APIs
email-renderer Blocks, previews, styles, presets, MJML validation and rendering
payment Explicit configuration/API helpers and Razorpay signature verification
syntax Interpolation extraction and segment types
UI Navigation types and explicit chart/drawflow runtime/plugin subpaths
viewer Renderers, source resolution, safe parsing, optional formats, uploads and conversion

check:public-api now matches all 58 packages. The name inventory complements the type and behavior checks; no export removal was accepted to make the check pass.

Visual review

Only the two outstanding hashes were accepted: packages/ui/styles/SelectStyles.wrn and packages/ui/ui.css. Review covered token-backed input/dropdown surfaces, radius, focus-visible treatment, selected states and native/control boundaries. No visual source was rewritten merely to satisfy a hash.

The focused Select/design-system suites pass 18 tests and 2,388 assertions. Native browser inspection confirmed Soft dark selects use the system's 16 px radius and token colors, Angular light uses sharp corners, and Square selection, switch hydration, modal opening, focus and dismissal work with the optimized runtime. Screenshots are in output/release-blocker-clearance/.

Validation and release hold

The current validation record is output/release-blocker-clearance/report.json; the Phase 7 readiness report links back to it. The final combined bun run check:production run and the rebuilt installed-package consumers both completed with exit code 0. Repository release blockers are cleared. Publication remains on hold.

Completed verification includes the complete package suite (2,561 pass, one existing live PG/MySQL test skipped without connection URLs), 62 example tests, 14 service tests, 64 editor tests, workspace repair probes, independent-version negative probes, package integrity probes and source formatting. The 16-package candidate was rebuilt and reinstalled into isolated consumers: shared pins, two applications, draft recovery and upgrades, installed declarations, prebuilt Studio/CLI, real component previews, MCP stdio and MCP-only installation all pass.

No registry authentication, version availability or publication was attempted. Before an actual publish, verify the target registry and unused versions through the established release process. This task does not grant publication authorization. Existing application configuration, browser storage keys, invalid draft recovery and agent history remain intact.