mcp-remlezrd 0.1.0__tar.gz

mcp_remlezrd-0.1.0/.gitignore

@@ -0,0 +1,26 @@
+# hidden directories ------------------
+/.*/
+!/.taskfile.d/
+
+# Cache and Working files -------------
+__pycache__/
+*.py[oc]
+WIP*
+*.tmp
+.codebook.toml
+/*.ods
+/*.csv
+/.taskfile.d/uv/ci_quality_job.sh
+*merge_codeclimate.py
+
+# Deliverables ------------------------
+/dist/
+
+# docs --------------------------------
+/docs/_meta/
+/docs/_ideas
+docs/help/
+docs/_adrs/
+docs/_glossary/
+docs/_skills/
+docs/_rules/

mcp_remlezrd-0.1.0/LICENSE.md

@@ -0,0 +1,157 @@
+# GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc.
+<https://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the
+terms and conditions of version 3 of the GNU General Public License,
+supplemented by the additional permissions listed below.
+
+## 0. Additional Definitions.
+
+As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the
+GNU General Public License.
+
+"The Library" refers to a covered work governed by this License, other
+than an Application or a Combined Work as defined below.
+
+An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+A "Combined Work" is a work produced by combining or linking an
+Application with the Library. The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+## 1. Exception to Section 3 of the GNU GPL.
+
+You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+## 2. Conveying Modified Versions.
+
+If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+-   a) under this License, provided that you make a good faith effort
+    to ensure that, in the event an Application does not supply the
+    function or data, the facility still operates, and performs
+    whatever part of its purpose remains meaningful, or
+-   b) under the GNU GPL, with none of the additional permissions of
+    this License applicable to that copy.
+
+## 3. Object Code Incorporating Material from Library Header Files.
+
+The object code form of an Application may incorporate material from a
+header file that is part of the Library. You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+-   a) Give prominent notice with each copy of the object code that
+    the Library is used in it and that the Library and its use are
+    covered by this License.
+-   b) Accompany the object code with a copy of the GNU GPL and this
+    license document.
+
+## 4. Combined Works.
+
+You may convey a Combined Work under terms of your choice that, taken
+together, effectively do not restrict modification of the portions of
+the Library contained in the Combined Work and reverse engineering for
+debugging such modifications, if you also do each of the following:
+
+-   a) Give prominent notice with each copy of the Combined Work that
+    the Library is used in it and that the Library and its use are
+    covered by this License.
+-   b) Accompany the Combined Work with a copy of the GNU GPL and this
+    license document.
+-   c) For a Combined Work that displays copyright notices during
+    execution, include the copyright notice for the Library among
+    these notices, as well as a reference directing the user to the
+    copies of the GNU GPL and this license document.
+-   d) Do one of the following:
+    -   0) Convey the Minimal Corresponding Source under the terms of
+        this License, and the Corresponding Application Code in a form
+        suitable for, and under terms that permit, the user to
+        recombine or relink the Application with a modified version of
+        the Linked Version to produce a modified Combined Work, in the
+        manner specified by section 6 of the GNU GPL for conveying
+        Corresponding Source.
+    -   1) Use a suitable shared library mechanism for linking with
+        the Library. A suitable mechanism is one that (a) uses at run
+        time a copy of the Library already present on the user's
+        computer system, and (b) will operate properly with a modified
+        version of the Library that is interface-compatible with the
+        Linked Version.
+-   e) Provide Installation Information, but only if you would
+    otherwise be required to provide such information under section 6
+    of the GNU GPL, and only to the extent that such information is
+    necessary to install and execute a modified version of the
+    Combined Work produced by recombining or relinking the Application
+    with a modified version of the Linked Version. (If you use option
+    4d0, the Installation Information must accompany the Minimal
+    Corresponding Source and Corresponding Application Code. If you
+    use option 4d1, you must provide the Installation Information in
+    the manner specified by section 6 of the GNU GPL for conveying
+    Corresponding Source.)
+
+## 5. Combined Libraries.
+
+You may place library facilities that are a work based on the Library
+side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+-   a) Accompany the combined library with a copy of the same work
+    based on the Library, uncombined with any other library
+    facilities, conveyed under the terms of this License.
+-   b) Give prominent notice with the combined library that part of it
+    is a work based on the Library, and explaining where to find the
+    accompanying uncombined form of the same work.
+
+## 6. Revised Versions of the GNU Lesser General Public License.
+
+The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+as you received it specifies that a certain numbered version of the
+GNU Lesser General Public License "or any later version" applies to
+it, you have the option of following the terms and conditions either
+of that published version or of any later version published by the
+Free Software Foundation. If the Library as you received it does not
+specify a version number of the GNU Lesser General Public License, you
+may choose any version of the GNU Lesser General Public License ever
+published by the Free Software Foundation.
+
+If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

mcp_remlezrd-0.1.0/PKG-INFO

@@ -0,0 +1,152 @@
+Metadata-Version: 2.4
+Name: mcp-remlezrd
+Version: 0.1.0
+Summary: Model Context Protocol (MCP) server for AI agents
+Project-URL: Documentation, https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/blob/main/README.md
+Project-URL: Homepage, https://gitlab.com/gp3t1/ai/mcp-remlezrd
+Project-URL: Issues, https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/issues
+Project-URL: Repository, https://gitlab.com/gp3t1/ai/mcp-remlezrd
+Author-email: gp3t1 <jeremy.petit@gmail.com>
+Maintainer-email: gp3t1 <jeremy.petit@gmail.com>
+License-File: LICENSE.md
+Keywords: ai,context,mcp,server
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.13
+Requires-Dist: dependency-injector[pydantic2]>=4.48.3
+Requires-Dist: fastmcp>=3.2.4
+Requires-Dist: marko>=2.2.2
+Requires-Dist: mcp[cli]>=1.16.0
+Requires-Dist: pydantic
+Requires-Dist: pydantic-settings>=2.13.1
+Requires-Dist: python-frontmatter>=1.1.0
+Requires-Dist: python-json-logger>=4.1.0
+Requires-Dist: pyyaml>=6.0.3
+Requires-Dist: sqlalchemy>=2.0.48
+Requires-Dist: sqlmodel
+Requires-Dist: tiktoken>=0.12.0
+Requires-Dist: typer
+Requires-Dist: watchfiles>=1.1.1
+Description-Content-Type: text/markdown
+
+# mcp-remlezrd
+
+[![python](https://img.shields.io/badge/python-3.13%2B-blue)](https://www.python.org/)
+[![uv](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json)](https://github.com/astral-sh/uv)
+[![latest](https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/badges/release.svg?order_by=release_at&key_text=latest&key_width=55)](https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/releases/permalink/latest)
+[![coverage](https://gitlab.com/gp3t1/ai/mcp-remlezrd/badges/master/coverage.svg)](https://gitlab.com/gp3t1/ai/mcp-remlezrd)
+[![license](https://img.shields.io/gitlab/license/75754026)](https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/blob/master/LICENSE.md)
+
+MCP server for AI agent collaboration through structured, shareable resources.
+
+## Features
+
+### 1. Agent Autonomy for Context Loading
+
+The server empowers AI agents to self-discover and load team standards (development, design,
+architecture, etc.) without hard-coding context:
+
+- **Discovery tools** — Provide a searchable index of all project and shared standards so the agent
+  knows what resources exist before reading them.
+- **Native MCP resources** — Standards are exposed as MCP resources in Markdown format, directly
+  accessible by the client.
+- **Tool fallback** — If the MCP client does not support resources, the same content is available
+  via dedicated read tools.
+
+### 2. (Agent|Human)-Friendly Workflow
+
+Designed for collaboration between developers and AI agents:
+
+- **Human-first editing** — All resources are plain Markdown files with YAML frontmatter. Developers
+  can read, edit, and version them with standard tools.
+- **Agent consumption** — Agents read resources natively via MCP (or through tools when resource
+  support is absent).
+- **Agent-assisted maintenance** — Agents can create, update, and delete standards through CRUD
+  tools, keeping conventions alive without manual boilerplate.
+
+### 3. Modular Standards, Universal Access
+
+- **Specialized resources** — Standards, procedures, and knowledge are stored in dedicated,
+  maintainable files instead of monolithic `README.md` or `AGENTS.md` .
+- **Universal format** — Uses the MCP protocol, avoiding IDE-specific formats such as `.cursorrules`
+  , `.windsurfrules` , or `CLAUDE.md` .
+
+### 4. Project-Only Resources (scoped to `cwd`)
+
+| Resource | Status | Description |
+|---|---|---|
+| **ADR** | `experiment` | Architecture Decision Records — capture technical choices, trade-offs, and their rationale. |
+| **Glossary** | `experiment` | Term definitions and domain vocabulary — ensure consistent language across the team. |
+
+### 5. Shareable Resources (external directory)
+
+| Resource | Status | Description |
+|---|---|---|
+| **Rule** | `experiment` | Coding standards and constraints — enforceable guidelines for agent behavior. |
+| **Skill** | `experiment` | Actionable procedures and how-to guides — step-by-step recipes for common tasks. |
+
+## Getting Started
+
+### Starting RemLezrd MCP Server
+
+Run with default settings:
+
+```bash
+uv run mcp-remlezrd
+uv run mcp-remlezrd --no-shared
+uv run mcp-remlezrd --disable-resources skill,glossary
+uv run mcp-remlezrd --no-write-servers project,shareable
+```
+
+Run with custom paths and logging:
+
+```bash
+uv run mcp-remlezrd --log-file /tmp/remlezrd.log
+uv run mcp-remlezrd --no-write-resources rule,skill --resource-as-tool
+```
+
+> **NOTE:** `--shared` controls whether the shared directory is mounted at startup (a physical
+> storage concern). Use `--disable-servers`, `--disable-resources`, `--no-write-servers`, or
+> `--no-write-resources` to control which MCP components are exposed and their access mode
+> (read-write vs read-only). These are independent mechanisms.
+
+### Configure MCP Clients (IDE, Agents, etc)
+
+TODO
+
+### CLI Options and environment variables
+
+```txt
+Usage: mcp-remlezrd [OPTIONS]
+
+╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ --shared              --no-shared                    Enable/disable shared directory (Disable to use project-only mode)                  │
+│                                                      [env var: REMLEZRD_ENABLE_SHARED_DIR]                                               │
+│                                                      [default: shared]                                                                   │
+│ --resource-as-tool    --no-resource-as-tool          Only for CLIENT with NO 'MCP Resources' Support                                     │
+│                                                      [env var: REMLEZRD_RESOURCES_AS_TOOLS]                                              │
+│                                                      [default: no-resource-as-tool]                                                      │
+│ --log-file                                     PATH  Path to log file [env var: REMLEZRD_LOG_FILE]                                       │
+│ --help                                               Show this message and exit.                                                         │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ Options: RemLezrd Features Activation (support comma-separated lists) ──────────────────────────────────────────────────────────────────╮
+│ --disable-servers           [project|shareable|onboarding]  List of servers to disable [env var: REMLEZRD_DISABLE_SERVERS]               │
+│ --no-write-servers          [project|shareable|onboarding]  List of servers to disable RW tools from                                     │
+│                                                             [env var: REMLEZRD_NO_WRITE_SERVERS]                                         │
+│ --disable-resources         [adr|glossary|rule|skill]       List of resource types to disable [env var: REMLEZRD_DISABLE_RESOURCES]      │
+│ --no-write-resources        [adr|glossary|rule|skill]       List of resource types to disable RW tools from                              │
+│                                                             [env var: REMLEZRD_NO_WRITE_RESOURCES]                                       │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+
+Other Environment Variables:
+🔹 Console handler log level  [env var: REMLEZRD_LOG_LEVEL]         [default: 'WARNING']
+🔹 File handler log level     [env var: REMLEZRD_LOG_FILE_LEVEL]    [default: 'INFO']
+🔹 Abs. path to Project dir   [env var: REMLEZRD_OVERRIDE_CWD]      [default: '<cwd>']
+🔹 Abs. path to Shared dir    [env var: REMLEZRD_SHARED_DIR]        [default: '~/.local/share/remlezrd']
+🔹 Subdir for ADRs            [env var: REMLEZRD_SUBDIR_ADR]        [default: 'docs/_adrs']
+🔹 Subdir for Glossaries      [env var: REMLEZRD_SUBDIR_GLOSSARY]   [default: 'docs/_glossary']
+🔹 Subdir for Rules           [env var: REMLEZRD_SUBDIR_RULE]       [default: 'docs/_rules']
+🔹 Subdir for Skills          [env var: REMLEZRD_SUBDIR_SKILL]      [default: 'docs/_skills']
+```

mcp_remlezrd-0.1.0/README.md

@@ -0,0 +1,119 @@
+# mcp-remlezrd
+
+[![python](https://img.shields.io/badge/python-3.13%2B-blue)](https://www.python.org/)
+[![uv](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json)](https://github.com/astral-sh/uv)
+[![latest](https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/badges/release.svg?order_by=release_at&key_text=latest&key_width=55)](https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/releases/permalink/latest)
+[![coverage](https://gitlab.com/gp3t1/ai/mcp-remlezrd/badges/master/coverage.svg)](https://gitlab.com/gp3t1/ai/mcp-remlezrd)
+[![license](https://img.shields.io/gitlab/license/75754026)](https://gitlab.com/gp3t1/ai/mcp-remlezrd/-/blob/master/LICENSE.md)
+
+MCP server for AI agent collaboration through structured, shareable resources.
+
+## Features
+
+### 1. Agent Autonomy for Context Loading
+
+The server empowers AI agents to self-discover and load team standards (development, design,
+architecture, etc.) without hard-coding context:
+
+- **Discovery tools** — Provide a searchable index of all project and shared standards so the agent
+  knows what resources exist before reading them.
+- **Native MCP resources** — Standards are exposed as MCP resources in Markdown format, directly
+  accessible by the client.
+- **Tool fallback** — If the MCP client does not support resources, the same content is available
+  via dedicated read tools.
+
+### 2. (Agent|Human)-Friendly Workflow
+
+Designed for collaboration between developers and AI agents:
+
+- **Human-first editing** — All resources are plain Markdown files with YAML frontmatter. Developers
+  can read, edit, and version them with standard tools.
+- **Agent consumption** — Agents read resources natively via MCP (or through tools when resource
+  support is absent).
+- **Agent-assisted maintenance** — Agents can create, update, and delete standards through CRUD
+  tools, keeping conventions alive without manual boilerplate.
+
+### 3. Modular Standards, Universal Access
+
+- **Specialized resources** — Standards, procedures, and knowledge are stored in dedicated,
+  maintainable files instead of monolithic `README.md` or `AGENTS.md` .
+- **Universal format** — Uses the MCP protocol, avoiding IDE-specific formats such as `.cursorrules`
+  , `.windsurfrules` , or `CLAUDE.md` .
+
+### 4. Project-Only Resources (scoped to `cwd`)
+
+| Resource | Status | Description |
+|---|---|---|
+| **ADR** | `experiment` | Architecture Decision Records — capture technical choices, trade-offs, and their rationale. |
+| **Glossary** | `experiment` | Term definitions and domain vocabulary — ensure consistent language across the team. |
+
+### 5. Shareable Resources (external directory)
+
+| Resource | Status | Description |
+|---|---|---|
+| **Rule** | `experiment` | Coding standards and constraints — enforceable guidelines for agent behavior. |
+| **Skill** | `experiment` | Actionable procedures and how-to guides — step-by-step recipes for common tasks. |
+
+## Getting Started
+
+### Starting RemLezrd MCP Server
+
+Run with default settings:
+
+```bash
+uv run mcp-remlezrd
+uv run mcp-remlezrd --no-shared
+uv run mcp-remlezrd --disable-resources skill,glossary
+uv run mcp-remlezrd --no-write-servers project,shareable
+```
+
+Run with custom paths and logging:
+
+```bash
+uv run mcp-remlezrd --log-file /tmp/remlezrd.log
+uv run mcp-remlezrd --no-write-resources rule,skill --resource-as-tool
+```
+
+> **NOTE:** `--shared` controls whether the shared directory is mounted at startup (a physical
+> storage concern). Use `--disable-servers`, `--disable-resources`, `--no-write-servers`, or
+> `--no-write-resources` to control which MCP components are exposed and their access mode
+> (read-write vs read-only). These are independent mechanisms.
+
+### Configure MCP Clients (IDE, Agents, etc)
+
+TODO
+
+### CLI Options and environment variables
+
+```txt
+Usage: mcp-remlezrd [OPTIONS]
+
+╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ --shared              --no-shared                    Enable/disable shared directory (Disable to use project-only mode)                  │
+│                                                      [env var: REMLEZRD_ENABLE_SHARED_DIR]                                               │
+│                                                      [default: shared]                                                                   │
+│ --resource-as-tool    --no-resource-as-tool          Only for CLIENT with NO 'MCP Resources' Support                                     │
+│                                                      [env var: REMLEZRD_RESOURCES_AS_TOOLS]                                              │
+│                                                      [default: no-resource-as-tool]                                                      │
+│ --log-file                                     PATH  Path to log file [env var: REMLEZRD_LOG_FILE]                                       │
+│ --help                                               Show this message and exit.                                                         │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ Options: RemLezrd Features Activation (support comma-separated lists) ──────────────────────────────────────────────────────────────────╮
+│ --disable-servers           [project|shareable|onboarding]  List of servers to disable [env var: REMLEZRD_DISABLE_SERVERS]               │
+│ --no-write-servers          [project|shareable|onboarding]  List of servers to disable RW tools from                                     │
+│                                                             [env var: REMLEZRD_NO_WRITE_SERVERS]                                         │
+│ --disable-resources         [adr|glossary|rule|skill]       List of resource types to disable [env var: REMLEZRD_DISABLE_RESOURCES]      │
+│ --no-write-resources        [adr|glossary|rule|skill]       List of resource types to disable RW tools from                              │
+│                                                             [env var: REMLEZRD_NO_WRITE_RESOURCES]                                       │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+
+Other Environment Variables:
+🔹 Console handler log level  [env var: REMLEZRD_LOG_LEVEL]         [default: 'WARNING']
+🔹 File handler log level     [env var: REMLEZRD_LOG_FILE_LEVEL]    [default: 'INFO']
+🔹 Abs. path to Project dir   [env var: REMLEZRD_OVERRIDE_CWD]      [default: '<cwd>']
+🔹 Abs. path to Shared dir    [env var: REMLEZRD_SHARED_DIR]        [default: '~/.local/share/remlezrd']
+🔹 Subdir for ADRs            [env var: REMLEZRD_SUBDIR_ADR]        [default: 'docs/_adrs']
+🔹 Subdir for Glossaries      [env var: REMLEZRD_SUBDIR_GLOSSARY]   [default: 'docs/_glossary']
+🔹 Subdir for Rules           [env var: REMLEZRD_SUBDIR_RULE]       [default: 'docs/_rules']
+🔹 Subdir for Skills          [env var: REMLEZRD_SUBDIR_SKILL]      [default: 'docs/_skills']
+```

mcp_remlezrd-0.1.0/docs/_policies/configuration.md

@@ -0,0 +1,99 @@
+---
+created_at: '2025-11-13'
+status: enforced
+tags:
+- configuration
+- cli
+- environment
+- storage
+- logging
+name: "configuration"
+description: "Configuration management policy"
+updated_at: '2025-11-13'
+---
+
+## Purpose
+
+This policy establishes standardized configuration management patterns to ensure consistent,
+predictable, and maintainable application configuration across all deployment environments. It
+prevents configuration drift, reduces deployment errors, and improves troubleshooting capabilities.
+
+## Principles
+
+- **Precedence Clarity**: Clear hierarchy for configuration source priority
+- **Environment Parity**: Same configuration mechanisms across all environments
+- **Discoverability**: All configuration options must be documented and accessible
+- **Security**: Sensitive configuration handled through secure channels
+- **Flexibility**: Support for both development and production deployment patterns
+
+## Rules
+
+### Configuration Precedence Order
+
+Configuration MUST follow this precedence order (highest to lowest priority):
+
+1. **CLI arguments** (highest priority)
+2. **Environment variables** (prefixed `REMLEZRD_`)
+3. **Default values** (defined in Pydantic model, lowest priority)
+
+### CLI Argument Conventions
+
+- **All CLI arguments MUST use kebab-case** (e.g., `--my-param`, `--custom-dir`)
+- **Arguments MUST have both short and long forms** where appropriate
+- **Help text MUST be descriptive** and include default values
+- **Boolean flags MUST use --flag/--no-flag pattern** as provided natively by Typer
+
+### Environment Variable Conventions
+
+- **All environment variables MUST be prefixed with `REMLEZRD_`**
+- **Variable names MUST use UPPER_SNAKE_CASE** after the prefix
+- **Examples**:
+  - `REMLEZRD_MY_STORAGE` for `--my-storage` argument
+  - `REMLEZRD_PARAM1` for `--param1` argument
+
+### Storage Configuration Requirements
+
+- **Shared storage path MUST be configurable**
+- **All project storage subdirectories MUST be configurable** relative to CWD
+
+### Logging Configuration Requirements
+
+- **Log level MUST be configurable** for debugging purposes
+- **Log file path MUST be configurable** for different deployment scenarios
+- **Debug mode MUST enable verbose logging** and framework internals
+- **Production mode MUST use appropriate log levels** for performance
+
+### Configuration Exposure Requirements
+
+- **Every configuration option MUST be exposed via both CLI argument and environment variable**
+- **Configuration validation MUST occur at startup** with clear error messages
+- **Default values MUST be documented** in help text and configuration schemas
+- **Configuration state MUST be logged** at startup (excluding sensitive values)
+
+### Development Tools Configuration
+
+- **pyproject.toml SHOULD be used** for centralized configuration of development tools
+- **Global scope**: Configuration precedence and validation patterns apply to all tools
+- **Avoid configuration fragmentation** : Prefer single configuration files over multiple
+  tool-specific files
+- **Integration**: Development toolchain configurations follow the same precedence order
+
+### Configuration Validation
+
+- **Path configurations MUST be validated** for basic accessibility
+- **Invalid configurations MUST provide clear error messages**
+- **Relative paths MUST be resolved consistently**
+- **Environment variable parsing MUST handle basic type conversion**
+
+## Exceptions
+
+- **Container deployments** may require different default paths with proper documentation
+- **CI/CD environments** may need special configuration handling for ephemeral filesystems
+- **Development setups** may use different default values with proper environment
+  detection
+
+## References
+
+- [Server Configuration Specification](../_specs/infra/configuration.md) - Detailed configuration parameters
+- [Environment Setup Guide](../../README.md#configuration) - User-facing configuration documentation
+- [Pydantic Settings](https://docs.pydantic.dev/latest/concepts/pydantic_settings/) - Configuration model implementation

mcp_remlezrd-0.1.0/docs/_policies/development-tools.md

@@ -0,0 +1,105 @@
+---
+created_at: '2025-11-13'
+status: enforced
+tags:
+- development
+- tools
+- ci
+- code-quality
+- debugging
+name: "development-tools"
+description: "Development tools and workflow policy"
+updated_at: '2025-11-13'
+---
+
+## Purpose
+
+This policy establishes standardized development toolchain and practices to ensure consistent code
+quality, maintainable build processes, and efficient debugging capabilities across the project. It
+prevents tool fragmentation, reduces onboarding complexity, and maintains uniform development
+experience.
+
+## Principles
+
+- **Toolchain Consistency** : Same tools and configurations across all development environments
+- **Configuration Centralization**: Single source of truth for tool configurations
+- **Quality Automation**: Automated code formatting, linting, and type checking
+- **Efficient Debugging** : Standardized debugging and inspection tools for development workflow
+- **Build Reproducibility**: Consistent build orchestration and dependency management
+
+## Rules
+
+### Code Quality Tools
+
+- **ruff MUST be used** for both code formatting and linting
+  - **Formatting**: Enforce consistent code style automatically
+  - **Linting**: Catch code quality issues and potential bugs
+  - **Configuration** : `[tool.ruff.format]` and `[tool.ruff.lint]` sections in `pyproject.toml`
+- **Static type checking MUST use one of** (in order of preference):
+  - **ty** (preferred) - Fast, modern Python type checker written in Rust
+  - **pyrefly** or **basedpyright** - Alternative high-performance type checkers
+  - **pyright** - Microsoft's standard Python type checker
+  - **Purpose**: Catch type-related errors before runtime
+  - **Configuration** : `[tool.ty]` , `[tool.pyrefly]` , `[tool.basedpyright]` , or `[tool.pyright]`
+    section in `pyproject.toml`
+
+### Testing Framework
+
+- **pytest MUST be used** as the primary test engine
+  - **Purpose**: Run and validate functionality tests
+  - **Configuration**: `[tool.pytest.ini_options]` section in `pyproject.toml`
+  - **Integration**: Follow Testing Policy for test strategy and patterns
+
+### Package Management
+
+- **uv MUST be used** for Python dependency management
+  - **Purpose**: Manage dependencies and virtual environments efficiently
+  - **Integration** : Tasks in `Taskfile.yml` for dependency operations (e.g., `uv:deps:update` )
+
+### Build Orchestration
+
+- **Taskfile MUST be used** for build, test, and development task orchestration
+  - **Configuration**: `Taskfile.yml` in project root
+  - **Purpose**: Provide consistent interface for all development operations
+  - **Tasks** : Include standard tasks for build, test, lint, format, and dependency management
+
+### Configuration Management
+
+- **pyproject.toml MUST be the primary configuration file** for all Python tools
+  - **Avoid configuration fragmentation** : Do not create additional config files when
+    centralization is possible
+  - **Centralization** : All tool configurations (ruff, type checker, pytest, uv) in single file
+  - **Consistency**: Standardized configuration patterns across projects
+  - **Maintenance**: Single location for tool configuration updates
+
+### MCP Debugging Tools
+
+- **mcp-inspector SHOULD be integrated** for MCP server debugging and inspection
+  - **Purpose**: Real-time monitoring of MCP tools, resources, and interactions
+  - **Integration**: `task run:inspector` for piping MCP server output to inspector
+  - **Usage**: Development and debugging workflow enhancement
+
+### Tool Integration Requirements
+
+- **All tools MUST be integrated** into the build pipeline
+- **Configuration consistency MUST be maintained** across development and CI environments
+- **Documentation MUST include** setup instructions for the complete toolchain
+
+## Exceptions
+
+- **Legacy projects** may maintain existing toolchain until migration is feasible with proper
+  documentation
+- **Specialized tools** may be added for specific domains with justification and integration plan
+- **External tool constraints** may require alternative configurations with documented rationale
+
+## References
+
+- [Configuration Management Policy](./configuration.md) - Configuration precedence and patterns
+- [Testing Policy](./testing.md) - Test strategy and framework integration
+- [ruff Documentation](https://docs.astral.sh/ruff/) - Formatting and linting tool
+- [ty Documentation](https://github.com/astral-sh/ty) - Preferred static type checker
+- [pyrefly Documentation](https://pyrefly.org/) - Alternative static type checker
+- [basedpyright Documentation](https://github.com/detachhead/basedpyright) - Alternative static type checker
+- [pyright Documentation](https://microsoft.github.io/pyright/) - Standard static type checker
+- [pytest Documentation](https://docs.pytest.org/) - Testing framework
+- [Taskfile Documentation](https://taskfile.dev/) - Build orchestration tool