refactor: remove Module 6, add resilience notes, update guides

- Delete module-6-marketplace-distribution (exercises 6.1 and 6.2)
- Merge marketplace creation into Capstone A (Step 6)
- Add resilience notes to exercises 3.1, 4.1, 7.1
- Fix ralph-wiggum → ralph-loop plugin name in exercise 7.1
- Update EXERCISE-GUIDE.md and README.md: 6 modules, 15 exercises

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: mjunaidca

EXERCISE-GUIDE.md

@@ -8,11 +8,11 @@ _By Panaversity -- Configure, Extend, Automate_
 
 ## How This Guide Works
 
-Every exercise in this guide teaches one layer of Claude Code's extensibility system -- from configuring settings through building and distributing plugins to running autonomous iteration loops. These aren't abstract concepts. They are working configurations you build, test, and debug on real scenarios.
+This guide contains 12 core exercises across 6 modules plus 3 capstone projects (15 total). Each exercise teaches one layer of Claude Code's extensibility system -- from configuring settings through building and distributing plugins to running autonomous iteration loops. These aren't abstract concepts. They are working configurations you build, test, and debug on real scenarios.
 
 **The exercise pattern:**
 
-Each module covers one extensibility layer with two exercises. Exercise X.1 is **Hands-on** -- you build or configure something real. Exercise X.2 is **Debug/Diagnose** -- you fix a broken configuration, audit a problematic setup, or analyze a failure.
+Each module covers one extensibility layer with two exercises. Exercise X.1 is **Hands-on** -- you build or configure something real. Exercise X.2 is **Debug/Diagnose** -- you fix a broken configuration, audit a problematic setup, or analyze a failure. Marketplace distribution is integrated into the Capstone A project rather than being a standalone module.
 
 **The three skills you'll develop:**
 
@@ -267,7 +267,7 @@ Packaging is just organization plus a manifest. The skills themselves don't chan
 
 ---
 
-### Exercise 5.2 -- Full Plugin Bundle
+### Exercise 5.2 -- Full Plugin Bundle (Advanced)
 
 **The Problem:**
 A complete "Team Productivity" plugin needs skills, hooks, and an MCP server configuration bundled together. This is the full plugin packaging exercise -- everything you've learned about skills, hooks, and plugins combined into one distributable package.
@@ -290,57 +290,6 @@ A complete "Team Productivity" plugin needs skills, hooks, and an MCP server con
 
 ---
 
-## Module 6: Marketplace Distribution
-
-> **Core Skill:** Create plugin marketplaces and distribute plugins to teams and the community.
-
-### Exercise 6.1 -- Create Marketplace
-
-**The Problem:**
-You have two plugins ready to share with your team, but they need a marketplace to discover and install them easily. You need to create a marketplace listing, organize the directory structure, and configure it as a marketplace source.
-
-**Your Task:**
-
-1. Create the marketplace directory structure
-2. Write a `marketplace.json` listing the two provided plugins
-3. Add the plugins to the marketplace directory
-4. Configure the marketplace as a source using `/plugin marketplace add`
-5. Verify plugins appear in the Discover tab
-
-**The Principle at Work:**
-A marketplace is just a catalog -- a `marketplace.json` file that points to plugin directories. The infrastructure is simple; the value is in organization and discoverability.
-
-**What You'll Learn:**
-
-- The `marketplace.json` format and required fields
-- How marketplace sources work (local, GitHub, GitLab)
-- The relationship between plugins and marketplaces (apps vs. app store)
-- How to test marketplace listings locally before publishing
-
----
-
-### Exercise 6.2 -- Cross-Marketplace
-
-**The Problem:**
-You're evaluating plugins from three different marketplace sources (official Anthropic, a community marketplace, and a company-internal marketplace). Each has plugins that partially overlap. You need to compare them and recommend the best plugin for a specific need.
-
-**Your Task:**
-
-1. Review the three marketplace listings provided
-2. Compare overlapping plugins across marketplaces
-3. Evaluate each based on: feature fit, maintenance quality, scope, and trust level
-4. Write a recommendation document with your analysis
-5. Create a "marketplace evaluation framework" for future decisions
-
-**What You'll Learn:**
-
-- How to evaluate plugin quality across different sources
-- Trust considerations: official vs. community vs. internal marketplaces
-- Feature overlap resolution: when two plugins solve the same problem
-- Documentation standards for plugin recommendations
-
----
-
 ## Module 7: Ralph Wiggum Loop
 
 > **Core Skill:** Design and execute autonomous iteration loops with proper completion promises, safety guardrails, and cost awareness.
