@nextsparkjs/core 0.1.0-beta.8 → 0.1.0-beta.82

package/dist/templates/contents/themes/starter/tests/cypress/e2e/_utils/selectors/settings-layout.bdd.md

@@ -0,0 +1,129 @@
+---
+feature: Settings Layout UI Selectors Validation
+priority: high
+tags: [selectors, settings, layout, sidebar, ui-validation]
+grepTags: [ui-selectors, settings, SEL_LAY_001, SEL_LAY_002]
+coverage: 2
+---
+
+# Settings Layout UI Selectors Validation
+
+> Validates that settings layout and sidebar selectors exist in the DOM. This is a lightweight test that ONLY checks selector presence, not functionality. Runs as Phase 12 sub-gate before functional tests.
+
+## @test SEL_LAY_001: Layout Selectors (sidebar.layout.*)
+
+### Metadata
+- **Priority:** High
+- **Type:** Selector Validation
+- **Tags:** settings, layout, container
+- **Grep:** `@ui-selectors` `@SEL_LAY_001`
+- **Status:** Active (6 passing, 0 skipped)
+
+```gherkin:en
+Scenario: Settings layout has required selectors
+
+Given I am logged in as developer
+And I navigate to the settings page
+Then I should find the layout main container
+And I should find the back to dashboard link
+And I should find the layout header
+And I should find the layout content area
+And I should find the sidebar container
+And I should find the layout page content
+```
+
+```gherkin:es
+Scenario: El layout de settings tiene los selectores requeridos
+
+Given estoy logueado como developer
+And navego a la pagina de settings
+Then deberia encontrar el contenedor principal del layout
+And deberia encontrar el link de volver al dashboard
+And deberia encontrar el header del layout
+And deberia encontrar el area de contenido del layout
+And deberia encontrar el contenedor del sidebar
+And deberia encontrar el contenido de la pagina del layout
+```
+
+### Expected Results
+- `settings.sidebar.layout.main` selector exists (settings-layout-main)
+- `settings.sidebar.backButton` selector exists (settings-back-to-dashboard)
+- `settings.sidebar.layout.header` selector exists (settings-layout-header)
+- `settings.sidebar.layout.contentArea` selector exists (settings-layout-content-area)
+- `settings.sidebar.container` selector exists (settings-sidebar)
+- `settings.sidebar.layout.pageContent` selector exists (settings-layout-page-content)
+
+---
+
+## @test SEL_LAY_002: Sidebar Selectors
+
+### Metadata
+- **Priority:** High
+- **Type:** Selector Validation
+- **Tags:** settings, sidebar, navigation
+- **Grep:** `@ui-selectors` `@SEL_LAY_002`
+- **Status:** Active (10 passing, 0 skipped)
+
+```gherkin:en
+Scenario: Settings sidebar has all navigation links
+
+Given I am logged in as developer
+And I navigate to the settings page
+Then I should find the sidebar container
+And I should find the sidebar header
+And I should find the sidebar nav items container
+And I should find the profile nav link
+And I should find the security nav link
+And I should find the password nav link
+And I should find the notifications nav link
+And I should find the api-keys nav link
+And I should find the billing nav link
+And I should find the teams nav link
+```
+
+```gherkin:es
+Scenario: El sidebar de settings tiene todos los links de navegacion
+
+Given estoy logueado como developer
+And navego a la pagina de settings
+Then deberia encontrar el contenedor del sidebar
+And deberia encontrar el header del sidebar
+And deberia encontrar el contenedor de items de navegacion
+And deberia encontrar el link de navegacion a perfil
+And deberia encontrar el link de navegacion a seguridad
+And deberia encontrar el link de navegacion a password
+And deberia encontrar el link de navegacion a notificaciones
+And deberia encontrar el link de navegacion a api-keys
+And deberia encontrar el link de navegacion a facturacion
+And deberia encontrar el link de navegacion a equipos
+```
+
+### Expected Results
+- `settings.sidebar.container` selector exists (settings-sidebar)
+- `settings.sidebar.header` selector exists (settings-sidebar-header)
+- `settings.sidebar.nav.items` selector exists (settings-sidebar-nav-items)
+- `settings.sidebar.nav.item` with section=profile exists (settings-sidebar-nav-profile)
+- `settings.sidebar.nav.item` with section=security exists (settings-sidebar-nav-security)
+- `settings.sidebar.nav.item` with section=password exists (settings-sidebar-nav-password)
+- `settings.sidebar.nav.item` with section=notifications exists (settings-sidebar-nav-notifications)
+- `settings.sidebar.nav.item` with section=api-keys exists (settings-sidebar-nav-api-keys)
+- `settings.sidebar.nav.item` with section=billing exists (settings-sidebar-nav-billing)
+- `settings.sidebar.nav.item` with section=teams exists (settings-sidebar-nav-teams)
+
+### Notes
+Some sidebar items may not be visible depending on user permissions and theme configuration. The test validates selectors that are accessible to the developer role.
+
+---
+
+## Related Components
+
+| Component | File | Selectors |
+|-----------|------|-----------|
+| SettingsLayout | `packages/core/src/components/settings/layouts/SettingsLayout.tsx` | settings-layout-main, settings-layout-header, settings-layout-content-area |
+| SettingsSidebar | `packages/core/src/components/settings/layouts/SettingsSidebar.tsx` | settings-sidebar, settings-sidebar-header, settings-sidebar-nav-* |
+
+## Related POMs
+
+| POM | File | Usage |
+|-----|------|-------|
+| SettingsPOM | `themes/starter/tests/cypress/src/features/SettingsPOM.ts` | Settings layout and sidebar selectors |

