branch fixes

specs/002-mcp-server/checklists/requirements.md

@@ -2,7 +2,7 @@
 
 **Purpose**: Validate specification completeness and quality before proceeding to planning  
 **Created**: 2026-01-30  
-**Feature**: specs/001-mcp-server/spec.md
+**Feature**: specs/002-mcp-server/spec.md
 
 ## Content Quality
 

specs/002-mcp-server/plan.md

@@ -1,7 +1,7 @@
 # Implementation Plan: MCP Server for Repo Maintenance
 
-**Branch**: `001-mcp-server` | **Date**: 2026-01-30 | **Spec**: specs/001-mcp-server/spec.md  
-**Input**: Feature specification from `/specs/001-mcp-server/spec.md`
+**Branch**: `002-mcp-server` | **Date**: 2026-01-30 | **Spec**: specs/002-mcp-server/spec.md  
+**Input**: Feature specification from `/specs/002-mcp-server/spec.md`
 
 ## Summary
 
@@ -34,7 +34,7 @@ Build a local-only MCP server under `scripts/` that Codex CLI can use to run doc
 ### Documentation (this feature)
 
 ```text
-specs/001-mcp-server/
+specs/002-mcp-server/
 ├── plan.md
 ├── research.md
 ├── data-model.md
@@ -59,7 +59,7 @@ scripts/mcp-server/
     └── test_docs_sync.py
 ```
 
-**Structure Decision**: Single Python project under `scripts/mcp-server` with src/tests layout; documentation lives in `docs/` and spec artifacts in `specs/001-mcp-server/`.
+**Structure Decision**: Single Python project under `scripts/mcp-server` with src/tests layout; documentation lives in `docs/` and spec artifacts in `specs/002-mcp-server/`.
 
 ## Complexity Tracking
 

specs/002-mcp-server/spec.md

@@ -1,6 +1,6 @@
 # Feature Specification: MCP Server for Repo Maintenance
 
-**Feature Branch**: `001-mcp-server`  
+**Feature Branch**: `002-mcp-server`  
 **Created**: 2026-01-30  
 **Status**: Draft  
 **Input**: User description: "build a mcp server under the directory /scripts the intention for this mcp server is to be consumed by codex-cli to help on modifying the repository by doing but not limited to, the tasks declared on the ai-oriented documentation found in /docs. as an extra, I want this mcp to have tests, which run on the gitea pipeline when any changes done to the mcp or docs directories are commited. expand the ai-documentation on /docs with info about the built mcp so that it is compliant with what of the available tools of the mcp can be called for what specific tasks, ensuring that the mcp provides the easiest up to date assistance to giving this repository maintenance. When it comes to the coding preferences for the server, I want: 1) indentation kept to the bare minimum 2) guard clauses & early returns 3) easy to read coding style, with no comments, but professional easy to maintain code structure 4) functions with docstrings, typehints, etc. 5) give preference to iteration tools such as lambdas, map, filters, as opposed to for loops and multiple ifs. 6) functional code, with reduced duplicated code 7) lint & format the code"

specs/002-mcp-server/tasks.md

@@ -1,6 +1,6 @@
 # Tasks: MCP Server for Repo Maintenance
 
-**Input**: Design documents from `/specs/001-mcp-server/`
+**Input**: Design documents from `/specs/002-mcp-server/`
 **Prerequisites**: plan.md, spec.md, research.md, data-model.md, contracts/
 
 ## Phase 1: Setup (Shared Infrastructure)