@polymorphism-tech/morph-spec 4.3.2 → 4.3.4

package/stacks/nextjs-supabase/.morph/standards/observability/tracing.md

@@ -1,132 +0,0 @@
-# Observability Standard: Distributed Tracing
-
-## Overview
-OpenTelemetry distributed tracing for cross-service correlation and performance analysis.
-
-## OpenTelemetry Setup
-
-### Packages
-```xml
-<PackageReference Include="OpenTelemetry.Extensions.Hosting" Version="1.*" />
-<PackageReference Include="OpenTelemetry.Instrumentation.AspNetCore" Version="1.*" />
-<PackageReference Include="OpenTelemetry.Instrumentation.Http" Version="1.*" />
-<PackageReference Include="OpenTelemetry.Instrumentation.SqlClient" Version="1.*" />
-<PackageReference Include="Azure.Monitor.OpenTelemetry.AspNetCore" Version="1.*" />
-```
-
-### Program.cs Configuration
-```csharp
-builder.Services.AddOpenTelemetry()
-    .WithTracing(tracing =>
-    {
-        tracing
-            .AddAspNetCoreInstrumentation(opts =>
-            {
-                opts.RecordException = true;
-                opts.Filter = ctx => !ctx.Request.Path.StartsWithSegments("/health");
-            })
-            .AddHttpClientInstrumentation()
-            .AddSqlClientInstrumentation(opts => opts.SetDbStatementForText = true)
-            .AddSource(ActivitySource.Name) // Custom activities
-            .AddAzureMonitorTraceExporter(opts =>
-            {
-                opts.ConnectionString = config["ApplicationInsights:ConnectionString"];
-            });
-    });
-
-// Custom ActivitySource for domain operations
-public static class Telemetry
-{
-    public static readonly ActivitySource ActivitySource = new("MyApp", "1.0.0");
-}
-```
-
-## Custom Span Creation
-
-### Service Method Tracing
-```csharp
-public async Task<Order> ProcessOrderAsync(CreateOrderCommand command)
-{
-    using var activity = Telemetry.ActivitySource.StartActivity("ProcessOrder");
-    activity?.SetTag("order.userId", command.UserId.ToString());
-    activity?.SetTag("order.itemCount", command.Items.Count.ToString());
-
-    try
-    {
-        var order = await _repository.CreateAsync(command);
-        activity?.SetTag("order.id", order.Id.ToString());
-        activity?.SetStatus(ActivityStatusCode.Ok);
-        return order;
-    }
-    catch (Exception ex)
-    {
-        activity?.SetStatus(ActivityStatusCode.Error, ex.Message);
-        activity?.RecordException(ex);
-        throw;
-    }
-}
-```
-
-### Baggage (Cross-Service Context)
-```csharp
-// Set correlation ID in baggage (propagates across HTTP calls)
-Activity.Current?.SetBaggage("correlationId", correlationId);
-Activity.Current?.SetBaggage("userId", userId.ToString());
-
-// Read baggage downstream
-var correlationId = Activity.Current?.GetBaggageItem("correlationId");
-```
-
-## Trace Context Propagation
-
-### HTTP Client (auto-propagated)
-```csharp
-// HttpClient automatically propagates W3C trace context
-// Configure in DI:
-builder.Services.AddHttpClient("ExternalApi")
-    .AddOpenTelemetryInstrumentation();
-```
-
-### Service Bus (manual propagation)
-```csharp
-// Sender: inject trace context into message properties
-var message = new ServiceBusMessage(body);
-var activity = Activity.Current;
-if (activity != null)
-{
-    message.ApplicationProperties["traceparent"] = activity.Id;
-    message.ApplicationProperties["tracestate"] = activity.TraceStateString;
-}
-
-// Receiver: restore trace context from message
-if (message.ApplicationProperties.TryGetValue("traceparent", out var traceparent))
-{
-    using var linkedActivity = Telemetry.ActivitySource.StartActivity(
-        "ProcessMessage",
-        ActivityKind.Consumer,
-        parentId: traceparent.ToString()!);
-    await ProcessAsync(message);
-}
-```
-
-## Trace Sampling Strategy
-
-| Environment | Strategy | Rate |
-|-------------|----------|------|
-| Development | Always | 100% |
-| Staging | Adaptive | 10% + errors |
-| Production | Adaptive | 5% + errors |
-
-```csharp
-// Production adaptive sampling (errors always sampled)
-.AddAspNetCoreInstrumentation(opts =>
-{
-    opts.Enrich = (activity, eventName, obj) =>
-    {
-        if (obj is HttpResponse response && response.StatusCode >= 400)
-        {
-            activity.SetSampled(true); // Always sample errors
-        }
-    };
-})
-```

