feat: PACT v3.0 Agent Teams migration

.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "PACT",
       "source": "./pact-plugin",
       "description": "PACT Framework - VSM-enhanced orchestration with specialist agents and viability sensing",
-      "version": "2.8.0",
+      "version": "3.0.0",
       "author": {
         "name": "ProfSynapse"
       },

pact-plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "PACT",
-  "version": "2.8.0",
+  "version": "3.0.0",
   "description": "PACT Framework - Prepare, Architect, Code, Test methodology with VSM-enhanced orchestration, specialist agents, and viability sensing for systematic AI-assisted development",
   "author": {
     "name": "ProfSynapse",

pact-plugin/agents/pact-architect.md

@@ -160,7 +160,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **BEFORE COMPLETING**
 
-Before returning your final output to the orchestrator:
+Before returning your final output to your assigner:
 
 1. **Save Memory**: Invoke the `pact-memory` skill and save a memory documenting:
    - Context: What you were designing and why
@@ -173,7 +173,7 @@ This ensures your design context persists across sessions and is searchable by f
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes

pact-plugin/agents/pact-backend-coder.md

@@ -108,7 +108,7 @@ Your work isn't done until smoke tests pass. Smoke tests verify: "Does it compil
 
 **HANDOFF**
 
-End with a structured handoff for the orchestrator:
+End with a structured handoff for your assigner:
 1. **Produced**: Files created/modified
 2. **Key decisions**: Decisions with rationale, assumptions that could be wrong
 3. **Areas of uncertainty** (PRIORITIZED):
@@ -148,7 +148,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **BEFORE COMPLETING**
 
-Before returning your final output to the orchestrator:
+Before returning your final output to your assigner:
 
 1. **Save Memory**: Invoke the `pact-memory` skill and save a memory documenting:
    - Context: What you were working on and why
@@ -161,7 +161,7 @@ This ensures your work context persists across sessions and is searchable by fut
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes

pact-plugin/agents/pact-database-engineer.md

@@ -126,7 +126,7 @@ Your work isn't done until smoke tests pass. Smoke tests verify: "Does the schem
 
 **HANDOFF**
 
-End with a structured handoff for the orchestrator:
+End with a structured handoff for your assigner:
 1. **Produced**: Files created/modified (schemas, migrations, queries)
 2. **Key decisions**: Decisions with rationale (normalization, indexes), assumptions that could be wrong
 3. **Areas of uncertainty** (PRIORITIZED):
@@ -166,7 +166,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **BEFORE COMPLETING**
 
-Before returning your final output to the orchestrator:
+Before returning your final output to your assigner:
 
 1. **Save Memory**: Invoke the `pact-memory` skill and save a memory documenting:
    - Context: What you were working on and why
@@ -179,7 +179,7 @@ This ensures your work context persists across sessions and is searchable by fut
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes

pact-plugin/agents/pact-frontend-coder.md

@@ -99,7 +99,7 @@ Your work isn't done until smoke tests pass. Smoke tests verify: "Does it compil
 
 **HANDOFF**
 
-End with a structured handoff for the orchestrator:
+End with a structured handoff for your assigner:
 1. **Produced**: Files created/modified
 2. **Key decisions**: Decisions with rationale, assumptions that could be wrong
 3. **Areas of uncertainty** (PRIORITIZED):
@@ -139,7 +139,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **BEFORE COMPLETING**
 
-Before returning your final output to the orchestrator:
+Before returning your final output to your assigner:
 
 1. **Save Memory**: Invoke the `pact-memory` skill and save a memory documenting:
    - Context: What you were working on and why
@@ -152,7 +152,7 @@ This ensures your work context persists across sessions and is searchable by fut
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes

pact-plugin/agents/pact-memory-agent.md

@@ -154,7 +154,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes

pact-plugin/agents/pact-n8n.md

@@ -130,7 +130,7 @@ Provide:
 
 **HANDOFF**
 
-End with a structured handoff for the orchestrator:
+End with a structured handoff for your assigner:
 1. **Produced**: Workflow created, key node configurations
 2. **Key decisions**: Pattern selection rationale with assumptions that could be wrong
 3. **Areas of uncertainty** (PRIORITIZED):
@@ -170,7 +170,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **BEFORE COMPLETING**
 
-Before returning your final output to the orchestrator:
+Before returning your final output to your assigner:
 
 1. **Save Memory**: Invoke the `pact-memory` skill and save a memory documenting:
    - Context: What workflow you were building and why
@@ -194,7 +194,7 @@ Templates provide battle-tested starting points that you can customize.
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes

pact-plugin/agents/pact-preparer.md

@@ -129,7 +129,7 @@ When evaluating multiple options:
 
 Remember: Your research forms the foundation for the entire project. Be thorough, accurate, and practical. When uncertain about conflicting information, present multiple viewpoints with clear source attribution. Your goal is to empower the Architect and subsequent phases with comprehensive, reliable information with a comprehensive markdown file. Save to the `docs/preparation` folder.
 
-MANDATORY: Pass back to the Orchestrator upon completion of your markdown files.
+MANDATORY: Pass back to your assigner upon completion of your markdown files.
 
 **AUTONOMY CHARTER**
 
@@ -161,7 +161,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **BEFORE COMPLETING**
 
-Before returning your final output to the orchestrator:
+Before returning your final output to your assigner:
 
 1. **Save Memory**: Invoke the `pact-memory` skill and save a memory documenting:
    - Context: What you were researching and why
@@ -174,7 +174,7 @@ This ensures your research context persists across sessions and is searchable by
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes

pact-plugin/agents/pact-test-engineer.md

@@ -184,7 +184,7 @@ When coders flag areas of uncertainty in their handoff:
 
 ### Signal Output System
 
-Report your findings to the orchestrator using this signal format:
+Report your findings to your assigner using this signal format:
 
 ```
 Risk Tier: {CRITICAL|HIGH|STANDARD|LIGHT}
@@ -229,7 +229,7 @@ The orchestrator passes CODE phase handoff summaries. Use these for context:
 
 **HANDOFF**
 
-End with a structured handoff for the orchestrator:
+End with a structured handoff for your assigner:
 1. **Produced**: Test files created, coverage achieved
 2. **Key decisions**: Testing approach with rationale, assumptions that could be wrong
 3. **Areas of uncertainty** (PRIORITIZED):
@@ -270,7 +270,7 @@ See [algedonic.md](../protocols/algedonic.md) for signal format and full trigger
 
 **BEFORE COMPLETING**
 
-Before returning your final output to the orchestrator:
+Before returning your final output to your assigner:
 
 1. **Save Memory**: Invoke the `pact-memory` skill and save a memory documenting:
    - Context: What you were testing and why
@@ -283,7 +283,7 @@ This ensures your testing context persists across sessions and is searchable by
 
 **HOW TO HANDLE BLOCKERS**
 
-If you run into a blocker, STOP what you're doing and report the blocker to the orchestrator, so they can take over and invoke `/PACT:imPACT`.
+If you run into a blocker, STOP what you're doing and report the blocker to your assigner, so they can take over and invoke `/PACT:imPACT`.
 
 Examples of blockers:
 - Same error after multiple fixes