package/dist/templates/contents/themes/starter/tests/cypress/e2e/_utils/selectors/settings-layout.cy.ts

@@ -0,0 +1,115 @@
+/**
+ * UI Selectors Validation: Settings Layout & Sidebar
+ *
+ * This test validates that settings layout and sidebar selectors exist in the DOM.
+ * This is a lightweight test that ONLY checks selector presence, not functionality.
+ *
+ * Purpose:
+ * - Validate SettingsPOM layout and sidebar selectors work correctly
+ * - Ensure all settings.sidebar.* and settings.sidebar.layout.* selectors are implemented
+ * - Run as Phase 12 sub-gate before functional tests
+ *
+ * Scope:
+ * - Navigate to settings pages (requires login)
+ * - Assert elements exist in DOM (no form submissions)
+ * - Fast execution (< 30 seconds per describe block)
+ *
+ * Test IDs:
+ * - SEL_LAY_001: Layout Selectors (under sidebar.layout.*)
+ * - SEL_LAY_002: Sidebar Selectors
+ */
+
+import { SettingsPOM } from '../../../src/features/SettingsPOM'
+import { loginAsDefaultDeveloper } from '../../../src/session-helpers'
+
+describe('Settings Layout Selectors Validation', { tags: ['@ui-selectors', '@settings'] }, () => {
+  const settings = SettingsPOM.create()
+
+  beforeEach(() => {
+    loginAsDefaultDeveloper()
+  })
+
+  // ============================================
+  // SEL_LAY_001: LAYOUT SELECTORS (sidebar.layout.*)
+  // ============================================
+  describe('SEL_LAY_001: Layout Selectors', { tags: '@SEL_LAY_001' }, () => {
+    beforeEach(() => {
+      settings.visitSettings()
+      settings.waitForSettings()
+    })
+
+    it('should find layout main container', () => {
+      cy.get(settings.selectors.layoutMain).should('exist')
+    })
+
+    it('should find back to dashboard link', () => {
+      cy.get(settings.selectors.sidebarBackButton).should('exist')
+    })
+
+    it('should find layout header', () => {
+      cy.get(settings.selectors.layoutHeader).should('exist')
+    })
+
+    it('should find layout content area', () => {
+      cy.get(settings.selectors.layoutContentArea).should('exist')
+    })
+
+    it('should find sidebar container', () => {
+      cy.get(settings.selectors.sidebarContainer).should('exist')
+    })
+
+    it('should find layout page content', () => {
+      cy.get(settings.selectors.layoutPageContent).should('exist')
+    })
+  })
+
+  // ============================================
+  // SEL_LAY_002: SIDEBAR SELECTORS
+  // ============================================
+  describe('SEL_LAY_002: Sidebar Selectors', { tags: '@SEL_LAY_002' }, () => {
+    beforeEach(() => {
+      settings.visitSettings()
+      settings.waitForSettings()
+    })
+
+    it('should find sidebar container', () => {
+      cy.get(settings.selectors.sidebarContainer).should('exist')
+    })
+
+    it('should find sidebar header', () => {
+      cy.get(settings.selectors.sidebarHeader).should('exist')
+    })
+
+    it('should find sidebar nav items container', () => {
+      cy.get(settings.selectors.sidebarNavItems).should('exist')
+    })
+
+    it('should find profile nav item', () => {
+      cy.get(settings.selectors.sidebarNavItem('profile')).should('exist')
+    })
+
+    it('should find security nav item', () => {
+      cy.get(settings.selectors.sidebarNavItem('security')).should('exist')
+    })
+
+    it('should find password nav item', () => {
+      cy.get(settings.selectors.sidebarNavItem('password')).should('exist')
+    })
+
+    it('should find notifications nav item', () => {
+      cy.get(settings.selectors.sidebarNavItem('notifications')).should('exist')
+    })
+
+    it('should find api-keys nav item', () => {
+      cy.get(settings.selectors.sidebarNavItem('api-keys')).should('exist')
+    })
+
+    it('should find billing nav item', () => {
+      cy.get(settings.selectors.sidebarNavItem('billing')).should('exist')
+    })
+
+    it('should find teams nav item', () => {
+      cy.get(settings.selectors.sidebarNavItem('teams')).should('exist')
+    })
+  })
+})