package/stacks/nextjs-supabase/.morph/standards/workflows/parallel-execution.md

@@ -1,112 +0,0 @@
-# Workflow Standard: Parallel Execution
-
-## When to Use Parallel Execution
-
-| Condition | Decision |
-|-----------|----------|
-| 5+ independent tasks | Use P-Threads |
-| Multi-domain (backend + frontend + infra) | Use P-Threads with squad templates |
-| 15+ files to create | Use P-Threads |
-| Tasks have zero dependency overlap | Use P-Threads |
-| Tasks share file scope | Do NOT parallelize |
-| Sequential data flow required | Do NOT parallelize |
-
-## Parallelization Planning
-
-### Step 1: Dependency Analysis
-```bash
-morph-spec detect-workflow user-auth
-
-# Identifies: parallelizable tasks, sequential chains, waves
-```
-
-### Step 2: File Scope Assignment
-Assign exclusive file ownership to each parallel worker:
-
-```
-Worker A (Backend):    Entities/, Services/, Controllers/, DTOs/
-Worker B (Frontend):   Pages/, Components/, CSS/
-Worker C (Infra):      infra/bicep/, .github/workflows/
-```
-
-No overlap allowed. If overlap is unavoidable, make it sequential.
-
-### Step 3: Choose Squad Template
-```bash
-morph-spec squad-template use full-stack --feature=user-auth
-
-# Creates execution plan based on full-stack.json template:
-# - dotnet-senior (backend lead)
-# - blazor-builder (frontend lead)
-# - bicep-architect (infra lead)
-# - thread-orchestrator (coordinator)
-```
-
-## Execution Flow
-
-```
-Orchestrator
-    │
-    ├── spawn parallel: Worker A (files: Entities/, Services/)
-    ├── spawn parallel: Worker B (files: Pages/, Components/)
-    └── spawn parallel: Worker C (files: infra/)
-    │
-    │   [Workers execute concurrently — no interaction]
-    │
-    ├── wait-all (poll or explicit sync)
-    │
-    ├── merge results (check for conflicts)
-    ├── run integration validation
-    └── report consolidated output
-```
-
-## Conflict Resolution
-
-### File Conflicts (two workers wrote same file)
-```bash
-# This should NOT happen if scopes are properly defined
-# If it does:
-morph-spec agents review aggregate user-auth \
-  --agents=dotnet-senior,blazor-builder \
-  --strategy=best-of-n
-```
-
-### Interface Mismatches (A expects contract B didn't fulfill)
-- Document the mismatch in the coordinator report
-- Fix in post-merge sequential step
-- Update contracts.cs to reflect actual implementation
-
-## Fusion vs Parallel
-
-| Aspect | Parallel (P-Thread) | Fusion (F-Thread) |
-|--------|--------------------|--------------------|
-| Goal | Divide scope | Compete on same scope |
-| Output | Different files | Same files, best one wins |
-| Workers collaborate? | No | No |
-| Merge | Combine all files | Select best implementation |
-| Use case | Large features | Design decisions, quality optimization |
-
-## Configuration
-```json
-// llm-interaction.json
-{
-  "parallelExecution": {
-    "enabled": true,
-    "maxConcurrent": 3,
-    "defaultStrategy": "best-of-n"
-  }
-}
-```
-
-## Squad Templates
-
-Pre-defined squad configurations in `framework/squad-templates/`:
-- `full-stack.json` — Backend + Frontend + Infra (6 agents)
-- `backend-only.json` — Backend specialists only (4 agents)
-- `frontend-only.json` — Frontend specialists only (3 agents)
-
-```bash
-morph-spec squad-template list
-morph-spec squad-template show full-stack
-morph-spec squad-template use full-stack --feature=user-auth
-```

