aios-core 2.2.2 → 3.0.0

package/.aios-core/development/tasks/github-devops-github-pr-automation.md

@@ -262,22 +262,209 @@ function extractStoryInfo(storyPath) {
 }
 ```
 
-### Step 4: Generate PR Title
+### Step 4: Generate PR Title (Configurable Format)
+
+> **Configuration-Driven:** PR title format is controlled by `core-config.yaml` → `github.pr.title_format`
+> This allows each project to choose the format that matches their workflow.
 
 ```javascript
+const yaml = require('js-yaml');
+const fs = require('fs');
+const path = require('path');
+
+/**
+ * Load PR configuration from core-config.yaml
+ * @returns {Object} PR configuration with defaults
+ */
+function loadPRConfig() {
+  const configPath = path.join(process.cwd(), '.aios-core', 'core-config.yaml');
+
+  // Default configuration (for projects without core-config)
+  const defaults = {
+    title_format: 'story-first',  // Safe default for most projects
+    include_story_id: true,
+    conventional_commits: {
+      enabled: false,
+      branch_type_map: {
+        'feature/': 'feat',
+        'feat/': 'feat',
+        'fix/': 'fix',
+        'bugfix/': 'fix',
+        'hotfix/': 'fix',
+        'docs/': 'docs',
+        'chore/': 'chore',
+        'refactor/': 'refactor',
+        'test/': 'test',
+        'perf/': 'perf',
+        'ci/': 'ci',
+        'style/': 'style',
+        'build/': 'build'
+      },
+      default_type: 'feat'
+    }
+  };
+
+  try {
+    if (fs.existsSync(configPath)) {
+      const config = yaml.load(fs.readFileSync(configPath, 'utf8'));
+      return { ...defaults, ...config?.github?.pr };
+    }
+  } catch (error) {
+    console.warn('Could not load core-config.yaml, using defaults');
+  }
+
+  return defaults;
+}
+
+/**
+ * Generate PR title based on project configuration.
+ *
+ * Supported formats (configured in core-config.yaml → github.pr.title_format):
+ *
+ * 1. "conventional" - Conventional Commits format (for semantic-release)
+ *    Example: "feat(auth): implement OAuth login [Story 6.17]"
+ *
+ * 2. "story-first" - Story ID first (legacy/simple projects)
+ *    Example: "[Story 6.17] Implement OAuth Login"
+ *
+ * 3. "branch-based" - Branch name converted to title
+ *    Example: "Feature User Auth"
+ *
+ * @param {string} branchName - Current git branch name
+ * @param {Object} storyInfo - Story information (id, title)
+ * @returns {string} Formatted PR title
+ */
 function generatePRTitle(branchName, storyInfo) {
+  const config = loadPRConfig();
+  const format = config.title_format || 'story-first';
+
+  switch (format) {
+    case 'conventional':
+      return generateConventionalTitle(branchName, storyInfo, config);
+    case 'story-first':
+      return generateStoryFirstTitle(branchName, storyInfo, config);
+    case 'branch-based':
+      return generateBranchBasedTitle(branchName, storyInfo, config);
+    default:
+      return generateStoryFirstTitle(branchName, storyInfo, config);
+  }
+}
+
+/**
+ * Format: {type}({scope}): {description} [Story {id}]
+ * Used for: Projects with semantic-release automation
+ */
+function generateConventionalTitle(branchName, storyInfo, config) {
+  const typeMap = config.conventional_commits?.branch_type_map || {};
+  const defaultType = config.conventional_commits?.default_type || 'feat';
+
+  // Detect commit type from branch prefix
+  let type = defaultType;
+  for (const [prefix, commitType] of Object.entries(typeMap)) {
+    if (branchName.startsWith(prefix)) {
+      type = commitType;
+      break;
+    }
+  }
+
+  // Extract scope from branch name (e.g., feat/auth/login -> scope=auth)
+  const scopeMatch = branchName.match(/^[a-z-]+\/([a-z-]+)\//);
+  const scope = scopeMatch ? scopeMatch[1] : null;
+  const scopeStr = scope ? `(${scope})` : '';
+
+  // Generate description
+  if (storyInfo && storyInfo.id && storyInfo.title) {
+    let cleanTitle = storyInfo.title
+      .replace(/^Story\s*\d+\.\d+[:\s-]*/i, '')
+      .trim();
+    cleanTitle = cleanTitle.charAt(0).toLowerCase() + cleanTitle.slice(1);
+
+    const storyRef = config.include_story_id ? ` [Story ${storyInfo.id}]` : '';
+    return `${type}${scopeStr}: ${cleanTitle}${storyRef}`;
+  }
+
+  // Fallback: convert branch name to description
+  const description = branchName
+    .replace(/^(feature|feat|fix|bugfix|hotfix|docs|chore|refactor|test|perf|ci|style|build)\//, '')
+    .replace(/^[a-z-]+\//, '')
+    .replace(/-/g, ' ')
+    .toLowerCase()
+    .trim();
+
+  return `${type}${scopeStr}: ${description}`;
+}
+
+/**
+ * Format: [Story {id}] {Title}
+ * Used for: Simple projects, legacy workflows, non-NPM projects
+ */
+function generateStoryFirstTitle(branchName, storyInfo, config) {
   if (storyInfo && storyInfo.id && storyInfo.title) {
     return `[Story ${storyInfo.id}] ${storyInfo.title}`;
   }
 
   // Fallback: convert branch name to title
   return branchName
-    .replace(/^feature\//, '')
+    .replace(/^(feature|feat|fix|bugfix|hotfix|docs|chore|refactor|test|perf|ci|style|build)\//, '')
     .replace(/-/g, ' ')
     .replace(/\b\w/g, c => c.toUpperCase());
 }
+
+/**
+ * Format: {Branch Name As Title}
+ * Used for: Minimal projects, quick iterations
+ */
+function generateBranchBasedTitle(branchName, storyInfo, config) {
+  const title = branchName
+    .replace(/^(feature|feat|fix|bugfix|hotfix|docs|chore|refactor|test|perf|ci|style|build)\//, '')
+    .replace(/-/g, ' ')
+    .replace(/\b\w/g, c => c.toUpperCase());
+
+  if (config.include_story_id && storyInfo?.id) {
+    return `${title} [Story ${storyInfo.id}]`;
+  }
+
+  return title;
+}
+```
+
+## Configuration Reference
+
+Add to your project's `core-config.yaml`:
+
+```yaml
+github:
+  pr:
+    # Options: conventional | story-first | branch-based
+    title_format: conventional  # For semantic-release projects
+    # title_format: story-first  # For simple projects (default)
+
+    include_story_id: true
+
+    conventional_commits:
+      enabled: true
+      branch_type_map:
+        feature/: feat
+        fix/: fix
+        docs/: docs
+        # Add custom mappings as needed
+      default_type: feat
+
+  semantic_release:
+    enabled: true  # Set false if not using semantic-release
 ```
 
+## Title Format Examples
+
+| Format | Branch | Story | Generated Title |
+|--------|--------|-------|-----------------|
+| `conventional` | `feature/user-auth` | 6.17: User Auth | `feat: user auth [Story 6.17]` |
+| `conventional` | `fix/cli/parsing` | 6.18: CLI Fix | `fix(cli): cLI fix [Story 6.18]` |
+| `story-first` | `feature/user-auth` | 6.17: User Auth | `[Story 6.17] User Auth` |
+| `story-first` | `fix/cli-bug` | - | `Cli Bug` |
+| `branch-based` | `feature/user-auth` | 6.17 | `User Auth [Story 6.17]` |
+| `branch-based` | `docs/readme` | - | `Readme` |
+
 ### Step 5: Generate PR Description
 
 ```javascript
@@ -415,10 +602,60 @@ Called by `@github-devops` via `*create-pr` command.
 ## Validation
 
 - PR created in correct repository (detected URL)
-- PR title includes story ID if available
+- PR title follows Conventional Commits format (required for semantic-release)
+- PR title includes story ID if available (e.g., `[Story 6.17]`)
 - PR description includes repository context
 - Base branch is correct (usually main/master)
 
+## Semantic-Release Integration (Optional)
+
+> **Note:** This section only applies when `core-config.yaml` has:
+> - `github.pr.title_format: conventional`
+> - `github.semantic_release.enabled: true`
+>
+> Projects without semantic-release should use `title_format: story-first` (default).
+
+**When enabled:** PRs merged via "Squash and merge" use the PR title as commit message, triggering semantic-release:
+
+| Branch Pattern | Generated Title | Release |
+|---------------|-----------------|---------|
+| `feature/user-auth` | `feat: user auth` | ✅ Minor |
+| `feat/auth/sso-login` | `feat(auth): sso login` | ✅ Minor |
+| `fix/cli-parsing` | `fix: cli parsing` | ✅ Patch |
+| `docs/readme-update` | `docs: readme update` | ❌ None |
+| `chore/deps-update` | `chore: deps update` | ❌ None |
+
+For breaking changes, manually edit the PR title to include `!`:
+- `feat!: redesign authentication API [Story 7.1]`
+
+## Configuration for Different Project Types
+
+### NPM Package with Semantic-Release (aios-core)
+```yaml
+github:
+  pr:
+    title_format: conventional
+  semantic_release:
+    enabled: true
+```
+
+### Simple Web App (no releases)
+```yaml
+github:
+  pr:
+    title_format: story-first  # [Story 6.17] Title
+  semantic_release:
+    enabled: false
+```
+
+### Quick Prototypes
+```yaml
+github:
+  pr:
+    title_format: branch-based  # Just branch name as title
+    include_story_id: false
+```
+
 ## Notes
 
 - Works with ANY repository

package/.aios-core/development/tasks/search-mcp.md

@@ -0,0 +1,309 @@
+# Search MCP Catalog Task
+
+> Search and discover available MCP servers in the Docker MCP Toolkit catalog.
+
+---
+
+## Task Definition
+
+```yaml
+task: searchMcp()
+responsavel: DevOps Agent
+responsavel_type: Agente
+atomic_layer: Infrastructure
+elicit: true
+
+**Entrada:**
+- campo: search_query
+  tipo: string
+  origem: User Input
+  obrigatorio: true
+  validacao: Search query for MCP catalog (e.g., "notion", "database", "slack")
+
+**Saida:**
+- campo: mcp_results
+  tipo: array
+  destino: Console output
+  persistido: false
+
+- campo: mcp_details
+  tipo: object
+  destino: Console output (if user selects an MCP)
+  persistido: false
+```
+
+---
+
+## Pre-Conditions
+
+```yaml
+pre-conditions:
+  - [ ] Docker MCP Toolkit running
+    tipo: pre-condition
+    blocker: true
+    validacao: docker mcp --version succeeds
+    error_message: "Docker MCP Toolkit required. Enable in Docker Desktop settings."
+
+  - [ ] Docker daemon running
+    tipo: pre-condition
+    blocker: true
+    validacao: docker info succeeds
+    error_message: "Start Docker Desktop before running this task"
+```
+
+---
+
+## Interactive Elicitation
+
+### Step 1: Search Query
+
+```
+ELICIT: MCP Search Query
+
+What type of MCP server are you looking for?
+
+Examples:
+  • "notion" - Workspace and document management
+  • "database" - Database integrations (postgres, mysql, sqlite)
+  • "slack" - Team messaging
+  • "browser" - Browser automation (puppeteer, playwright)
+  • "storage" - Cloud storage (s3, gcs)
+  • "*" - List all available MCPs
+
+→ Enter search query: _______________
+```
+
+### Step 2: Display Results
+
+```
+ELICIT: Search Results
+
+Found {n} MCPs matching "{query}":
+
+┌─────────────────────────────────────────────────────────────────┐
+│ #  │ MCP Name        │ Description                             │
+├─────────────────────────────────────────────────────────────────┤
+│ 1  │ mcp/notion      │ Notion workspace integration            │
+│ 2  │ mcp/postgres    │ PostgreSQL database access              │
+│ 3  │ mcp/sqlite      │ SQLite local database                   │
+│ 4  │ mcp/mysql       │ MySQL database access                   │
+└─────────────────────────────────────────────────────────────────┘
+
+Options:
+  • Enter a number to see details
+  • Type "add {number}" to add the MCP
+  • Type "search {query}" to search again
+  • Type "exit" to finish
+
+→ Select option: ___
+```
+
+### Step 3: Show MCP Details (Optional)
+
+```
+ELICIT: MCP Details
+
+📦 mcp/{name}
+
+Description: {full_description}
+
+🔧 Tools Provided:
+   • tool1 - Description of tool1
+   • tool2 - Description of tool2
+   • tool3 - Description of tool3
+
+🔑 Required Credentials:
+   • {CREDENTIAL_NAME} - {description}
+   • (none) - if no credentials needed
+
+📋 Example Usage:
+   docker mcp server add {name}
+   docker mcp tools call {name}.{tool} --param value
+
+Options:
+  • Type "add" to add this MCP
+  • Type "back" to return to results
+  • Type "exit" to finish
+
+→ Select option: ___
+```
+
+---
+
+## Implementation Steps
+
+### 1. Search the Catalog
+
+```bash
+# Basic search
+docker mcp catalog search {query}
+
+# Example: Search for "notion"
+docker mcp catalog search notion
+
+# List all MCPs
+docker mcp catalog search "*"
+
+# Example output:
+# NAME           DESCRIPTION
+# mcp/notion     Notion workspace integration
+# mcp/postgres   PostgreSQL database access
+```
+
+### 2. Get MCP Details
+
+```bash
+# Get detailed info about an MCP
+docker mcp catalog info {mcp-name}
+
+# Example: Get notion details
+docker mcp catalog info notion
+
+# Example output:
+# Name: mcp/notion
+# Description: Notion workspace integration
+# Tools:
+#   - getPage: Retrieve a Notion page
+#   - createPage: Create a new page
+#   - search: Search Notion workspace
+# Environment:
+#   - NOTION_API_KEY (required)
+```
+
+### 3. Filter by Category (if supported)
+
+```bash
+# Search by category
+docker mcp catalog search --category database
+docker mcp catalog search --category productivity
+docker mcp catalog search --category automation
+```
+
+---
+
+## Post-Conditions
+
+```yaml
+post-conditions:
+  - [ ] Search results displayed
+    tipo: post-condition
+    blocker: false
+    validacao: User can see matching MCPs or "no results" message
+    error_message: "Search failed - check Docker MCP connection"
+```
+
+---
+
+## Error Handling
+
+### Error: No Results Found
+
+```
+Resolution:
+1. Try a broader search query
+2. Use wildcards: docker mcp catalog search "*database*"
+3. Check available categories: docker mcp catalog categories
+4. Browse full catalog: docker mcp catalog search "*"
+```
+
+### Error: Docker MCP Not Available
+
+```
+Resolution:
+1. Verify Docker Desktop 4.50+ is installed
+2. Enable MCP Toolkit: Docker Desktop > Settings > Extensions > MCP Toolkit
+3. Restart Docker Desktop
+4. Verify: docker mcp --version
+```
+
+### Error: Catalog Timeout
+
+```
+Resolution:
+1. Check internet connection
+2. Docker MCP catalog requires network access
+3. Retry: docker mcp catalog search {query}
+4. Check Docker proxy settings if behind firewall
+```
+
+---
+
+## Success Output
+
+```
+✅ MCP Catalog Search Complete
+
+🔍 Query: "{query}"
+📦 Results: {n} MCPs found
+
+┌─────────────────────────────────────────────────────────────────┐
+│ MCP Name        │ Description              │ Credentials       │
+├─────────────────────────────────────────────────────────────────┤
+│ mcp/notion      │ Notion workspace         │ NOTION_API_KEY    │
+│ mcp/postgres    │ PostgreSQL access        │ DATABASE_URL      │
+│ mcp/sqlite      │ SQLite local DB          │ None              │
+└─────────────────────────────────────────────────────────────────┘
+
+Next steps:
+1. View details: *search-mcp → select number
+2. Add an MCP: *add-mcp {name}
+3. List enabled MCPs: *list-mcps
+```
+
+---
+
+## Common Search Examples
+
+| Search Query | Finds | Use Case |
+|--------------|-------|----------|
+| `notion` | Notion workspace MCP | Document management |
+| `database` | postgres, mysql, sqlite, redis | Database access |
+| `slack` | Slack messaging MCP | Team communication |
+| `browser` | puppeteer, playwright | Browser automation |
+| `storage` | s3, gcs, azure-blob | Cloud storage |
+| `github` | GitHub API MCP | Repository management |
+| `*` | All available MCPs | Browse full catalog |
+
+---
+
+## Related Commands
+
+| Command | Description |
+|---------|-------------|
+| `*add-mcp` | Add an MCP server to Docker MCP Toolkit |
+| `*list-mcps` | List currently enabled MCPs |
+| `*remove-mcp` | Remove an MCP from Docker MCP Toolkit |
+| `*setup-mcp-docker` | Initial Docker MCP Toolkit setup |
+
+---
+
+## Performance
+
+```yaml
+duration_expected: 1-2 minutes
+cost_estimated: $0 (local Docker operation)
+token_usage: ~200-500 tokens
+```
+
+---
+
+## Metadata
+
+```yaml
+task: search-mcp
+version: 1.0.0
+story: Story 6.14 - MCP Governance Consolidation
+dependencies:
+  - Docker MCP Toolkit
+  - Docker Desktop 4.50+
+tags:
+  - infrastructure
+  - mcp
+  - docker
+  - discovery
+  - catalog
+created_at: 2025-12-17
+updated_at: 2025-12-17
+agents:
+  - devops
+```

package/.aios-core/development/tasks/setup-mcp-docker.md

@@ -1,10 +1,10 @@
 # Setup Docker MCP Toolkit
 
 **Task ID:** setup-mcp-docker
-**Version:** 2.0.0
+**Version:** 2.1.0
 **Created:** 2025-12-08
-**Updated:** 2025-12-08
-**Agent:** @devops (Gage) / @dev (Dex)
+**Updated:** 2025-12-17
+**Agent:** @devops (Gage)
 
 ---
 
@@ -63,7 +63,7 @@ Configure Docker MCP Toolkit as the primary MCP infrastructure for AIOS, using *
 
 ```yaml
 task: setupMcpDocker()
-responsável: DevOps Agent / Dev Agent
+responsável: DevOps Agent
 responsavel_type: Agente
 atomic_layer: Infrastructure
 
@@ -556,8 +556,8 @@ token_usage: ~500-1,000 tokens (this task only)
 ## Metadata
 
 ```yaml
-story: Docker MCP Migration (Story 5.11)
-version: 2.0.0
+story: Story 6.14 - MCP Governance Consolidation
+version: 2.1.0
 dependencies:
   - Docker Desktop 4.50+
   - Docker MCP Toolkit
@@ -568,11 +568,14 @@ tags:
   - docker
   - setup
   - http-transport
-updated_at: 2025-12-08
+created_at: 2025-12-08
+updated_at: 2025-12-17
 agents:
   - devops
-  - dev
 changelog:
+  2.1.0:
+    - Changed: DevOps Agent now exclusive responsible (Story 6.14)
+    - Removed: Dev Agent from agents list
   2.0.0:
     - BREAKING: Changed from stdio to HTTP transport
     - Added: gateway-service.yml for persistent gateway