Align restored feedback with shared consent, optional email and focus behavior

[sarthakagrawal927]

Remaining shared feedback parity

The Oct 4 releases restored the launcher on desktop, tablet and phone, but the deployed npm 0.2.1 form still requires email and lacks the current shared component consent/privacy and focus management. This is a remaining requirement for the approved 02 Direct line rollout, not a new visual direction.

Bounded implementation

Keep the catalog publishable-key resolver, timeout, fail-closed behavior and focused/shared route suppression. Replace the legacy form with the existing first-party hosted https://sassmaker.com/feedback-launcher.js module, loaded only when the owner-approved hover feedback trigger is used. Mount the maintained shared form into an empty child node; preserve React ownership boundaries. Reopen with openSharedFooterFeedback; unmount on cleanup and use a fresh mount node after failure/unmount, since the current launcher retains its data marker. No new production dependency, credential or production configuration is required.

Use the deployed official shared component rather than an unverified npm version: npm latest is 0.4.0, while current source is 0.4.1 and that version is not published. Do not blindly bump the dependency.

Acceptance

• Optional email; explicit unchecked consent; working privacy link.
• Keyboard focus entry, trap, Escape dismissal and return to trigger.
• Reopen without duplicate roots/listeners; unmount safely during pending module/config work.
• Loader error/retry gives a truthful usable state; never submit without consent.
• Preserve focused practice and shared route suppression.
• Render at 390/768/1440 against approved shared direction; retain required design receipt/check evidence if composition changes.
• Focused regression tests for loading, cleanup, reopen and route suppression; existing release checks and exact deployed SHA qualification.

Tradeoff: lazy loading reduces the initial legacy-widget payload, but follows the shared mutable first-party asset. A reproducibly published matching package is the long-term pinning path. Current restoration remains live while this parity work is prepared.

[sarthakagrawal927]

Fresh live verification and prepared adapter — 2026-10-04

Actual Chrome dashboard form still requires email, has no consent checkbox, and closes to the page instead of the trigger. No form was submitted. Screenshot retained locally at /private/tmp/swe-feedback-before-20261004.png.

Created an isolated managed writer at exact remote main 54d52e0. Preserve-lane design preflight passed with a fresh receipt and before capture. The two-file adapter/test patch loads the official hosted launcher on intent, uses an empty fresh mount child, reopens the same live root, preserves catalog resolver and route guards, keeps the trigger enabled/focused, and handles script failure/timeout/retry and cleanup. No dependency, lockfile, credential, or production configuration change.

Frozen offline install succeeded with pnpm 10.33.2. git diff --check passed. Focused tests have not run: both managed invocations stopped before command start because the registry lock belongs to a currently live Motion task. The lock and other agent tasks are preserved. Rendered after-state, design completion check, CI, and deployed SHA qualification remain pending; this comment does not claim a shipped fix.

[sarthakagrawal927]

Rendered qualification update for candidate 69e0f31582e4bfb8116d4f55c89573586b904847:

• Full CI run 37191994997 passed all 991 tests plus quality/build gates.
• Preview deployment run 37192111701 succeeded with migrations disabled. Chrome returns ERR_SSL_VERSION_OR_CIPHER_MISMATCH for both emitted preview addresses; this is an unresolved rendered-preview qualification gap.
• Local browser harness renders the actual adapter with the current official hosted SDK and production stylesheet. At 390/768/1440px: one dialog, no horizontal overflow; native trigger measures 44px. Email is optional, consent is required and initially unchecked. Initial focus enters Title; Tab from Submit wraps to Close; Escape and Close restore focus to Feedback; repeated opens reuse one dialog.
• No form submission was made. Private screenshots and structured observations are retained in the owning managed writer.

The harness is not the complete candidate app and does not prove production release or focused/public-share route behavior. PR remains draft pending the full rendered/release gates.

[sarthakagrawal927]

Full-app qualification has progressed beyond the component harness:

• Candidate e91fc369664c270dca8221bd2e69b0bc37d1d473 passed CI 37192953403, including the complete quality gate.
• A CI-only artifact step retains the already-built static app for one day, excludes the large WASM directory, and uses read-only repository permissions. No runtime dependency or production deployment configuration changed.
• Downloaded artifact browser-build-e91fc369664c270dca8221bd2e69b0bc37d1d473 (provider artifact 11299243654) was rendered locally as the complete guest-mode app. Backend requests explicitly return 503 rather than being simulated as successful.
• Captured actual app plus shared feedback form at 390, 768 and 1440px. One dialog, initial Title focus, Escape restoration to Feedback. The settled /study/concept/tokenization route renders Tokenization and zero Feedback buttons, proving the focused-route guard in the complete candidate app.
• Private full-app screenshots and structured proof retained in the writer. Final rendered/design qualification and production release remain pending. Preview TLS failure is still unresolved, and no production result is claimed.

[sarthakagrawal927]

Production release verified:

• PR Fix hosted feedback consent, optional email and focus parity #123 merged to b03843ebc144c6ce2121236d7db2c6e80dcf4def.
• Exact-main CI 37193550997 passed the full quality gate.
• Production deployment 37193688908 succeeded, migrations skipped, production smoke passed. Pages deployment emitted 6f5bc228.swe-interview-prep.pages.dev.
• Fresh Chrome production dashboard loads assets/index-ebSIu1ey.js and the native Feedback trigger opens one shared dialog. Email is optional; consent is required and initially unchecked; privacy links to SaaS Maker. Title receives focus and Escape restores focus to Feedback.
• Complete CI-built app was rendered at 390/768/1440 and actual focused-study/public-shared-roadmap guards were checked. Fresh design-workflow receipt passes. Screenshots/raw reports and structured release proof are retained privately.

No QA submission was made during this qualification. This closes the obsolete form/consent/focus adapter repair, not the full Fleet capture rollout or response-alert qualification. Preview-host TLS remains an operational follow-up; production custom domain renders successfully.