@@ -401,23 +350,24 @@ An activity log from a Ralph Wiggum Loop that ran for 12 iterations without comp
 ### Capstone A -- Full Plugin from Scratch
 
 **The Problem:**
-Build a complete "Code Review" plugin that includes skills for review patterns, hooks for automated checks, and documentation for team adoption. Package it, test it, and create a marketplace entry.
+Build a complete "Code Review" plugin that includes skills for review patterns, hooks for automated checks, and documentation for team adoption. Package it, test it, create a marketplace entry, and distribute it.
 
 **Your Task:**
 
 1. Design the plugin: define skills, hooks, and configurations needed
 2. Create each component: skills for review checklists, hooks for pre-commit checks
 3. Write the plugin manifest (`plugin.json`)
-4. Create marketplace entry (`marketplace.json`)
-5. Test the complete plugin locally with `--plugin-dir`
-6. Write user documentation explaining how to install and use the plugin
+4. Test the complete plugin locally with `--plugin-dir`
+5. Write user documentation explaining how to install and use the plugin
+6. Create a marketplace listing and distribute the plugin
 
 **Deliverables:**
 
 - Working plugin directory with all components
 - Plugin manifest and marketplace listing
 - User documentation (README.md inside the plugin)
 - Test results showing all components work together
+- Marketplace entry with installation instructions
 
 **Estimated Time:** 2-4 hours
 
@@ -477,15 +427,14 @@ Audit your own Claude Code workflow and identify what's missing from your extens
 
 For each exercise, evaluate yourself on:
 
-| Criteria               |          Beginner (1)          |           Developing (2)            |                 Proficient (3)                 |                Advanced (4)                |
-| ---------------------- | :----------------------------: | :---------------------------------: | :--------------------------------------------: | :----------------------------------------: |
-| Settings Understanding |       Uses only defaults       |        Configured one level         |  Manages all 3 levels with correct precedence  | Designs team-wide configuration strategies |
-| Hook Implementation    |      Cannot create hooks       |   Basic hooks, no error handling    | Multi-event hooks with matchers and exit codes | Production hooks with logging and testing  |
-| Plugin Evaluation      |  Cannot navigate marketplace   |         Browses marketplace         |          Evaluates fit systematically          |  Creates evaluation frameworks for teams   |
-| Plugin Creation        |     Cannot create manifest     |     Basic manifest with skills      |          Full bundle with hooks + MCP          |   Production plugins with docs and tests   |
-| Marketplace Competence | Unaware of marketplace concept |      Uses official marketplace      |         Creates personal marketplaces          |     Multi-source marketplace strategy      |
-| Autonomous Iteration   |     Never used Ralph Loop      | Basic loop, poor completion promise |     Effective promises with safety limits      |     Complex loops with cost management     |
-| Integration Thinking   |    Components in isolation     |        Combines 2 components        |            Full extensibility stack            |    Team-wide extensibility architecture    |
+| Criteria               |        Beginner (1)         |           Developing (2)            |                 Proficient (3)                 |                           Advanced (4)                            |
+| ---------------------- | :-------------------------: | :---------------------------------: | :--------------------------------------------: | :---------------------------------------------------------------: |
+| Settings Understanding |     Uses only defaults      |        Configured one level         |  Manages all 3 levels with correct precedence  |            Designs team-wide configuration strategies             |
+| Hook Implementation    |     Cannot create hooks     |   Basic hooks, no error handling    | Multi-event hooks with matchers and exit codes |             Production hooks with logging and testing             |
+| Plugin Evaluation      | Cannot navigate marketplace |         Browses marketplace         |          Evaluates fit systematically          |              Creates evaluation frameworks for teams              |
+| Plugin Creation        |   Cannot create manifest    |     Basic manifest with skills      |          Full bundle with hooks + MCP          | Production plugins with docs, tests, and marketplace distribution |
+| Autonomous Iteration   |    Never used Ralph Loop    | Basic loop, poor completion promise |     Effective promises with safety limits      |                Complex loops with cost management                 |
+| Integration Thinking   |   Components in isolation   |        Combines 2 components        |            Full extensibility stack            |               Team-wide extensibility architecture                |
 
 ---
 

