PulseTrade.Comm.Spa.Dynamic 0.1.48

PulseTrade.Comm.Spa.Dynamic

This project is a dynamic SDUI (Server-Driven UI) and Actor extension for PulseTrade.Comm.Spa, built with WebSharper.

Current 0.3.7 accepted-query authoritative settlement

Daedilus在0.3.6邊界結案後把獨立2018 return-tail縮成Renderer時序：ChangeTaQuery accepted callback於對應authoritative frames完成prepared commit前求viewport，舊2018 timeline回NoIntersection並保留Viewing1-1028；稍後DataRevision25/queryGeneration19的1450-bar frame又因scope未變而不會重套。0.3.7以dispatch當下DataRevision/queryGeneration建立generation-scoped pending intent，只在兩個authority皆前進的prepared frame上消耗；newer local query可取消舊intent，無timer/retry/wire變更。Source b9a3628249785bb0a734e86bee9c3e3721022dab已push；final Renderer／Interactive.Client SHA-256=A140F48AA5BC69AEF046954F3D9EC239BCAF684C3B2D3B8D575169FFDC356BD7 / 796941913373DC1CBDF6639EA7FB3B5C856C0D045CF2808C234E59F3E536EF17，RepositoryCommit/ProductVersion與SDK10.0.402 cache均exact。DYN-T-733/733B 2/2、Renderer124/124、Interactive.Client20/20、package verifier與fresh exact-package BrowserDemo Release均GREEN（僅既有WS9002／0 errors）。Daedilus原真return gate仍是consumer close authority，未GREEN前不宣稱完成。

0.3.6 navigator right-edge release

Renderer／Interactive.Client 0.3.5 fixed the cross-axis resident-track left edge and passed Daedilus left-edge-80 plus true Earlier coverage. The same exact consumer then exposed the symmetric right visual edge: the rendered move target reaches the track edge, but preserving its 1px grab inset rounds the bar delta three bars short (local4418 instead of maxStart 4421) even though the action already carries the correct NavigatorWindow intent. The 0.3.6 release freezes the actual rendered move-target bounds at pointerdown and snaps only an inside-track selection whose translated visual edge reaches the physical track edge; a pointer outside the track remains Later coverage. Source e0575622b5efcf78619d37a68f91e353af417d6a is pushed. Final Renderer／Interactive.Client SHA-256 are 36593858F26EA84270C0956818B404304C8FB0A17667A129EA9721A4ED8ABB48 and 4B76912C398F740EB2A7477130332DEB9C7F33BC5BE44BEC95EBD211C184E2D6; provenance and SDK 10.0.402 hashes match. Final owner gates are Renderer 122/122, Interactive.Client 20/20, package verifier PASS, and fresh exact-package BrowserDemo Release with the existing WS9002 warning and zero errors. Daedilus exact real Gate B is GREEN for resize, middle, left edge, Earlier overscroll, right edge (local4421), and Later overscroll with zero browser/action errors. Adjacent A/D, highlight, Tagging, FirstPaint, No1K, and formal-core stress are also GREEN. The pre-existing independent 2018 return-tail case remains a separate pending issue and was not changed by this release.

Current TA release graph

The current owner release graph remains Contracts [0.1.36] → Renderer [0.2.8] → Interactive.Client [0.2.8]; Dynamic.Ptcs [0.1.57], and Ptcs.Client [0.1.132] exact-pins Contracts and Renderer. RFC-0032/0033/0034/0036 provide independent overview/detail axes, bounded overview anchors, event-time selection/stripe alignment, provider-open-earlier range authority, stable loaded-coverage data refs, pending/resync rebase, exact rendered-preview/release parity, optimistic viewport continuity while a coverage action awaits both its response and matching projection, semantic left/right/body gesture ownership across reactive SVG replacement, and active-gesture ownership across authoritative-frame replacement. Daedalus formal consumption rejected 0.2.5 because a new gesture could fall back to stale authoritative geometry while the prior response was pending. The owner-verified 0.2.8 replacement keeps the visible rendered draft and ratios as the next pointerdown authority. Renderer 0.2.8 is public; Interactive.Client 0.2.8 is installed in the active SDK local feed and NuGet.org reports it already exists while the public v3 index catches up. Daedalus owns the pending 18884 chained-gesture rerun. The separate global resident thumbnail UI is not present in 0.2.8. Its owner implementation is Contracts 0.1.38, Renderer 0.2.10, and Interactive.Client 0.2.10; all three have verified fresh local-first packages. Published 0.1.37/0.2.9 artifacts reused stale Release DLLs and must not be consumed. Renderer/Client 0.2.10 package-consuming BrowserDemo build and focused Expecto Playwright pass; Daedalus 18884 formal consumer validation remains pending. Renderer 0.1.130, 0.2.1, and the failed local 0.2.6/0.2.7 candidates must not be consumed.

