28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
# WP-02 — UI extraction & experience skeleton
|
|
|
|
**Purpose:** Deliver the strongest OnCo-style interaction patterns on generic data.
|
|
|
|
**Dependencies:** see `INDEX.md`. **Status:** planned. **Owner:** to assign. **Estimate:** to refine after WP-00.
|
|
|
|
## Work packages
|
|
|
|
- [ ] Extract/port UI tokens, layout, header, hero and reusable table from pinned upstream.
|
|
- [ ] Create registry-based kind index and entity detail with no oncology imports.
|
|
- [ ] Adapt BrowserRow via a pure mapper and add configurable generic cell renderers.
|
|
- [ ] Preserve shareable URL query, facets and sorting; test browser back/forward.
|
|
- [ ] Implement keyboard search, empty/loading/error states and responsive layouts.
|
|
|
|
## Acceptance gates
|
|
|
|
- [ ] Browse/search/filter/sort/detail works for two dataspaces.
|
|
- [ ] Component dependency check prohibits `/oncology|cancer|drug|target/` domain imports in generic code.
|
|
- [ ] Copying upstream components retains provenance headers/notices.
|
|
- [ ] Keyboard and small-screen smoke tests pass.
|
|
|
|
## Key risk / mitigation focus
|
|
|
|
R4: extraction too expensive; use greenfield component where warranted. Log evidence and deviations in the workplan review before marking complete.
|
|
|
|
## Evidence artifacts
|
|
|
|
Pull requests, test logs, pinned artifacts, screenshots or comparison report where applicable. Add explicit `ImplementationNotes.md` and `Review.md` on completion; do not mark a gate passed without a verifiable link.
|