fix: move AI tool config files back to .github/ directory

Reverts part of previous commit - copilot-tasks.md and custom-instructions.md
are AI tool configuration files, not user-facing documentation.

Changes:
- Move docs/COPILOT_TASKS.md back to .github/copilot-tasks.md
- Move docs/CUSTOM_INSTRUCTIONS.md back to .github/custom-instructions.md
- Update .github/README.md to list these files as root-level config
- Update docs/FILE_ORGANIZATION.md to clarify distinction between:
  * .github/ = Infrastructure and AI tool configuration
  * docs/ = User-facing documentation for developers and contributors

Clarification: Only permanent user-facing documentation belongs in docs/.
AI tool configurations belong in .github/ with other infrastructure.

Author: ashleyshaw

.github/README.md

@@ -20,14 +20,12 @@ This directory contains GitHub-specific configuration files for the {{theme_name
 - **reports/** - Completed task reports and validation outcomes
 - **schemas/** - JSON schemas and configuration templates
 - **workflows/** - GitHub Actions CI/CD workflow definitions
+- `copilot-tasks.md` - Copilot task definitions and specifications
+- `custom-instructions.md` - Custom AI instructions for Copilot
 
 ## Documentation
 
-Permanent documentation is stored in the [docs/](../docs/) folder, not here. See:
-
-- [docs/FILE_ORGANIZATION.md](../docs/FILE_ORGANIZATION.md) - File organization guide
-- [docs/COPILOT_TASKS.md](../docs/COPILOT_TASKS.md) - Copilot task definitions
-- [docs/CUSTOM_INSTRUCTIONS.md](../docs/CUSTOM_INSTRUCTIONS.md) - Custom AI instructions
+Permanent user-facing documentation is stored in the [docs/](../docs/) folder. See [docs/FILE_ORGANIZATION.md](../docs/FILE_ORGANIZATION.md) for the complete file organization guide.
 
 ## Workflows
 

docs/COPILOT_TASKS.md .github/copilot-tasks.mddocs/COPILOT_TASKS.md renamed to .github/copilot-tasks.md

@@ -24,6 +24,7 @@ Projects use status indicators to show current progress:
 **Purpose:** Comprehensive plan to reduce token bloat and context usage in the block-theme-scaffold repository.
 
 **Phases:**
+
 - ✅ Phase 1: Delete Model-Specific Files (~495 lines removed)
 - ✅ Phase 2: Consolidate Documentation (merged governance and development docs)
 - ✅ Phase 3: Optimize Core Index Files (reduced AGENTS.md, agent.md, prompts.md)
@@ -45,6 +46,7 @@ Projects use status indicators to show current progress:
    - Example: `context-reduction.md`
 
 2. Include project header:
+
    ```markdown
    # Project Title
 

docs/CUSTOM_INSTRUCTIONS.md .github/custom-instructions.mddocs/CUSTOM_INSTRUCTIONS.md renamed to .github/custom-instructions.md

@@ -9,12 +9,14 @@ This directory contains JSON schemas and configuration templates used for code g
 **Purpose:** Official JSON Schema defining all valid configuration options for theme generation.
 
 **Usage:**
+
 - Defines the structure and validation rules for theme configuration files
 - Used by theme generators to validate user input
 - Referenced by editors and IDEs for autocomplete and validation
 - Provides documentation for all available configuration options
 
 **Schema Defines:**
+
 - Required fields (theme_slug, theme_name, author)
 - Optional fields (description, version, license, etc.)
 - Design system tokens (colors, typography, spacing)
@@ -23,6 +25,7 @@ This directory contains JSON schemas and configuration templates used for code g
 - Content options
 
 **Example:**
+
 ```bash
 # Validate a configuration file against the schema
 jq -f .github/schemas/theme-config.schema.json my-config.json
@@ -33,18 +36,21 @@ jq -f .github/schemas/theme-config.schema.json my-config.json
 **Purpose:** Pre-filled example configuration showing realistic values for all schema fields.
 
 **Usage:**
+
 - Template for users creating new theme configurations
 - Reference implementation of all available options
 - Documentation through working example
 - Copy and customize for new projects
 
 **Content:**
+
 - Complete theme-config with all sections populated
 - Realistic values for Tour Operator theme
 - Comments explaining each major section
 - Valid against theme-config.schema.json
 
 **Example:**
+
 ```bash
 # Copy example to create your own configuration
 cp .github/schemas/theme-config.example.json my-theme-config.json

.github/projects/README.md

@@ -13,16 +13,17 @@ This document explains where different types of files are stored in the block-th
 
 ## Core Policy: Documentation Location
 
-**🔑 Key Rule:** All permanent documentation must be stored in the `docs/` folder, not in `.github/` subdirectories.
+**🔑 Key Rule:** All permanent user-facing documentation must be stored in the `docs/` folder, not in `.github/` subdirectories.
 
-- `.github/` is for infrastructure, configuration, and transient work (projects, reports)
-- `docs/` is for permanent, versioned documentation
+- `.github/` is for infrastructure, AI tool configuration, and transient work (projects, reports)
+- `docs/` is for permanent documentation that developers and contributors read regularly
 - `tmp/` and `logs/` do NOT include README.md files
 
 This separation ensures:
 
-- Clear distinction between infrastructure and documentation
+- Clear distinction between infrastructure/tooling and user documentation
 - Permanent docs are discoverable and grouped together
+- AI tool configuration stays with GitHub infrastructure
 - Easier navigation for developers and AI agents
 - Reduces cognitive overhead
 
@@ -37,14 +38,14 @@ block-theme-scaffold/
 │   ├── instructions/         # AI agent & coding standards
 │   ├── agents/               # Agent specifications and code
 │   ├── workflows/            # GitHub Actions CI/CD
-│   └── prompts/              # Prompt templates for AI generation
-├── docs/                     # ⭐ ALL permanent documentation here
+│   ├── prompts/              # Prompt templates for AI generation
+│   ├── copilot-tasks.md      # Copilot task definitions
+│   └── custom-instructions.md # Custom AI instructions
+├── docs/                     # ⭐ ALL permanent user-facing documentation here
 │   ├── GOVERNANCE-START-HERE.md  # Navigation hub
 │   ├── GOVERNANCE.md         # Core policies & standards
 │   ├── ARCHITECTURE.md       # Project structure
 │   ├── FILE_ORGANIZATION.md  # This file
-│   ├── CUSTOM_INSTRUCTIONS.md    # Custom AI instructions
-│   ├── COPILOT_TASKS.md      # Copilot task definitions
 │   └── [other comprehensive guides]/
 ├── src/                      # Source code (JS, CSS)
 ├── inc/                      # PHP includes