mdcompose 0.1.0__tar.gz

mdcompose-0.1.0/.gitattributes

@@ -0,0 +1,11 @@
+# Normalize every text file to LF in the repository and in working copies.
+# This project's whole design turns on line-ending correctness, so it must not
+# depend on a contributor's core.autocrlf setting.
+* text=auto eol=lf
+
+# Test fixtures that deliberately carry a specific encoding or line ending must
+# survive checkout byte for byte, otherwise the tests that prove normalization
+# works would be testing normalized inputs.
+tests/fixtures/**/*.crlf.md  -text
+tests/fixtures/**/*.bom.md   -text
+tests/fixtures/**/*.cp1252.md -text

mdcompose-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,51 @@
+name: Bug report
+description: Something mdcompose does wrong
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        A failing test case is the fastest possible bug report. If you can write
+        one, open a pull request instead of an issue.
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened
+      description: The command you ran and what mdcompose did.
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What you expected instead
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Smallest reproduction
+      description: The fewest steps, files, or snippets that still show the problem.
+    validations:
+      required: true
+  - type: textarea
+    id: doctor
+    attributes:
+      label: Output of mdcompose doctor
+      render: text
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: mdcompose version and how you installed it
+      placeholder: 0.1.0, pipx
+    validations:
+      required: true
+  - type: input
+    id: platform
+    attributes:
+      label: Operating system and Python version
+      placeholder: Windows 11, Python 3.12
+    validations:
+      required: true

mdcompose-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question or discussion
+    url: https://github.com/Rovetown/mdcompose/discussions
+    about: Usage questions and early ideas that are not yet a bug or a concrete request.

mdcompose-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,28 @@
+name: Feature request
+description: Suggest a capability or a change
+labels: [enhancement]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Read the "Deliberate non-goals" section of AGENTS.md first: a few things
+        are excluded on purpose, with the reasoning.
+  - type: textarea
+    id: problem
+    attributes:
+      label: The problem
+      description: What are you trying to do that mdcompose makes hard or impossible?
+    validations:
+      required: true
+  - type: textarea
+    id: idea
+    attributes:
+      label: The change you have in mind
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you considered
+    validations:
+      required: false

mdcompose-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+<!-- What does this change, and why.
+Link the issue if there is one. -->
+
+## Checklist
+
+- [ ] `uv run pytest` passes, and so does `uv sync --locked --python 3.11 && uv run --no-sync pytest`
+- [ ] `uv run ruff check .` is clean
+- [ ] `uv run pre-commit run --all-files` is clean
+- [ ] Every commit is a Conventional Commit (`uv run cz check --rev-range origin/main..HEAD`)
+- [ ] Plain ASCII in everything the change adds
+- [ ] Behavior change: [docs/core-contract.md](../docs/core-contract.md) updated in the same commit

mdcompose-0.1.0/.github/workflows/bump.yml

@@ -0,0 +1,97 @@
+name: bump
+
+# The release button. Run this from the Actions tab and pick a channel:
+#
+#   stable -> a stable release   (0.3.1 -> 0.3.2 / 0.4.0 / 1.0.0, from the commits)
+#   alpha  -> 0.4.0a1, then a2, ...   feature-incomplete, breakage expected
+#   beta   -> 0.4.0b1, ...            feature-complete, bug hunting
+#   rc     -> 0.4.0rc1, ...           believed shippable
+#
+# Run it again with "stable" to promote the current pre-release to the final
+# version. cz bump derives the number from the Conventional Commits since
+# the last tag, rewrites [project].version and CHANGELOG.md, commits, and pushes
+# the tag that release.yml publishes on. You never type a version.
+#
+# Requires a repository secret RELEASE_TOKEN: a fine-grained PAT (or GitHub App
+# token) with contents:write. The built-in GITHUB_TOKEN cannot be used here,
+# because a tag it pushes does not trigger release.yml and its push is blocked by
+# branch protection. See TODO.md, "The bump.yml PAT wrinkle".
+
+on:
+  workflow_dispatch:
+    inputs:
+      prerelease:
+        description: Release channel
+        type: choice
+        default: stable
+        options:
+          - stable
+          - alpha
+          - beta
+          - rc
+
+# Never let two bumps run at once.
+concurrency:
+  group: bump
+  cancel-in-progress: false
+
+permissions:
+  contents: read
+
+jobs:
+  bump:
+    name: bump version, changelog and tag
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    # A release comes only off the mainline.
+    if: github.ref == 'refs/heads/main'
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          # Full history so cz bump can read every commit since the last tag,
+          # and the PAT so the pushed commit and tag are not blocked by branch
+          # protection and the tag triggers release.yml.
+          fetch-depth: 0
+          token: ${{ secrets.RELEASE_TOKEN }}
+          persist-credentials: true
+
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Sync the locked environment
+        run: uv sync --locked
+
+      - name: Identify the committer
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+
+      - name: Bump
+        env:
+          PRERELEASE: ${{ inputs.prerelease }}
+        run: |
+          if [ "$PRERELEASE" = "stable" ]; then
+            uv run --no-sync cz bump --yes --changelog
+          else
+            uv run --no-sync cz bump --yes --changelog --prerelease "$PRERELEASE"
+          fi
+
+      - name: Fold the refreshed lockfile into the bump commit
+        # cz bump rewrites [project].version but not uv.lock, which pins the
+        # project's own version. Left stale, every `uv sync --locked` downstream
+        # (CI, the release build) fails with "the lockfile needs to be updated".
+        # The bump commit and tag are still local here, so amend rather than add
+        # a follow-up commit, and re-point the annotated tag at the new commit.
+        run: |
+          uv lock
+          if ! git diff --quiet -- uv.lock; then
+            tag="$(git describe --tags --exact-match HEAD)"
+            git add uv.lock
+            git commit --amend --no-edit
+            git tag -f -a "$tag" -m "$tag"
+          fi
+
+      - name: Push the bump commit and the tag
+        run: git push --follow-tags origin HEAD:main

