@polymorphism-tech/morph-spec 4.12.0 → 4.14.0

package/framework/commands/morph-apply.md

@@ -57,9 +57,9 @@ Do NOT proceed until all phases are complete and all gates approved.
 Read all prerequisite files in a single parallel call — every file listed here matters for implementation quality:
 
 ```
-Read: .morph/features/$ARGUMENTS/1-design/spec.md              (→ functional requirements, API contracts)
-    + Read: .morph/features/$ARGUMENTS/1-design/contracts.cs    (or contracts.ts / contracts-vsa.cs → C# interfaces)
-    + Read: .morph/features/$ARGUMENTS/1-design/decisions.md    (→ ADRs, architectural choices)
+Read: .morph/features/$ARGUMENTS/2-design/spec.md              (→ functional requirements, API contracts)
+    + Read: .morph/features/$ARGUMENTS/2-design/contracts.cs    (or contracts.ts / contracts-vsa.cs → C# interfaces)
+    + Read: .morph/features/$ARGUMENTS/2-design/decisions.md    (→ ADRs, architectural choices)
     + Read: .morph/features/$ARGUMENTS/3-plan/plan.md           (→ TDD structure, execution strategy)
     + Read: .morph/features/$ARGUMENTS/4-tasks/tasks.md         (→ task breakdown with T### IDs)
     + Read: .morph/config/config.json                           (→ architecture.style for VSA routing)
@@ -82,7 +82,6 @@ cat .morph/config/config.json | grep -A3 '"architecture"'
 ```
 
 - **`"vertical-slice"`** → follow VSA implementation patterns from `framework/standards/architecture/vertical-slice/vertical-slice.md`. Each task is a complete slice (Handler + Validator + Endpoint in one folder).
-- **Otherwise** → follow DDD/Clean Architecture patterns. Tasks map to domain layers.
 
 ### 4. Get agent dispatch config
 
