PACC 1.0 Release - Critical Bug Fixes & Configuration Enhancement (completes PACC-38)

.claude/settings.json

@@ -1,15 +1,3 @@
 {
-  "hooks": [
-    {
-      "name": "pacc-celebration-hook",
-      "path": "hooks/pacc-celebration-hook.json",
-      "events": [
-        "*"
-      ],
-      "matchers": [
-        "*"
-      ]
-    }
-  ],
-  "mcps": []
+
 }

ai_docs/knowledge/claude-code-subagents-docs.md

@@ -1,4 +1,4 @@
-# Subagents
+# Subagents ([Source])(https://docs.anthropic.com/en/docs/claude-code/sub-agents.md)
 
 > Create and use specialized AI subagents in Claude Code for task-specific workflows and improved context management.
 
@@ -15,60 +15,6 @@ Subagents are pre-configured AI personalities that Claude Code can delegate task
 
 When Claude Code encounters a task that matches a subagent's expertise, it can delegate that task to the specialized subagent, which works independently and returns results.
 
-## Key benefits
-
-<CardGroup cols={2}>
-  <Card title="Context preservation" icon="layer-group">
-    Each subagent operates in its own context, preventing pollution of the main conversation and keeping it focused on high-level objectives.
-  </Card>
-
-  <Card title="Specialized expertise" icon="brain">
-    Subagents can be fine-tuned with detailed instructions for specific domains, leading to higher success rates on designated tasks.
-  </Card>
-
-  <Card title="Reusability" icon="rotate">
-    Once created, subagents can be used across different projects and shared with your team for consistent workflows.
-  </Card>
-
-  <Card title="Flexible permissions" icon="shield-check">
-    Each subagent can have different tool access levels, allowing you to limit powerful tools to specific subagent types.
-  </Card>
-</CardGroup>
-
-## Quick start
-
-To create your first subagent:
-
-<Steps>
-  <Step title="Open the subagents interface">
-    Run the following command:
-
-    ```
-    /agents
-    ```
-  </Step>
-
-  <Step title="Select 'Create New Agent'">
-    Choose whether to create a project-level or user-level subagent
-  </Step>
-
-  <Step title="Define the subagent">
-    * **Recommended**: Generate with Claude first, then customize to make it yours
-    * Describe your subagent in detail and when it should be used
-    * Select the tools you want to grant access to (or leave blank to inherit all tools)
-    * The interface shows all available tools, making selection easy
-    * If you're generating with Claude, you can also edit the system prompt in your own editor by pressing `e`
-  </Step>
-
-  <Step title="Save and use">
-    Your subagent is now available! Claude will use it automatically when appropriate, or you can invoke it explicitly:
-
-    ```
-    > Use the code-reviewer subagent to check my recent changes
-    ```
-  </Step>
-</Steps>
-
 ## Subagent configuration
 
 ### File locations

apps/pacc-cli/CHANGELOG.md

@@ -61,6 +61,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Updated documentation with plugin user guide
 - Restructured codebase to support plugin architecture
 
+### Fixed
+- CommandsValidator no longer incorrectly requires `name` field in frontmatter (PR #3)
+- CommandsValidator now correctly treats frontmatter as optional
+- AgentsValidator now expects `tools` as comma-separated string per Claude Code docs
+- AgentsValidator removed invalid optional fields not in Claude Code specification
+- Validators now properly warn about unknown fields instead of failing
+- `pacc info` now handles directories correctly like `pacc validate` does
+
 ### Security
 - Comprehensive validation before any file operations
 - Atomic configuration updates with rollback