chore: rename first-gen to 1st-gen and second-gen to 2nd-gen

- Rename first-gen directory to 1st-gen
- Rename second-gen directory to 2nd-gen
- Remove conflicting root .eslintrc.json (use flat config)
- Fix 2nd-gen ESLint config to use root HEADER file
- Update yarn.lock after clean reinstall

Author: caseyisonit

.changeset/README.md

@@ -8,9 +8,9 @@ find the full documentation for it [in our repository](https://github.com/change
 
 Changesets are a way to manage versions and changelogs for monorepos. Each changeset:
 
--   Describes changes made in one or more packages
--   Indicates the type of change (major, minor, patch)
--   Contains a brief markdown summary of the changes
+- Describes changes made in one or more packages
+- Indicates the type of change (major, minor, patch)
+- Contains a brief markdown summary of the changes
 
 ## How to Add a Changeset
 
@@ -29,18 +29,25 @@ Changesets are a way to manage versions and changelogs for monorepos. Each chang
 
 The command will create a new markdown file in the `.changeset` directory with your changes.
 
+## Important: @spectrum-web-components/core and component updates
+
+When making changes to `@spectrum-web-components/core`, you **must** also include the corresponding `@spectrum-web-components` component in the same changeset to ensure the changes appear in the component's changelog. This is because `@spectrum-web-components/core` changes are internal and don't automatically propagate to the component changelogs.
+
+**Best practice**: Create a single changeset that includes both packages when updating core functionality that affects a specific component.
+
 ## Example Changeset
 
 A typical changeset file looks like this:
 
 ```markdown
 ---
+'@spectrum-web-components/core': patch
 '@spectrum-web-components/button': minor
 '@spectrum-web-components/theme': patch
 ---
 
--   **Added**: Added new variant `tertiary` to `<sp-button>` component [#9999](https://github.com/adobe/spectrum-web-components/pull/9999)
--   **Fixed**: Fixed `<sp-theme>` theme compatibility issues [#10000](https://github.com/adobe/spectrum-web-components/pull/10000)
+- **Added**: Added new variant `tertiary` to `<sp-button>` component [#9999](https://github.com/adobe/spectrum-web-components/pull/9999)
+- **Fixed**: Fixed `<sp-theme>` theme compatibility issues [#10000](https://github.com/adobe/spectrum-web-components/pull/10000)
 ```
 
 For our guidelines on writing changesets, see [our writing changesets guide](https://opensource.adobe.com/spectrum-web-components/guides/writing-changesets/).
@@ -61,6 +68,6 @@ We have a quick list of common questions to get you started engaging with this p
 
 ## Additional Resources
 
--   [Changesets Documentation](https://github.com/changesets/changesets)
--   [Common Questions](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)
--   [Detailed Release Process](https://github.com/changesets/changesets/blob/main/docs/detailed-explanation.md)
+- [Changesets Documentation](https://github.com/changesets/changesets)
+- [Common Questions](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)
+- [Detailed Release Process](https://github.com/changesets/changesets/blob/main/docs/detailed-explanation.md)

.changeset/config.json

@@ -7,12 +7,22 @@
         }
     ],
     "commit": false,
-    "fixed": [["@spectrum-web-components/*"]],
-    "linked": [],
+    "fixed": [
+        [
+            "@spectrum-web-components/*",
+            "!@spectrum-web-components/core",
+            "!@spectrum-web-components/1st-gen",
+            "!@spectrum-web-components/2nd-gen"
+        ]
+    ],
+    "linked": [["@adobe/swc", "@spectrum-web-components/core"]],
     "access": "public",
     "baseBranch": "main",
     "updateInternalDependencies": "patch",
-    "ignore": [],
+    "ignore": [
+        "@spectrum-web-components/1st-gen",
+        "@spectrum-web-components/2nd-gen"
+    ],
     "snapshot": {
         "useCalculatedVersion": true,
         "prereleaseTemplate": "{tag}.{datetime}"

.changeset/short-pans-know.md

@@ -0,0 +1,5 @@
+---
+'@spectrum-web-components/status-light': patch
+---
+
+**Fixed**: Added missing `accent` and `cyan` variant to status light.

.changeset/weak-streets-raise.md

@@ -0,0 +1,5 @@
+---
+'@spectrum-web-components/overlay': patch
+---
+
+- **Fixed**: Expanded `<overlay-trigger>` `type` property to accept all overlay types ('auto', 'hint', 'manual', 'modal', 'page') instead of the incorrect, previous restricted subset.

.circleci/config.yml

@@ -1,7 +1,52 @@
 ---
-description: Useful for updating auto-generated content in the contributor docs
+description: Useful for updating auto-generated navigation and validating links in the contributor docs
 alwaysApply: false
 ---
-If the user requests an update to the contributor docs (located in the CONTRIBUTOR_DOCS folder at the repository root), run the update process as described in the agent instructions within that folder.
 
-To locate the instructions, search for "ai-agent-instructions", or fall back to a recursive directory search if needed.
+# Contributor docs navigation and link validation
+
+## When to apply this rule
+
+Recognize and apply this rule when the user requests any of the following:
+- Update contributor docs navigation
+- Update nav / TOC / breadcrumbs in contributor docs
+- Regenerate contributor docs
+- Validate/verify links in contributor docs
+- Fix broken links in contributor docs
+- Any mention of "CONTRIBUTOR-DOCS" or "contributor docs" with "update", "nav", "links", or "verify"
+
+## Instructions location
+
+**Primary path:** `CONTRIBUTOR-DOCS/01_contributor-guides/07_authoring-contributor-docs/01_ai-agent-instructions.md`
+
+## What to do
+
+1. **Verify the instructions file exists** at the path above
+   - If the file exists, read it and follow the instructions for "Role 1: Operator"
+   - If the file does NOT exist, see "Self-correction procedure" below
+
+2. **Follow the AI agent instructions** to:
+   - Run the nav update script (which automatically validates links)
+   - Handle any broken links that are reported
+   - Report results to the user
+
+## Self-correction procedure
+
+If the instructions file is not found at the expected path:
+
+1. Search for the file using: `glob_file_search` with pattern `**/ai-agent-instructions.md`
+2. Filter results to find the one in `CONTRIBUTOR-DOCS/` folder
+3. Read the found file to confirm it contains the nav update instructions
+4. **Update this rule file** with the new path by modifying the "Primary path" line above
+5. Inform the user that you've updated the rule with the new location
+6. Continue with the nav update process
+
+## Quick reference
+
+The nav update process typically involves:
+- Running a Node.js script in the authoring-contributor-docs folder
+- The script automatically updates breadcrumbs, TOC, and validates all links
+- If broken links are found, fix straightforward issues automatically
+- Only consult the user for ambiguous cases
+
+Execution time is typically 20-200ms for the entire CONTRIBUTOR-DOCS tree.

.cursor/rules/contributor-doc-update.mdc

@@ -93,6 +93,7 @@ Use the following labels to categorize pull requests. Only use labels that exist
 - `Browser: Edge (Legacy)`: Issue with pre-chromium Edge
 - `Browser: FireFox`: Firefox browser issues
 - `Browser: Safari`: Safari browser issues
+- `iOS`: iOS-specific issues and bugs
 
 ### Development and process labels
 
@@ -107,11 +108,9 @@ Common additional labels include:
 
 - `chore`: Routine tasks, maintenance, or non-feature changes
 - `dependencies`: Updates or changes to project dependencies
-- `docs`: Documentation updates or improvements
-- `enhancement`: Improvements to existing features
-- `feature`: New feature implementations
+- `Documentation`: Documentation updates or improvements
+- `feature`: New feature implementations or improvements to existing features
 - `i18n`: Internationalization and localization work
-- `iOS`: iOS-specific issues and bugs
 - `mobile`: Mobile platform issues and responsive design
 - `performance`: Performance-related improvements or regressions
 - `refactor`: Code restructuring and refactoring work

.cursor/rules/github-description.mdc

@@ -185,7 +185,7 @@ Use the following labels to categorize tickets appropriately:
 - `s2foundations`: Spectrum 2 Foundations related work
 - `spectrum2`: Spectrum 2 platform specific tasks
 - `team-processes`: Internal team workflow improvements
-- `testing`: Test implementation or testing infrastructure work
+- `test`: Test implementation or testing infrastructure work
 - `triage`: New tickets requiring team assessment and prioritization
 - `VoiceOver`: VoiceOver screen reader specific issues
 

.cursor/rules/jira-ticket.mdc

@@ -1,7 +1,7 @@
 name: Feature request
 description: Describe the feature you would like added
 title: '[Feat]: '
-labels: [enhancement, triage, needs jira ticket]
+labels: [feature, triage, needs jira ticket]
 # assignees:
 body:
     - type: markdown

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -1,7 +1,7 @@
 name: New component
 description: Outline the requirements for a new component
 title: '[NEW]: '
-labels: [missing components, triage, needs jira ticket]
+labels: [new component, triage, needs jira ticket]
 # assignees:
 body:
     - type: markdown