package/stacks/nextjs-supabase/.morph/standards/workflows/thread-management.md

@@ -1,113 +0,0 @@
-# Workflow Standard: Thread Management
-
-## Thread Types
-
-| Type | Code | Purpose | Lifecycle |
-|------|------|---------|-----------|
-| Base | B-Thread | Default implementation thread | Bounded by feature phase |
-| Parallel | P-Thread | Concurrent isolated execution | Short (1 task scope) |
-| Fusion | F-Thread | Best-of-N competing implementations | Short (1 prompt scope) |
-| Long-Running | L-Thread | Multi-session persistent work | Days/weeks |
-| Zero-Touch | Z-Thread | Fully autonomous execution | Bounded by trust level |
-
-## Thread Lifecycle
-
-```
-pending → running → completed
-                  → failed → (retry) → running
-                           → killed
-```
-
-## Creating Threads
-```bash
-# Create a base thread (default)
-morph-spec threads status morph-next-gen
-
-# Create parallel threads for feature
-morph-spec spawn-team morph-next-gen --parallel backend,frontend,infra
-
-# Create fusion thread
-morph-spec agents fuse \
-  --prompt "Implement caching strategy for UserService" \
-  --count=3 \
-  --strategy=best-of-n \
-  --feature=morph-next-gen
-```
-
-## Thread State in state.json
-```json
-{
-  "threads": {
-    "thread-abc12345": {
-      "id": "thread-abc12345",
-      "type": "parallel",
-      "agent": "dotnet-senior",
-      "feature": "user-auth",
-      "status": "running",
-      "startedAt": "2026-02-19T00:00:00Z",
-      "events": [
-        { "type": "started", "timestamp": "..." },
-        { "type": "checkpoint_passed", "timestamp": "...", "checkpointNum": 1 }
-      ],
-      "metrics": {
-        "tasksCompleted": 3,
-        "checkpointsPassed": 1,
-        "errors": 0
-      }
-    }
-  }
-}
-```
-
-## Parallel Execution Rules (P-Threads)
-
-1. **File scope isolation**: Each P-Thread has exclusive write access to its files
-2. **No cross-thread dependencies**: P-Thread tasks are self-contained
-3. **Shared read access**: All P-Threads can read spec.md, standards, contracts
-4. **Merge on completion**: Coordinator merges results after all P-Threads complete
-5. **Max concurrent**: Default 3, max 5 (configurable in llm-interaction.json)
-
-## Dependency Analysis
-```bash
-# Analyze task dependencies for parallel opportunities
-morph-spec detect-workflow morph-next-gen
-
-# Output:
-# Parallelizable tasks: T001, T002, T003 (no dependencies)
-# Sequential: T004 (depends on T001), T005 (depends on T002)
-# Execution plan:
-#   Wave 1: [T001, T002, T003] (parallel)
-#   Wave 2: [T004, T005] (parallel, after wave 1)
-#   Wave 3: [T006] (sequential)
-```
-
-## Long-Running Threads (L-Threads)
-
-### Stop Hooks
-L-Threads run periodic stop hooks every 30 minutes:
-```json
-// llm-interaction.json
-{
-  "stopHooks": {
-    "enabled": true,
-    "interval": 30,
-    "maxRetries": 5,
-    "hooks": ["validate-and-continue", "validate-checkpoints"]
-  }
-}
-```
-
-### Resume Pattern
-```bash
-# Resume L-Thread from bundle
-morph-spec bundle load morph-next-gen
-# Load resume context, continue from checkpoint
-```
-
-## Monitoring
-```bash
-morph-spec threads list morph-next-gen
-morph-spec threads analytics morph-next-gen
-morph-spec threads wait-all morph-next-gen
-morph-spec threads wait-any morph-next-gen
-```

