@adia-ai/adia-ui-factory 0.2.2 → 0.2.3

package/skills/adia-ui-kit/references/session-log-template.md

@@ -0,0 +1,118 @@
+---
+name: session-log-template
+load-when: When emitting a session log entry — template + worked examples + the required fields per session
+load-size-tokens: ~1,200
+required-for:
+  - session-log emission
+  - audit-trail compliance
+---
+
+# [YYYY-MM-DD HH:MM] — <one-line intent>
+
+**Intent:** <what the user asked for>
+**Versions:** @adia-ai/web-components@<version>, @adia-ai/web-modules@<version>
+**Environment:** <Vite + vanilla JS | React | Vue | plain HTML>
+
+### GenUI Plan summary
+- Domain: <entities and tasks>
+- Shell: <admin-shell | chat-shell | …>
+- Views: <list of views/routes>
+
+### Components used
+| Component | Purpose | Binding |
+|---|---|---|
+| `<table-ui>` | Claims queue | `data-stream-src="/api/claims"` |
+| `<drawer-ui>` | Claim detail | row select event |
+| `<badge-ui>` | Status indicator | `variant="warning"` |
+
+### Issues encountered
+- [ ] `<X>` rendered blank — icon loader not configured (see §Setup step 3)
+- [ ] Design board showed a Gantt component — no AdiaUI equivalent, flagged
+
+### Output files
+- `src/pages/claims-list.html`
+- `src/pages/claim-detail.html`
+- `src/main.js`
+```
+
+The log is **shareable with teammates** for debugging and reproduces a
+session's decisions. Commit it to the repo when working in a team.
+
+---
+
+### Feedback tickets — the defensible-feedback discipline
+
+**When to use:**
+
+- `write ui-kit bug ticket [for xyz]` — concrete framework bug, reproducible
+- `write ui-kit feature request [for xyz]` — missing primitive, prop, or event
+- `write ui-kit feedback ticket` — mixed bug + request bundle (preferred for >2 items)
+
+**Don't file as a feedback ticket:**
+
+- Consumer-side dogfooding misses ("the primitive already exists; I just didn't use it")
+- Third-party tool issues (Vite cache, TypeScript inference, browser quirks)
+- Speculative concerns without a concrete pain point
+- Single workaround that USAGE.md prescribes
+
+For the first two, capture in `.adia-ui-kit/notes/` for your team.
+For the last two, don't file at all.
+
+---
+
+### Procedure (follow in order)
+
+#### Step 1 — Inventory raw findings
+
+Before deciding what to file, list every rough edge from the session.
+**Don't filter yet.** A list of 15 items where half get rejected is
+healthier than a list of 6 where 3 are weak.
+
+```bash
+# Re-read the work that surfaced the feedback
+git log --oneline -20
+git diff HEAD~5..HEAD -- src/
+cat .adia-ui-kit/session-log.md | head -100
+```
+
+#### Step 2 — Classify each finding into one of four buckets
+
+| Bucket | Examples | Action |
+|---|---|---|
+| **Framework bug** | Crash, type-vs-runtime drift, prop ignored, parser mis-classification | File as P0 (reproducible) or P1 (subtle) |
+| **Framework gap** | Missing primitive, missing prop, missing event type, no theme knob | File as P1-P3 based on workaround cost |
+| **Consumer dogfooding miss** | "Primitive X already exists; I just didn't use it" | NOT feedback — capture in `.adia-ui-kit/notes/<date>-miss.md` |
+| **Third-party / scope** | Vite cache stale, TS doesn't infer, browser quirk | NOT feedback — note in related-observations, don't file |
+
+**The classification gate eliminates ~30% of raw findings.** Anything
+that doesn't survive the bucket-check shouldn't go in.
+
+#### Step 3 — Verify "already-shipped" exclusions
+
+For every item you intend to exclude on grounds of "already resolved,"
+**prove it** by opening the installed source:
+
+```bash
+# Example: claim "<select-ui> event types shipped"
+cat node_modules/@adia-ai/web-components/components/select/select.d.ts | grep -E "EventDetail|CustomEvent"
+
+# Example: claim "field-ui align prop shipped in v0.6.6"
+grep -n "align" node_modules/@adia-ai/web-components/components/field/field.yaml
+
+# Example: claim "phantom event removed"
+grep -n "ToastCloseEvent" node_modules/@adia-ai/web-components/components/toast/toast.d.ts
+# Empty output = confirmed removed
+```
+
+Save the file path + line number — cite them in the defense block.
+
+**If you can't verify in <2 minutes, don't exclude on those grounds.**
+Filing a duplicate is cheap; mis-claiming "already shipped" damages
+trust.
+
+#### Step 4 — For each surviving finding, produce the five-block structure
+
+Every item gets the same shape. Drop sections that don't apply (a doc
+ask doesn't need a stack trace), but **every P0 needs every block.**
+
+```markdown