README.md

@@ -2,7 +2,7 @@
 
 **By Panaversity -- Master the Full Plugin Lifecycle**
 
-Welcome! This package contains 14 exercises + 3 capstone projects covering Claude Code's extensibility system -- from settings hierarchy and hooks through plugin creation, marketplace distribution, and autonomous iteration with Ralph Wiggum Loop. You'll configure real settings, write working hooks, build plugins from scratch, and run autonomous loops.
+Welcome! This package contains 12 exercises + 3 capstone projects (15 total) covering Claude Code's extensibility system -- from settings hierarchy and hooks through plugin creation and autonomous iteration with Ralph Wiggum Loop. You'll configure real settings, write working hooks, build plugins from scratch, distribute them via marketplaces (in Capstone A), and run autonomous loops.
 
 ---
 
@@ -26,15 +26,12 @@ plugins-exercises/
 |   +-- exercise-4.2-plugin-workflow-chain/          (chain plugins for a complete workflow)
 +-- module-5-plugin-packaging/
 |   +-- exercise-5.1-package-skills-plugin/         (package skills into a plugin)
-|   +-- exercise-5.2-full-plugin-bundle/            (build a complete plugin bundle)
-+-- module-6-marketplace-distribution/
-|   +-- exercise-6.1-create-marketplace/            (create a marketplace listing)
-|   +-- exercise-6.2-cross-marketplace/             (evaluate and compare marketplaces)
+|   +-- exercise-5.2-full-plugin-bundle/            (build a complete plugin bundle -- Advanced)
 +-- module-7-ralph-wiggum/
 |   +-- exercise-7.1-autonomous-loop/               (run your first Ralph Wiggum loop)
 |   +-- exercise-7.2-stuck-loop-debug/              (diagnose a stuck loop from logs)
 +-- module-8-capstones/