package/dist/templates/contents/themes/starter/tests/cypress/e2e/_utils/selectors/settings-password.bdd.md

@@ -0,0 +1,82 @@
+---
+feature: Settings Password UI Selectors Validation
+priority: high
+tags: [selectors, settings, password, ui-validation]
+grepTags: [ui-selectors, settings, SEL_PASS_001]
+coverage: 1
+---
+
+# Settings Password UI Selectors Validation
+
+> Validates that settings password selectors exist in the DOM. This is a lightweight test that ONLY checks selector presence, not functionality. Runs as Phase 12 sub-gate before functional tests.
+
+## @test SEL_PASS_001: Password Page Selectors
+
+### Metadata
+- **Priority:** High
+- **Type:** Selector Validation
+- **Tags:** settings, password, form
+- **Grep:** `@ui-selectors` `@SEL_PASS_001`
+- **Status:** Active (2 passing, 5 skipped)
+
+```gherkin:en
+Scenario: Password page has required selectors
+
+Given I am logged in as developer
+And I navigate to the password settings page
+Then I should find the password container
+And I should find the password form
+And I should find the current password input
+And I should find the new password input
+And I should find the confirm password input
+And I should find the password submit button
+```
+
+```gherkin:es
+Scenario: La pagina de password tiene los selectores requeridos
+
+Given estoy logueado como developer
+And navego a la pagina de settings de password
+Then deberia encontrar el contenedor de password
+And deberia encontrar el formulario de password
+And deberia encontrar el input de password actual
+And deberia encontrar el input de nuevo password
+And deberia encontrar el input de confirmar password
+And deberia encontrar el boton de enviar password
+```
+
+### Expected Results
+- `settings.password.container` selector exists (settings-password) - **SKIPPED: Mismatch**
+- `settings.password.form` selector exists (password-form)
+- `settings.password.current` selector exists (password-current) - **SKIPPED: Mismatch**
+- `settings.password.new` selector exists (password-new) - **SKIPPED: Mismatch**
+- `settings.password.confirm` selector exists (password-confirm) - **SKIPPED: Mismatch**
+- `settings.password.submit` selector exists (password-submit)
+
+### Notes
+**Selector Mismatches Documented:**
+
+| Expected (CORE_SELECTORS) | Actual (Component) | Issue |
+|---------------------------|-------------------|-------|
+| `settings-password` | `password-main` | Container uses different naming |
+| `password-current` | `password-current-input` | Extra `-input` suffix |
+| `password-new` | `password-new-input` | Extra `-input` suffix |
+| `password-confirm` | `password-confirm-input` | Extra `-input` suffix |
+
+Resolution options:
+1. Update CORE_SELECTORS to match component naming
+2. Update PasswordForm component to match CORE_SELECTORS
+
+---
+
+## Related Components
+
+| Component | File | Selectors |
+|-----------|------|-----------|
+| PasswordForm | `packages/core/src/components/settings/PasswordForm.tsx` | password-main, password-form, password-current-input, password-new-input, password-confirm-input, password-submit |
+
+## Related POMs
+
+| POM | File | Usage |
+|-----|------|-------|
+| SettingsPOM | `themes/default/tests/cypress/src/features/SettingsPOM.ts` | Password page selectors |