Actor Dynamic / Actor Argu modes

PulseTrade.Comm.Spa.Dynamic owns Dynamic rendering and Dynamic target binding; PulseTrade.Comm.Spa owns the append page shell, key registry, pending replay, and actor-argu command path.

Current mode split:

Key shapes:

Direct actor key:
[ actorAddress ]

DU/FormInput target:
[ actorAddress; duTypeOrTemplateKey; canonicalArgString ]

Explicit ActorArgu target through proxy:
[ proxyActorAddress; "target-v1"; targetActorAddress; duTypeOrTemplateKey; canonicalArgString ]

Dynamic proxy key:
[ proxyActorAddress; "proxy-v1"; rnActorAddress; targetKind ]

When an Actor Dynamic selected key is only [ actorAddress ], the extension intentionally returns no FormInput renderer. PTCS fallback input accepts arbitrary text or JSON DSL. If the actor replies with Canvas JSON DSL, the Dynamic message renderer draws the canvas; otherwise PTCS normal message rendering is used.

For ActorArgu Add Target Key, the selected key routes the command to proxyActorAddress because it remains the first key segment. PTCS core sends ActorArguTargetCommand.ActorAddress = proxyActorAddress, TargetActorAddress = Some targetActorAddress, and RawArgu = <input text>. The proxy actor owns native invocation and durability. Dynamic must not hide this route by creating or rewriting proxy actors in an add-key hook.

ActorsPage Renderer

RFC-PTCS-DYNAMIC-0005.actors-page-renderer.md defines the Dynamic-side contract for PTCS /actors.

This is not the generic Canvas message renderer. When PTCS provides an ActorsPage / ActorTopologyPage DSL document and the extension supports that renderer, Dynamic must render the whole Actors page: node blocks, actor hierarchy tree, grid, cards, reload/report controls, and status UI. The page must group actors by actorSystem@host:port and order node blocks as PTCS Host, GW Host, RN Host, then Unknown.

If Dynamic does not support ActorsPage, it must return not-supported and let PTCS use its fallback tree/grid/table. It must not display a Canvas summary card, raw JSON preview, or Expand Canvas button as a substitute for ActorsPage support.

First implementation slice keeps the renderer inside Client/ActorDynamicTab.fs instead of a new client compile unit. In this checkout, WebSharper 10.1.5.674 crashes wsfsc.exe when a new [<JavaScript>] client file is added, and also crashes on String.Contains; the current classifier uses a single IndexOf("ActorTopologyPage") gate. This is sufficient for PTCS page renderer dispatch because PTCS only sends ActorsPage documents to page renderers.

Current package slice: PulseTrade.Comm.Spa.Dynamic 0.1.3-beta106, PulseTrade.Comm.Spa.Dynamic.Ptcs 0.1.0-alpha7-win52, and PulseTrade.Comm.Spa.Dynamic.Ptcs.Client 0.1.0-alpha8-win70, aligned to exact PulseTrade.Comm.Spa 0.2.5-beta117. The adapters also consume the current Contracts alpha12 / Renderer alpha33 graph with exact FSharp.Core 10.1.302, avoiding the stale alpha11/alpha32 restore warnings. This is a dependency-only alignment; Dynamic renderer, SDUI wire, Actor Argu target and transient-channel behavior are unchanged. The current Actor Argu Add Target Key schema is [proxyActorAddress; "target-v1"; targetActorAddress; duTypeOrTemplateKey; canonicalArgString]; the invalidated beta64 actor-argu-proxy hidden rewrite path is historical only. Add Actor Key keeps the native actor address as its key and relies on the PTCS fabric's installed platform provider for low-cognitive string -> fCell2<string> -> native actor -> fCell2<string> -> reply dispatch.

The current stable transient adapters are PulseTrade.Comm.Spa.Dynamic.Ptcs 0.1.11 and PulseTrade.Comm.Spa.Dynamic.Ptcs.Client 0.1.19, exact-pinned to PulseTrade.Comm.Spa 0.2.19 and PulseTrade.Comm.Spa.Dynamic.Contracts 0.1.10. These releases are dependency-only; they do not change the Dynamic wire, renderer, reducer, or browser lifecycle.

