feat: open Calendar commitments onto Event Lineage (v2.14.0)

[seonghobae]

Summary

Stacked on #260. Opening a Calendar commitment focuses Event Lineage the same way Weekly VOC and report-member opens do.

• Buyer Calendar names authorized commitments as current and asks the user to open one to read Event Lineage (ADR 0094).
• That open focuses the popup Event Lineage heading and names Keyman and evaluation next.
• A Board home-list open does not gain that focus or copy.
• Advanced-review Calendar stays silent so lab status queries remain unique.
• No TEPP theta or CalDAV event is invented.

Correctness repair

The first focus repair prevented the auto-drilled Keyman path from moving keyboard focus to Ask for Calendar and Weekly VOC. The same effect still called scrollIntoView() unconditionally, so the viewport could jump to Ask even though Event Lineage correctly retained focus.

A bounded one-shot RED→GREEN workflow adds a Calendar regression that waits until related evidence lands, confirms Event Lineage still owns focus, and rejects any scroll to #post-ask. It then gates both focus and scrolling on the report-member-only hand-off, runs the focused and full frontend suites, lint, production build, and Storybook, and publishes only from the exact tested branch head. The workflow removes itself before publishing the production commit.

No passing result is claimed while that exact-head workflow remains queued, running, or failed.

Merge safety

• Re-check the exact head after the one-shot workflow publishes its production commit.
• Current-head checks and a qualifying independent approval are required.
• Do not self-approve, force-merge, or treat the earlier 93 passed evidence as current-head evidence.
• Issues Milestone 2: port verified direct-PostgreSQL analysis into the protected product architecture #79 and Milestone 2.1: add normalized runtime-analysis schema bridge after v0.77 #87 remain open.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: beb55bb3-a86e-4cd8-a55c-3583dc2ee190

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Cycle 2026-08-19T16:08 KST: write-retry. Independent exact-head APPROVE still required. Do not self-approve. Issues #79 and #87 stay open.

[seonghobae]

Cycle 2026-08-19T16:16 KST: v2.15 Customer master Event Lineage focus is stacked on this exact head as feat/customer-master-open-focus-event-lineage-v2150. Independent exact-head APPROVE still required here. Do not self-approve.

[seonghobae]

Cycle 2026-08-19T16:31 KST. Stack continues #261 → #262 → #263 (v2.16 Ask Agent). Independent exact-head APPROVE still required. Do not self-approve. Issues #79 and #87 stay open.