Story 1.1: Core Contract and Export Baseline

[RudoiDmytro]

Epic

Epic 1: Core Controls and Contract Foundation

Parent Initiative

• Plan and implement missing UI toolkit components #5

Source

• specs/planning-artifacts/epics.md

Story

As a consumer-team developer,
I want core controls to expose a consistent public contract and entrypoint exports,
So that I can integrate toolkit components predictably across company projects.

Acceptance Criteria:

Given the existing core control components are present
When I inspect their public props and export surface
Then each core control has documented and typed contract fields aligned to the shared API policy (or documented exception)
And each core control is exported from src/components/index.ts.

Given contract behavior is part of release quality gates
When contract verification checks are run
Then failing export/contract mismatches are detectable before release
And results are reported in a way that blocks non-compliant changes.

Given this epic must preserve compatibility
When contract adjustments are introduced
Then existing public API behavior remains backward compatible unless explicitly approved
And any approved exception is documented.

Related PR

• Story 1.1: core contract and export baseline #9

[coderabbitai]

🔗 Related PRs

#6 - specs: plan UI toolkit completion (PRD, architecture, epics) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!