vnma 0.1.0__tar.gz

vnma-0.1.0/LICENSE

@@ -0,0 +1,38 @@
+Copyright (c) 2026, GrandKenzy / VNMA Team and Contributors.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice,
+   this list of conditions, and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions, and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Commercial Sale Restriction:
+   Direct commercial sale or resale of this software itself, in whole or in
+   substantial part, as a standalone product or service is strictly prohibited.
+   Use, modification, and execution of this software to manage dependencies
+   within proprietary or commercial applications is fully permitted without royalty.
+
+4. Vendor Share-Alike Distribution Requirement:
+   Any downstream distribution, vendoring bundle, fork, or sub-component derived
+   from this software must be distributed under these same license terms and include
+   a copy of this license.
+
+5. Neither the name of the copyright holder nor the names of its contributors
+   may be used to endorse or promote products derived from this software without
+   specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

vnma-0.1.0/PKG-INFO

@@ -0,0 +1,169 @@
+Metadata-Version: 2.4
+Name: vnma
+Version: 0.1.0
+Summary: Vendor Manager for Python — hermetic, zero-venv dependency management.
+Author: VNMA Team
+License: Copyright (c) 2026, GrandKenzy / VNMA Team and Contributors.
+        All rights reserved.
+        
+        Redistribution and use in source and binary forms, with or without
+        modification, are permitted provided that the following conditions are met:
+        
+        1. Redistributions of source code must retain the above copyright notice,
+           this list of conditions, and the following disclaimer.
+        
+        2. Redistributions in binary form must reproduce the above copyright notice,
+           this list of conditions, and the following disclaimer in the documentation
+           and/or other materials provided with the distribution.
+        
+        3. Commercial Sale Restriction:
+           Direct commercial sale or resale of this software itself, in whole or in
+           substantial part, as a standalone product or service is strictly prohibited.
+           Use, modification, and execution of this software to manage dependencies
+           within proprietary or commercial applications is fully permitted without royalty.
+        
+        4. Vendor Share-Alike Distribution Requirement:
+           Any downstream distribution, vendoring bundle, fork, or sub-component derived
+           from this software must be distributed under these same license terms and include
+           a copy of this license.
+        
+        5. Neither the name of the copyright holder nor the names of its contributors
+           may be used to endorse or promote products derived from this software without
+           specific prior written permission.
+        
+        THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+        ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+        WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+        IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+        INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+        BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+        DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+        LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+        OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+        ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+        
+Project-URL: Homepage, https://github.com/GrandKenzy/vnma
+Project-URL: Documentation, https://github.com/GrandKenzy/vnma/tree/main/docs
+Project-URL: Repository, https://github.com/GrandKenzy/vnma.git
+Project-URL: Bug Tracker, https://github.com/GrandKenzy/vnma/issues
+Keywords: vendoring,packaging,dependencies,hermetic,pip
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# VNMA (Vendor Manager)
+
+> **Status:** Beta (v0.1.0)  
+> **Platform Support:** CPython 3.11+ (Tested on Windows and Linux)
+
+`vnma` is a dependency and vendoring manager for Python projects. It manages project dependencies inside a local, isolated vendor directory (`vendor/` or `vendor_vnma/`) instead of creating or replicating full Python virtual environments (`venv`).
+
+---
+
+## Overview
+
+Traditional Python development relies on virtual environments, which duplicate the interpreter executable and standard library layout. While effective for system isolation, virtual environments introduce overhead in container builds, portable deployments, and shared team workflows where only runtime libraries are required.
+
+`vnma` addresses this by downloading, building, and extracting platform-compatible wheels directly into the project directory while maintaining runtime path isolation and native binary compatibility.
+
+### Key Capabilities
+
+* **Hermetic Path Isolation:** Sanitizes `sys.path` during execution to prevent accidental leakage from system or user `site-packages`.
+* **Static O(1) Binary Resolution:** Avoids filesystem tree traversal at startup by recording precomputed dynamic link library (DLL/SO) paths during installation.
+* **Transitive DAG Resolution:** Evaluates version constraints across dependency trees, evaluating PEP 508 environment markers and detecting version conflicts.
+* **Explicit Configuration (`vnma_config.toml`):** Allows local packages and complex dependencies to specify exact DLL directories, entry points, and export boundaries without heuristic guesswork.
+* **Multi-Source Support:** Installs packages from PyPI, local filesystem paths (monorepos), and remote Git repositories.
+* **Reproducible Builds:** Emits a deterministic `vnma.lock` tracking versions, sources, and binary metadata.
+* **Automatic IDE Configuration:** Generates configuration for Visual Studio Code (`extraPaths`) and JetBrains PyCharm (`.idea` and `.env`).
+
+---
+
+## Current Status: Beta Notice
+
+`vnma` is currently in **Beta**. While core workflows—such as installing native packages (`pygame-ce`), complex transitive graphs (`requests`), and local source trees—have been validated, edge cases exist across different platforms, compilers, and non-standard packaging layouts.
+
+Users are encouraged to verify builds in testing environments before deploying to critical production pipelines. See [docs/en/02-Advice/01-beta-status.md](docs/en/02-Advice/01-beta-status.md) for detailed considerations.
+
+---
+
+## Quickstart
+
+### Installation
+
+Install `vnma` using `pip`:
+
+```bash
+pip install -e .
+```
+
+### Basic Commands
+
+Initialize a project:
+```bash
+vnma init
+```
+
+Install a package from PyPI:
+```bash
+vnma install requests
+```
+
+Install a package from a local directory:
+```bash
+vnma install "C:/path/to/my-library"
+```
+
+Execute a script using the vendored runtime:
+```bash
+vnma run main.py
+```
+
+List installed packages:
+```bash
+vnma list
+```
+
+Prune orphaned packages not declared in `vnma.toml`:
+```bash
+vnma prune --dry-run
+vnma prune --yes
+```
+
+Restore dependencies in offline mode:
+```bash
+vnma install --offline
+```
+
+---
+
+## Documentation
+
+Full documentation is available in the `docs/` directory:
+
+* **Usage Guide:** [docs/en/01-Use/](docs/en/01-Use/)
+  * [01. Getting Started](docs/en/01-Use/01-getting-started.md)
+  * [02. Dependency Management](docs/en/01-Use/02-dependency-management.md)
+  * [03. Configuration Specifications](docs/en/01-Use/03-configuration-specs.md)
+  * [04. Runtime Execution Model](docs/en/01-Use/04-runtime-execution.md)
+  * [05. IDE Integration](docs/en/01-Use/05-ide-integration.md)
+* **Design & Guidance:** [docs/en/02-Advice/](docs/en/02-Advice/)
+  * [01. Beta Status & Stability](docs/en/02-Advice/01-beta-status.md)
+  * [02. Known Limitations](docs/en/02-Advice/02-known-limitations.md)
+  * [03. Future Roadmap](docs/en/02-Advice/03-future-roadmap.md)
+  * [04. Community Vision](docs/en/02-Advice/04-community-vision.md)
+
+---
+
+## License
+
+This software is released under a modified permissive license. Commercial resale of the tool itself is prohibited, and bundled distributions must retain reciprocal licensing. See [LICENSE](LICENSE) for terms.