-    +-- capstone-A-full-plugin/                     (build a complete plugin from scratch)
+    +-- capstone-A-full-plugin/                     (build a complete plugin + marketplace distribution)
     +-- capstone-B-team-extensibility-kit/          (design extensibility for a team)
     +-- capstone-C-your-workflow/                   (audit and extend your own workflow)
 ```
@@ -67,9 +64,8 @@ plugins-exercises/
 **Week 3 (Plugin Discovery):** Exercises 3.1, 3.2
 **Week 4 (Plugin Usage):** Exercises 4.1, 4.2
 **Week 5 (Plugin Packaging):** Exercises 5.1, 5.2
-**Week 6 (Marketplace Distribution):** Exercises 6.1, 6.2
-**Week 7 (Ralph Wiggum Loop):** Exercises 7.1, 7.2
-**Week 8 (Capstone):** Choose one capstone project
+**Week 6 (Ralph Wiggum Loop):** Exercises 7.1, 7.2
+**Week 7 (Capstone):** Choose one capstone project
 
 ---
 
@@ -88,15 +84,14 @@ Use this for every exercise:
 
 ## Self-Assessment Rubric
 
-| Criteria               |         Beginner (1)         |         Developing (2)          |             Proficient (3)             |                  Advanced (4)                  |
-| ---------------------- | :--------------------------: | :-----------------------------: | :------------------------------------: | :--------------------------------------------: |
-| Settings Understanding |  Uses only default settings  |      Configured one level       |  Manages all 3 levels with precedence  |   Designs team-wide configuration strategies   |
-| Hook Design            |     Cannot create hooks      |    Basic single-event hooks     |    Multi-event hooks with matchers     |  Hook systems with error handling and logging  |
-| Plugin Usage           |    Cannot install plugins    | Installs and uses basic plugins |   Evaluates plugin fit for workflows   |      Chains plugins for complex workflows      |
-| Plugin Creation        |    Cannot create plugins     | Basic manifest with skills only |  Full plugin bundle with hooks + MCP   | Production-quality plugins with documentation  |
-| Marketplace Knowledge  |   Unaware of marketplaces    |    Uses official marketplace    |     Creates personal marketplaces      |   Manages multi-source marketplace strategy    |
-| Autonomous Iteration   |    Never used Ralph Loop     |   Basic loop with simple task   | Effective completion promises + safety | Complex multi-stage loops with cost management |
-| Integration Thinking   | Components used in isolation |      Combines 2 components      |  Full extensibility stack configured   |      Team-wide extensibility architecture      |
+| Criteria               |         Beginner (1)         |         Developing (2)          |             Proficient (3)             |                           Advanced (4)                            |
+| ---------------------- | :--------------------------: | :-----------------------------: | :------------------------------------: | :---------------------------------------------------------------: |
+| Settings Understanding |  Uses only default settings  |      Configured one level       |  Manages all 3 levels with precedence  |            Designs team-wide configuration strategies             |
+| Hook Design            |     Cannot create hooks      |    Basic single-event hooks     |    Multi-event hooks with matchers     |           Hook systems with error handling and logging            |
+| Plugin Usage           |    Cannot install plugins    | Installs and uses basic plugins |   Evaluates plugin fit for workflows   |               Chains plugins for complex workflows                |
+| Plugin Creation        |    Cannot create plugins     | Basic manifest with skills only |  Full plugin bundle with hooks + MCP   | Production plugins with docs, tests, and marketplace distribution |
+| Autonomous Iteration   |    Never used Ralph Loop     |   Basic loop with simple task   | Effective completion promises + safety |          Complex multi-stage loops with cost management           |
+| Integration Thinking   | Components used in isolation |      Combines 2 components      |  Full extensibility stack configured   |               Team-wide extensibility architecture                |
 
 ---
 

module-3-plugin-discovery/exercise-3.1-marketplace-explorer/INSTRUCTIONS.md

@@ -13,6 +13,8 @@ Learn to survey the Claude Code plugin marketplace and make informed decisions a
 
 ## Your Tasks
 
+> **Note**: The plugin marketplace evolves over time. If no plugin matches a workflow need, that's a valid finding — recommend "Build Custom" and describe what you'd create. The evaluation PROCESS matters more than finding a perfect match.
+
 ### Step 1: Review the Workflow Needs
 
 Read `workflow-needs.md` carefully. Each need describes a concrete workflow problem that might be solved by an existing plugin.

module-4-plugin-usage/exercise-4.1-install-and-use/INSTRUCTIONS.md

@@ -12,6 +12,8 @@ Install a plugin from the official marketplace and use it on a real project. Exp
 
 ## Your Tasks
 
+> **Prerequisites check**: Run `npm --version` to verify Node.js is installed. If installing an LSP plugin, ensure the language server binary is available (e.g., `typescript-language-server --version`). If LSP installation fails, complete the exercise using only `commit-commands` — the core learning is the install-configure-verify cycle, not the specific plugin.
+
 ### Step 1: Install the commit-commands Plugin
 
 Install from the official marketplace: