diff --git a/.codex/prompts/speckit.implement.md b/.codex/prompts/speckit.implement.md index 41da7b93..3fc0b298 100644 --- a/.codex/prompts/speckit.implement.md +++ b/.codex/prompts/speckit.implement.md @@ -53,7 +53,21 @@ ## Outline - **IF EXISTS**: Read research.md for technical decisions and constraints - **IF EXISTS**: Read quickstart.md for integration scenarios -4. **Project Setup Verification**: +4. **UI/Productization Coverage Guardrail**: + - Before implementing, determine whether this spec adds, removes, renames, or materially changes any reachable UI surface. + - A UI surface includes pages, routes, navigation entries, tables, forms, modals, drawers, wizard steps, actions, dangerous-action confirmations, empty/loading/error states, customer-facing views, and operator workflow surfaces. + - If UI is affected: + - update the UI/UX audit inventory under `docs/ui-ux-enterprise-audit/` + - assign page archetype + - assign design depth + - assign repo-truth level + - link to an existing pattern or document the missing pattern/mockup need + - review customer-safe and dangerous-action implications where applicable + - update the coverage matrix or unresolved/manual-review ledger + - If no reachable UI surface is affected, ensure the active spec contains exactly `- [x] No UI surface impact` with a short rationale. + - Do not mark the spec complete if a new or changed reachable UI surface remains unclassified. + +5. **Project Setup Verification**: - **REQUIRED**: Create/verify ignore files based on actual project setup: **Detection & Creation Logic**: @@ -97,27 +111,27 @@ ## Outline - **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl` - **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt` -5. Parse tasks.md structure and extract: +6. Parse tasks.md structure and extract: - **Task phases**: Setup, Tests, Core, Integration, Polish - **Task dependencies**: Sequential vs parallel execution rules - **Task details**: ID, description, file paths, parallel markers [P] - **Execution flow**: Order and dependency requirements -6. Execute implementation following the task plan: +7. Execute implementation following the task plan: - **Phase-by-phase execution**: Complete each phase before moving to the next - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks - **File-based coordination**: Tasks affecting the same files must run sequentially - **Validation checkpoints**: Verify each phase completion before proceeding -7. Implementation execution rules: +8. Implementation execution rules: - **Setup first**: Initialize project structure, dependencies, configuration - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios - **Core development**: Implement models, services, CLI commands, endpoints - **Integration work**: Database connections, middleware, logging, external services - **Polish and validation**: Unit tests, performance optimization, documentation -8. Progress tracking and error handling: +9. Progress tracking and error handling: - Report progress after each completed task - Halt execution if any non-parallel task fails - For parallel tasks [P], continue with successful tasks, report failed ones @@ -125,7 +139,7 @@ ## Outline - Suggest next steps if implementation cannot proceed - **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file. -9. Completion validation: +10. Completion validation: - Verify all required tasks are completed - Check that implemented features match the original specification - Validate that tests pass and coverage meets requirements diff --git a/.gitea/pull_request_template.md b/.gitea/pull_request_template.md index 882fa7f4..c49b1ba5 100644 --- a/.gitea/pull_request_template.md +++ b/.gitea/pull_request_template.md @@ -25,6 +25,7 @@ ## Migration / Config / Ops (falls relevant) ## UI (Filament/Livewire) (falls relevant) - [ ] UI-Flows geprüft - [ ] Screenshots/Notizen hinzugefügt +- [ ] UI Surface Impact in der Spec dokumentiert: entweder `[x] No UI surface impact` mit Begründung oder UI/Productization Coverage + Audit-Artefakte aktualisiert ## Notes - \ No newline at end of file + diff --git a/.gitea/workflows/test-pr-fast-feedback.yml b/.gitea/workflows/test-pr-fast-feedback.yml index 6f446631..67519023 100644 --- a/.gitea/workflows/test-pr-fast-feedback.yml +++ b/.gitea/workflows/test-pr-fast-feedback.yml @@ -21,6 +21,11 @@ jobs: - name: Checkout repository uses: actions/checkout@v4 + - name: Run UI/Productization Coverage guard + run: | + git fetch origin dev --depth=1 + bash scripts/check-ui-productization-coverage origin/dev + - name: Set up PHP uses: shivammathur/setup-php@v2 with: diff --git a/.github/agents/speckit.implement.agent.md b/.github/agents/speckit.implement.agent.md index 41da7b93..3fc0b298 100644 --- a/.github/agents/speckit.implement.agent.md +++ b/.github/agents/speckit.implement.agent.md @@ -53,7 +53,21 @@ ## Outline - **IF EXISTS**: Read research.md for technical decisions and constraints - **IF EXISTS**: Read quickstart.md for integration scenarios -4. **Project Setup Verification**: +4. **UI/Productization Coverage Guardrail**: + - Before implementing, determine whether this spec adds, removes, renames, or materially changes any reachable UI surface. + - A UI surface includes pages, routes, navigation entries, tables, forms, modals, drawers, wizard steps, actions, dangerous-action confirmations, empty/loading/error states, customer-facing views, and operator workflow surfaces. + - If UI is affected: + - update the UI/UX audit inventory under `docs/ui-ux-enterprise-audit/` + - assign page archetype + - assign design depth + - assign repo-truth level + - link to an existing pattern or document the missing pattern/mockup need + - review customer-safe and dangerous-action implications where applicable + - update the coverage matrix or unresolved/manual-review ledger + - If no reachable UI surface is affected, ensure the active spec contains exactly `- [x] No UI surface impact` with a short rationale. + - Do not mark the spec complete if a new or changed reachable UI surface remains unclassified. + +5. **Project Setup Verification**: - **REQUIRED**: Create/verify ignore files based on actual project setup: **Detection & Creation Logic**: @@ -97,27 +111,27 @@ ## Outline - **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl` - **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt` -5. Parse tasks.md structure and extract: +6. Parse tasks.md structure and extract: - **Task phases**: Setup, Tests, Core, Integration, Polish - **Task dependencies**: Sequential vs parallel execution rules - **Task details**: ID, description, file paths, parallel markers [P] - **Execution flow**: Order and dependency requirements -6. Execute implementation following the task plan: +7. Execute implementation following the task plan: - **Phase-by-phase execution**: Complete each phase before moving to the next - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks - **File-based coordination**: Tasks affecting the same files must run sequentially - **Validation checkpoints**: Verify each phase completion before proceeding -7. Implementation execution rules: +8. Implementation execution rules: - **Setup first**: Initialize project structure, dependencies, configuration - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios - **Core development**: Implement models, services, CLI commands, endpoints - **Integration work**: Database connections, middleware, logging, external services - **Polish and validation**: Unit tests, performance optimization, documentation -8. Progress tracking and error handling: +9. Progress tracking and error handling: - Report progress after each completed task - Halt execution if any non-parallel task fails - For parallel tasks [P], continue with successful tasks, report failed ones @@ -125,7 +139,7 @@ ## Outline - Suggest next steps if implementation cannot proceed - **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file. -9. Completion validation: +10. Completion validation: - Verify all required tasks are completed - Check that implemented features match the original specification - Validate that tests pass and coverage meets requirements diff --git a/.specify/memory/constitution.md b/.specify/memory/constitution.md index be14d1fb..52f0ba5a 100644 --- a/.specify/memory/constitution.md +++ b/.specify/memory/constitution.md @@ -1,35 +1,35 @@