vnma-0.1.0/README.md

@@ -0,0 +1,106 @@
+# VNMA (Vendor Manager)
+
+> **Status:** Beta (v0.1.0)  
+> **Platform Support:** CPython 3.11+ (Tested on Windows and Linux)
+
+`vnma` is a dependency and vendoring manager for Python projects. It manages project dependencies inside a local, isolated vendor directory (`vendor/` or `vendor_vnma/`) instead of creating or replicating full Python virtual environments (`venv`).
+
+---
+
+## Overview
+
+Traditional Python development relies on virtual environments, which duplicate the interpreter executable and standard library layout. While effective for system isolation, virtual environments introduce overhead in container builds, portable deployments, and shared team workflows where only runtime libraries are required.
+
+`vnma` addresses this by downloading, building, and extracting platform-compatible wheels directly into the project directory while maintaining runtime path isolation and native binary compatibility.
+
+### Key Capabilities
+
+* **Hermetic Path Isolation:** Sanitizes `sys.path` during execution to prevent accidental leakage from system or user `site-packages`.
+* **Static O(1) Binary Resolution:** Avoids filesystem tree traversal at startup by recording precomputed dynamic link library (DLL/SO) paths during installation.
+* **Transitive DAG Resolution:** Evaluates version constraints across dependency trees, evaluating PEP 508 environment markers and detecting version conflicts.
+* **Explicit Configuration (`vnma_config.toml`):** Allows local packages and complex dependencies to specify exact DLL directories, entry points, and export boundaries without heuristic guesswork.
+* **Multi-Source Support:** Installs packages from PyPI, local filesystem paths (monorepos), and remote Git repositories.
+* **Reproducible Builds:** Emits a deterministic `vnma.lock` tracking versions, sources, and binary metadata.
+* **Automatic IDE Configuration:** Generates configuration for Visual Studio Code (`extraPaths`) and JetBrains PyCharm (`.idea` and `.env`).
+
+---
+
+## Current Status: Beta Notice
+
+`vnma` is currently in **Beta**. While core workflows—such as installing native packages (`pygame-ce`), complex transitive graphs (`requests`), and local source trees—have been validated, edge cases exist across different platforms, compilers, and non-standard packaging layouts.
+
+Users are encouraged to verify builds in testing environments before deploying to critical production pipelines. See [docs/en/02-Advice/01-beta-status.md](docs/en/02-Advice/01-beta-status.md) for detailed considerations.
+
+---
+
+## Quickstart
+
+### Installation
+
+Install `vnma` using `pip`:
+
+```bash
+pip install -e .
+```
+
+### Basic Commands
+
+Initialize a project:
+```bash
+vnma init
+```
+
+Install a package from PyPI:
+```bash
+vnma install requests
+```
+
+Install a package from a local directory:
+```bash
+vnma install "C:/path/to/my-library"
+```
+
+Execute a script using the vendored runtime:
+```bash
+vnma run main.py
+```
+
+List installed packages:
+```bash
+vnma list
+```
+
+Prune orphaned packages not declared in `vnma.toml`:
+```bash
+vnma prune --dry-run
+vnma prune --yes
+```
+
+Restore dependencies in offline mode:
+```bash
+vnma install --offline
+```
+
+---
+
+## Documentation
+
+Full documentation is available in the `docs/` directory:
+
+* **Usage Guide:** [docs/en/01-Use/](docs/en/01-Use/)
+  * [01. Getting Started](docs/en/01-Use/01-getting-started.md)
+  * [02. Dependency Management](docs/en/01-Use/02-dependency-management.md)
+  * [03. Configuration Specifications](docs/en/01-Use/03-configuration-specs.md)
+  * [04. Runtime Execution Model](docs/en/01-Use/04-runtime-execution.md)
+  * [05. IDE Integration](docs/en/01-Use/05-ide-integration.md)
+* **Design & Guidance:** [docs/en/02-Advice/](docs/en/02-Advice/)
+  * [01. Beta Status & Stability](docs/en/02-Advice/01-beta-status.md)
+  * [02. Known Limitations](docs/en/02-Advice/02-known-limitations.md)
+  * [03. Future Roadmap](docs/en/02-Advice/03-future-roadmap.md)
+  * [04. Community Vision](docs/en/02-Advice/04-community-vision.md)
+
+---
+
+## License
+
+This software is released under a modified permissive license. Commercial resale of the tool itself is prohibited, and bundled distributions must retain reciprocal licensing. See [LICENSE](LICENSE) for terms.

