c139 Phase 4, cloud session 2: the lab brought to calls 5 and 9

For: New session → Cloud, repository qpoint-io/design, from its default branch. Written: 2026-11-13, after review stop 1 was walked. Paste everything below the rule as the session's prompt.

Bring design c139's lab (medium A, the native skin) to two of Mark's rulings from review stop 1 (2026-11-13), record it in the cycle, and open a PR; don't merge it.

Read first: cycles/c139.updates/CYCLE.md, plan.md, review-1.md, the mocks app/pages/pages/native/settings-updates.vue and updates-tray.vue, app/data/c139-updates-mock.ts, the skin's chrome app/components/native/Window.vue, and the /partner-digest skill (.claude/skills/partner-digest/), whose sources (git logs, cycle Key Changes, sharp edges) feed the notes. The rulings below may not be in review-1.md on this branch yet; they are Mark's.

Call 5, ruled: the release notes are drafted automatically, summarised from the commit messages, with room for manual additions; engineering and design write the additions now, product later. Build:

• scripts/release-notes-draft.mjs: given a repository and a commit range (default: the native app, ../qnative, last tag to HEAD), group the commit subjects and the cited cycles' Key Changes into the partner notes' sections (What changed for you · What to try · Sharp edges fixed · Still known), each line citing its record, and write the draft as the feed's notes field (JSON) beside an "Added by the team" list the script never touches. When ../qnative isn't in the checkout, run it on this repository's own history to show it works, and say so.
• The Updates mock shows the generated lines and the "Added by the team" section, kept apart, with who added each line (engineering, design; product later).

Call 9, ruled: an App Settings rail item with a submenu (the layer's NavVerticalSubmenu pattern, design c98: a parent item with its pages nested under it) grouping General · Updates · Notifications · Data · Developer; ⌘, opens it; the tray menu gets "Check for updates…" and "Settings…". Build it in the native skin's rail (NativeWindow), drawn only where a mock links it as the skin's other sections are, so earlier captures keep their rail; the Updates mock sits under it; Notifications points to Safety & Security → Settings (design c147's noise control, /pages/native/safety-settings). The rest of the eleven rulings are the plan's defaults and need no change in the lab.

Then: voice-check every new person-facing string with the brand voice rules (brand/ and the qpoint-brand MCP's check-brand-voice if available); recapture the Updates mocks with the c139 shot program (scripts/shot-programs/c139-*.json, the window at 2×) if a dev server can run here (the layer package may need the workaround review-1.md §What was and wasn't verified describes); add a Key Changes bullet to cycles/c139.updates/CYCLE.md; open the PR with what was built and what couldn't be verified.