mdcompose-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,318 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+# The default token is read-only. No job here writes to the repository.
+permissions:
+  contents: read
+
+env:
+  # Colour is decided by TTY detection, and a runner is not a TTY. Setting this
+  # anyway keeps log output identical to what a piped run produces locally.
+  NO_COLOR: "1"
+
+jobs:
+  test:
+    # The full matrix runs on all three operating systems rather than only on
+    # Linux. Cross-platform path and encoding handling is what this project
+    # claims to do better than its neighbours, so it is the last thing that
+    # should be tested on one platform and assumed elsewhere.
+    name: test ${{ matrix.python }} on ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 20
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        python: ["3.11", "3.12", "3.13", "3.14"]
+
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Sync the locked environment
+        # --locked fails if uv.lock is out of date with pyproject.toml, so a
+        # dependency change that was not locked cannot pass CI unnoticed.
+        run: uv sync --locked --python ${{ matrix.python }}
+
+      - name: Run the test suite
+        run: uv run --no-sync pytest
+
+      - name: Smoke test the doctor command
+        # The suite covers doctor thoroughly, but only through the in-process
+        # entry point. This runs the installed console script the way a user
+        # does, which is what would have caught the Path.exists divergence
+        # between Python versions.
+        shell: bash
+        run: |
+          uv run --no-sync mdcompose --version
+          uv run --no-sync mdcompose doctor
+          uv run --no-sync mdcompose doctor --json > report.json
+          uv run --no-sync python -c "import json,pathlib; d=json.loads(pathlib.Path('report.json').read_text()); assert d['os'] in {'windows','macos','linux'}, d; assert d['paths'], d; print('doctor json ok on', d['os'])"
+
+      - name: Verify quiet mode reduces doctor to its exit code
+        shell: bash
+        run: |
+          output=$(uv run --no-sync mdcompose doctor --quiet)
+          if [ -n "$output" ]; then
+            echo "expected no stdout in quiet mode, got: $output"
+            exit 1
+          fi
+
+  lint:
+    name: lint
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Sync the locked environment
+        run: uv sync --locked
+
+      - name: Run ruff
+        run: uv run --no-sync ruff check .
+
+      - name: Run mypy
+        # Strict type checking over mdcompose/. Config in [tool.mypy].
+        run: uv run --no-sync mypy
+
+      - name: Check dependency hygiene
+        # Unused, missing, or misplaced dependencies, inferred from the imports.
+        run: uv run --no-sync deptry .
+
+  coverage:
+    # A single-platform coverage floor. The full matrix in `test` proves the
+    # suite passes everywhere; this one run enforces `fail_under` from
+    # [tool.coverage.report] so coverage cannot slide unnoticed between
+    # ratchets. It is not the matrix's job because branch coverage differs by
+    # platform (winreg, /mnt/) and the floor is set against one of them.
+    name: coverage floor
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Sync the locked environment
+        run: uv sync --locked
+
+      - name: Run the suite under coverage
+        run: uv run --no-sync pytest --cov=mdcompose --cov-report=term-missing
+
+  ascii:
+    # This project requires every character it generates, and every character in
+    # its own documents, to be ASCII. The reason is not style: a Windows console
+    # on a cp1252 or cp437 code page cannot encode an emoji or an em dash, so
+    # emitting one raises an encoding error on a primary target platform. A rule
+    # that is only enforced by review stops being enforced. The same script runs
+    # as a pre-commit hook, so a violation fails locally before it is pushed.
+    name: ascii convention
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - name: Check that sources and documents are plain ASCII
+        run: python3 scripts/check_ascii.py
+
+  build:
+    name: build and install
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Build the wheel and sdist
+        run: uv build
+
+      - name: Install the built wheel into a clean environment and run it
+        # Proves the package works as published, not only as an editable
+        # checkout. A missing file in the wheel would pass every other job.
+        shell: bash
+        run: |
+          uv venv --python 3.11 /tmp/fresh
+          uv pip install --python /tmp/fresh/bin/python dist/*.whl
+          /tmp/fresh/bin/mdcompose --version
+          /tmp/fresh/bin/mdcompose doctor
+
+  workflows:
+    # The two workflow-file linters that pre-commit.ci cannot run in its sandbox
+    # (actionlint fetches a binary, zizmor ships as a compiled tool), run here
+    # from pinned releases instead. Everything else in .pre-commit-config.yaml
+    # is left to pre-commit.ci; those two are listed in its `ci.skip`.
+    name: workflow lint
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Install actionlint
+        env:
+          # renovate: datasource=github-releases depName=rhysd/actionlint
+          ACTIONLINT_VERSION: 1.7.12
+        run: |
+          curl -sSfL "https://github.com/rhysd/actionlint/releases/download/v${ACTIONLINT_VERSION}/actionlint_${ACTIONLINT_VERSION}_linux_amd64.tar.gz" \
+            | sudo tar -xz -C /usr/local/bin actionlint
+
+      - name: actionlint
+        run: actionlint -color
+
+      - name: zizmor
+        env:
+          # renovate: datasource=pypi depName=zizmor
+          ZIZMOR_VERSION: 1.30.1
+        run: uv tool run "zizmor==${ZIZMOR_VERSION}" .
+
+      - name: check-github-workflows
+        run: >-
+          uv tool run --from check-jsonschema
+          check-jsonschema --builtin-schema github-workflows .github/workflows/*.yml
+
+  commits:
+    # Every commit on a pull request branch must be a Conventional Commit, so
+    # the release-time version bump derived from those commits is trustworthy.
+    name: conventional commits
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Sync the locked environment
+        run: uv sync --locked
+
+      - name: Check every commit in the pull request
+        env:
+          RANGE: ${{ github.event.pull_request.base.sha }}..${{ github.event.pull_request.head.sha }}
+        run: uv run --no-sync cz check --rev-range "$RANGE"
+
+  gitleaks:
+    # The pre-commit gitleaks hook only sees a working tree. This scans the full
+    # history, so a secret committed and then removed in a later commit is still
+    # caught. The gitleaks binary is run directly rather than through
+    # gitleaks-action: the action diffs only the pushed range, which has no
+    # valid base on the first push of a rewritten history.
+    name: secret scan
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+
+      - name: Install gitleaks
+        env:
+          # renovate: datasource=github-releases depName=gitleaks/gitleaks
+          GITLEAKS_VERSION: 8.24.3
+        run: |
+          curl -sSfL "https://github.com/gitleaks/gitleaks/releases/download/v${GITLEAKS_VERSION}/gitleaks_${GITLEAKS_VERSION}_linux_x64.tar.gz" \
+            | sudo tar -xz -C /usr/local/bin gitleaks
+
+      - name: Scan the full history
+        run: gitleaks git --redact --exit-code 1 --verbose .
+
+  all-green:
+    # The single check branch protection requires: it passes only if every job
+    # it needs passed or was legitimately skipped (commits is skipped outside a
+    # pull request). Adding a job above without adding it here is the one way to
+    # weaken the gate, so the list is deliberately explicit.
+    name: all green
+    if: always()
+    needs: [test, lint, coverage, ascii, build, workflows, commits, gitleaks]
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    steps:
+      - name: Require every needed job to have passed
+        env:
+          RESULTS: ${{ join(needs.*.result, ' ') }}
+        run: |
+          echo "job results: $RESULTS"
+          for result in $RESULTS; do
+            case "$result" in
+              success|skipped) ;;
+              *) echo "a required job did not pass"; exit 1 ;;
+            esac
+          done
+
+  # DORMANT, repo-gated. The suite (tests/benchmarks) and the `benchmark`
+  # dependency group both exist; what is missing is a CodSpeed project, which
+  # needs the GitHub repo. CodSpeed runs the benchmarks instrumented rather than
+  # wall-clock, so the numbers are stable across runners, and it posts the delta
+  # as a pull request check rather than failing hard. Free for open source. To
+  # enable: connect the repo at codspeed.io, uncomment this job, and leave it
+  # out of the all-green needs list (benchmarks never block a merge).
+  #
+  # benchmarks:
+  #   name: benchmarks
+  #   runs-on: ubuntu-latest
+  #   timeout-minutes: 20
+  #   steps:
+  #     - uses: actions/checkout@v4
+  #       with:
+  #         persist-credentials: false
+  #     - uses: astral-sh/setup-uv@v5
+  #       with:
+  #         enable-cache: true
+  #         cache-dependency-glob: uv.lock
+  #     - run: uv sync --locked --group benchmark
+  #     - uses: CodSpeedHQ/action@v3
+  #       with:
+  #         run: uv run --no-sync pytest tests/benchmarks --codspeed

mdcompose-0.1.0/.github/workflows/codeql.yml

@@ -0,0 +1,39 @@
+name: codeql
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: "41 5 * * 2"
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  analyze:
+    name: analyze python
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    permissions:
+      security-events: write
+      actions: read
+      contents: read
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@b96794f015dfd88f77b49b1c93e0fa7110f94c63 # v4
+        with:
+          languages: python
+          queries: security-and-quality
+
+      - name: Analyze
+        uses: github/codeql-action/analyze@b96794f015dfd88f77b49b1c93e0fa7110f94c63 # v4

mdcompose-0.1.0/.github/workflows/dependency-review.yml

@@ -0,0 +1,45 @@
+name: dependency review
+
+# On a pull request that changes dependencies, block the merge if it introduces
+# a known-vulnerable package or a copyleft licence. Complements
+# scripts/check_licenses.py (which runs on the resolved tree) by catching the
+# change at review time. Does nothing until the repository is on GitHub and a
+# pull request exists.
+
+on:
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  review:
+    name: dependency review
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - uses: actions/dependency-review-action@a1d282b36b6f3519aa1f3fc636f609c47dddb294 # v5.0.0
+        with:
+          fail-on-severity: moderate
+          # The DENY tier from scripts/check_licenses.py: the strong and linking
+          # copyleft families (GPL, LGPL, AGPL, EUPL, SSPL), every SPDX spelling
+          # of each. `deny-licenses` matches exact ids, so each -only and
+          # -or-later variant and each deprecated id is listed. That script is
+          # the real gate (deny by default over the resolved tree); this one
+          # catches the same families at review time.
+          deny-licenses: >-
+            GPL-1.0-only, GPL-1.0-or-later, GPL-2.0, GPL-2.0-only, GPL-2.0-or-later,
+            GPL-3.0, GPL-3.0-only, GPL-3.0-or-later,
+            LGPL-2.0, LGPL-2.0-only, LGPL-2.0-or-later,
+            LGPL-2.1, LGPL-2.1-only, LGPL-2.1-or-later,
+            LGPL-3.0, LGPL-3.0-only, LGPL-3.0-or-later,
+            AGPL-1.0-only, AGPL-1.0-or-later, AGPL-3.0, AGPL-3.0-only, AGPL-3.0-or-later,
+            EUPL-1.1, EUPL-1.2, SSPL-1.0

mdcompose-0.1.0/.github/workflows/mutation.yml

@@ -0,0 +1,55 @@
+name: mutation testing
+
+# Mutation testing: mutmut mutates mdcompose/core (flips a comparison, deletes a
+# line, ...) and runs the suite against each mutant. A mutant that survives is
+# behaviour the tests do not actually check. It runs the whole suite once per
+# mutant, so this is a weekly cron and a manual button, never a required check
+# and never on a pull request. Read the job summary to see where freshly written
+# code needs more tests; the survivors feed the TDD coverage review in the
+# roadmap quality pass.
+
+on:
+  schedule:
+    - cron: "0 4 * * 1"
+  workflow_dispatch:
+
+concurrency:
+  group: mutation
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  mutmut:
+    name: mutmut over core
+    runs-on: ubuntu-latest
+    timeout-minutes: 60
+    # Reporting only. Nothing depends on this job and it never blocks a merge.
+    continue-on-error: true
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        with:
+          persist-credentials: false
+
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Sync the locked environment with the mutation group
+        run: uv sync --locked --group mutation
+
+      - name: Run mutmut
+        continue-on-error: true
+        run: uv run --no-sync mutmut run
+
+      - name: Write the results to the job summary
+        if: always()
+        run: |
+          {
+            echo '## mutmut results'
+            echo '```'
+            uv run --no-sync mutmut results || true
+            echo '```'
+          } >> "$GITHUB_STEP_SUMMARY"