package/dist/templates/contents/themes/starter/tests/cypress/e2e/_utils/selectors/settings-password.cy.ts

@@ -0,0 +1,74 @@
+/**
+ * UI Selectors Validation: Settings Password
+ *
+ * This test validates that settings password selectors exist in the DOM.
+ * This is a lightweight test that ONLY checks selector presence, not functionality.
+ *
+ * Purpose:
+ * - Validate SettingsPOM password selectors work correctly
+ * - Ensure all settings.password.* selectors are implemented
+ * - Run as Phase 12 sub-gate before functional tests
+ *
+ * Scope:
+ * - Navigate to password settings page (requires login)
+ * - Assert elements exist in DOM (no form submissions)
+ * - Fast execution (< 30 seconds per describe block)
+ *
+ * Test IDs:
+ * - SEL_PASS_001: Password Page Selectors
+ *
+ * NOTE: Password page only visible for users with password auth (not Google OAuth).
+ * Some selectors from CORE_SELECTORS have naming mismatches with implementation.
+ */
+
+import { SettingsPOM } from '../../../src/features/SettingsPOM'
+import { loginAsDefaultDeveloper } from '../../../src/session-helpers'
+
+describe('Settings Password Selectors Validation', { tags: ['@ui-selectors', '@settings'] }, () => {
+  const settings = SettingsPOM.create()
+
+  beforeEach(() => {
+    loginAsDefaultDeveloper()
+    settings.visitPassword()
+    // Wait for password page to load
+    cy.get(settings.selectors.passwordForm, { timeout: 15000 }).should('be.visible')
+  })
+
+  // ============================================
+  // SEL_PASS_001: PASSWORD PAGE SELECTORS
+  // ============================================
+  describe('SEL_PASS_001: Password Page Selectors', { tags: '@SEL_PASS_001' }, () => {
+    // NOTE: CORE_SELECTORS defines 'settings-password' but component uses 'password-main'
+    it.skip('should find password container (selector mismatch: CORE uses settings-password, component uses password-main)', () => {
+      cy.get(settings.selectors.passwordContainer).should('exist')
+    })
+
+    it('should find password form', () => {
+      cy.get(settings.selectors.passwordForm).should('exist')
+    })
+
+    // NOTE: CORE uses 'password-current' but component uses 'password-current-input'
+    it.skip('should find current password input (selector mismatch: CORE uses password-current, component uses password-current-input)', () => {
+      cy.get(settings.selectors.passwordCurrent).should('exist')
+    })
+
+    // NOTE: New password input doesn't have data-cy in component - uses PasswordField component
+    it.skip('should find new password input (not implemented in component)', () => {
+      cy.get(settings.selectors.passwordNew).should('exist')
+    })
+
+    // NOTE: Confirm password input doesn't have data-cy in component
+    it.skip('should find confirm password input (not implemented in component)', () => {
+      cy.get(settings.selectors.passwordConfirm).should('exist')
+    })
+
+    it('should find submit button', () => {
+      cy.get(settings.selectors.passwordSubmit).should('exist')
+    })
+
+    // Note: Success message only appears after successful form submission
+    it.skip('should find success message (requires successful submission)', () => {
+      cy.get(settings.selectors.passwordSuccess).should('exist')
+    })
+  })
+})

