docs: rewrite README, init docmd, restructure docs (Refs: #7, #8)

- Rewrite README.md with project purpose, tech stack, architecture,
  CLI cheatsheet, build instructions, and docs index
- Fix all monolize → spark references in docs/usage/*.md (7 files)
- Init docmd config (docmd.config.js) with sky theme, SPA layout,
  search/mermaid/llms plugins
- Add GitHub Actions workflow for GitHub Pages deployment
- Restructure docs/ (move analysis/, add features/spec/tips dirs)
- Update CLAUDE.md with corrected module name and command hierarchy
- Add node_modules/, site/, package-lock.json to .gitignore

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

Author: qdriven

.github-task-workflow.active-issue

@@ -1 +1 @@
-6
+8

.github/workflows/docs.yml

@@ -0,0 +1,50 @@
+name: Deploy Docs to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'docs/**'
+      - 'docmd.config.js'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Build docs
+        run: npx docmd build
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -4,4 +4,7 @@ go.sum
 spark
 __pycache__/
 **/__pycache__/
-.github-task-workflow.active-issue
+.github-task-workflow.active-issue
+node_modules/
+site/
+package-lock.json

CLAUDE.md

@@ -5,7 +5,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 ## Build & Test Commands
 
 ```bash
-make build          # Build for current OS (outputs ./spark)
+make build          # Build for current OS + install to ~/.local/bin/spark
 make build-linux    # Cross-compile for Linux amd64
 make build-darwin   # Cross-compile for macOS amd64
 make test           # Run all unit tests (go test ./... -v)
@@ -21,40 +21,54 @@ go test ./internal/git/... -v -run TestFunctionName
 
 ## Architecture
 
-Spark is a Go CLI tool (`module monolize`, binary `spark`) for managing multiple Git repositories. Built with **Cobra** (CLI), **Viper** (config), **PTerm** + **Bubble Tea** (TUI), tested with **Ginkgo/Gomega** (BDD).
+Spark is a Go CLI tool (`module spark`, binary `spark`) for managing multiple Git repositories, AI agent configs, scripts, and task workflows. Built with **Cobra** (CLI), **Viper** (config), **PTerm** + **Bubble Tea** (TUI), tested with **Ginkgo/Gomega** (BDD).
 
 ### Code Structure
 
 - **`main.go`** → calls `cmd.Execute()`
-- **`cmd/`** — Cobra command definitions. `root.go` loads config from `~/.spark.yaml`. Subdirectories `cmd/git/` and `cmd/magic/` group related commands.
+- **`cmd/`** — Cobra command definitions. `root.go` loads config from `~/.spark.yaml` and auto-migrates from legacy `~/.monolize.yaml`. Subdirectories group commands:
+  - `cmd/git/` — Git repo management commands
+  - `cmd/magic/` — System utility commands (DNS flush, mirror switching)
+  - `cmd/script/` — Script management commands
+  - `cmd/agent.go`, `cmd/agent_profile.go`, `cmd/task.go` — Top-level commands in the root `cmd/` package
 - **`internal/`** — Business logic, separated by domain:
-  - `agent/` — AI agent config management (Claude Code, Codex, Kimi, GLM)
+  - `agent/` — AI agent config management (Claude Code, Codex, Kimi, GLM) and profile templates
   - `config/` — Configuration loading and management
-  - `git/` — Core Git operations (update, create, sync)
+  - `git/` — Core Git operations (find repos, update, remote management, URL conversion)
+  - `github/` — GitHub API interactions (list org repos, parse org URLs)
   - `mono/` — Mono-repo creation and submodule management
-  - `task/` — Task dispatch/sync and GitHub repo creation
-  - `tui/` — Shared terminal UI components (spinner, dialogs)
+  - `script/` — Script discovery (from config and `scripts/` dir) and execution
+  - `task/` — Task init/dispatch/sync, feature CRUD, and implementation via `kimi` CLI
+  - `tui/` — Shared terminal UI components (spinner, dialogs, selector)
 - **`docs/usage/`** — Usage documentation per command
 
 ### Command Hierarchy
 
 ```
 spark
-├── git [update|create|sync|gitcode|config|url|clone-org]
-├── agent [list|view|edit|use|current] + agent profile [list|add|edit]
-├── task [list|dispatch|sync]
-└── magic [dns]
+├── git [update|create|sync|gitcode|config|url|clone-org|update-org-status]
+├── agent [list|view|edit|reset] + agent profile [list|add|edit]
+├── task [list|init|dispatch|sync|create|delete|impl]
+├── script [list|run]
+└── magic [flush-dns|pip|go|node]     # Mirror source switching + DNS
 ```
 
+### Key Patterns
+
+- **TUI mode**: `task`, `agent`, and other commands accept `--tui` flag for interactive mode with Bubble Tea selectors and PTerm spinners. CLI mode is the default.
+- **Config binding**: Flags are bound to Viper via `viper.BindPFlag()` in `init()` functions. Config keys use snake_case in YAML but camelCase in struct tags.
+- **Script sources**: Scripts can come from `~/.spark.yaml` (`spark.scripts` or top-level `scripts`) or from a `scripts/` directory. Config scripts take precedence.
+
 ### Config
 
-User config at `~/.spark.yaml` (see `.spark.yaml.example`). Key sections: `repo-path` (list of directories to scan), `git` (default username/email), `task_dir`, `github_owner`, `work_dir`.
+User config at `~/.spark.yaml`. Key sections: `repo-path` (list of directories to scan), `git` (default username/email), `task_dir`, `github_owner`, `work_dir`, `spark.scripts`.
 
 ## Development Conventions
 
 - Follow standard Go conventions; no comments unless explicitly requested
 - New features require BDD-style tests using Ginkgo/Gomega
 - Test files use `_test.go` suffix, live alongside source in `internal/`
+- Test suite files (`*_suite_test.go`) register the Ginkgo test runner for each package
 - Keep `Makefile` as the single source of truth for build/test commands
 - New commands should have usage docs in `docs/usage/`
 - The UI language is primarily Chinese (documentation, user-facing messages)