Use shared private feedback with published UI beta.124 - #52
Conversation
|
Shared implementation merged in mdbase-dev/mdbase-connect#558 at ef35e45047a1aea15abeb58ddd8179dc12b8e16c after successful full merge-queue qualification (attempt 2). This consumer remains a draft: update UI pins/lockfile only once the normal coordinated release publishes these exports, then repeat clean-install CI and acceptance before merging. No package or service was published/deployed by this task. |
|
Qualified against the real published UI beta.124 from a fresh frozen install. Local full checks/build, PDF regression and intercepted desktop/mobile feedback acceptance passed. Exact-head GitHub CI passed on attempt 2 after one existing PDF long-press selection failure on attempt 1; no test/timeouts/checks were bypassed. Source integration is merged; live feedback remains disabled until the reviewed host/widget/acceptance gate in cloud-ops #741 is completed. |
Shared private feedback
Uses the actual published
@mdbase-dev/ui@0.1.0-beta.124, with normal registry dependencies/lockfile and no local worktree links. Integrated current Reader main and resolved the header conflict while preserving the new mark activity and resource/schema upgrades.The shared form owns description-first reporting, explicit optional screenshots/markup, three topics and consented bounded diagnostics. Reader supplies only fixed product/view/build metadata plus opt-in collection context. No telemetry, raw exception text or new delivery adapter.
Qualified locally from a fresh frozen install
Rollout boundary
The compatible Worker and UI publication are complete. Exact Reader/Writer host configuration is proposed separately in mdbase-cloud-ops #741 (draft), pending explicit host confirmation, Turnstile Edit credential and live staging/inbox acceptance. Leave deployment feedback variables unset until accepted; entries remain hidden. This PR does not alter widgets/secrets/Worker origins, enable feedback in a live build, or deploy production. Normal CI/merge and separate protected app rollout gates remain mandatory.