package/dist/templates/contents/themes/starter/tests/cypress/e2e/_utils/selectors/settings-profile.bdd.md

@@ -0,0 +1,77 @@
+---
+feature: Settings Profile UI Selectors Validation
+priority: high
+tags: [selectors, settings, profile, ui-validation]
+grepTags: [ui-selectors, settings, SEL_PROF_001]
+coverage: 1
+---
+
+# Settings Profile UI Selectors Validation
+
+> Validates that settings profile selectors exist in the DOM. This is a lightweight test that ONLY checks selector presence, not functionality. Runs as Phase 12 sub-gate before functional tests.
+
+## @test SEL_PROF_001: Profile Page Selectors
+
+### Metadata
+- **Priority:** High
+- **Type:** Selector Validation
+- **Tags:** settings, profile, form
+- **Grep:** `@ui-selectors` `@SEL_PROF_001`
+- **Status:** Active (6 passing, 3 skipped)
+
+```gherkin:en
+Scenario: Profile page has required selectors
+
+Given I am logged in as developer
+And I navigate to the profile settings page
+Then I should find the profile container
+And I should find the profile form
+And I should find the first name input
+And I should find the last name input
+And I should find the email input
+And I should find the profile submit button
+```
+
+```gherkin:es
+Scenario: La pagina de perfil tiene los selectores requeridos
+
+Given estoy logueado como developer
+And navego a la pagina de settings de perfil
+Then deberia encontrar el contenedor de perfil
+And deberia encontrar el formulario de perfil
+And deberia encontrar el input de nombre
+And deberia encontrar el input de apellido
+And deberia encontrar el input de email
+And deberia encontrar el boton de enviar perfil
+```
+
+### Expected Results
+- `settings.profile.container` selector exists (settings-profile) ✅
+- `settings.profile.form` selector exists (profile-form) ✅
+- `settings.profile.firstName` selector exists (profile-first-name) ✅
+- `settings.profile.lastName` selector exists (profile-last-name) ✅
+- `settings.profile.email` selector exists (profile-email) ✅
+- `settings.profile.submit` selector exists (profile-submit) ✅
+- `settings.profile.avatar` selector - **SKIPPED: Feature not implemented**
+- `settings.profile.avatarUpload` selector - **SKIPPED: Feature not implemented**
+- `settings.profile.successMessage` selector - **SKIPPED: Requires form submission (functional test)**
+
+### Notes
+**Skipped Tests (3):**
+1. `profile-avatar` - Avatar feature not implemented in ProfilePage component
+2. `profile-avatar-upload` - Avatar upload feature not implemented
+3. `profile-success` - Success message only appears after form submission (functional test, not selector validation)
+
+---
+
+## Related Components
+
+| Component | File | Selectors |
+|-----------|------|-----------|
+| ProfilePage | `apps/dev/app/dashboard/settings/profile/page.tsx` | settings-profile, profile-form, profile-first-name, profile-last-name, profile-email, profile-submit, profile-success |
+
+## Related POMs
+
+| POM | File | Usage |
+|-----|------|-------|
+| SettingsPOM | `themes/default/tests/cypress/src/features/SettingsPOM.ts` | Profile page selectors |

package/dist/templates/contents/themes/starter/tests/cypress/e2e/_utils/selectors/settings-profile.cy.ts

