Build config excludes wrong example folder and test suite has no coverage

[alx-so]

Problem

The repository uses example-expo, but build and test ignore configuration still references example. The Jest suite also contains only a placeholder test.

This means local and release validation can miss real regressions, and the TypeScript build target can unintentionally include the example app.

Impact

Packaging and release checks may be noisy or inaccurate. More importantly, the current test suite does not protect core behavior such as search updates, controlled values, multi-select tags, or public prop wiring.

Code references

• tsconfig.build.json#L1-L4: build config excludes example and lib, but the actual example folder is example-expo.
• package.json#L102-L104: workspace is named example-expo.
• package.json#L106-L111: Jest ignore pattern references <rootDir>/example/node_modules rather than the current example workspace.
• src/__tests__/index.test.tsx#L1: test suite only contains it.todo("write a test").

Acceptance criteria

• Build and Jest ignore configuration references the actual example-expo workspace.
• Static validation can run after dependency installation without unintentionally compiling the example app as part of the package build.
• Placeholder test is replaced with focused regression coverage or removed once real tests exist.
• Tests are added for the stabilization issues in this milestone where practical.
• Document the expected local validation commands in contributing docs if they are not already clear.

[alx-so]

Testing foundation work has been split into focused tasks under #13:

• Make local and CI test commands reproducible before bug fixes #9 reproducible local and CI validation commands
• Replace placeholder Jest test with baseline utility coverage #10 baseline utility coverage
• Add component smoke tests for public library exports #11 component smoke coverage for public exports
• Add regression-test requirements to stabilization bug fixes #12 regression-test requirements for stabilization fixes

This issue can stay focused on the build/test configuration drift called out here, especially the example vs example-expo mismatch and the removal of placeholder-only coverage once real tests exist.