StrangeDaysTech · montfort · Mar 2, 2026 · Mar 2, 2026 · Mar 2, 2026 · Mar 2, 2026
diff --git a/.cursor/rules/devtrail.md b/.cursor/rules/devtrail.md
diff --git a/.cursorrules b/.cursorrules
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -27,31 +27,8 @@ jobs:
 
       - name: Create distribution ZIP
         run: |
-          # Read files from dist-manifest.yml and create ZIP
           mkdir -p dist-staging
-
-          # Core framework
-          cp -r .devtrail dist-staging/
-          cp DEVTRAIL.md dist-staging/
-          cp dist-manifest.yml dist-staging/
-
-          # Agent skills
-          cp -r .claude/skills dist-staging/.claude/skills 2>/dev/null || true
-          cp -r .gemini/skills dist-staging/.gemini/skills 2>/dev/null || true
-          cp -r .agent/workflows dist-staging/.agent/workflows 2>/dev/null || true
-
-          # Scripts
-          mkdir -p dist-staging/scripts
-          cp scripts/devtrail-new.sh dist-staging/scripts/ 2>/dev/null || true
-          cp scripts/devtrail-status.sh dist-staging/scripts/ 2>/dev/null || true
-          cp scripts/pre-commit-docs.sh dist-staging/scripts/ 2>/dev/null || true
-          cp scripts/validate-docs.ps1 dist-staging/scripts/ 2>/dev/null || true
-
-          # CI/CD
-          mkdir -p dist-staging/.github/workflows
-          cp .github/copilot-instructions.md dist-staging/.github/ 2>/dev/null || true
-          cp .github/workflows/docs-validation.yml dist-staging/.github/workflows/ 2>/dev/null || true
-
+          cp -a dist/. dist-staging/
           cd dist-staging
           zip -r "../devtrail-v${{ steps.version.outputs.version }}.zip" .
           cd ..

diff --git a/.gitignore b/.gitignore
@@ -1,5 +1,15 @@
 # DevTrail - .gitignore
 
+# =============================================================================
+# AI Tool Dev Configs (distribution content lives in dist/)
+# =============================================================================
+
+/.claude/
+/.gemini/
+/.agent/
+/.cursorrules
+/.cursor/
+
 # =============================================================================
 # Desarrollo interno de Strange Days Tech
 # =============================================================================
@@ -81,7 +91,7 @@ yarn.lock
 # =============================================================================
 
 cli/target/