@@ -0,0 +1,79 @@
+/**
+ * UI Selectors Validation: Settings Profile
+ *
+ * This test validates that settings profile selectors exist in the DOM.
+ * This is a lightweight test that ONLY checks selector presence, not functionality.
+ *
+ * Purpose:
+ * - Validate SettingsPOM profile selectors work correctly
+ * - Ensure all settings.profile.* selectors are implemented
+ * - Run as Phase 12 sub-gate before functional tests
+ *
+ * Scope:
+ * - Navigate to profile settings page (requires login)
+ * - Assert elements exist in DOM (no form submissions)
+ * - Fast execution (< 30 seconds per describe block)
+ *
+ * Test IDs:
+ * - SEL_PROF_001: Profile Page Selectors
+ *
+ * NOTE: Only 2 selectors are NOT implemented (feature doesn't exist):
+ * - profile-avatar, profile-avatar-upload (avatar feature not in current implementation)
+ */
+
+import { SettingsPOM } from '../../../src/features/SettingsPOM'
+import { loginAsDefaultDeveloper } from '../../../src/session-helpers'
+
+describe('Settings Profile Selectors Validation', { tags: ['@ui-selectors', '@settings'] }, () => {
+  const settings = SettingsPOM.create()
+
+  beforeEach(() => {
+    loginAsDefaultDeveloper()
+    settings.visitProfile()
+    // Wait for profile page to load - use profile form as indicator
+    cy.get(settings.selectors.profileForm, { timeout: 15000 }).should('be.visible')
+  })
+
+  // ============================================
+  // SEL_PROF_001: PROFILE PAGE SELECTORS
+  // ============================================
+  describe('SEL_PROF_001: Profile Page Selectors', { tags: '@SEL_PROF_001' }, () => {
+    it('should find profile container', () => {
+      cy.get(settings.selectors.profileContainer).should('exist')
+    })
+
+    it('should find profile form', () => {
+      cy.get(settings.selectors.profileForm).should('exist')
+    })
+
+    // NOTE: Avatar selectors not implemented in current ProfilePage component
+    it.skip('should find profile avatar (not implemented in component)', () => {
+      cy.get(settings.selectors.profileAvatar).should('exist')
+    })
+
+    it.skip('should find avatar upload button (not implemented in component)', () => {
+      cy.get(settings.selectors.profileAvatarUpload).should('exist')
+    })
+
+    it('should find first name input', () => {
+      cy.get(settings.selectors.profileFirstName).should('exist')
+    })
+
+    it('should find last name input', () => {
+      cy.get(settings.selectors.profileLastName).should('exist')
+    })
+
+    it('should find email input', () => {
+      cy.get(settings.selectors.profileEmail).should('exist')
+    })
+
+    it('should find submit button', () => {
+      cy.get(settings.selectors.profileSubmit).should('exist')
+    })
+
+    // Note: Success message only appears after successful form submission
+    it.skip('should find success message (requires successful submission)', () => {
+      cy.get(settings.selectors.profileSuccess).should('exist')
+    })
+  })
+})

package/dist/templates/contents/themes/starter/tests/cypress/e2e/_utils/selectors/settings-teams.bdd.md