Realtime TA新路徑使用PulseTrade.Comm.Spa.Dynamic.Ptcs 0.1.0-alpha6-win1 server adapter、PulseTrade.Comm.Spa.Dynamic.Ptcs.Client 0.1.0-alpha7-win4 pure WebSharper client adapter與Renderer 0.1.0-alpha5。server端exact PTCS beta85 + Contracts alpha4，持有authenticated transient context與canonical reducer；browser只走same-origin /sync/ws、bounded ta-browser.v1 wire與Renderer，不接受任意URL或credential。真PTCS desktop/mobile gate位於tests/PulseTrade.Comm.Spa.Dynamic.Ptcs.LiveDemo與scripts/verify-ptcs-ta-live-playwright.fsx。Legacy Dynamic bundle暫不reference新adapters；禁止raw JavaScript或HTTP polling。

poc.full.nuget.journal.ACL.fsx quiet startup mode must not capture Console.Out with a disposable StringWriter: Suave can retain the writer after startWithSharing returns, and later listener output can crash with ObjectDisposedException. The script now uses TextWriter.Null while suppressed. Latest quiet no-wait proof: dotnet fsi --exec .\src\poc.full.nuget.journal.ACL.fsx -- --no-wait --local-port 18102 --github-port 18101 --cluster-port 18801 --pcsl-root .\.pcsl\verify.acl.beta56.dual-host.quiet.

0.1.3-beta56 keeps the normal Release WebSharper compile/pack path against PTCS 0.2.5-beta66. If wsfsc.exe fails with UnauthorizedAccessException deleting src\websharper.log, stop stale wsfscservice.exe, remove the generated src\websharper.log, and rebuild; this is a compiler-service file-lock issue, not a Dynamic source failure.

The current renderer already builds a page-level Actors UI with action shell, count cards, host/port node blocks, hierarchy rows, grid rows, and boxed + / - tree toggles. A PTCS source-host Playwright MCP gate verified that Dynamic owns the /actors DOM when loaded: fallback rows are 0, blocks are ordered PTCS Host → GW Host → RN Host, full akka.tcp://... addresses are visible, and tree toggle clicks actually collapse and expand rows. 0.1.3-beta24 restored the early hierarchy visual language inside each host block: virtual /user and /system ancestors stay in the relevant PTCS/GW/RN block, rows expose status dots and connector lines, and virtual parents no longer create a synthetic Unknown block. 0.1.3-beta27 keeps that hierarchy, adds stable row metadata (data-node-kind, data-display-address, data-parent-id) and virtual-path grouping, and is paired with PTCS 0.2.5-beta40 so accepted Dynamic pages do not mix PTCS core fallback actor-node / actor-card DOM underneath the Dynamic page. 0.1.3-beta29 adds the browser-local Actors report schedule start/stop control and supersedes 0.1.3-beta28, whose pushed package used a stale source Release JS bundle where schedule stayed disabled. 0.1.3-beta30 adds offline-like status display and ordering support for the PTCS beta41 backend cleanup path; default public /actors reload now removes stale/offline node blocks before Dynamic renders the page. Latest public 81 health/alignment release is live81-ptcs-beta66-dynamic-beta56-acl-reload-202607010805; authenticated ActorsPage evidence is G:\PulseTrade.fs\log\20260701\ptcs81-beta66-actors-snapshot.md, G:\PulseTrade.fs\log\20260701\ptcs81-beta66-actors.png, and G:\PulseTrade.fs\log\20260701\ptcs81-beta66-actors-console.txt. The reusable accepted-path gate is G:\PulseTrade2.fs\Libs\PulseTrade.Comm.Spa\Scripts\verify.actorsPageDynamic.playwright.fsx; the PTCS fallback gate is G:\PulseTrade2.fs\Libs\PulseTrade.Comm.Spa\Scripts\verify.actorsActorTree.playwright.fsx -- --with-unsupported-client-extension, with Playwright MCP evidence at G:\PulseTrade.fs\log\20260629\20260629001159.actors-unsupported-fallback-playwright-mcp.png. src\poc.full.nuget.2.fsx is the beta41/beta30 POC that keeps Actor Argu Add target key available while disabling + Page Actor Dynamic page creation; it also registers its real nuget2-echo actor into PTCS actor registry so /actors is non-empty. POC2 browser evidence is G:\PulseTrade.fs\log\20260629\poc2-actors-page-fixed-deep-snapshot.md and .png. src\poc.full.nuget.fsx remains the original beta40/beta29 full POC. Full strict schema parsing, server-side persisted report scheduling, restart/cache sync, and failover visual states remain tracked by DYN-WBS-519.