package/stacks/nextjs-supabase/CLAUDE.md

@@ -1,155 +0,0 @@
-# MORPH-SPEC - Claude Code Instructions
-
-> by Polymorphism Tech
-
-Spec-driven development system. Specialized agent hub for multi-stack projects with Infrastructure as Code.
-
----
-
-## CRITICAL RULES
-
-### NEVER:
-- Skip to code without a specification
-- Implement without design approval
-- Ignore standards in `.morph/standards/`
-- Create infrastructure manually
-- Generate code without defined contracts
-
-### ALWAYS:
-- Follow the 5 mandatory phases
-- Generate outputs in `.morph/project/outputs/{feature}/`
-- Document decisions in `decisions.md`
-- Checkpoint every 3 implemented tasks
-- Use Infrastructure as Code
-
----
-
-## WORKFLOW (5 Phases)
-
-| Phase | Trigger | Actions | Output | Pause? |
-|-------|---------|---------|--------|--------|
-| **1. SETUP** | Feature request | Read project context, identify stack, activate agents, create folder | proposal.md | No |
-| **2. DESIGN** | Setup done | Spec + contracts + decisions + costs | spec.md, contracts, decisions.md | **Yes** |
-| **3. CLARIFY** | Design approved | Ambiguities, questions, edge cases | Updated spec | No |
-| **4. TASKS** | Clarifications resolved | Break into tasks, ordering, checkpoints, dependencies | tasks.md | **Yes** |
-| **5. IMPLEMENT** | Tasks approved | Task by task, checkpoint every 3, recap | Code + recap.md | No |
-
----
-
-## PROJECT STRUCTURE
-
-```
-project/
-├── CLAUDE.md
-├── .morph/
-│   ├── config/                     # config.json, agents.json
-│   ├── standards/                  # coding, architecture, stack-specific
-│   ├── templates/                  # Output templates
-│   ├── project/
-│   │   ├── context/                # detection-log.md, project.md
-│   │   ├── standards/              # inferred.md, overrides.md
-│   │   └── outputs/{feature}/     # Features in development
-│   │       ├── proposal.md, spec.md, tasks.md
-│   │       ├── contracts, decisions.md, recap.md
-└── .claude/commands/               # Slash commands
-```
-
----
-
-## AGENTS
-
-### Tier 1 — Orchestrators (Always Active)
-
-| Agent | Responsibilities |
-|-------|-----------------|
-| **Standards Architect** | Standards, naming, review, cross-cutting concerns |
-| **AI System Architect** | Agent systems, AI integrations, LLM orchestration |
-| **Thread Orchestrator** | Parallel execution, thread management, context optimization |
-
-### Tier 2 — Domain Leaders
-
-| Agent | Responsibilities |
-|-------|-----------------|
-| **Tech Lead** | Architecture decisions, code quality, task breakdown |
-| **DevOps Engineer** | CI/CD, deployment pipelines, infrastructure |
-| **QA Lead** | Test strategies, validation, quality gates |
-
-### Tier 3 — Specialists (Activated by keywords)
-
-| Agent | Keywords |
-|-------|---------|
-| **Next.js Expert** | nextjs, react, frontend, app router, pages |
-| **Blazor Builder** | blazor, razor, mudblazor, fluent ui |
-| **API Designer** | api, endpoint, rest, openapi, swagger |
-| **.NET Senior** | dotnet, csharp, minimal api, ef core |
-| **EF Modeler** | entity framework, migrations, dbcontext |
-| **Azure Architect** | azure, container apps, bicep, app service |
-| **Bicep Architect** | bicep, iac, arm template, azure resources |
-| **Azure Deploy Specialist** | deploy, ci/cd, github actions, azure devops |
-| **Container Specialist** | docker, dockerfile, compose, kubernetes |
-| **Supabase Expert** | supabase, postgresql, rls, realtime, pgvector |
-| **Azure Identity** | auth, authentication, entra id, jwt, oauth |
-| **Clerk Auth** | clerk, auth0, authentication, social login |
-| **Asaas Financial** | payment, billing, subscription, asaas |
-| **Resend Email** | email, resend, smtp, notifications |
-| **Hangfire Orchestrator** | background jobs, queue, scheduling, hangfire |
-| **MS Agent Expert** | semantic kernel, microsoft agents, ai pipeline |
-| **UI/UX Designer** | design, ux, wireframe, mockup, figma |
-| **SEO Growth Hacker** | seo, performance, analytics, lighthouse |
-| **PO/PM Advisor** | product, roadmap, requirements, user stories |
-| **Prompt Engineer** | prompts, system prompts, llm, few-shot |
-| **Context Optimizer** | context window, token optimization, chunking |
-| **Vector Search Expert** | vector db, embeddings, semantic search, rag |
-| **Observability Expert** | logging, tracing, metrics, opentelemetry |
-| **Code Analyzer** | refactor, analysis, code review, complexity |
-| **Testing Specialist** | tests, coverage, tdd, bdd, vitest, jest, xunit |
-
-### Tier 4 — Validators
-
-| Agent | Responsibilities |
-|-------|-----------------|
-| **Contract Compliance Validator** | Ensures implementation matches spec contracts |
-
----
-
-## TEMPLATES
-
-> ALWAYS use `morph-spec template render` to render. NEVER fill placeholders manually.
-
-### Placeholders: `{{PLACEHOLDER}}`
-
-| Placeholder | Example |
-|-------------|---------|
-| `{{FEATURE_NAME}}` | `scheduled-reports` |
-| `{{FEATURE_NAME_PASCAL}}` | `ScheduledReports` |
-| `{{FEATURE_NAME_CAMEL}}` | `scheduledReports` |
-| `{{STACK}}` | `blazor-azure` or `nextjs-supabase` |
-| `{{DATE}}`, `{{AUTHOR}}`, `{{NAMESPACE}}` | Auto from config.json |
-
----
-
-## COMMANDS
-
-| Command | Action |
-|---------|--------|
-| `/morph-proposal {feature}` | Full spec pipeline (phases 1-4, auto-continuation with pauses) |
-| `/morph-apply {feature}` | Implement feature (phase 5) |
-| `/morph-status` | Dashboard |
-| `/morph-archive {feature}` | Archive completed feature |
-| `/morph-infra {action}` | Manage infrastructure |
-| `/morph-preflight` | Pre-deploy validation |
-| `/morph-troubleshoot {error}` | Error troubleshooting |
-
----
-
-## REFERENCES
-
-- `.morph/config/config.json` — Project configuration
-- `.morph/config/agents.json` — Full agent definitions
-- `.morph/standards/` — Coding, architecture, stack-specific standards
-- `.morph/project/context/` — Detection log, project context
-- `.morph/project/standards/inferred.md` — Auto-detected project standards
-
----
-
-*MORPH-SPEC v4.3.0 by Polymorphism Tech*

