Merge branch staging/pfv6 into chore/skill-readme-instructions

Author: zeroedin

.claude/skills/review-api/SKILL.md

@@ -106,6 +106,7 @@ Read `.claude/ADVICE.md` for reference rules.
 - [ ] `static styles = [styles]` array form?
 - [ ] Controllers for cross-cutting concerns?
 - [ ] `isServer` guards on browser-only APIs?
+- [ ] Quoting attribute values in Lit templates `src="{$this.src}"`?
 
 #### Lint
 ```bash
@@ -124,13 +125,16 @@ npx stylelint elements/pf-v6-{name}/**/*.css
 - [ ] No arrow functions in test blocks?
 - [ ] Behavioral expectations from React tests covered?
 
-### Phase 5: JSDoc
+### Phase 5: JSDoc and cem documentation comments
 
 - [ ] `@summary` present on element class?
 - [ ] All public properties/methods have `/** */` JSDoc (not `//` comments)?
-- [ ] `@cssprop` with CSS data types: `@cssprop {color} --pf-v6-c-button--Color`?
-- [ ] `@csspart` for all exposed parts?
-- [ ] `@slot` for all slots (prescriptive descriptions)?
+- [ ] CSS custom properties documented with `/** */` comments in the CSS file,
+co-located with the declaration or `var()` reference?
+- [ ] CSS parts documented with `<!-- summary: ... -->` HTML comments before the
+`part="..."` element in the template?
+- [ ] Slots documented with `<!-- summary: ... -->` HTML comments before the `<slot>`
+element in the template?
 - [ ] `@fires` for all dispatched events?
 - [ ] No unnecessary `@default` tags (analyzer picks up initializers)?
 

.claude/skills/update-element/SKILL.md

@@ -291,7 +291,11 @@ whether values are actually configurable or hardcoded.
 
 See `elements/pf-v6-tooltip/README.md` for a reference example.
 
-### Phase 9: Audit
+### Phase 9: Delete v5 element
+
+Delete the directory and it's contents from ./elements/`pf-v5-{name}`. replace all references to `pf-v5-{name}`, except historical changelogs, and update their usage to conform to new APIs. This includes demos for v6 elements which use v5 dependencies.
+
+### Phase 10: Audit
 
 Prompt the user to activate /review-api, /review-demos, and /review-a11y