mmu-cli 0.1.0.dev0__tar.gz → 0.1.1__tar.gz

{mmu_cli-0.1.0.dev0 → mmu_cli-0.1.1}/.gitignore

@@ -1,269 +1,301 @@
-# Byte-compiled / optimized / DLL files
-__pycache__/
-*.py[codz]
-*$py.class
-
-# C extensions
-*.so
-
-# Distribution / packaging
-.Python
-build/
-develop-eggs/
-dist/
-downloads/
-eggs/
-.eggs/
-lib/
-lib64/
-parts/
-sdist/
-var/
-wheels/
-share/python-wheels/
-*.egg-info/
-.installed.cfg
-*.egg
-MANIFEST
-
-# PyInstaller
-#   Usually these files are written by a python script from a template
-#   before PyInstaller builds the exe, so as to inject date/other infos into it.
-*.manifest
-*.spec
-
-# Installer logs
-pip-log.txt
-pip-delete-this-directory.txt
-
-# Unit test / coverage reports
-htmlcov/
-.tox/
-.nox/
-.coverage
-.coverage.*
-.cache
-nosetests.xml
-coverage.xml
-*.cover
-*.py.cover
-.hypothesis/
-.pytest_cache/
-cover/
-
-# mutmut (mutation testing) : bac a sable et cache de campagne, jamais commites
-mutants/
-.mutmut-cache*
-
-# Translations
-*.mo
-*.pot
-
-# Django stuff:
-*.log
-local_settings.py
-db.sqlite3
-db.sqlite3-journal
-
-# Flask stuff:
-instance/
-.webassets-cache
-
-# Scrapy stuff:
-.scrapy
-
-# Sphinx documentation
-docs/_build/
-
-# PyBuilder
-.pybuilder/
-target/
-
-# Jupyter Notebook
-.ipynb_checkpoints
-
-# IPython
-profile_default/
-ipython_config.py
-
-# pyenv
-#   For a library or package, you might want to ignore these files since the code is
-#   intended to run in multiple environments; otherwise, check them in:
-# .python-version
-
-# pipenv
-#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
-#   However, in case of collaboration, if having platform-specific dependencies or dependencies
-#   having no cross-platform support, pipenv may install dependencies that don't work, or not
-#   install all needed dependencies.
-# Pipfile.lock
-
-# UV
-#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-# uv.lock
-
-# poetry
-#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
-# poetry.lock
-# poetry.toml
-
-# pdm
-#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
-#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
-#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
-# pdm.lock
-# pdm.toml
-.pdm-python
-.pdm-build/
-
-# pixi
-#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
-# pixi.lock
-#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
-#   in the .venv directory. It is recommended not to include this directory in version control.
-.pixi
-
-# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
-__pypackages__/
-
-# Celery stuff
-celerybeat-schedule
-celerybeat.pid
-
-# Redis
-*.rdb
-*.aof
-*.pid
-
-# RabbitMQ
-mnesia/
-rabbitmq/
-rabbitmq-data/
-
-# ActiveMQ
-activemq-data/
-
-# SageMath parsed files
-*.sage.py
-
-# Environments
-.env
-.envrc
-.venv
-env/
-venv/
-ENV/
-env.bak/
-venv.bak/
-
-# Spyder project settings
-.spyderproject
-.spyproject
-
-# Rope project settings
-.ropeproject
-
-# mkdocs documentation
-/site
-
-# mypy
-.mypy_cache/
-.dmypy.json
-dmypy.json
-
-# Pyre type checker
-.pyre/
-
-# pytype static type analyzer
-.pytype/
-
-# Cython debug symbols
-cython_debug/
-
-# PyCharm
-#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
-#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
-#   and can be added to the global gitignore or merged into this file.  For a more nuclear
-#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
-# .idea/
-
-# Abstra
-#   Abstra is an AI-powered process automation framework.
-#   Ignore directories containing user credentials, local state, and settings.
-#   Learn more at https://abstra.io/docs
-.abstra/
-
-# Visual Studio Code
-#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
-#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
-#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
-#   you could uncomment the following to ignore the entire vscode folder
-# .vscode/
-# Temporary file for partial code execution
-tempCodeRunnerFile.py
-
-# Ruff stuff:
-.ruff_cache/
-
-# PyPI configuration file
-.pypirc
-
-# Marimo
-marimo/_static/
-marimo/_lsp/
-__marimo__/
-
-# Streamlit
-.streamlit/secrets.toml
-
-# .claude/skills/ etait ignore ici (jonction locale vers .agents/skills, deja
-# versionnes la-bas). Reversé le 2026-08-05, sur decision d'Egan: dans un
-# environnement distant (claude.ai/code), chaque session repart d'un clone
-# frais du depot, donc un dossier non suivi disparaissait a chaque nouvelle
-# session. Les liens symboliques commites ici sont legers (le blob ne porte
-# que la cible du lien, jamais une copie de SKILL.md): .agents/skills/ reste
-# la seule source de contenu, .claude/skills/ n'est qu'un index de decouverte
-# que Claude Code sait scanner nativement.
-
-# Etat local de Claude Code, propre a la machine et jamais partageable:
-# settings.local.json porte des chemins absolus Windows et l'URL du proxy
-# headroom; .headroom_wrap_marker.json est un marqueur de session vivante
-# (pid + port), reecrit a chaque demarrage. La config partagee du depot reste
-# .claude/settings.json, qui lui est versionne.
-.claude/settings.local.json
-.claude/.headroom_wrap_marker.json
-
-# Apercus de correction couleur: 35 Mo regenerables en une commande
-# (scripts/research/preview_color_correction.py --images)
-_bmad-output/test-artifacts/apercu-correction/
-mixed_media_utility.code-workspace
-
-# Captures de l'interface (scripts/gui/capturer_ecrans.py). Elles se
-# regenerent en une commande et changent a chaque passe de chrome : les
-# versionner ferait un diff binaire a chaque commit de design.
-captures-gui/
-
-# Journal de la sonde clavier jetable (vague 1 bis) : une sortie de mesure,
-# regeneree a chaque lancement, jamais un livrable.
-_bmad-output/planning-artifacts/ux-designs/*/trace_clavier.log
-
-# Bancs de mesure des agents (revues, campagnes de mutation). Regeneres a
-# chaque campagne, et une copie d arbre y pese jusqu a 4,5 Go : une couche de
-# revue en a laisse 5309 fichiers non suivis le 2026-08-28, que git status
-# rendait illisible. Les mesures vivent dans les rapports, pas ici.
-scratchpad/
-# Les courses de scripts/mesure/mesure.py : des mesures, pas des sources.
-.mesures/
-
-# --- Dossier de travail local, JAMAIS versionne (arbitrage Egan, 2026-09-03) ---
-# `projects/` porte les rushes, scans et planches reels. Il portait 97 % du volume
-# Git LFS du depot (2 217 Mo) et AUCUN test ne le lisait -- les occurrences de
-# `projects/` dans `tests/` sont toutes dans des commentaires. Verbatim d Egan :
-# << c est un dossier qui a vocation a rester local, tout fichier qui devra etre
-# partage devra passer par tests/ >>.
-projects/
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# mutmut (mutation testing) : bac a sable et cache de campagne, jamais commites
+mutants/
+.mutmut-cache*
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   TRANCHE ICI le 2026-09-10 : ce depot declare ses dependances dans
+#   `requirements.txt` et `pyproject.toml`, et `uv` n'apparait dans AUCUN
+#   workflow, AUCUNE page de documentation et AUCUN script. Le `uv.lock`
+#   versionne jusque-la portait TROIS lignes et verrouillait ZERO paquet :
+#   il annoncait une chaine d'outillage qui n'existe pas.
+uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# .claude/skills/ etait ignore ici (jonction locale vers .agents/skills, deja
+# versionnes la-bas). Reversé le 2026-08-05, sur decision d'Egan: dans un
+# environnement distant (claude.ai/code), chaque session repart d'un clone
+# frais du depot, donc un dossier non suivi disparaissait a chaque nouvelle
+# session. Les liens symboliques commites ici sont legers (le blob ne porte
+# que la cible du lien, jamais une copie de SKILL.md): .agents/skills/ reste
+# la seule source de contenu, .claude/skills/ n'est qu'un index de decouverte
+# que Claude Code sait scanner nativement.
+
+# Etat local de Claude Code, propre a la machine et jamais partageable:
+# settings.local.json porte des chemins absolus Windows et l'URL du proxy
+# headroom; .headroom_wrap_marker.json est un marqueur de session vivante
+# (pid + port), reecrit a chaque demarrage. La config partagee du depot reste
+# .claude/settings.json, qui lui est versionne.
+.claude/settings.local.json
+.claude/.headroom_wrap_marker.json
+
+# Apercus de correction couleur: 35 Mo regenerables en une commande
+# (scripts/research/preview_color_correction.py --images)
+_bmad-output/test-artifacts/apercu-correction/
+mixed_media_utility.code-workspace
+
+# Captures de l'interface (scripts/gui/capturer_ecrans.py). Elles se
+# regenerent en une commande et changent a chaque passe de chrome : les
+# versionner ferait un diff binaire a chaque commit de design.
+captures-gui/
+
+# Journal de la sonde clavier jetable (vague 1 bis) : une sortie de mesure,
+# regeneree a chaque lancement, jamais un livrable.
+_bmad-output/planning-artifacts/ux-designs/*/trace_clavier.log
+
+# Bancs de mesure des agents (revues, campagnes de mutation). Regeneres a
+# chaque campagne, et une copie d arbre y pese jusqu a 4,5 Go : une couche de
+# revue en a laisse 5309 fichiers non suivis le 2026-08-28, que git status
+# rendait illisible. Les mesures vivent dans les rapports, pas ici.
+scratchpad/
+# Les courses de scripts/mesure/mesure.py : des mesures, pas des sources.
+.mesures/
+# Les worktrees que le harnais cree pour isoler un agent (`isolation: worktree`).
+# Meme motif que `scratchpad/` juste au-dessus, et le meme ordre de grandeur :
+# une revue en trois couches en ouvre TROIS, chacune etant une copie complete de
+# l arbre. Ils sont deja des arbres git a part entiere -- les versionner
+# reviendrait a commiter le depot dans le depot. Pose le 2026-09-08, quand la
+# revue de la story 8.10 les a fait apparaitre en non suivis.
+.claude/worktrees/
+
+# --- Dossier de travail local, JAMAIS versionne (arbitrage Egan, 2026-09-03) ---
+# `projects/` porte les rushes, scans et planches reels. Il portait 97 % du volume
+# Git LFS du depot (2 217 Mo) et AUCUN test ne le lisait -- les occurrences de
+# `projects/` dans `tests/` sont toutes dans des commentaires. Verbatim d Egan :
+# << c est un dossier qui a vocation a rester local, tout fichier qui devra etre
+# partage devra passer par tests/ >>.
+projects/
+
+# --- Residus de racine retires le 2026-09-10 (LOT 4A du nettoyage) ---
+# Trois familles mesurees SANS LECTEUR -- zero construction de chemin sur l AST
+# de `tests/`, `src/` et `scripts/`, et zero lecture ailleurs.
+#
+# `temp/` : quatre comptes rendus d experience d aout 2026 plus un brief. Ils
+# ne sont LUS par rien ; ils sont ECRITS par quatre bancs de recherche
+# (`scripts/research/{qr_feasibility_experiment,codec_metadata_experiment,
+# encode_robustness_bench}.py` et la cible de mesure de
+# `build_measurement_target.py`), qui les REGENERENT a la demande. C est donc
+# exactement le cas de `projects/` : une sortie locale, pas une source. Les
+# stories qui les citent (4.3, 4.6, 6.0, 6.3) citent une PROVENANCE, et leurs
+# chiffres sont deja repris dans les stories elles-memes.
+temp/
+#
+# `.serena/` : configuration d un serveur LSP tiers, entree le 2026-08-17 par
+# un commit tiers, hors perimetre de la story 5.22 qui l a subie (finding
+# `[Review][Defer]` de cette story, et question ouverte de `deferred-work.md`).
+# Le retrait tranche cette question : outillage d un poste, pas du depot.
+.serena/