-dist/
+dist-staging/
 *.tar.gz
 release/
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -7,6 +7,7 @@ Thank you for your interest in contributing to DevTrail! This document provides
 ## Table of Contents
 
 - [Code of Conduct](#code-of-conduct)
+- [Contributor License Agreement (CLA)](#contributor-license-agreement-cla)
 - [How Can I Contribute?](#how-can-i-contribute)
 - [Development Setup](#development-setup)
 - [Pull Request Process](#pull-request-process)
@@ -17,15 +18,24 @@ Thank you for your interest in contributing to DevTrail! This document provides
 
 ## Code of Conduct
 
-This project adheres to a Code of Conduct that all contributors are expected to follow. Please be respectful, inclusive, and constructive in all interactions.
+This project is governed by our [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
 
-### Our Standards
+In short: be respectful, inclusive, and constructive in all interactions. Harassment, discrimination, and trolling are not tolerated. Please read the [full Code of Conduct](CODE_OF_CONDUCT.md) before contributing.
 
-- Be welcoming and inclusive
-- Be respectful of differing viewpoints
-- Accept constructive criticism gracefully
-- Focus on what is best for the community
-- Show empathy towards other community members
+---
+
+## Contributor License Agreement (CLA)
+
+This project requires all contributors to sign a **Contributor License Agreement (CLA)** before their pull requests can be merged. We use [CLA Assistant](https://cla-assistant.io/) to manage this process.
+
+### How it works
+
+1. When you open your first pull request, CLA Assistant will automatically post a comment asking you to sign the CLA.
+2. Click the link in the comment to review and sign the agreement.
+3. The CLA only needs to be signed once — it covers all future contributions to this project.
+4. Once signed, CLA Assistant will update the PR check status and your contribution can proceed to review.
+
+If you have questions about the CLA, please open a [Discussion](https://github.com/StrangeDaysTech/devtrail/discussions).
 
 ---
 
@@ -77,45 +87,51 @@ Code contributions should:
 
 ### Prerequisites
 
-- Git
-- A text editor (VS Code recommended)
-- Bash (for Linux/Mac validation scripts)
-- PowerShell (for Windows validation scripts)
-- Node.js (optional, for markdownlint)
+- **Git**
+- **A text editor** (VS Code recommended)
+- **Bash** (for Linux/Mac validation scripts)
+- **PowerShell** (for Windows validation scripts)
+- **Rust toolchain** (for CLI development — install via [rustup.rs](https://rustup.rs/))
+- **Node.js 20+** (optional, for markdownlint)
 
 ### Setup Steps
 
 1. **Fork the repository**
 
-   Click "Fork" on the GitHub repository page.
+   Click "Fork" on the [GitHub repository page](https://github.com/StrangeDaysTech/devtrail).
 
 2. **Clone your fork**
    ```bash
    git clone https://github.com/your-username/devtrail.git
-   cd devtrail-framework
+   cd devtrail
    ```
 
-3. **Create a branch**
+3. **Install the pre-commit hook**
    ```bash
-   git checkout -b feature/your-feature-name
-   # or
-   git checkout -b fix/your-bug-fix
+   cp dist/scripts/pre-commit-docs.sh .git/hooks/pre-commit
+   chmod +x .git/hooks/pre-commit
    ```
 
 4. **Install development tools (optional)**
    ```bash
+   # Markdown linting
    npm install -g markdownlint-cli
    ```
 
-5. **Make your changes**
+5. **Create a branch**
+   ```bash
+   git checkout -b feature/your-feature-name
+   # or
+   git checkout -b fix/your-bug-fix
+   ```
 
-6. **Validate your changes**
+6. **Make your changes and validate**
    ```bash
    # Linux/Mac
-   bash scripts/pre-commit-docs.sh
+   bash dist/scripts/pre-commit-docs.sh
 
    # Windows
-   .\scripts\validate-docs.ps1
+   .\dist\scripts\validate-docs.ps1
    ```
 
 ---
@@ -229,24 +245,21 @@ DevTrail documents:
 If you're proposing a new document type:
 
 1. **Create the template**
-   - Add `TEMPLATE-NEWTYPE.md` to `.devtrail/templates/`
+   - Add `TEMPLATE-NEWTYPE.md` to `dist/.devtrail/templates/`
    - Follow existing template patterns
 
 2. **Update governance docs**
-   - `.devtrail/00-governance/DOCUMENTATION-POLICY.md`
-   - `.devtrail/00-governance/AGENT-RULES.md`
-   - `.devtrail/QUICK-REFERENCE.md`
+   - `dist/.devtrail/00-governance/DOCUMENTATION-POLICY.md`
+   - `dist/.devtrail/00-governance/AGENT-RULES.md`
+   - `dist/.devtrail/QUICK-REFERENCE.md`
 
 3. **Update agent configs**
-   - `CLAUDE.md`
-   - `GEMINI.md`
-   - `.cursorrules`
-   - `.github/copilot-instructions.md`
+   - `dist/dist-templates/directives/` (distribution templates)
 
 4. **Update validation**
-   - `scripts/pre-commit-docs.sh`
-   - `scripts/validate-docs.ps1`
-   - `.github/workflows/docs-validation.yml`
+   - `dist/scripts/pre-commit-docs.sh`
+   - `dist/scripts/validate-docs.ps1`
+   - `dist/.github/workflows/docs-validation.yml`
 
 5. **Document the change**
    - Create an ADR explaining the new type