Verification

Current beta44 package verification uses the normal Release build from this repo path:

dotnet build .\src\PulseTrade.Comm.Spa.Dynamic.fsproj -c Release
dotnet run --project .\tests\PulseTrade.Comm.Spa.Dynamic.Tests.fsproj -c Release --no-restore

PulseTrade.Comm.Spa.Dynamic is developed under a long Windows path. If WebSharper wsfsc.exe crashes without diagnostics, first inspect whether stale wsfscservice.exe has locked generated src\websharper.log; stop that service and remove the generated log before retrying. If the problem is genuinely path-length related, use the short-path fallback command recorded in doc/Verification.md:

dotnet build .\src\PulseTrade.Comm.Spa.Dynamic.fsproj -c Debug `
  -p:BaseIntermediateOutputPath=C:\ptcsdyn-build\obj\ `
  -p:OutputPath=C:\ptcsdyn-build\bin\

WebSharper Bundle Project & NuGet Packaging Quirks

When developing a WebSharper Bundle project (or spa project) that is intended to be distributed as a NuGet package, there is an important behavior to note regarding how static assets (wwwroot) are packaged and consumed.

The Problem

By default, when you run dotnet pack on a WebSharper Bundle project, the compiled JavaScript files and static assets (located in wwwroot/js/) are NOT placed alongside the compiled .dll inside the lib/<tfm>/ directory of the resulting .nupkg.

Depending on the WebSharper/MSBuild pack path, they can be packed under either:

• content/wwwroot/js/
• contentFiles/any/<tfm>/wwwroot/js/

If your server-side F# code (e.g., an extension registration mechanism using typeof<SomeActor>.Assembly.Location) attempts to locate these static assets at runtime by looking relative to the DLL's path, it will fail when the library is consumed via a NuGet reference (like #r "nuget: MyPackage" or <PackageReference>). The DLL will be running from ~/.nuget/packages/.../lib/<tfm>/, where no wwwroot folder exists.

Dynamic demo actor contracts

• showcase-dynamic-actor：收到合法 fskynet-sdui payload時回顯該 payload；其他輸入回 simple showcase。
• sdui-echo-actor：回顯 ActorArguTargetCommand.RawArgu，供任意 Canvas DSL round-trip。
• showcase-dynamic-actor2：固定回 built-in complex showcase2；輸入 payload不會改變 marqueeData，這是 fixed showcase by design。

以上 actor都使用 ActorArguTargetCommand → ActorArguTargetReply contract。string-only/fCell2-only legacy actor需透過 explicit Add Target Key指定 proxy與 native target，不可直接當作 Add actor key target。

The Solution

To resolve these static assets from a NuGet cache, probe the local build path first and then both NuGet layouts. Do not assume that every generated package uses contentFiles.

Example of how to locate the wwwroot/js folder robustly:

let assembly = typeof<ShowcaseDemoActor>.Assembly
let dllPath = assembly.Location
let dir = System.IO.Path.GetDirectoryName(dllPath)

// Local development path (e.g., bin/Debug/net10.0/wwwroot/js)
let localJsDir = System.IO.Path.Combine(dir, "wwwroot", "js")

// NuGet package layouts seen in supported WebSharper pack flows.
let contentJsDir = System.IO.Path.Combine(dir, "..", "..", "content", "wwwroot", "js")
let contentFilesJsDir = System.IO.Path.Combine(dir, "..", "..", "contentFiles", "any", "net10.0", "wwwroot", "js")

// Fallback logic
let jsDir =
    [ localJsDir; contentJsDir; contentFilesJsDir ]
    |> List.tryFind System.IO.Directory.Exists

match jsDir with
| Some jsDir ->
    // Successfully found the assets, proceed to serve them
    let allJsFiles = System.IO.Directory.GetFiles(jsDir, "*.js", System.IO.SearchOption.AllDirectories)
    // ...
| None ->
    // Register no script URL and report the missing extension asset explicitly.
    ()

The beta72 server extension implements this ordered discovery. Host/demo deployment may also copy the discovered files into its extension directory, but it must copy from the package's actual layout rather than hard-code one path.