@@ -96,7 +95,7 @@ This shows which agents are active for implementation and how tasks can be group
 morph-spec dispatch-agents $ARGUMENTS implement
 ```
 
-The JSON output includes `shouldDispatch`, `agents[]`, and `taskGroups` for multi-agent coordination.
+The JSON output includes `shouldDispatch`, `recommended` (agents by group), and `tasks` (task IDs by group) for multi-agent coordination.
 
 ---
 
@@ -142,7 +141,6 @@ morph-spec task start $ARGUMENTS {task-id}
 #    - Follow spec.md and contracts
 #    - Follow coding standards from framework/standards/ and .morph/context/
 #    - For VSA: create all slice files in one folder (Handler + Validator + Endpoint)
-#    - For DDD: implement in the correct domain layer
 
 # 3. Verify before completing — run validate-feature or check your work
 #    matches the spec and contracts before marking done

package/framework/commands/morph-preflight.md

@@ -1,269 +1,192 @@
----
-description: Validate project readiness before Azure deploy — checks specs, contracts, tests, and infrastructure
-argument-hint: [feature-name]
-allowed-tools: Read, Bash, Glob, Grep
----
-
-# Pre-Flight Check for Azure Deployment
-
-Validates project readiness before deploying to Azure.
-
-## Usage
-
-```
-/morph-preflight azure
-```
-
-## Purpose
-
-Detect problems **before** deploy that would cause production failures. Saves time and avoids debugging in Azure environment.
-
----
-
-## MORPH-SPEC Validation (run before all other checks)
-
-These checks verify that the morph-spec workflow is complete for the feature being deployed. Skip only if deploying a non-morph-spec project.
-
-```bash
-# Verify implementation is complete
-morph-spec state get {feature}
-morph-spec approval-status {feature}
-morph-spec validate-feature {feature}
-```
-
-| Check | Command | Pass Criteria |
-|-------|---------|---------------|
-| Phase is implement or later | `state get` | phase derived as `implement` |
-| All gates approved | `approval-status` | design, plan, tasks gates all approved |
-| Feature validation passes | `validate-feature` | 100% pass rate |
-| All tasks complete | `state get` → tasks array | 0 tasks in `pending` or `in_progress` |
-| Recap generated | Read `5-implement/recap.md` | File exists and is non-empty |
-
-**If any MORPH check fails:** Show which check failed and recommend: `Run /morph-apply {feature} to complete implementation before deploying.`
-
----
-
-## Test Suite (run before infrastructure checks)
-
-```bash
-dotnet test --verbosity normal
-```
-
-**Pass criteria:** 100% test pass rate. Zero tolerance — any failing test blocks deployment. If tests fail, categorize each failure:
-- **Genuine bug** → fix implementation
-- **Flaky/environment test** → isolate and fix
-- **Outdated assertion** → update test to match correct new behavior
-
----
-
-## Validations Performed
-
-### 1. Package Version Conflicts
-
-**What it checks:**
-- `Azure.Identity` explicitly specified
-- No version conflicts (NU1605, NU1608)
-- Critical packages with compatible versions
-
-**How to check:**
-```bash
-dotnet restore --verbosity normal 2>&1 | grep -E "(NU1605|NU1608|warning)"
-```
-
-**Common fix:**
-```xml
-<PackageReference Include="Azure.Identity" Version="1.14.2" />
-```
-
----
-
-### 2. EF Core Migrations
-
-**What it checks:**
-- No pending model changes
-- Applicable migrations exist
-- Migration scripts are valid
-
-**How to check:**
-```bash
-dotnet ef migrations has-pending-model-changes \
-  --project src/Infrastructure \
-  --startup-project src/Web
-```
-
-**Common fix:**
-```bash
-dotnet ef migrations add <MigrationName> \
-  --project src/Infrastructure \
-  --startup-project src/Web
-```
-
----
-
-### 3. Dockerfile Validation (if Container Apps)
-
-**What it checks:**
-- Dockerfile exists
-- Base image is valid
-- Multi-stage build configured
-- EXPOSE ports correct
-- ENTRYPOINT defined
-
-**How to check:**
-```bash
-docker build --check .
-# Or manual Dockerfile validation
-```
-
----
-
-### 4. Blazor .NET 10 Assets
-
-**What it checks:**
-- `RequiresAspNetWebAssets` is `true` (if Blazor + .NET 10)
-- Static web assets configured correctly
-
-**How to check:**
-```bash
-grep -r "RequiresAspNetWebAssets" *.csproj
-```
-
-**Fix:**
-```xml
-<PropertyGroup>
-  <RequiresAspNetWebAssets>true</RequiresAspNetWebAssets>
-</PropertyGroup>
-```
-
----
-
-### 5. Bicep Syntax Validation
-
-**What it checks:**
-- `.bicep` files without syntax errors
-- Required parameters defined
-- Resources with valid names
-
-**How to check:**
-```bash
-az bicep build --file infra/main.bicep --stdout > /dev/null
-```
-
----
-
-### 6. Key Vault Configuration
-
-**What it checks:**
-- Key Vault URI configured in `appsettings.json` or environment
-- Key Vault not conditioned on environment (common bug)
-- Managed Identity enabled
-
-**How to check:**
-```bash
-grep -r "KeyVaultUri\|AzureKeyVault" appsettings*.json
-grep -r "IsDevelopment()" Program.cs | grep -i keyvault
-```
-
-**Anti-pattern to detect:**
-```csharp
-// ❌ WRONG - Doesn't load Key Vault in dev!
-if (!builder.Environment.IsDevelopment())
-{
-    builder.Configuration.AddAzureKeyVault(...);
-}
-```
-
----
-
-### 7. Connection Strings Security
-
-**What it checks:**
-- Connection strings not hardcoded in code
-- Secrets in Key Vault or User Secrets
-- No credentials in `appsettings.json` (except Development)
-
-**How to check:**
-```bash
-# Detect passwords in appsettings
-grep -rE "(Password=|Pwd=|Secret=)" appsettings*.json | grep -v Development
-```
-
----
-
-## Example Output
-
-```
-🔍 MORPH Pre-Flight Check: Azure Deployment
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-✅ Packages: No version conflicts detected
-✅ Migrations: No pending model changes
-✅ Dockerfile: Valid multi-stage build
-✅ Blazor Assets: RequiresAspNetWebAssets=true
-✅ Bicep: Syntax valid
-❌ Key Vault: URI not configured in appsettings.Production.json
-⚠️ Connection Strings: Found password in appsettings.Staging.json
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📋 Summary: 5 passed, 1 failed, 1 warning
-
-❌ BLOCKED: Fix Key Vault configuration before deploy!
-
-Recommended fixes:
-1. Add KeyVaultUri to appsettings.Production.json
-2. Move password from appsettings.Staging.json to Key Vault
-```
-
----
-
-## Usage Workflow
-
-### Before creating PR for production
-
-```bash
-/morph-preflight azure
-```
-
-### In CI/CD pipeline
-
-```yaml
-- script: |
-    # Package check
-    dotnet restore 2>&1 | grep -E "NU1605|NU1608" && exit 1
-
-    # Migration check
-    dotnet ef migrations has-pending-model-changes \
-      --project src/Infrastructure \
-      --startup-project src/Web
-    if [ $? -ne 0 ]; then exit 1; fi
-
-    # Bicep check
-    az bicep build --file infra/main.bicep --stdout > /dev/null
-    if [ $? -ne 0 ]; then exit 1; fi
-
-    echo "Pre-flight checks passed!"
-  displayName: 'Pre-flight validation'
-```
-
----
-
-## Future Validations (Roadmap)
-
-- [ ] Cost estimation validation (within budget)
-- [ ] RBAC permissions check
-- [ ] Network security rules validation
-- [ ] Health probe endpoint exists
-- [ ] Application Insights configured
-
----
-
-## References
-
-- [azure.md](../../standards/azure.md) - Azure Standards
-- [dotnet10-migration.md](../../standards/dotnet10-migration.md) - Breaking changes .NET 10
-- [blazor-efcore.md](../../../../framework/standards/blazor-efcore.md) - EF Core patterns
-
----
-
-*MORPH-SPEC by Polymorphism Tech*
+---
+description: Validate project readiness before deploy — checks specs, contracts, tests, Docker, Supabase, and EasyPanel configuration
+argument-hint: [feature-name]
+allowed-tools: Read, Bash, Glob, Grep
+---
+
+# Pre-Flight Check for Deployment
+
+Validates project readiness before deploying to Docker/EasyPanel + Supabase.
+
+## Usage
+
+```
+/morph-preflight
+```
+
+## Purpose
+
+Detect problems **before** deploy that would cause production failures. Saves time and avoids debugging in production.
+
+---
+
+## MORPH-SPEC Validation (run before all other checks)
+
+These checks verify that the morph-spec workflow is complete for the feature being deployed.
+
+```bash
+# Verify implementation is complete
+morph-spec state get {feature}
+morph-spec approval-status {feature}
+morph-spec validate-feature {feature}
+```
+
+| Check | Command | Pass Criteria |
+|-------|---------|---------------|
+| Phase is implement or later | `state get` | phase derived as `implement` |
+| All gates approved | `approval-status` | design, plan, tasks gates all approved |
+| Feature validation passes | `validate-feature` | 100% pass rate |
+| All tasks complete | `state get` → tasks | 0 tasks in `pending` or `in_progress` |
+| Recap generated | Read `5-implement/recap.md` | File exists and is non-empty |
+
+**If any MORPH check fails:** Show which check failed and recommend: `Run /morph-apply {feature} to complete implementation before deploying.`
+
+---
+
+## Test Suite (run before infrastructure checks)
+
+```bash
+dotnet test --verbosity normal
+```
+
+**Pass criteria:** 100% test pass rate. Zero tolerance — any failing test blocks deployment.
+
+---
+
+## Validations Performed
+
+### 1. Package Version Conflicts
+
+**What it checks:**
+- No version conflicts (NU1605, NU1608)
+- Critical packages with compatible versions
+
+**How to check:**
+```bash
+dotnet restore --verbosity normal 2>&1 | grep -E "(NU1605|NU1608|warning)"
+```
+
+---
+
+### 2. Supabase Migrations
+
+**What it checks:**
+- No pending migrations
+- RLS policies defined for all public tables
+- Database schema matches expected state
+
+**How to check:**
+```bash
+# Check for pending migrations
+npx supabase db diff --local
+
+# Verify RLS is enabled on all tables
+npx supabase db lint --level warning
+```
+
+**Common fix:**
+```bash
+npx supabase migration new <migration-name>
+```
+
+---
+
+### 3. Dockerfile Validation
+
+**What it checks:**
+- Dockerfile exists for each service (API, Web)
+- Multi-stage build configured
+- EXPOSE ports correct
+- ENTRYPOINT defined
+- .dockerignore present
+
+**How to check:**
+```bash
+# Validate API Dockerfile
+docker build --check -f Dockerfile.api .
+
+# Validate Web Dockerfile
+docker build --check -f Dockerfile.web .
+```
+
+---
+
+### 4. Docker Compose
+
+**What it checks:**
+- `docker-compose.yml` exists and is valid
+- All services have health checks
+- Environment variables reference `.env` (not hardcoded)
+- Volumes mapped correctly
+
+**How to check:**
+```bash
+docker compose config --quiet
+```
+
+---
+
+### 5. Environment Variables & Secrets
+
+**What it checks:**
+- Connection strings not hardcoded in code
+- Secrets in environment variables (not in appsettings)
+- `.env.example` exists with all required vars documented
+- No credentials in source code
+
+**How to check:**
+```bash
+# Detect passwords in appsettings
+grep -rE "(Password=|Pwd=|Secret=|sk_live|pk_live)" appsettings*.json src/ --include="*.cs" --include="*.json" | grep -v Development
+
+# Verify .env.example exists
+test -f .env.example && echo "OK" || echo "MISSING .env.example"
+```
+
+---
+
+### 6. EasyPanel Configuration
+
+**What it checks:**
+- Services correctly defined for EasyPanel
+- Health check endpoints exist (`/health` or `/healthz`)
+- Port mappings match Dockerfile EXPOSE
+
+**How to check:**
+```bash
+# Verify health endpoint exists in code
+grep -rn "MapGet.*health" src/ --include="*.cs"
+```
+
+---
+
+## Example Output
+
+```
+MORPH Pre-Flight Check: Deployment
+
+  Packages: No version conflicts detected
+  Migrations: No pending changes
+  Dockerfile: Valid multi-stage build (API + Web)
+  Docker Compose: Valid configuration
+  Secrets: No hardcoded credentials found
+  EasyPanel: Health endpoint found at /healthz
+
+Summary: 6 passed, 0 failed, 0 warnings
+
+READY TO DEPLOY
+```
+
+---
+
+## Usage Workflow
+
+### Before creating PR for production
+
+```bash
+/morph-preflight
+```
+
+---
+
+*MORPH-SPEC by Polymorphism Tech*