Have something to say?
Corporate provisioning: outstanding fixes
**Area:** Coach Pulse Admin — User Management / corporate provisioning **What this covers:** the open corporate provisioning defects and change items carried forward from the Aug 17–21 QA passes. **Open app defects from the Aug 17 test:** 1. Corporate rows default to "Sales Associate" job title — remove the default, collect no job title 2. Role/privilege not editable after creation — edit should route through the same role picker as create, with an audit entry 3. Re-adding an existing email dead-ends on "already exists" — add flow should offer in-place reactivate/link 4. Store "Add user" affordance shows in the corporate context and should be hidden **Open role/scope items:** - Market SuperAdmin containment still fails on the admin console read path (reaches content outside its market) — retested on both EU and North America - Read-Only still presents actionable controls (Today, Rewards, image upload). Requirement is zero clickable actions in the admin console, server-side refusal, Knowledge Base unreachable by direct URL - Consumer Access requires a region selection; it should require MARKET (NA / EU / Global). Existing region-only accounts to be backfilled by script **Reference:** CoachPulse_CorporateProvisioning_QA_Findings_v1.docx, CoachPulse_RoleValidation_QA_Findings_v6.docx, CoachPulse_AdminAccessControl_QA_Findings_v1.docx, CoachPulse_ContentRoleConsolidation_ChangeRequest_v7.docx
Culture Feed: feed freezes during use
**Area:** Coach Pulse — Culture Feed (consumer) **Issue:** Culture Feed freezes during use. Logged from Harrison's fix list on Aug 25 2026. **Still to capture before dev picks this up:** - Environment (PROD / QA) and app version - Device and browser - Whether it freezes on scroll, on video playback, or on opening a specific post - Provider of the post in view when it froze (Instagram / TikTok / article) - Whether the whole app freezes or only the feed surface **Possible relation:** the Culture Feed has an open cluster of player-layer defects — audio autoplay (four occurrences, all TikTok), countdown timer jumping, and Instagram static/carousel posts rendering through the video card shell. Worth checking whether the freeze shares the provider-embed root cause before treating it as a separate defect.
Culture Feed: Publish Week changes do not stick on the post card or timeline
**Area:** Coach Pulse Admin — Culture Feed **Issue:** Changing Publish Week on the Create/Edit Post form saves in settings, but the post card and timeline footer keep showing the old week. Repro: post "A realistic day in my life with my Tabby @coach" stayed at week of 2026-07-27 after being set to Week of Mon, Aug 24. **Related:** weekly publish count per region shows the configured weekly target (e.g. 12/week) as the published amount even when fewer posts have gone live, so regions behind on content read as complete. **Root requirement:** publish week and its counts must read from current saved state, everywhere it is displayed. **Acceptance:** rollups, region views, the admin post card/timeline and the associate-facing feed all read the same week value after a change. Regression check across all four surfaces. **Reference:** CoachPulse_CultureFeedAdmin_QA_Findings_v1.docx (F1, F2 — both P0)
Session report headers still read "What to celebrate" — should be "Where it clicked"
**Reported by:** Lauren Mucci (Teams, Aug 24 2026, 10:26 AM). Sarah Heitner confirmed. **Issue:** The practice-session report screen in production still carries the Aug 14 section wording. The strength/growth block renders a combined eyebrow reading "What to celebrate & where to lean in", a left tile labeled "What to celebrate", and a right tile labeled "Where to lean in". The right tile is correct. The left tile and the combined eyebrow are not. **Expected:** | Element | Current | Target | | --- | --- | --- | | Combined section eyebrow | What to celebrate & where to lean in | Where it clicked & where to lean in | | Left tile label | What to celebrate | Where it clicked | | Right tile label | Where to lean in | no change | Per the Aug 19 / Aug 20 feedback-screen decisions, the pair is "Where it clicked" (highest-scoring ELX area) and "Where to lean in" (lowest). The celebrate phrasing was explicitly rejected. **Scope:** String-level only. No scoring, layout, ordering or binding changes. Both instances must change, and every supported market language needs the equivalent update. A repo-wide search on the celebrate phrasing should return zero live matches when complete. **Notes:** Not testable in the prior QA pass (per Sarah). Went live Friday as a fire drill, which is how the older copy carried through. Harrison committed on the thread to switching it ASAP, realistically Thursday Aug 27. Fix spec: CoachPulse_SessionReportCopy_Fix_v1.docx
Culture Feed video: second tap on the volume control pauses playback instead of re-muting
Surface: Consumer PWA · Culture Feed · video card. Environment: Production. Severity: P1. What is happening. Culture Feed videos begin playing with audio off. Tapping the volume control turns audio on and the video keeps playing, as intended. Tapping the volume control a second time — the associate’s attempt to turn audio back off — pauses playback rather than re-muting. Mute state and playback state are being changed by the same gesture. Why it happens. The volume control is nested inside the video card, and the card carries its own tap-to-play/pause handler, so a tap on the volume icon runs both the mute toggle and the playback toggle. The first tap looks correct only because the unmute path calls play() explicitly (browsers block unmuted autoplay, so unmute has to re-kick playback), which immediately undoes the pause the card handler just applied. The mute path has no equivalent play() call, so on the second tap the pause is the only change the associate sees. Steps to reproduce. Open the Culture Feed in the Consumer PWA and scroll to a video post. Video autoplays muted. Tap the volume control — audio turns on, playback continues. Tap the volume control again to turn audio off — the video pauses instead of muting. Proposed fix. Stop the volume control’s event from reaching the card: call stopPropagation() and preventDefault() in the mute toggle handler, and add nativeEvent.stopImmediatePropagation() if the card’s play/pause listener is attached natively rather than through React (React 17+ delegates at the root, so a native ancestor listener fires first and is not stopped by React’s stopPropagation alone). In the same pass, remove the play() call from the unmute path so mute state and playback state are fully independent. To confirm during the fix. Whether the card’s play/pause listener is a React onClick or a native addEventListener — that determines whether stopImmediatePropagation is also required. That the volume control is not nested inside a card-level link or anchor wrapper, which would introduce a third handler on the same tap. Verification on a physical iPhone in the installed PWA — iOS Safari can dispatch pointer and click events separately on some button configurations and reproduce the double-toggle even after propagation is handled. Reference: CoachPulse_CultureFeed_VideoAudio_QA_Findings_v1, finding F1.
C360 endpoint cutover to production
The QA C360 gateway froze after 07-25, so the nightly acquisition job has been writing stale numbers while still reporting success. This cutover points the job at the production endpoint and production client-id. Change: update the client-id in Secrets Manager and register new ECS task-def revisions adding the C360_URL variable. Environment and secret only. No schema change, no frontend deploy. Prerequisites: the production gateway must allowlist our egress IPs 3.93.139.220 and 3.93.243.176. Cutover should happen before Sunday 08-09, after which one week of data becomes unrecoverable. Rollback: re-register the prior task-def revision and restore the old client-id. Dependency: AWS writes require Ajay, as our role is read-only. Full runbook held separately.
Tapestry AI Summit Training Module Gameplay
Create new version of Train module gameplay where users sign up with email and complete 1 of 3 available personas. Scores are logged and full scoring reports emailed top user. Leaderboard accessible from admins who name winners./