package/stacks/nextjs-supabase/README.md

@@ -1,103 +0,0 @@
-# Stack: Next.js + Supabase
-
-> MORPH-SPEC stack for .NET 10 Minimal API + Next.js 15 + Supabase Cloud + EasyPanel (VPS)
-
-## When to Use This Stack
-
-| Criteria | This Stack | Blazor+Azure Stack |
-|----------|------------|-------------------|
-| Frontend | React/Next.js (SSR + CSR) | Blazor Server (C# only) |
-| Database | Supabase Cloud (PostgreSQL) | Azure SQL |
-| Auth | Supabase Auth (built-in) | Azure Identity / Clerk |
-| Deploy | VPS + EasyPanel (Docker) | Azure Container Apps |
-| Cost (dev) | ~$6/month | ~$15/month |
-| Cost (prod) | ~$31/month | ~$50+/month |
-| Best for | MVPs, SaaS, AI apps (pgvector) | Enterprise, full-.NET teams |
-| Realtime | Supabase Realtime (PostgreSQL) | SignalR |
-| Vector search | pgvector (native) | Azure AI Search |
-
-## Architecture
-
-```
-Browser
-  |
-  v
-Next.js 15 (App Router)          Supabase Cloud
-  |-- Server Components --------> Auth (JWT validation)
-  |-- Client Components --------> PostgREST (direct queries via RLS)
-  |-- Route Handlers (BFF) -----> .NET 10 API --> PostgreSQL + pgvector
-  |                                              Storage
-  v                                              Realtime
-EasyPanel (VPS)
-  |-- Next.js Container (:3000)
-  |-- .NET API Container (:8080)
-  |-- Nginx reverse proxy (:443)
-```
-
-## Quick Start
-
-### 1. Copy stack to your project
-
-```bash
-cp -r stacks/nextjs-supabase/.morph/ your-project/.morph/
-cp -r stacks/nextjs-supabase/.claude/ your-project/.claude/
-cp stacks/nextjs-supabase/CLAUDE.md your-project/CLAUDE.md
-```
-
-### 2. Configure
-
-Edit `.morph/project.md` with your project details.
-
-### 3. Start developing
-
-```bash
-/morph-proposal my-feature
-```
-
-## Directory Structure
-
-```
-stacks/nextjs-supabase/
-├── CLAUDE.md                           # Stack-specific Claude instructions
-├── README.md                           # This file
-├── .morph/
-│   ├── project.md                      # Project template
-│   └── config/
-│       └── agents.json                 # 12 agents configured
-│   # Note: All standards moved to framework/standards/ (universal knowledge)
-│   ├── templates/                      # 11 templates
-│   └── examples/                       # 2 reference examples
-│       ├── crud-nextjs-supabase/
-│       └── saas-nextjs-supabase/
-└── .claude/
-    └── skills/                         # 4 agent skills
-        └── level-2-domains/
-            ├── integrations/supabase-expert.md
-            ├── infrastructure/easypanel-deployer.md
-            ├── backend/dotnet-supabase.md
-            └── frontend/nextjs-supabase.md
-```
-
-## Key Differences from Blazor+Azure
-
-| Aspect | Blazor+Azure | Next.js+Supabase |
-|--------|-------------|-----------------|
-| IaC | Bicep templates | Dockerfiles + Docker Compose |
-| ORM | EF Core (LINQ) | Npgsql + Dapper (SQL) |
-| Migrations | C# EF Migrations | SQL (Supabase CLI) |
-| Auth middleware | Azure Identity | @supabase/ssr + JWT |
-| RLS | Application-level | Database-level (PostgreSQL RLS) |
-| File storage | Azure Blob Storage | Supabase Storage |
-| Deploy | Azure Container Apps | EasyPanel (VPS Docker) |
-
-## Shared with Blazor+Azure
-
-- MORPH-SPEC 5-phase workflow (Setup > Design > Clarify > Tasks > Implement)
-- Framework standards: coding.md, architecture.md
-- CLI commands: /morph-proposal, /morph-apply, /morph-status
-- Validation pipeline and checkpoint system
-- .NET 10 backend patterns (C# 14, sealed records, CancellationToken)
-
----
-
-*MORPH-SPEC by Polymorphism Tech*