@polymorphism-tech/morph-spec 4.11.1 → 4.13.0

package/framework/index/troubleshooting-index.json

@@ -1,184 +0,0 @@
-{
-  "version": "1.0.0",
-  "lastUpdated": "2025-01-25",
-  "problems": [
-    {
-      "id": "efcore-pending-changes",
-      "title": "PendingModelChangesWarning no EF Core 10",
-      "keywords": ["PendingModelChanges", "migration", "EF Core", "database update", "pending", "model changed"],
-      "errorPattern": "PendingModelChangesException|pending changes|model.*has pending changes",
-      "file": "framework/standards/backend/database/ef-core.md",
-      "section": "Migrations - .NET 10 PendingModelChangesWarning",
-      "severity": "critical",
-      "scope": "blazor-azure,nextjs-supabase",
-      "category": "efcore",
-      "cause": "EF Core 10 lança exceção se modelo mudou desde última migration.",
-      "solution": "dotnet ef migrations add <Name> antes de database update"
-    },
-    {
-      "id": "dbcontext-concurrent",
-      "title": "DbContext Concurrency Error",
-      "keywords": ["DbContext", "concurrent", "second operation", "Task.Run", "background", "thread"],
-      "errorPattern": "A second operation was started|concurrently using the same instance",
-      "file": "framework/standards/backend/database/ef-core.md",
-      "section": "The Problem: DbContext Concurrency",
-      "severity": "critical",
-      "scope": "blazor-azure,nextjs-supabase",
-      "category": "efcore",
-      "cause": "DbContext scoped está sendo usado em operações paralelas/background.",
-      "solution": "Usar IDbContextFactory para operações em background"
-    },
-    {
-      "id": "navigation-include-empty",
-      "title": "Include() retorna coleção vazia",
-      "keywords": ["Include", "HasMany", "navigation", "empty", "vazia", "collection", "ICollection"],
-      "errorPattern": "Items\\.Count == 0|collection.*empty|Include.*not working",
-      "file": "framework/standards/backend/database/ef-core.md",
-      "section": "Navigation Properties - Correct Configuration",
-      "severity": "high",
-      "scope": "blazor-azure,nextjs-supabase",
-      "category": "efcore",
-      "cause": "HasMany<T>() sem navigation property causa Include() falhar silenciosamente.",
-      "solution": "Usar HasMany(x => x.Property) em vez de HasMany<T>()"
-    },
-    {
-      "id": "azure-identity-conflict",
-      "title": "Azure.Identity Version Conflict",
-      "keywords": ["Azure.Identity", "NU1605", "downgrade", "version", "conflict", "package"],
-      "errorPattern": "NU1605.*Azure\\.Identity|package downgrade.*Azure\\.Identity",
-      "file": "framework/standards/infrastructure/azure/azure.md",
-      "section": "Package Version Conflicts",
-      "severity": "high",
-      "scope": "blazor-azure",
-      "category": "azure",
-      "cause": "Dependências transitivas puxam versões diferentes do Azure.Identity.",
-      "solution": "<PackageReference Include=\"Azure.Identity\" Version=\"1.14.2\" />"
-    },
-    {
-      "id": "keyvault-di-fail",
-      "title": "Key Vault não carrega em Development",
-      "keywords": ["KeyVault", "IsDevelopment", "DI", "secrets", "not registered", "service"],
-      "errorPattern": "IBlobStorageService.*not registered|IPaymentService.*not registered|service.*not registered",
-      "file": "framework/standards/infrastructure/azure/azure.md",
-      "section": "Key Vault Configuration",
-      "severity": "critical",
-      "scope": "blazor-azure",
-      "category": "azure",
-      "cause": "Key Vault condicionado ao ambiente (!IsDevelopment) não carrega secrets.",
-      "solution": "Não condicionar Key Vault ao ambiente - carregar sempre que URI existir"
-    },
-    {
-      "id": "credential-slow",
-      "title": "DefaultAzureCredential lento no container",
-      "keywords": ["DefaultAzureCredential", "slow", "timeout", "container", "startup", "30 seconds"],
-      "errorPattern": "timeout|30 seconds|startup.*slow|credential.*timeout",
-      "file": "framework/standards/infrastructure/azure/azure.md",
-      "section": "DefaultAzureCredential Optimization",
-      "severity": "medium",
-      "scope": "blazor-azure",
-      "category": "azure",
-      "cause": "DefaultAzureCredential tenta múltiplos métodos de autenticação sequencialmente.",
-      "solution": "Desabilitar credenciais não usadas com ExcludeXxxCredential = true"
-    },
-    {
-      "id": "containerapp-not-updating",
-      "title": "Container App não atualiza após push",
-      "keywords": ["Container App", "revision", "not updating", "old version", "push", "deploy"],
-      "errorPattern": "old version|not updating|same image",
-      "file": "framework/standards/infrastructure/azure/azure.md",
-      "section": "Container App Deployment Issues",
-      "severity": "medium",
-      "scope": "blazor-azure",
-      "category": "azure",
-      "cause": "Mesmo digest de imagem não triggera nova revisão.",
-      "solution": "Usar DEPLOY_TIMESTAMP=$(date +%s) para forçar nova revisão"
-    },
-    {
-      "id": "migrations-not-applied",
-      "title": "Invalid object name - Tabela não existe",
-      "keywords": ["Invalid object name", "table", "migration", "not applied", "database"],
-      "errorPattern": "Invalid object name|table.*does not exist|object.*not found",
-      "file": "framework/standards/backend/database/ef-core.md",
-      "section": "Auto-Migration on Startup",
-      "severity": "high",
-      "scope": "blazor-azure,nextjs-supabase",
-      "category": "efcore",
-      "cause": "Migrations não foram aplicadas ao banco de dados.",
-      "solution": "Rodar dotnet ef database update ou adicionar auto-migration no startup"
-    },
-    {
-      "id": "di-httpcontext",
-      "title": "HttpContext null em background thread",
-      "keywords": ["HttpContext", "null", "background", "Task.Run", "accessor"],
-      "errorPattern": "HttpContext.*null|IHttpContextAccessor.*null",
-      "file": "framework/standards/frontend/blazor/pitfalls.md",
-      "section": "Dependency Injection Pattern",
-      "severity": "critical",
-      "scope": "blazor-azure",
-      "category": "blazor",
-      "cause": "HttpContext não está disponível em threads background.",
-      "solution": "Capturar dados do HttpContext antes de iniciar Task.Run"
-    },
-    {
-      "id": "jsruntime-prerender",
-      "title": "JSRuntime error during prerendering",
-      "keywords": ["JSRuntime", "prerender", "JavaScript", "interop", "OnInitializedAsync"],
-      "errorPattern": "JavaScript interop.*prerendering|JSRuntime.*not available",
-      "file": "framework/standards/frontend/blazor/pitfalls.md",
-      "section": "JSRuntime Lifecycle",
-      "severity": "high",
-      "scope": "blazor-azure",
-      "category": "blazor",
-      "cause": "JSRuntime não disponível durante prerendering.",
-      "solution": "Usar OnAfterRenderAsync com firstRender check"
-    },
-    {
-      "id": "static-files-404",
-      "title": "Static files retornando 404",
-      "keywords": ["static files", "wwwroot", "CSS", "JS", "404", "assets"],
-      "errorPattern": "static.*404|wwwroot.*not found|css.*404|js.*404",
-      "file": "framework/standards/frontend/blazor/pitfalls.md",
-      "section": "Static Files",
-      "severity": "high",
-      "scope": "blazor-azure",
-      "category": "blazor",
-      "cause": "UseStaticFiles() não configurado ou arquivos não em wwwroot.",
-      "solution": "Adicionar app.UseStaticFiles() e verificar caminho dos arquivos"
-    },
-    {
-      "id": "rendermode-mismatch",
-      "title": "Componente não renderiza interativamente",
-      "keywords": ["RenderMode", "InteractiveServer", "static", "onclick", "not working"],
-      "errorPattern": "@onclick.*not working|button.*not responding|interactive.*not working",
-      "file": "framework/standards/frontend/blazor/pitfalls.md",
-      "section": "RenderModes",
-      "severity": "high",
-      "scope": "blazor-azure",
-      "category": "blazor",
-      "cause": "Componente está em modo estático mas precisa de interatividade.",
-      "solution": "Adicionar @rendermode InteractiveServer no componente"
-    }
-  ],
-  "categories": {
-    "blazor": {
-      "name": "Blazor Server/WASM",
-      "description": "Problemas com componentes Blazor, lifecycle, renderização"
-    },
-    "efcore": {
-      "name": "Entity Framework Core",
-      "description": "Problemas com DbContext, migrations, queries"
-    },
-    "azure": {
-      "name": "Azure Infrastructure",
-      "description": "Problemas com Azure services, deploy, identity"
-    },
-    "auth": {
-      "name": "Authentication/Authorization",
-      "description": "Problemas com login, tokens, claims"
-    },
-    "deploy": {
-      "name": "Deployment/CI-CD",
-      "description": "Problemas com build, deploy, pipelines"
-    }
-  }
-}

