diff --git a/.github/skills/codebase-summary/SKILL.md b/.github/skills/codebase-summary/SKILL.md
new file mode 100644
index 0000000..d409999
--- /dev/null
+++ b/.github/skills/codebase-summary/SKILL.md
@@ -0,0 +1,51 @@
+---
+name: codebase-summary
+description: Generate a repo-specific map of self-correcting-executor, including the tree, key dependencies, and MCP verification steps. Use this when asked to summarize the architecture or prepare an agent run for this repository.
+---
+
+When asked to summarize or orient an agent in this repository, use the current
+repo structure instead of generic MCP examples.
+
+1. Start from `/home/runner/work/self-correcting-executor/self-correcting-executor`.
+2. Build the summary around these directories:
+ - `agents/`
+ - `connectors/`
+ - `mcp_server/`
+ - `protocols/`
+ - `frontend/`
+ - `tests/`
+3. Call out the primary dependency sources:
+ - `requirements.txt`
+ - `requirements-ci.txt`
+ - `requirements-test.txt`
+ - `frontend/package.json`
+4. When MCP is relevant, explicitly distinguish:
+ - **host**: external Copilot/CLI/operator
+ - **client**: external MCP-aware caller
+ - **server**: the repo's implementations in `mcp_server/` and
+ `quantum_mcp_server/`
+5. Use the live baseline verification sequence before claiming MCP is working:
+
+ ```python
+ import asyncio
+ from mcp_server.main import MCPServer
+
+ async def main():
+ server = MCPServer()
+ await server.handle_request(
+ {
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "initialize",
+ "params": {"clientInfo": {"name": "summary-skill", "version": "1.0"}},
+ }
+ )
+ await server.handle_request(
+ {"jsonrpc": "2.0", "id": 2, "method": "tools/list", "params": {}}
+ )
+
+ asyncio.run(main())
+ ```
+
+6. Point the reader to `docs/REPO_MAP.md` for the maintained tree, mermaid
+ diagram, dependency snapshot, workflow checklist, and CI/MCP notes.
diff --git a/.github/skills/github-actions-failure-debugging/SKILL.md b/.github/skills/github-actions-failure-debugging/SKILL.md
new file mode 100644
index 0000000..10dc739
--- /dev/null
+++ b/.github/skills/github-actions-failure-debugging/SKILL.md
@@ -0,0 +1,57 @@
+---
+name: github-actions-failure-debugging
+description: Guide for debugging failing GitHub Actions workflows in self-correcting-executor. Use this when asked to investigate Python CI, Frontend CI, or PR workflow failures in this repository.
+---
+
+Use GitHub MCP tools first, then reproduce locally with the repo's existing
+commands.
+
+1. List recent workflow runs for `groupthinking/self-correcting-executor`.
+ Focus on:
+ - `.github/workflows/python-ci.yml`
+ - `.github/workflows/frontend-ci.yml`
+2. Get job logs for the failed run or failed jobs.
+3. Interpret the result against this repo's workflow behavior:
+ - `python-ci.yml` runs `black --check .`
+ - `python-ci.yml` currently masks `flake8` and `pytest` failures with
+ `|| echo ...` and `continue-on-error`, so a green workflow does not always
+ mean imports/tests are healthy
+ - `frontend-ci.yml` runs `npm ci || npm install`, then lint/test/build from
+ `/frontend`
+4. Reproduce only the relevant local command:
+
+ ```bash
+ cd /home/runner/work/self-correcting-executor/self-correcting-executor
+ python -m pytest tests/ -q
+ cd /home/runner/work/self-correcting-executor/self-correcting-executor/frontend
+ npm run lint
+ npm run build
+ ```
+
+5. If the failure touches MCP behavior, also run the repo's live MCP baseline:
+
+ ```bash
+ cd /home/runner/work/self-correcting-executor/self-correcting-executor
+ python -m pytest tests/test_repo_assist_docs.py -q
+ python - <<'PY'
+ import asyncio
+ from mcp_server.main import MCPServer
+
+ async def main():
+ server = MCPServer()
+ response = await server.handle_request(
+ {
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "initialize",
+ "params": {"clientInfo": {"name": "ci-debug", "version": "1.0"}},
+ }
+ )
+ print(response["result"]["serverInfo"])
+
+ asyncio.run(main())
+ PY
+ ```
+
+6. Keep fixes surgical. Do not "clean up" unrelated files just because the
+ workflow surfaced pre-existing noise.
diff --git a/README.md b/README.md
index 81997fc..ad4478d 100644
--- a/README.md
+++ b/README.md
@@ -33,4 +33,12 @@ Open http://localhost:8080/health to verify the API is running.
## Development
-The workspace includes a **DevContainer** definition – simply open the folder in VS Code or Cursor and choose *Reopen in Container* to get an IDE connected to the running services.
\ No newline at end of file
+The workspace includes a **DevContainer** definition – simply open the folder in VS Code or Cursor and choose *Reopen in Container* to get an IDE connected to the running services.
+
+## Repo assist
+
+For a repo-specific map of the current tree, dependency snapshot, mermaid
+architecture diagram, MCP capability-verification notes, and agent workflow
+checklist, see
+`/home/runner/work/self-correcting-executor/self-correcting-executor/docs/REPO_MAP.md`
+(also tracked in the repository as [`docs/REPO_MAP.md`](docs/REPO_MAP.md)).
\ No newline at end of file
diff --git a/docs/REPO_MAP.md b/docs/REPO_MAP.md
new file mode 100644
index 0000000..30a0c23
--- /dev/null
+++ b/docs/REPO_MAP.md
@@ -0,0 +1,213 @@
+# Repo Map, MCP Verification, and Agent Workflow Checklist
+
+This repository mixes agent orchestration, MCP servers, connectors, protocols,
+and a small frontend. This document makes the issue's requested "repo assist"
+material specific to `groupthinking/self-correcting-executor` so an agent can
+map the repo, verify the MCP baseline live, and decide what to check before
+commit/merge.
+
+## Repo tree (focused map)
+
+```text
+self-correcting-executor/
+├── agents/ # A2A framework, executor, mutator, MCP integrations
+│ ├── a2a_framework.py
+│ ├── a2a_mcp_integration.py
+│ ├── executor.py
+│ ├── mutator.py
+│ ├── specialized/
+│ └── unified/
+├── analyzers/ # Pattern analysis helpers
+├── auth/ # Auth helpers
+├── config/ # MCP and component configuration
+├── connectors/ # D-Wave, GitHub, LLM, xAI, MCP base connectors
+├── docs/ # Architecture, planning, and task guides
+├── fabric/ # State continuity and integrated MCP fabric
+├── frontend/ # Vite + React UI
+├── llm/ # Continuous learning system
+├── mcp_runtime_template_hg/ # SDK/API/CLI MCP runtime template
+├── mcp_server/ # JSON-RPC MCP server + FastMCP-backed server
+├── middleware/ # Security middleware
+├── protocols/ # Executable protocols/tasks
+├── quantum_mcp_server/ # Quantum-focused MCP server variant
+├── scripts/ # Setup, compliance, cleanup, security scripts
+├── test_data/ # Real input fixtures used by tests/scripts
+├── tests/ # Pytest suite
+├── ui/ # Additional UI assets and guide content
+└── utils/ # Shared logging and DB tracking
+```
+
+## Dependency snapshot
+
+- Python runtime dependencies: `requirements.txt` currently pins **117**
+ packages, including `mcp`, `mcp-use`, FastAPI, D-Wave Ocean SDK, LangChain,
+ SQLAlchemy, Redis, and transformer-related packages.
+- CI/test dependencies: `requirements-ci.txt` contains the lightweight
+ verification stack (`black`, `flake8`, `pytest`, `pytest-cov`,
+ `pytest-asyncio`).
+- Frontend runtime dependencies: `frontend/package.json` currently declares
+ **7** runtime packages (`react`, `react-dom`, `@tanstack/react-query`,
+ `axios`, `framer-motion`, `lucide-react`, `three`) and **12** dev
+ dependencies for TypeScript, ESLint, and Vite.
+
+## Mermaid diagram
+
+```mermaid
+flowchart TD
+ H[Host / Copilot / operator]
+ O[orchestrator.py
orchestrator_mapreduce.py]
+
+ subgraph Servers[MCP servers]
+ M1[mcp_server/main.py
custom JSON-RPC MCPServer]
+ M2[mcp_server/real_mcp_server.py
FastMCP tool server]
+ M3[quantum_mcp_server/]
+ end
+
+ subgraph Tools[Declared MCP tools]
+ T1[code_analyzer]
+ T2[protocol_validator]
+ T3[self_corrector]
+ end
+
+ subgraph Connectors[Connectors]
+ C1[github_mcp_connector.py]
+ C2[dwave_quantum_connector.py]
+ C3[llm_connector.py]
+ C4[xai_connector.py]
+ end
+
+ subgraph Tasks[protocols/*.py]
+ P1[data_processor]
+ P2[file_validator]
+ P3[database_health_check]
+ P4[system_monitor]
+ end
+
+ H --> O
+ O --> M1
+ O --> M2
+ O --> M3
+ M1 --> T1
+ M1 --> T2
+ M1 --> T3
+ M2 --> C1
+ M2 --> C2
+ M2 --> C3
+ M2 --> C4
+ O --> Tasks
+ Tasks --> P1
+ Tasks --> P2
+ Tasks --> P3
+ Tasks --> P4
+```
+
+## Agentic workflow checklist for this repo
+
+- [x] **Agents**: `agents/a2a_framework.py`, `agents/a2a_mcp_integration.py`,
+ and `agents/unified/` contain agent coordination logic.
+- [x] **Tools**: `mcp_server/main.py` declares `code_analyzer`,
+ `protocol_validator`, and `self_corrector`.
+- [x] **MCP**: the repo is actively using MCP packages and MCP-shaped servers
+ (`mcp_server/main.py`, `mcp_server/real_mcp_server.py`,
+ `config/mcp_config.py`, `connectors/mcp_base.py`).
+- [x] **Pull / push / request / commit / merge**: human workflows use GitHub
+ pull requests; cloud-agent workflows in this repo should publish progress
+ via PR updates instead of pushing directly from the sandbox.
+- [x] **Issues**: link changes back to GitHub issues with `Closes #`.
+- [x] **Code**: the main test entrypoint is `pytest` with `pytest.ini`
+ configured to use `tests/`.
+- [x] **Deps**: Python dependencies live in `requirements*.txt`; frontend
+ dependencies live in `frontend/package.json`.
+- [x] **Database**: DB-aware execution paths are visible in `utils/db_tracker.py`
+ and `protocols/database_health_check.py`.
+- [x] **Actions**: `.github/workflows/python-ci.yml` and
+ `.github/workflows/frontend-ci.yml` define CI.
+- [x] **Role assignment / security**: `auth/` and `middleware/` contain auth
+ and security logic.
+
+## MCP baseline: is this repo using MCP?
+
+Yes. The repository is using MCP in two forms:
+
+1. A custom JSON-RPC server in `/home/runner/work/self-correcting-executor/self-correcting-executor/mcp_server/main.py`
+ with explicit MCP methods such as `initialize`, `tools/list`, `tools/call`,
+ `resources/list`, and `resources/read`.
+2. A FastMCP-based server in `/home/runner/work/self-correcting-executor/self-correcting-executor/mcp_server/real_mcp_server.py`
+ built on the `mcp` package.
+
+Compared with the MCP architecture/specification dated `2026-07-28`, this repo
+already covers the **server** side baseline well enough to negotiate tools and
+resources, but it does **not** implement a full host/client runtime in-repo.
+That is acceptable for this codebase because GitHub Copilot/GitHub MCP acts as
+the host environment around these servers.
+
+### Host / client / server mapping for this repo
+
+- **Host**: external agent host (for example Copilot, CLI, or another MCP-aware
+ operator) orchestrates requests and permissions.
+- **Client**: the MCP-aware caller is external to this repo; this repo does not
+ ship a standalone client implementation.
+- **Server**: this repo implements the server side in `mcp_server/` and
+ `quantum_mcp_server/`.
+
+## Live verification steps
+
+The minimum capability-negotiation proof for this repo is to exercise the
+custom MCP server directly and confirm that `initialize` advertises
+capabilities, then `tools/list` and `tools/call` work end-to-end.
+
+```bash
+cd /home/runner/work/self-correcting-executor/self-correcting-executor
+python - <<'PY'
+import asyncio
+import json
+from mcp_server.main import MCPServer
+
+async def main():
+ server = MCPServer()
+ for request in (
+ {
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "initialize",
+ "params": {"clientInfo": {"name": "repo-assist", "version": "1.0"}},
+ },
+ {"jsonrpc": "2.0", "id": 2, "method": "tools/list", "params": {}},
+ {
+ "jsonrpc": "2.0",
+ "id": 3,
+ "method": "tools/call",
+ "params": {
+ "name": "code_analyzer",
+ "arguments": {"code": "def verify():\n return 1\n"},
+ },
+ },
+ ):
+ print(json.dumps(await server.handle_request(request), indent=2))
+
+asyncio.run(main())
+PY
+```
+
+Focused automated verification for the repo-assist additions:
+
+```bash
+python -m pytest tests/test_repo_assist_docs.py -q
+```
+
+## CI baseline observed from GitHub Actions
+
+- The repo has active `Python CI` and `Frontend CI` workflows.
+- The inspected recent `Python CI` job logs showed `black` passing.
+- The same logs also showed that `flake8` findings and `pytest` collection
+ errors are currently masked by `|| echo ...` and `continue-on-error`, so the
+ workflow can report success even when Python imports/tests are not clean.
+
+## Skills added for this repo
+
+Project-scoped skills now live under `.github/skills/`:
+
+- `github-actions-failure-debugging`: tailored to the repo's Python/Frontend CI
+ workflows and GitHub MCP debugging flow.
+- `codebase-summary`: tailored to this repo's tree mapping, dependency checks,
+ and MCP verification workflow.
diff --git a/tests/test_repo_assist_docs.py b/tests/test_repo_assist_docs.py
new file mode 100644
index 0000000..3f2cd6a
--- /dev/null
+++ b/tests/test_repo_assist_docs.py
@@ -0,0 +1,37 @@
+from pathlib import Path
+
+REPO_ROOT = Path(__file__).resolve().parents[1]
+
+
+def test_repo_map_contains_requested_sections():
+ repo_map = REPO_ROOT / "docs" / "REPO_MAP.md"
+
+ assert repo_map.exists()
+ content = repo_map.read_text()
+ assert "## Repo tree (focused map)" in content
+ assert "## Dependency snapshot" in content
+ assert "## Mermaid diagram" in content
+ assert "## Agentic workflow checklist for this repo" in content
+ assert "## MCP baseline: is this repo using MCP?" in content
+ assert "## Live verification steps" in content
+
+
+def test_repo_skills_are_present_and_repo_specific():
+ skills = {
+ "github-actions-failure-debugging": (
+ REPO_ROOT
+ / ".github"
+ / "skills"
+ / "github-actions-failure-debugging"
+ / "SKILL.md"
+ ),
+ "codebase-summary": (
+ REPO_ROOT / ".github" / "skills" / "codebase-summary" / "SKILL.md"
+ ),
+ }
+
+ for name, skill_path in skills.items():
+ assert skill_path.exists(), f"Missing skill: {name}"
+ content = skill_path.read_text()
+ assert f"name: {name}" in content
+ assert "self-correcting-executor" in content