modulatio 0.9.4__tar.gz

modulatio-0.9.4/.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,120 @@
+name: Bug report
+description: Something is broken or behaves incorrectly.
+title: "[bug]: "
+labels: ["bug", "status:triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug. Please fill in the form so the maintainer
+        and triage automation can route it. If Modulatio crashed and dumped
+        a log to `~/.config/modulatio/crashes/`, paste it into the **Logs**
+        field below — the log is auto-redacted for common secret-shaped
+        flags but please re-check before pasting.
+
+  - type: input
+    id: modulatio-version
+    attributes:
+      label: Modulatio version
+      description: Output of `pip show modulatio | grep Version` or the tag/SHA you installed from.
+      placeholder: e.g. 0.1.0
+    validations:
+      required: true
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python version
+      placeholder: e.g. 3.12.3
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: OS / platform
+      placeholder: e.g. Ubuntu 24.04, macOS 14.5
+    validations:
+      required: true
+
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      description: |
+        - **critical**: data loss, security, or fully unusable
+        - **high**: major feature broken or wrong
+        - **medium**: workaround exists; degraded UX
+        - **low**: cosmetic, edge case, or minor polish
+      options:
+        - critical
+        - high
+        - medium
+        - low
+      default: 2
+    validations:
+      required: true
+
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component
+      options:
+        - engine (plan execution, dispatch, daemon, runner)
+        - cli (subcommands, argparse, output)
+        - tui (terminal UI, panes, F-keys)
+        - wizard (first-run / setup)
+        - providers (LiteLLM, OAuth, model presets)
+        - standards (TQM standards, QC axes)
+        - packaging (pyproject, install, wheels)
+        - documentation
+        - other / unsure
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Reproduction steps
+      description: Minimum sequence of commands or actions that triggers the bug.
+      placeholder: |
+        1. Run `modulatio kickoff --code FOO`
+        2. Type "..." at the prompt
+        3. Observe ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / crash report
+      description: |
+        If Modulatio crashed, paste the contents of the most recent file
+        in `~/.config/modulatio/crashes/` here. Otherwise paste relevant
+        output from stderr or `~/.config/modulatio/daemon.log`.
+        The crash log is auto-redacted but please re-check before pasting.
+      render: shell
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+      description: Anything else that might matter — provider/model in use, plan config, recent changes, etc.
+    validations:
+      required: false

modulatio-0.9.4/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: How to file an effective issue
+    url: https://github.com/ModulatioAI/modulatio/blob/main/CONTRIBUTING.md
+    about: Read this first — what to include, how labels are applied, and how to attach a crash log.

modulatio-0.9.4/.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,58 @@
+name: Feature / enhancement
+description: Propose a new capability or an improvement to an existing one.
+title: "[feature]: "
+labels: ["enhancement", "status:triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for proposing an enhancement. The fields below help the
+        maintainer evaluate fit and avoid scope drift.
+
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component this would touch
+      options:
+        - engine
+        - cli
+        - tui
+        - wizard
+        - providers
+        - standards
+        - packaging
+        - documentation
+        - cross-cutting / unsure
+    validations:
+      required: true
+
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use case
+      description: What problem does this solve? What workflow does it enable?
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed
+    attributes:
+      label: Proposed solution
+      description: Sketch how it would look — CLI shape, config keys, behavior, etc.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Other approaches you weighed and why this one is preferred.
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+    validations:
+      required: false

modulatio-0.9.4/.github/ISSUE_TEMPLATE/regression.yml

@@ -0,0 +1,113 @@
+name: Regression report
+description: Worked in a prior version, broken now.
+title: "[regression]: "
+labels: ["bug", "regression", "status:triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template only when the same workflow worked in a prior
+        Modulatio version and now fails. For brand-new bugs use the
+        regular **Bug report** template instead.
+
+  - type: input
+    id: current-version
+    attributes:
+      label: Current (broken) version
+      placeholder: e.g. 0.1.0
+    validations:
+      required: true
+
+  - type: input
+    id: last-good-version
+    attributes:
+      label: Last known good version
+      description: Most recent version where this workflow still worked. If you bisected, give the exact tag.
+      placeholder: e.g. 0.1.0
+    validations:
+      required: true
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python version
+      placeholder: e.g. 3.12.3
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: OS / platform
+    validations:
+      required: true
+
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      options:
+        - critical
+        - high
+        - medium
+        - low
+      default: 1
+    validations:
+      required: true
+
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component
+      options:
+        - engine
+        - cli
+        - tui
+        - wizard
+        - providers
+        - standards
+        - packaging
+        - documentation
+        - other / unsure
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Reproduction steps
+      description: Sequence that worked in the last-good version and now fails.
+    validations:
+      required: true
+
+  - type: textarea
+    id: working-output
+    attributes:
+      label: Output on the last-good version
+      render: shell
+    validations:
+      required: false
+
+  - type: textarea
+    id: broken-output
+    attributes:
+      label: Output on the current (broken) version
+      render: shell
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / crash report
+      description: Paste from `~/.config/modulatio/crashes/` or `~/.config/modulatio/daemon.log` if relevant.
+      render: shell
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+    validations:
+      required: false

modulatio-0.9.4/.github/workflows/install-smoke.yml

@@ -0,0 +1,39 @@
+name: install-smoke
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  install:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ['3.12']
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install (editable, dev extras)
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Smoke import
+        run: python -c "import modulatio"
+
+      - name: Lint (src + tests)
+        # Tests are ruff-clean. Run the lint over the whole repo on CI
+        # so a regression that re-introduces unused imports /
+        # multi-statement lines / `lambda` assigns / unused locals
+        # fails the install-smoke job.
+        run: ruff check src/ tests/
+
+      - name: Pytest
+        run: pytest -q --tb=no

modulatio-0.9.4/.gitignore

@@ -0,0 +1,35 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+.env
+.env.*
+!.env.example
+.pytest_cache/
+.ruff_cache/
+.runs/
+scripts/smoke/*/.vault/
+# Reviewer diff scratch (Nemo/Lovecraft/CC review rounds) — transient, not source.
+scripts/smoke/*/review/
+scripts/smoke/*/review-*/
+# uv lockfile — Modulatio ships via its own install flow + pyproject; the lock
+# is a local dev convenience, deliberately not tracked (matches the released state).
+uv.lock
+*.db
+*.sqlite
+*.sqlite3
+/dist/
+build/
+# mkdocs build output — regenerable, not source-of-truth.
+site/
+# docs/dist/ holds the bundled DOCX + PDF that ship with releases —
+# explicitly NOT ignored. The /dist/ rule above is anchored to repo root
+# so Python build artifacts there don't conflict with this.
+.DS_Store
+scripts/eval/*/.vault/
+.vault/
+scripts/smoke/*/run.log
+/cliftest/
+
+# internal reviewer-session logs (hermes/lovecraft stdout) — never published
+scripts/smoke/security-audit/