Upstream: Adopt dashboard contracts and retire integration glue

[kent8192]

Prerequisites

• Searched open and closed dashboard integration/form trackers.
• Reused existing Upstream: Adopt generated views for named auth ClientForms #903, Upstream: Adopt the owned-runtime ModelForm view for clusters #904, Upstream: Share URL declarations for native-only HTTP endpoints #905, and Track ORM conditional partial update support for API token usage touch #726 rather than filing replacements for their original upstream requests.

Summary

Track downstream adoption of the framework integration improvements listed below. Completion means that a containing release has been adopted, obsolete application glue has been removed, and the same dashboard workflows pass through the supported APIs.

This issue coordinates adoption and cross-feature verification; it does not duplicate the implementation scope of linked issues.

Motivation / Problem

The dashboard owns socket retry/teardown, direct DOM notification updates, custom build-time settings preparation, and WASM asset fingerprinting. Several form and routing improvements already have dedicated adoption trackers. A version bump or an upstream issue closure alone does not prove that the consumer has stopped relying on its old implementation.

The source baseline is Cloud b860e667cfeb2f0b4e7e299c18d6fbc4305f2917, whose dashboard pins alpha.14.

Proposed Solution

New framework work to adopt

Upstream work	Downstream removal target
kent8192/reinhardt-web#6333	Replace reusable socket/retry/lifecycle machinery in shared/client/ws.rs; retain Cloud-specific subscription policy.
kent8192/reinhardt-web#6334	Adopt the validated form-to-patch bridge where it removes mapping duplication, after the immediate application repair in #909.
kent8192/reinhardt-web#6335	Replace selector-based badge changes and split log state with typed subscriptions and Query/Signal state updates.
kent8192/reinhardt-web#6336	Remove temporary runtime-secret assignments used only for collectstatic.
kent8192/reinhardt-web#6337	Remove bespoke shell hashing/renaming of the WASM/JavaScript bundle.

Existing trackers to reuse

• Upstream: Adopt generated views for named auth ClientForms #903: named auth ClientForm views; upstream implementation PR feat(pages): render named ClientForms with owned mutations reinhardt-web#6302 is merged.
• Upstream: Adopt the owned-runtime ModelForm view for clusters #904: configured ModelForm views for cluster creation; upstream implementation PR feat(pages): render ModelForms through configured mutations reinhardt-web#6301 is merged.
• Upstream: Share URL declarations for native-only HTTP endpoints #905: shared URL declarations; upstream implementation PR feat(routing): erase native handlers from shared URL declarations reinhardt-web#6303 is merged.
• Track ORM conditional partial update support for API token usage touch #726: API-key usage-touch partial update. The tracker is closed, but the pinned source still contains its query-builder workaround. Verify the supported dependency API and retire the remaining workaround with its conditional-update regression test; do not infer adoption from the closed state.

For each row, record the implementing commit, containing published version, dependency/lockfile update, adoption PR, removed workaround, and regression evidence. Do not equate a merged development-branch PR with a published package.

Acceptance Criteria

• Feature: Use scoped partial writes for cluster mutations #909 is completed using the already-available partial-update API; it is not blocked on a new framework release.
• Existing Upstream: Adopt generated views for named auth ClientForms #903/Upstream: Adopt the owned-runtime ModelForm view for clusters #904/Upstream: Share URL declarations for native-only HTTP endpoints #905 acceptance criteria are verified through their existing trackers, with one runtime/mutation owner and unchanged public routes.
• Login, registration, protected navigation, cluster creation, one-time result display/dismissal, and logout pass through the adopted APIs.
• Disconnect/reconnect/resubscribe/refetch and subsequent logout/login leave no stale socket, subscriptions, or cached identity.
• Live status and log updates use explicit application state rather than an independent DOM-only state path.
• Static collection runs without unrelated runtime secrets or live application services after #6336 adoption.
• Browser loading succeeds with manifest-generated JavaScript/WASM/CSS paths after #6337 adoption.
• The remaining Track ORM conditional partial update support for API token usage touch #726 workaround is either removed using the supported API or retained with a concrete verified blocker and removal condition.
• Native, WASM, browser, and database checks record actual commands and results for the exact adopted dependency set.
• Close only after the adopted paths and removable glue are verified, not merely because upstream issues are closed.

Alternatives Considered

Independent version bumps without consumer acceptance tests can preserve obsolete paths indefinitely. Reimplementing framework primitives in Cloud retains the duplicated ownership this work is intended to remove. Blocking the immediate #909 repair on future abstractions is unnecessary.

Additional Context

• Socket manager: https://github.com/kent8192/reinhardt-cloud/blob/b860e667cfeb2f0b4e7e299c18d6fbc4305f2917/dashboard/src/shared/client/ws.rs
• Build pipeline: https://github.com/kent8192/reinhardt-cloud/blob/b860e667cfeb2f0b4e7e299c18d6fbc4305f2917/dashboard/Dockerfile
• API-key workaround: https://github.com/kent8192/reinhardt-cloud/blob/b860e667cfeb2f0b4e7e299c18d6fbc4305f2917/dashboard/src/apps/auth/services/api_key.rs

Non-goals: changing Cloud's organization/RBAC policy, moving import orchestration into Reinhardt, or duplicating #900/#901.