feat: open Customer master related posts onto Event Lineage (v2.15.0)

[seonghobae]

Summary

Stacked on #261. Opening a Customer master related post uses the same Event Lineage focus contract as Weekly VOC and Calendar.

• Customer master names authorized customer entities as current and opens a related post onto Event Lineage (ADR 0095).
• The opened post is marked current, with Keyman and evaluation as the next read.
• Board home-list and Ask Agent opens do not accidentally inherit Customer-master origin.
• No TEPP theta, cutoff body, parent, or customer is invented.

Correctness repair

Customer master keeps one relatedLoading owner while an entity's related posts are fetched. Previously, if entity A's request finished after the user had already expanded entity B, A's unconditional finally cleared B's shared loading state and briefly rendered No linked posts yet. for B even though its request remained pending.

Exact head 0c490d98009f96d399e927543f5891abeb43036e changes cleanup to clear the state only when that request still owns it:

setRelatedLoading((current) => (current === entityId ? null : current));

The branch carries a regression that defers both entity requests, completes the older request first, and requires the newly expanded customer to remain in the loading state until its own response arrives. The one-shot bootstrap is absent from the current tree.

Current validation state

Repository Tests run 32327612802 is queued for the exact head. No current-head passing result is claimed while that run or any required security, SAST, coverage, ontology, or supply-chain gate is pending, absent, failed, cancelled, or skipped-required.

Merge safety

• Re-fetch the exact head, current feat: open Calendar commitments onto Event Lineage (v2.14.0) #261 base, reviews, threads, and required checks after the stack settles.
• Required current-head checks and a qualifying independent approval must be terminal-success.
• Do not self-approve, force-merge, or reuse the earlier 120 passed evidence as current-head evidence.
• Merge only after feat: deliver buyer evidence board and source-grounded ontology surface #258 → feat: name Weekly VOC and focus Event Lineage (v2.13.0) #260 → feat: open Calendar commitments onto Event Lineage (v2.14.0) #261 have landed and this branch has been restacked and revalidated.
• 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: 33b548f3-6411-4f67-84dd-000431fdeac0

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]

Buyer increment stacked as #263 (0aaf992, v2.16.0) on this exact head d25eeda. Ask Agent cited-post opens now share the Event Lineage focus path. Independent exact-head APPROVE still required on this PR and on #263. Do not self-approve. Issues #79 and #87 stay open.

[seonghobae]

@opencode-agent Review exact current head 0c490d98009f96d399e927543f5891abeb43036e against exact parent #261@6a6385208a87be00ad40323ffd618250199c9134. Verify Customer master related-post origin, Event Lineage focus and current-post marker, Keyman/evaluation next action, isolation from Board home and Ask Agent opens, shared relatedLoading ownership under overlapping entity requests, and absence of invented TEPP/cutoff/parent/customer evidence or repair workflows. Publish a durable receipt and formal exact-head verdict or explicit fail-visible evidence. Do not merge, retarget, or update branches.