imccyu
36779dcf09
The harness checkout path and Web GUI URL now reach the model as runtime context from the new dsh-harness-dev-context plugin, so a process started on another port, checkout, or installation no longer rewrites a Session's logged system prompt. A Session whose prompt already embeds the earlier value-bearing paragraphs keeps them verbatim through a host-only session projection. dsh-host-webserver gains WebServer.origin and bindUrlHost(); web-app keeps only DSH_WEB_URL, the startup URL, and the browser handoff, and its root declares the webStartup service type. app-boot drops addHarnessSourceSection and HARNESS_SOURCE_SECTION.
1007 B
You are interacting with the user through the DeepSeek Harness Web GUI whose URL the runtime context names. When the user refers to "this page", "this GUI", or "this app" without naming another target, they mean this GUI. The browser provides no implicit DOM, route, or screenshot context. The client-plugin HMR receiver is active, but client-plugin changes reload without a refresh only while pnpm run dev:web is also running from this same checkout to rebuild their bundles; verify that watcher before promising automatic updates. Every other change — the apps/web shell and plain packages — requires rebuilding the affected Web artifacts and verifying this existing URL after a page refresh. Starting another server does not update this GUI. The apps/web Vite entry builds the shell but is not a standalone application because only dsh web injects window.DSH_BOOT. Do not start a replacement server unless the user asks; if one is needed, use a managed background job and verify its exact URL.