Skip to content

DKF v0.10.1: Live UI Preview & Visual Verification - #41

Draft
eybersjp wants to merge 122 commits into
mainfrom
feature/v0.10.1-live-ui-preview
Draft

eybersjp wants to merge 122 commits into
mainfrom
feature/v0.10.1-live-ui-preview

Conversation

@eybersjp

@eybersjp eybersjp commented Sep 19, 2026

Copy link
Copy Markdown
Owner

DKF v0.10.1 — Live UI Preview & Visual Verification

Adds automatic live frontend visibility to the existing v0.10 reliability baseline without changing the canonical lifecycle or Acceptance Engine.

Behaviour

  • UI/design context immediately arms Live UI Preview.
  • New apps safely enter WAITING_FOR_RUNNABLE_UI until the first runnable frontend exists.
  • DKF uses the project's declared scripts.dev and detected package manager.
  • Healthy DKF-known previews are reused rather than duplicated.
  • External local servers are adopted only when their localhost URL is explicitly supplied.
  • Provider-neutral browser contract supports host-controlled OPEN_OR_REUSE, native system browser, and headless test mode.
  • DKF-owned preview shutdown is ownership-token protected.
  • Normal dev/HMR workflow is preserved.
  • Formal browser-runtime-verification remains authoritative during VERIFY.

Workflow integration

  • /dk-autopilot
  • /dk-design
  • /dk-build
  • /dk-build-auto
  • development conductor
  • frontend implementer
  • browser runtime verification

Verification completed

  • Focused Live UI Preview suite: 14/14 passing
  • Real spawned development-server fixture: start -> health -> repeated ensure/reuse -> browser action -> ownership-safe stop
  • Explicit external-server reuse: adopted only by supplied localhost URL and never killed by DKF
  • Workflow integration assertions
  • npm package consumer proof for preview runtime and CLI
  • Documentation/version consistency
  • Plugin canonical/mirror synchronization
  • Full release:validate
  • Ubuntu CI: PASS
  • Windows CI: PASS
  • Windows-specific portability defects discovered by CI were corrected:
    • file URL/path conversion now uses fileURLToPath
    • npm/pnpm/yarn/bun Windows shims execute deterministically through cmd.exe

Real consumer validation

The existing private eybersjp/energy-capital repository was inspected against the detector contract:

  • Next.js 16.3.4
  • pnpm-lock.yaml present -> pnpm
  • scripts.dev = "next dev"
  • detector mapping -> pnpm run dev, framework next, normal Next candidate port 3000
  • real application routes/components are present under src/app

The current execution environment cannot materialize that private repository checkout or open its desktop browser, so the final Product Owner/local UX acceptance remains: run the v0.10.1 preview against the local Energy Capital checkout and observe browser open/reuse plus HMR during an actual UI edit. This is intentionally not represented as already completed.

Scope explicitly excluded

  • generic runtime-smoke acceptance for non-UI changes
  • Acceptance Engine redesign
  • baseline-failure semantics changes
  • visual-regression screenshot diffing
  • v0.11 Adaptive Reliability work

Version

Targets 0.10.1. v0.11 remains reserved for Adaptive Reliability.

Release state

  • Baseline frozen at baseline/v0.10.0-pre-live-ui-preview
  • Feature isolated on feature/v0.10.1-live-ui-preview
  • PR remains draft
  • main is unchanged
  • no tag, GitHub Release, or npm publication has been performed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant