@polymorphism-tech/morph-spec 4.16.0 → 4.18.0

package/framework/commands/morph-preflight.md

@@ -1,192 +1,200 @@
----
-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*
+---
+description: Validate project readiness before deploy — checks specs, contracts, tests, Docker, Neon/PostgreSQL, 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 + Neon/PostgreSQL.
+
+## 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. Database Migrations (Neon/PostgreSQL)
+
+**What it checks:**
+- Database is reachable
+- No pending migrations
+- RLS policies defined for all public tables
+- Database schema matches expected state
+
+**How to check:**
+```bash
+# Step 0: Verify database connectivity
+psql "$(neonctl connection-string)" -c "SELECT 1" 2>/dev/null && \
+  echo "✓ Database reachable" || \
+  echo "✗ Database unreachable — skip remaining migration checks"
+
+# Check for pending migrations (skip if connectivity failed)
+neonctl branches diff <branch>
+
+# Verify RLS is enabled on all tables
+psql "$(neonctl connection-string)" -c "SELECT tablename FROM pg_tables WHERE schemaname='public' AND tablename NOT IN (SELECT tablename FROM pg_policies)"
+```
+
+> **Important:** If the database connectivity check fails, skip all migration checks and warn the user. Do not block the preflight — the database may be intentionally scaled to zero.
+
+**Common fix:**
+```bash
+dotnet ef migrations add <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*

package/framework/hooks/claude-code/session-start/inject-morph-context.js

@@ -273,7 +273,7 @@ try {
     if (currentPhaseForCli) {
       const cliChecks = [
         { name: 'docker', cmd: 'docker --version', phases: ['design', 'implement'] },
-        { name: 'supabase', cmd: 'npx supabase --version', phases: ['design', 'implement'] },
+        { name: 'neonctl', cmd: 'neonctl --version', phases: ['design', 'implement'] },
         { name: 'psql', cmd: 'psql --version', phases: ['design', 'implement'] },
         { name: 'az', cmd: 'az version --output none', phases: ['implement'] },
         { name: 'gh', cmd: 'gh --version', phases: ['design', 'tasks', 'implement'] },

package/framework/rules/gsap-standards.md

@@ -0,0 +1,13 @@
+---
+paths:
+  - "**/*.tsx"
+  - "**/*.ts"
+stacks:
+  - nextjs
+---
+
+# GSAP Animation Standards
+
+@.morph/framework/standards/frontend/gsap/gsap-core.md
+@.morph/framework/standards/frontend/gsap/gsap-scrolltrigger.md
+@.morph/framework/standards/frontend/gsap/gsap-plugins.md

package/framework/rules/neon-auth-standards.md

@@ -0,0 +1,13 @@
+---
+paths:
+  - "**/Auth/**"
+  - "**/auth/**"
+  - "**/Identity/**"
+  - "**/neon-auth/**"
+stacks:
+  - neon
+---
+
+# Neon Auth Standards
+
+@.morph/framework/standards/backend/integrations/neon-auth/neon-auth.md

package/framework/rules/neon-standards.md

@@ -0,0 +1,26 @@
+---
+paths:
+  - "**/neon/**"
+  - "**/database/**"
+  - "**/*Migration*.sql"
+  - "**/*migration*.sql"
+stacks:
+  - neon
+---
+
+# Neon PostgreSQL Standards
+
+@.morph/framework/standards/infrastructure/neon/neon-setup.md
+@.morph/framework/standards/infrastructure/neon/neon-pgvector.md
+@.morph/framework/standards/infrastructure/neon/neon-pgrag.md
+@.morph/framework/standards/infrastructure/neon/neon-semantic-kernel.md
+@.morph/framework/standards/backend/integrations/neon-auth/neon-auth.md
+
+## SQL Templates
+
+| Template | Path | Purpose |
+|----------|------|---------|
+| PostgreSQL Migration | `.morph/framework/templates/code/sql/postgresql-migration.sql` | Database migration |
+| PostgreSQL RLS Policy | `.morph/framework/templates/code/sql/postgresql-rls-policy.sql` | Row-level security |
+
+Read the template and adapt to your project structure.

package/framework/skills/level-0-meta/mcp-registry.json

@@ -121,7 +121,7 @@
         },
         "credentials": [],
         "prerequisites": [],
-        "stackRelevance": ["nextjs", "nextjs-supabase", "vercel"],
+        "stackRelevance": ["nextjs", "nextjs-neon", "vercel"],
         "warnings": ["Uses OAuth — you will be prompted to authenticate via browser when first connecting."],
         "setupGuide": "Run: claude mcp add --transport http vercel https://mcp.vercel.com"
       }