package/framework/rules/testing-standards.md

@@ -1,14 +0,0 @@
----
-paths:
-  - "tests/**"
-  - "**/*.test.*"
-  - "**/*.spec.*"
-  - "**/*Tests.cs"
-stacks:
-  - dotnet
-  - blazor
----
-
-# Testing Standards
-
-@.morph/framework/standards/core/testing.md

package/framework/skills/level-0-meta/morph-replicate/SKILL.md

@@ -1,230 +0,0 @@
----
-name: morph-replicate
-description: Simplified workflow for converting HTML prototypes into functional Blazor components, extracting design patterns and mapping HTML elements to Fluent UI/MudBlazor equivalents. Use when an approved HTML prototype exists and needs conversion to Blazor without a full MORPH-SPEC spec pipeline.
-user-invocable: true
-argument-hint: "[feature-name] [prototype-path]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
-stacks:
-  - blazor
----
-
-# MORPH Replicate — HTML to Blazor Conversion
-
-> Simplified workflow for replicating HTML prototypes in Blazor.
-> Use when you have a ready HTML prototype and need to convert it to functional Blazor code.
-
-## Command
-
-```bash
-/morph-replicate {feature-name} {prototype-path}
-```
-
-**Example:**
-```bash
-/morph-replicate ui-redesign prototipo/
-```
-
----
-
-## Simplified Workflow
-
-### PHASE 1: PROTOTYPE ANALYSIS
-
-1. **Read all HTML files in `{prototype-path}/`**
-   ```bash
-   # Find all HTML files
-   glob: {prototype-path}/**/*.html
-   glob: {prototype-path}/**/code.html  # Common prototype pattern
-   ```
-
-2. **Extract patterns from each file:**
-   - Layout (grid, flexbox, structure)
-   - Components (cards, buttons, forms, modals)
-   - Colors (extract from inline styles and CSS)
-   - Fonts (font-family, sizes)
-   - Spacing (padding, margin, gap)
-   - CSS classes used
-
-3. **Generate HTML → Blazor mapping:**
-
-   **Read the reference file first:** `references/blazor-html-mapping.md` — this contains the complete mapping table for HTML→Fluent UI and HTML→MudBlazor conversions. Load it before generating the prototype-specific mapping.
-
-   Then document the relevant mappings for this specific prototype, citing the reference:
-   ```markdown
-   ## HTML → Blazor Mapping (this prototype)
-   > Source: references/blazor-html-mapping.md
-   - <HTML element> → <BlazorComponent>
-   ```
-
-4. **Generate list of CSS classes to create:**
-   ```markdown
-   ## Required CSS Classes
-
-   - [ ] .page-layout
-   - [ ] .home-hero
-   - [ ] .card-premium
-   - [ ] .checkout-form
-   - [ ] .modal-overlay
-   - [ ] .animate-slideInUp
-   ```
-
-**PAUSE:** Approve mapping and CSS list
-
----
-
-### PHASE 2: TASKS (Screen List)
-
-Generate screen list to implement in correct order:
-
-```markdown
-## Implementation Tasks
-
-### T001: Setup Design System
-- Create/update wwwroot/css/design-system.css
-- Add all listed CSS classes
-- Validate with `morph-spec validate`
-
-### T002: {Screen Name 1}
-- Read: {prototype-path}/{screen1}.html
-- Create/Update: Pages/{Screen1}.razor
-- Components: FluentCard, FluentButton, etc.
-- CSS: .home-hero, .card-premium
-
-### T003: {Screen Name 2}
-- Read: {prototype-path}/{screen2}.html
-- Create/Update: Pages/{Screen2}.razor
-- ...
-
-### TXXX: Final Validation
-- Full build
-- `morph-spec validate`
-- Test responsiveness
-```
-
-**PAUSE:** Approve task list
-
----
-
-### PHASE 3: IMPLEMENT (Per Screen)
-
-For each screen, follow this flow:
-
-1. **Read prototype HTML**
-   ```
-   Read: {prototype-path}/{screen}.html
-   ```
-
-2. **Read current .razor file** (if exists)
-   ```
-   Read: Pages/{Screen}.razor
-   ```
-
-3. **Rewrite .razor using Fluent UI/MudBlazor**
-   - Keep prototype layout structure
-   - Replace HTML elements with Blazor components
-   - Apply design-system CSS classes
-
-4. **Add CSS to design-system.css**
-   - If new class was used in .razor
-   - Follow naming pattern (prefix by page)
-
-5. **Build to validate**
-   ```bash
-   dotnet build
-   ```
-
-6. **Validate CSS**
-   ```bash
-   morph-spec validate src/MyApp.Web
-   ```
-
----
-
-## Outputs
-
-All outputs go in `.morph/features/{feature-name}/5-implement/`:
-
-| File | Location | Description |
-|---------|----------|-----------|
-| `.razor` files | Project source (Pages/, Components/, Shared/) | Converted pages |
-| `design-system.css` | `wwwroot/css/design-system.css` | Updated CSS |
-| `recap.md` | `.morph/features/{feature-name}/5-implement/recap.md` | Implementation summary |
-
-After completion, mark the output:
-```bash
-morph-spec state mark-output {feature-name} recap
-```
-
-**Does NOT generate:** proposal.md, spec.md, contracts.cs, tasks.md
-
----
-
-## Execution Example
-
-```markdown
-/morph-replicate checkout-redesign prototipo/checkout/
-
-📁 Analyzing prototype in prototipo/checkout/...
-
-**Files found:**
-- step1-cart.html
-- step2-payment.html
-- step3-confirmation.html
-
-**Extracted patterns:**
-
-Colors:
-- Primary: #FF6B35
-- Secondary: #2D3047
-- Background: #FAFAFA
-
-CSS classes to create:
-- [ ] .checkout-layout
-- [ ] .checkout-steps
-- [ ] .checkout-form
-- [ ] .checkout-summary
-- [ ] .payment-options
-- [ ] .confirmation-message
-
-HTML → Blazor Mapping:
-- form.checkout-form → EditForm + FluentTextField
-- div.payment-card → FluentCard
-- button.btn-pay → FluentButton Accent
-
----
-
-⛔ **MANDATORY PAUSE**
-
-**Next steps:**
-1. ✅ Approve and generate implementation tasks
-2. 🔄 Adjust mapping
-3. 📋 See more component details
-```
-
----
-
-## When to Use
-
-- ✅ HTML prototype ready (hand-coded, exported, etc.)
-- ✅ Design already approved by client
-- ✅ Visual conversion only (no new business logic)
-- ✅ Existing Blazor code to update
-
-## When NOT to Use
-
-- ❌ New feature with complex logic (use FULL MORPH)
-- ❌ Azure infrastructure needed (use FULL MORPH)
-- ❌ No prototype defined (use STANDARD or FULL MORPH)
-
----
-
-## References
-
-- **Ref:** `framework/standards/frontend/blazor/html-conversion.md`
-- **Ref:** `framework/standards/frontend/design-system/naming.md`
-- **Ref:** `framework/standards/frontend/design-system/animations.md`
-- **Ref:** `framework/standards/frontend/blazor/fluent-ui.md`
-
----
-
-*MORPH-SPEC by Polymorphism Tech*