vnma-0.1.0/plan.md

@@ -0,0 +1,243 @@
+# 📦 VNMA — Vendor Manager para Python
+**Documento de Planificación y Especificación Técnica**
+
+---
+
+## 1. Visión del Proyecto
+`vnma` (*Vendor Manager*) es una herramienta para Python diseñada para gestionar dependencias de proyectos mediante el patrón **vendoring**, eliminando la necesidad de crear y duplicar entornos virtuales completos (`venv`, copias completas de `python.exe`, librerías estándar).
+
+Inspirado en la ergonomía de herramientas modernas como `npm`, `pnpm` o `cargo`:
+- Las dependencias se instalan localmente en el proyecto en una carpeta aislada (`vendor/` o `vendor_vnma/`).
+- La configuración de dependencias es declarativa vía TOML.
+- No se suben binarios pesados al repositorio: un simple `vnma install` en cualquier máquina/arquitectura restaura las dependencias exactas y compatibles.
+- Cero fricción con IDEs (autocompletado inmediato en VS Code y PyCharm).
+
+---
+
+## 2. Estructura de Directorios
+
+```text
+mi-proyecto/
+├── .vscode/
+│   └── settings.json            <-- Generado/actualizado por vnma (extraPaths)
+├── .idea/
+│   └── mi-proyecto.iml          <-- Actualizado con sourceFolder vendor
+├── vendor/ (o vendor_vnma/)     <-- Ignorado en git automáticamente
+│   ├── .vnma_meta/
+│   │   ├── manifest.json        <-- Registro de archivos por paquete (para uninstall limpio)
+│   │   ├── python_version       <-- Versión de Python con la que se compiló/instaló
+│   │   └── .bin/                <-- Ejecutables CLI / wrappers (estilo node_modules/.bin)
+│   ├── pygame/                  <-- Código y binarios .pyd / DLLs
+│   ├── pygame-2.5.6.dist-info/
+│   └── __bootstrap__.py         <-- Inyector de sys.path y os.add_dll_directory
+├── .gitignore                   <-- vnma añade automáticamente vendor/
+├── vnma.toml                    <-- Declaración de dependencias del proyecto (o pyproject.toml)
+├── vnma.lock                    <-- Lockfile con versiones exactas, hashes y compatibilidad
+├── main.py
+└── test.py
+```
+
+### Reglas de selección de directorio:
+1. Si no existe ninguna carpeta: crear `vendor/`.
+2. Si `vendor/` existe y pertenece a otra herramienta (no contiene metadatos de vnma ni fue creado por él): usar `vendor_vnma/`.
+3. Si el usuario lo prefiere, permitir configurarlo vía `vnma.toml` (`[tool.vnma] vendor_dir = "custom_vendor"`).
+
+---
+
+## 3. Declaración de Dependencias y Lockfile (Exportabilidad)
+
+### A. Archivo de Configuración (`vnma.toml` o `pyproject.toml`)
+Para permitir exportar el código sin paquetes compilados (estilo `npm install`):
+
+```toml
+[project]
+name = "mi-proyecto"
+version = "0.1.0"
+
+[dependencies]
+pygame = ">=2.5.0, <2.6.0"
+requests = "^2.31.0"
+
+[dev-dependencies]
+pytest = "*"
+
+[tool.vnma]
+vendor_dir = "vendor"
+ide_integration = ["vscode", "pycharm"]
+```
+
+### B. `vnma.lock` (Reproducibilidad Garantizada)
+Guarda la versión exacta resuelta y los hashes de los Wheels para asegurar que cada máquina reconstruya el mismo árbol de dependencias:
+```json
+{
+  "version": "1.0",
+  "python_requires": ">=3.10",
+  "packages": {
+    "pygame": {
+      "version": "2.5.6",
+      "dependencies": {},
+      "hashes": ["sha256:..."]
+    }
+  }
+}
+```
+
+---
+
+## 4. Resolución e Instalación Multiplataforma
+
+### Flujo de `vnma install` (sin argumentos) o `vnma install .`:
+1. Lee `vnma.toml` (o sección `[tool.vnma]` en `pyproject.toml`).
+2. Comprueba si existe `vnma.lock`:
+   - Si existe, usa las versiones fijadas.
+   - Si no existe, resuelve el grafo de dependencias contra PyPI.
+3. **Detección de Arquitectura y Plataforma Anfitrión**:
+   - Detecta la versión de Python (`sys.version_info`), sistema operativo (`win32`, `linux`, `darwin`) y arquitectura (`amd64`, `arm64`).
+   - Busca el Wheel óptimo (`cp311-win_amd64.whl`, `manylinux_x86_64.whl`, etc.) o fallback a sdist/pure-python si aplica.
+4. **Caché Global de Paquetes (`~/.vnma/cache/wheels`)**:
+   - Evita volver a descargar ruedas si ya fueron bajadas anteriormente para otro proyecto.
+5. **Extracción y Registro**:
+   - Descomprime el Wheel en `vendor/`.
+   - Lee el archivo `RECORD` dentro del `.dist-info` y guarda el mapeo en `manifest.json`.
+6. **Guardado de versión de Python**:
+   - Escribe en `vendor/.vnma_meta/python_version` la tupla `(major, minor, micro)`.
+
+---
+
+## 5. Soporte de Binarios, DLLs y Extensiones C/C++
+
+### El desafío en Windows (Python 3.8+)
+En Windows, Python 3.8+ ya no busca DLLs secundarias usando el `PATH` global del sistema ni carpetas relativas no registradas. Si una librería como `pygame` o `numpy` contiene DLLs empaquetadas (como `SDL2.dll` o `openblas.dll`), fallará al importarse a menos que se use `os.add_dll_directory()`.
+
+### Solución en VNMA:
+1. **Archivo `__bootstrap__.py` generado en `vendor/`**:
+   ```python
+   import sys
+   import os
+
+   VENDOR_ROOT = os.path.dirname(os.path.abspath(__file__))
+
+   # 1. Inyectar sys.path prioritario
+   if VENDOR_ROOT not in sys.path:
+       sys.path.insert(0, VENDOR_ROOT)
+
+   # 2. Registrar directorios con DLLs en Windows
+   if sys.platform == "win32" and hasattr(os, "add_dll_directory"):
+       os.add_dll_directory(VENDOR_ROOT)
+       for root, dirs, files in os.walk(VENDOR_ROOT):
+           if any(f.lower().endswith(".dll") for f in files):
+               try:
+                   os.add_dll_directory(root)
+               except OSError:
+                   pass
+   ```
+2. **Métodos de Consumo por el Usuario**:
+   - **Opción A (automática con runner)**: `vnma run main.py` inyecta automáticamente el bootstrap antes de arrancar.
+   - **Opción B (código nativo sin CLI)**: Al inicio de `main.py`, el usuario solo necesita:
+     ```python
+     import vendor.__bootstrap__
+     import pygame
+     ```
+
+---
+
+## 6. Integración Inteligente con Git (`.gitignore`)
+
+Al ejecutar `vnma init`, `vnma install`, o cuando se detecte un `.gitignore`:
+1. Verifica si `.gitignore` existe en la raíz del proyecto. Si no existe, pregunta o lo crea.
+2. Comprueba si el directorio vendor ya está ignorado (evitando duplicados mediante comprobación de regex/línea exacta).
+3. Añade un bloque limpio y delimitado:
+   ```gitignore
+   # --- VNMA (Vendor Manager) ---
+   /vendor/
+   /vendor_vnma/
+   vnma_cache/
+   ```
+
+---
+
+## 7. Integración con IDEs (VS Code y PyCharm)
+
+Para que los IDEs reconozcan los paquetes, ofrezcan autocompletado y análisis estático de tipos:
+
+### A. Visual Studio Code
+Actualiza o crea `.vscode/settings.json` sin borrar configuraciones existentes del usuario:
+```json
+{
+  "python.analysis.extraPaths": ["./vendor"],
+  "python.autoComplete.extraPaths": ["./vendor"]
+}
+```
+
+### B. PyCharm
+- Detecta archivos `.idea/*.iml` y agrega `<sourceFolder url="file://$MODULE_DIR$/vendor" isTestSource="false" />`.
+- Como salvaguarda adicional universal, crea o actualiza un archivo `.env` en la raíz del proyecto con `PYTHONPATH=./vendor`, que PyCharm carga de forma nativa en todas sus configuraciones de ejecución y consola.
+
+### C. Generación de Stubs para Binarios (.pyd)
+- Para paquetes compilados que no incluyan archivos `.pyi` de fábrica, `vnma` incluirá una opción `vnma stubs generate` para inspeccionar los `.pyd` y generar stubs con firmas de funciones, garantizando autocompletado perfecto.
+
+---
+
+## 8. CLI y Binarios Ejecutables (`.bin` estilo `npx`)
+
+Cuando se instalan herramientas de línea de comandos en `vendor/` (por ejemplo `black`, `flake8`, `pytest`):
+- Los Wheels incluyen scripts en `nombre_paquete.data/scripts/` o definen `entry_points` en `entry_points.txt`.
+- `vnma` generará wrappers ejecutables en `vendor/.vnma_meta/.bin/` (archivos `.bat` / `.cmd` en Windows y scripts bash en Unix).
+- Comando `vnma exec <tool>`:
+  ```bash
+  vnma exec pytest
+  vnma exec black .
+  ```
+
+---
+
+## 9. Detección de Desajustes de Versión de Python
+
+Si un usuario instaló `vendor/` usando Python 3.10 y luego abre el proyecto con Python 3.12 (o viceversa):
+- Los binarios `.pyd` de Python 3.10 fallarán inmediatamente con errores Crípticos de importación (`DLL load failed: specified module could not be found`).
+- `vnma` guarda la versión activa en `vendor/.vnma_meta/python_version`.
+- Al ejecutar `vnma run` o invocar el bootstrap, verifica:
+  ```text
+  [WARNING] 'vendor/' fue construido con Python 3.10.4, pero estás ejecutando Python 3.12.1.
+  Los paquetes con binarios compilados podrían fallar.
+  Ejecuta 'vnma install --rebuild' para reinstalar para la versión actual.
+  ```
+
+---
+
+## 10. Catálogo de Comandos de `vnma`
+
+| Comando | Descripción |
+| :--- | :--- |
+| `vnma init` | Crea `vnma.toml`, configura `.gitignore` y sincroniza IDEs. |
+| `vnma install` | Instala todas las dependencias declaradas en `vnma.toml` / `vnma.lock`. |
+| `vnma install <pkg> [flags]` | Descarga e instala un paquete específico (ej: `vnma install pygame==2.5.6`). |
+| `vnma uninstall <pkg>` | Desinstala un paquete y elimina sus archivos según su `RECORD`. |
+| `vnma prune` | Elimina del directorio `vendor/` cualquier paquete que no esté en `vnma.toml`. |
+| `vnma run <script.py>` | Ejecuta un script inyectando `vendor/` y DLLs en el intérprete del sistema. |
+| `vnma exec <binary>` | Ejecuta un CLI instalado en `vendor/` (ej: `vnma exec pytest`). |
+| `vnma sync-ide` | Regenera configuraciones de VS Code y PyCharm. |
+| `vnma check` | Valida compatibilidad de binarios, versiones de Python y salud de `vendor/`. |
+
+---
+
+## 11. Hoja de Ruta de Implementación (Fases)
+
+1. **Fase 1: Módulo Core y Descargador de Wheels**
+   - Lógica de detección de plataforma y tags (`packaging.tags` / `sys_tags`).
+   - Cliente de descarga PyPI con caché en disco.
+   - Extractor de Wheels y gestor de carpetas `vendor/` / `vendor_vnma/`.
+2. **Fase 2: Desinstalador y Manifiesto**
+   - Parseo de `RECORD` e índices de metadatos.
+   - Limpieza de paquetes y dependencias no compartidas.
+3. **Fase 3: Declaratividad (`vnma.toml` & `vnma.lock`)**
+   - Parser TOML.
+   - Comando `vnma install` estilo `npm install`.
+4. **Fase 4: Runtime Bootstrap & Windows DLLs**
+   - Generación de `vendor/__bootstrap__.py`.
+   - Comando `vnma run`.
+5. **Fase 5: Sincronización de Entorno (Git & IDEs)**
+   - Modificador idempotente de `.gitignore`.
+   - Modificador de `.vscode/settings.json`, `.idea/` y `.env`.
+6. **Fase 6: CLI Definitiva y Pruebas Reales**
+   - Pruebas end-to-end con `pygame` y paquetes binarios en Windows.

vnma-0.1.0/pyproject.toml

@@ -0,0 +1,41 @@
+[build-system]
+requires = ["setuptools>=61.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "vnma"
+version = "0.1.0"
+description = "Vendor Manager for Python — hermetic, zero-venv dependency management."
+readme = "README.md"
+license = { file = "LICENSE" }
+requires-python = ">=3.11"
+authors = [
+    { name = "VNMA Team" }
+]
+keywords = ["vendoring", "packaging", "dependencies", "hermetic", "pip"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Topic :: Software Development :: Build Tools",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Operating System :: OS Independent",
+]
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/GrandKenzy/vnma"
+Documentation = "https://github.com/GrandKenzy/vnma/tree/main/docs"
+Repository = "https://github.com/GrandKenzy/vnma.git"
+"Bug Tracker" = "https://github.com/GrandKenzy/vnma/issues"
+
+[project.scripts]
+vnma = "vnma.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["."]
+include = ["vnma*"]
+exclude = ["tests*", "docs*"]

vnma-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+