feat(ui): inventory related-node chips in one module (v0.76.0)

[seonghobae]

Buyer impact

Stacked on #92 @ 9bb5829. Related-node walk chips share RelatedNodeChip and a Storybook inventory (ADR 0014). After seed, walking from Demo Corp still shows Ada West, Demo Corp (Our side). Priya Nair stays Priya Nair (Counterparty) — two orgs never invent a primary. Click a chip to continue the walk or open that post.

• Caption and accessible name live in relatedNodeCaption.ts (WCAG 2.5.3).
• RelatedNodeChip.stories.tsx inventories the four buyer states. Host with Storybook 10 when the later token stack lands; vitest locks the same behavior now.
• The synthetic Figma OurSidePerson component is synchronized to Ada West, Demo Corp (Our side) so the design inventory and current feat(ui): show business context on related-node chips (v0.75.0) #92/Storybook contract no longer disagree.
• Does not add affiliation_ambiguous or "multiple organizations" next-action copy (feat(ui): mark plural affiliations on related-node chips (v0.76.0) #123 / feat(ui): name next action on plural affiliation chips (v0.77.0) #192).
• Does not add commits to feat(ui): show business context on related-node chips (v0.75.0) #92.

Exact head and repair

Current head: dc8fb15fe2eb5eedfb31db57e671c4b1d6eb443c on feat/related-node-storybook-chips-v0760.

Base: feat/related-node-person-side-labels-main (#92) @ 9bb5829f706d4eb98420e8ac4586e7ac4200223e.

The original story objects widened args.action to plain string. Because tsconfig.app.json includes all of src and the existing RelatedNodeChip.test.tsx passes those story args into the typed RelatedNodeChipAction prop, tsc -b has a compile-time contract failure even though Vitest can transpile the files. Current head fixes the owning Storybook boundary by constraining story args with satisfies RelatedNodeStoryArgs; it does not weaken the component action union or add Storybook runtime dependencies.

No predecessor-head check or review evidence transfers to this head. The Figma synchronization is design-source alignment, not merge evidence.

Review gate

• Do not mix into Role, responsibility, and agent ontology (v2.10.0) #74.
• Do not add commits to feat(ui): show business context on related-node chips (v0.75.0) #92.
• Independent exact-head APPROVE required before squash.
• Do not self-approve.
• Do not merge from this PR author.
• Owner/self COMMENT is not APPROVE.
• This PR body is not an approval.

Not in this slice

Valkey outbox is #229. RankWeave landed as #220. TEPP is #214. naruon is #217. ThreadWeave is #219. Keyverse is #221. Orchestrator is #228. Plural next-action is #192. Strix ModelBehaviorError classifier is ContextualWisdomLab/.github#1091.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[seonghobae]

Exact head 68d073d stacked on #92 @ 9bb5829.

Buyer: Ada West, Demo Corp (Our side); Priya Nair stays side-only. Click a chip to continue the walk or open that post. No commits added to #92.

Independent exact-head APPROVE required. This comment is not an approval. Do not mix into #74. Do not self-approve. Owner/self COMMENT is not APPROVE.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 57d01d6b-ed3b-4e5f-a039-78143c72faa9

📥 Commits

Reviewing files that changed from the base of the PR and between 9bb5829 and dc8fb15.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (14)

• AGENTS.md
• ARCHITECTURE.md
• CHANGELOG.md
• docs/adr/0014-related-node-chip-stories.md
• frontend/package.json
• frontend/src/App.tsx
• frontend/src/RelatedNodeChip.stories.tsx
• frontend/src/RelatedNodeChip.test.tsx
• frontend/src/RelatedNodeChip.tsx
• frontend/src/relatedNodeCaption.test.ts
• frontend/src/relatedNodeCaption.ts
• frontend/src/relatedNodeTokens.css
• lineageweave/__init__.py
• pyproject.toml

---

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]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.