package/framework/skills/level-0-meta/morph-replicate/references/blazor-html-mapping.md

@@ -1,70 +0,0 @@
-# HTML → Blazor Component Mapping Reference
-
-> Reference for converting HTML prototype elements to Fluent UI / MudBlazor equivalents.
-> Used during FASE 1 of the `/morph-replicate` workflow.
-
-## Common Component Mappings
-
-| HTML Pattern | Fluent UI Equivalent | MudBlazor Equivalent |
-|---|---|---|
-| `<button class="btn-primary">` | `<FluentButton Appearance="Appearance.Accent">` | `<MudButton Variant="Variant.Filled" Color="Color.Primary">` |
-| `<button class="btn-secondary">` | `<FluentButton Appearance="Appearance.Outline">` | `<MudButton Variant="Variant.Outlined">` |
-| `<div class="card">` | `<FluentCard>` | `<MudCard>` |
-| `<input type="text">` | `<FluentTextField>` | `<MudTextField>` |
-| `<input type="search">` | `<FluentSearch>` | `<MudTextField Adornment="Adornment.Start" AdornmentIcon="Icons.Material.Filled.Search">` |
-| `<select>` | `<FluentSelect>` | `<MudSelect>` |
-| `<input type="checkbox">` | `<FluentCheckbox>` | `<MudCheckBox>` |
-| `<input type="radio">` | `<FluentRadio>` | `<MudRadio>` |
-| `<div class="modal">` | `<FluentDialog>` | `<MudDialog>` |
-| `<nav>` / `<ul class="nav">` | `<FluentNavMenu>` | `<MudNavMenu>` |
-| `<table>` | `<FluentDataGrid>` | `<MudTable>` |
-| `<div class="spinner">` | `<FluentProgressRing>` | `<MudProgressCircular>` |
-| `<div class="progress-bar">` | `<FluentProgress>` | `<MudProgressLinear>` |
-| `<span class="badge">` | `<FluentBadge>` | `<MudChip>` |
-| `<div class="alert">` | `<FluentMessageBar>` | `<MudAlert>` |
-| `<form>` | `<EditForm>` | `<EditForm>` |
-| `<div class="tooltip">` | `<FluentTooltip>` | `<MudTooltip>` |
-| `<img>` | `<FluentIcon>` (for icons) / `<img>` | `<MudImage>` / `<img>` |
-| `<div class="tabs">` | `<FluentTabs>` | `<MudTabs>` |
-| `<details>/<summary>` | `<FluentAccordion>` | `<MudExpansionPanel>` |
-
-## Layout Mappings
-
-| HTML Layout Pattern | Blazor/CSS Approach |
-|---|---|
-| `display: grid` | Keep as CSS grid (no Fluent/MudBlazor equivalent) |
-| `display: flex` | Keep as CSS flexbox |
-| `class="container"` | Keep as CSS class in design-system.css |
-| `class="row col-*"` | Keep as CSS or use CSS grid |
-| `class="sidebar"` | `<FluentBodyContent>` or custom CSS layout |
-
-## Form Patterns
-
-| HTML Form Pattern | Blazor Equivalent |
-|---|---|
-| `<input required>` | FluentValidation rule + `<FluentValidationMessage>` |
-| `<input pattern="...">` | FluentValidation `Matches()` rule |
-| `<input min/max>` | FluentValidation `InclusiveBetween()` rule |
-| Form submission | `<EditForm OnValidSubmit="HandleSubmit">` |
-| Error display | `<FluentValidationSummary>` or `<DataAnnotationsValidator>` |
-
-## Animation Mappings
-
-| CSS Animation Class | Blazor Approach |
-|---|---|
-| `animate-fadeIn` | CSS class in design-system.css (keep as-is) |
-| `animate-slideInUp` | CSS class in design-system.css (keep as-is) |
-| `animate-pulse` | CSS class or `<FluentProgressRing>` |
-
-> For animation standards, see: `framework/standards/frontend/design-system/animations.md`
-
-## Decision Guide
-
-When a direct component mapping doesn't exist:
-1. **Check Fluent UI docs** — it may have a less obvious equivalent
-2. **Use HTML wrapper** — wrap plain HTML in a `<div>` with design-system CSS classes
-3. **Create a custom Razor component** — when the design is project-specific and reused across pages
-4. **Keep as HTML** — for one-off layout elements that don't need a component
-
-> For full Fluent UI reference: `framework/standards/frontend/blazor/fluent-ui.md`
-> For MudBlazor reference: `framework/standards/frontend/blazor/html-conversion.md`