coulomb-social/docs/usecases/reichelag-weekly-call.md

CSOC-UC-008 — ReichelAg weekly founder call

Evidence: user-confirmed workflow, 2026-10-06. Original Bubble behavior was reported by the user; no fresh browser observation or private notes inspected. Owner: CSOC-WP-0008-T03/T05/T08/T09/T10. Transfer: pending user review, deployment and real-content reconciliation.

User goal and actual workflow

Every week I hold a phone call with ReichelAg's founder. I use the previous call's full protocol as the starting point for the next call's bullet-list agenda. I edit the copy by hand, document the call in the new protocol, then copy the protocol's content to the clipboard and paste it into an external email client for manual distribution.

The user explicitly confirmed: copy the full protocol, then edit it by hand. Duplicate must not remove closed points, summarize content, or alter the source. The way notes are produced from the call beyond manual editing is unspecified; no AI transcription/recording or automated mail delivery is assumed.

Original steps (confirmed by description; exact UI pending observation)

1. Open ReichelAg and locate the latest weekly-call entry.
2. Make a copy of that complete entry for the next call.
3. Edit the copied bullet list by hand to prepare the agenda.
4. Record the new call's protocol in the copied entry.
5. Use the copy-content-to-clipboard icon/button.
6. Paste the notes into an email draft and distribute it manually.

Equivalent rebuild journey

1. Sign in and open the migrated ReichelAg space; open the latest protocol.
2. Choose Duplicate page, give the next entry a distinct slug/title, and create it in the same space. Full markdown, metadata and relative Visual asset are copied; arbitrary body-linked assets remain a fidelity gap.
3. Open Edit page and edit the copy's agenda/protocol by hand. Save and reopen it. The old protocol must remain unchanged.
4. Choose Copy content to clipboard on the finished page. Rich-text email editors receive rendered headings/bullets; plain-text editors receive text with bullet markers. App navigation, action buttons, metadata frontmatter and source diagnostics are excluded.
5. Paste into the external email draft, check formatting and recipients, then send manually. The app does not contact an email provider or send messages.

If clipboard access is blocked/unavailable, show the prepared plain text selected for Ctrl+C/Cmd+C. Do not report success without a successful clipboard write. Readers may copy content they are allowed to read; they may not modify protocols. Unrelated members must not gain access to the protocol or its copy interface.

Review milestone for this concrete cohort

“I can use last week's real ReichelAg protocol to prepare next week's call, write the new protocol without changing last week's record, and paste usable notes into my email client. I can return later and the protocol is still there.”

Review on the pinned new-app release with a privately nominated latest protocol:

Check	Expected outcome	Status
Find the latest entry	Date/title/navigation identifies the correct call	Pending real-content review; no automatic latest-entry selection implemented
Duplicate	Full protocol preserved; independent new entry	Implemented; synthetic regression evidence
Prepare/write/save	Hand-edited bullets and notes reopen correctly; source stays unchanged	Implemented; synthetic regression evidence
Copy for email	Rendered list/heading formatting or readable plain bullets; no app chrome	Verified with synthetic Playwright clipboard interception; real mail-client review pending
Clipboard blocked	Selected manual text and clear instructions; no false success	Verified with synthetic Playwright clipboard interception; real mail-client review pending
Paste into your mail client	Useful protocol presentation and working relevant links	Pending your actual mail-client review
Privacy and continuity	Access stays appropriate; restart/paired recovery succeeds	Access tests exist; live persistence/restore pending

User acceptance is still pending. Historical reichelag rehearsal contains 30 pages/29 assets (2026-08-13); it does not prove the latest weekly protocol is present, complete or in the correct page/chunk form. Reconcile that privately before a review. Missing protocol structure, imagery or links becomes live work, not a silent acceptance exception.

Implementation evidence — 2026-10-06

uv run pytest: 87 passed, including full-copy/manual-edit/source-independence and reader copy visibility. New workflow test passes Ruff. node scripts/test-copy-content.mjs: Chromium checks pass for native ClipboardItem HTML/plain payload construction, plain-only fallback and denied/manual selection. Clipboard writes are intercepted with synthetic content; no real clipboard or email recipient is used. This does not certify pasting into the user's mail client.

Continuous regression protection

Registered in registry.json with a synthetic scenario and mandatory fast/browser node IDs. make check drives the actual isolated app through duplication, manual editing, reopen, HTML/plain/manual clipboard export and reader/outsider checks. See README.md for setup, reports and extending protection to further cases. This protects established behavior without marking productive transfer accepted.