Run 7 — Package API — Byproducts

Discovered Issues

1. Pre-existing test failure: entity-viewer.test.tsx

File: src/components/extras/organisms/shared/entity-viewer/entity-viewer.test.tsx Test: useEntityViewer > Tab navigation > navigateToTab fails when validation has errors Failure: expected true to be false

This test was failing before Run 7 changes (baseline check: 44 failures pre-Run-7 vs 1 post-Run-7). Not caused by Run 7. Requires investigation in a follow-up run or separate fix.

Severity: Low — the hook logic still works for passing cases; this failure suggests a specific validation-on-navigation edge case has a behavior mismatch.

2. TypeScript 5.9.3 vs API Extractor bundled 5.8.2

During npm run build:lib, the API Extractor emits *** The target project appears to use TypeScript 5.9.3 which is newer than the bundled compiler engine; consider upgrading API Extractor. repeatedly (8 times, once per entry point).

This is a non-blocking warning — the build succeeds. However, the API Extractor version bundled with vite-plugin-dts lags behind the TypeScript version. Consider upgrading vite-plugin-dts when the pinned typescript: 5.9.3 version becomes stable.

@radix-ui/react-tooltip was removed from dependencies, but it may still appear in package-lock.json as a transitive dependency if something else pulls it in. This is harmless — the important change is that the project no longer explicitly depends on it.

4. src/canary-refactor/components/columnPresets.tsx is modified (not by Run 7)

git status shows this file as modified (from a previous run). It likely still references react-icons (which was the LuCaptions usage documented in the dependencies analysis). This file’s modification is pre-existing on the branch — it was addressed in a prior run. Not a Run 7 concern.

5. `normalizeOptions` not exported from canary.ts

The canary/atoms/grid/select/index.ts exports normalizeOptions as an implementation utility. It was NOT added to canary.ts because it is an internal implementation helper. If callers need to normalize select options, consider adding it in a future run or promoting it explicitly.

6. Stale MDX documentation referencing detail-field

Four MDX doc files in src/docs/ reference detail-field in tutorial/example text:

src/docs/workflows/canary-components/how-to-extract-and-publish.mdx
src/docs/components/guidelines.mdx
src/docs/workflows/publishing.mdx
src/docs/workflows/canary-components/example.mdx

These should be updated in a documentation cleanup run to use ReadOnlyField as the canonical example instead of the now-deleted ArdaDetailField.

TODOs for Later Runs

Fix entity-viewer validation-navigation test — determine if the hook or the test expectation is wrong.
Update stale MDX docs — replace detail-field / ArdaDetailField examples with ReadOnlyField.
Upgrade vite-plugin-dts — to pick up a newer bundled TypeScript API Extractor to eliminate version mismatch warnings during library build.
Document ArdaBadge collision in MDX — the canary ArdaBadge and the extras ArdaBadge have the same name but different import paths. The canary version should be noted as the canonical one in component documentation.

Observations

The package.json on the target branch was cleaner than expected. The packages to be “removed” (next-themes, react-icons, shadcn, pako, qr-scanner, react-dropzone, @storybook/addon-links) were all already absent — they had been cleaned up in prior runs or were never added to this branch.
The four new devDependencies (@reduxjs/toolkit, react-redux, redux-persist, sonner) were already in package-lock.json and node_modules on this branch. npm install reported “up to date”. The only change was adding the declarations to package.json.
Run 7 reduced failing test count from 44 (baseline before Run 7 changes) to 1. The 43 tests fixed were caused by broken imports from deleted enum/ and detail-field/ directories that the old canary.ts was still referencing — meaning the pre-Run-7 canary.ts was pointing at files that no longer existed on the branch.
dist/canary.js grew from ~178 KB (CJS) + ~258 KB (ESM) — significantly larger than the pre-consolidation size, reflecting the addition of sidebar, item-grid, and new atom components.