@@ -0,0 +1,130 @@
+---
+feature: Settings Teams UI Selectors Validation
+priority: high
+tags: [selectors, settings, teams, ui-validation]
+grepTags: [ui-selectors, settings, SEL_STMS_001, SEL_STMS_002]
+coverage: 2
+---
+
+# Settings Teams UI Selectors Validation
+
+> Validates that settings teams selectors exist in the DOM. This is a lightweight test that ONLY checks selector presence, not functionality. Runs as Phase 12 sub-gate before functional tests.
+
+## @test SEL_STMS_001: Teams Page Selectors
+
+### Metadata
+- **Priority:** High
+- **Type:** Selector Validation
+- **Tags:** settings, teams, management
+- **Grep:** `@ui-selectors` `@SEL_STMS_001`
+- **Status:** Active (6 passing, 0 skipped)
+
+```gherkin:en
+Scenario: Teams settings page has required selectors
+
+Given I am logged in as developer
+And I navigate to the teams settings page
+Then I should find the teams main container
+And I should find the teams header
+And I should find the teams list
+And I should find at least one team item in the list
+And I should find the create team button
+When I click on a team item
+Then I should find the team details section
+```
+
+```gherkin:es
+Scenario: La pagina de settings de teams tiene los selectores requeridos
+
+Given estoy logueado como developer
+And navego a la pagina de settings de teams
+Then deberia encontrar el contenedor principal de teams
+And deberia encontrar el header de teams
+And deberia encontrar la lista de teams
+And deberia encontrar al menos un item de equipo en la lista
+And deberia encontrar el boton de crear equipo
+When hago click en un item de equipo
+Then deberia encontrar la seccion de detalles del equipo
+```
+
+### Expected Results
+- `teams-settings-main` selector exists ✅
+- `teams-settings-header` selector exists ✅
+- `teams-settings-teams-list` selector exists ✅
+- `team-item-{id}` selector exists for team items ✅
+- `teams-settings-team-details` selector exists when team selected ✅
+- `create-team-button` selector exists ✅
+
+---
+
+## @test SEL_STMS_002: Create Team Dialog Documentation
+
+### Metadata
+- **Priority:** Medium
+- **Type:** Documentation
+- **Tags:** settings, teams, dialog
+- **Grep:** `@ui-selectors` `@SEL_STMS_002`
+- **Status:** Active (1 passing, 0 skipped)
+
+```gherkin:en
+Scenario: Create Team Dialog selectors are documented
+
+Given the Create Team Dialog can be opened from teams settings
+Then the following selectors are documented:
+| Selector | Value |
+| create-team-dialog | Dialog container |
+| team-name-input | Name input field |
+| team-slug-input | Slug input field |
+| team-description-input | Description input |
+| cancel-create-team | Cancel button |
+| submit-create-team | Submit button |
+```
+
+```gherkin:es
+Scenario: Los selectores del dialogo de crear equipo estan documentados
+
+Given el dialogo de crear equipo puede abrirse desde settings de teams
+Then los siguientes selectores estan documentados:
+| Selector | Valor |
+| create-team-dialog | Contenedor del dialogo |
+| team-name-input | Campo de nombre |
+| team-slug-input | Campo de slug |
+| team-description-input | Campo de descripcion |
+| cancel-create-team | Boton cancelar |
+| submit-create-team | Boton enviar |
+```
+
+### Expected Results
+- Create Team Dialog selectors are documented for reference ✅
+- Actual dialog testing done in teams.cy.ts (SEL_TEAM_003)
+
+### Notes
+The Create Team Dialog selectors are shared between:
+- Teams settings page (`/dashboard/settings/teams`)
+- Team switcher create button
+
+This test documents the selectors for cross-reference with teams.cy.ts.
+
+---
+
+## Related Components
+
+| Component | File | Selectors |
+|-----------|------|-----------|
+| TeamsSettings | `packages/core/templates/app/dashboard/settings/teams/page.tsx` | teams-settings-main, teams-settings-header, teams-settings-teams-list, teams-settings-team-details, team-item-{id} |
+| CreateTeamDialog | `packages/core/src/components/teams/CreateTeamDialog.tsx` | create-team-dialog, cancel-create-team, submit-create-team |
+
+## Related POMs
+
+| POM | File | Usage |
+|-----|------|-------|
+| SettingsPOM | `themes/default/tests/cypress/src/features/SettingsPOM.ts` | Teams settings page selectors |
+| TeamSwitcherPOM | `themes/default/tests/cypress/src/components/TeamSwitcherPOM.ts` | Create team dialog selectors |
+
+## Test Summary
+
+| Test ID | Description | Status | Tests |
+|---------|-------------|--------|-------|
+| SEL_STMS_001 | Teams Page Selectors | Active | 6 |
+| SEL_STMS_002 | Create Team Dialog Documentation | Active | 1 |
+| **Total** | | **All Active** | **7** |