mk-qa-master 0.5.0__tar.gz

mk_qa_master-0.5.0/.dockerignore

@@ -0,0 +1,33 @@
+# Keep the image small and predictable — only the package source needs
+# to enter the build context.
+.git
+.gitignore
+.github
+.venv
+venv
+.python-version
+
+# Python build artifacts
+__pycache__
+*.py[cod]
+*.egg-info
+build
+dist
+
+# Test outputs from local development (don't ship sample data)
+tests_project
+test-results
+
+# Repo-level docs, examples, branding — not needed at runtime
+docs
+examples
+assets
+index.html
+sample_report.html
+*.zh-TW.md
+CNAME
+
+# Editor / OS noise
+.DS_Store
+.vscode
+.idea

mk_qa_master-0.5.0/.github/CODEOWNERS

@@ -0,0 +1,5 @@
+# Single-maintainer repo — every change requires owner review.
+# Paired with branch protection's "Require review from Code Owners"
+# so even if the auto-close workflow ever misfires, nothing can merge
+# without @kao273183 approving.
+* @kao273183

mk_qa_master-0.5.0/.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# Surfaces a ❤️ Sponsor button on the repo page.
+# Add more entries here when GitHub Sponsors / Ko-fi / etc. come online.
+buy_me_a_coffee: minikao

mk_qa_master-0.5.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,53 @@
+name: Bug report
+description: Something broken or behaving unexpectedly in mk-qa-master.
+title: "[Bug] "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug! / 感謝回報問題！
+        This repo is maintained solo — external PRs are auto-closed. Please describe the issue here and I'll handle the fix.
+
+  - type: input
+    id: runner
+    attributes:
+      label: QA_RUNNER
+      description: Which runner are you using? (pytest / jest / cypress / go / maestro)
+      placeholder: maestro
+    validations:
+      required: true
+
+  - type: input
+    id: env
+    attributes:
+      label: Environment
+      description: OS / Python version / Maestro version (if mobile) / client (Claude Desktop, Cursor, Codex CLI, Gemini CLI...)
+      placeholder: "macOS 14.5, Python 3.11, Maestro 1.36, Claude Desktop"
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      description: Minimal steps. If it involves a specific prompt, paste the exact prompt.
+      placeholder: |
+        1. Set QA_RUNNER=maestro and QA_ANDROID_HOST=127.0.0.1:5555
+        2. Ask Claude to "analyze the home screen"
+        3. ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected vs actual
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs / error output
+      render: shell

mk_qa_master-0.5.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Discussions / Q&A
+    url: https://github.com/kao273183/mk-qa-master/discussions
+    about: General questions, ideas, or chat that aren't bug reports or feature requests.

mk_qa_master-0.5.0/.github/ISSUE_TEMPLATE/feature_suggestion.yml

@@ -0,0 +1,47 @@
+name: Feature suggestion
+description: Idea for a new runner, tool, or behavior. I'll evaluate and implement if it fits.
+title: "[Idea] "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the idea! / 感謝你的點子！
+        This repo is maintained solo and **doesn't accept external PRs** — please describe the suggestion here. If it fits the project, I'll build it.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve?
+      description: Concrete scenario where the current behavior falls short.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed behavior
+      description: What should happen. Sketches / pseudocode / API shape welcome.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you considered (optional)
+
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Which layer?
+      multiple: true
+      options:
+        - Runner (pytest / jest / cypress / go / maestro / new framework)
+        - Analyzer (analyze_url / analyze_screen)
+        - Generator (generate_test / auto_generate_tests)
+        - Optimizer / self-improvement coach
+        - HTML reporter
+        - QA knowledge layer
+        - MCP tool surface (server.py)
+        - Docs / examples
+        - Other

mk_qa_master-0.5.0/.github/pull_request_template.md

@@ -0,0 +1,21 @@
+<!--
+⚠️ Heads up — external PRs are auto-closed.
+
+This repo is maintained solo. If you're not @kao273183 or an invited
+collaborator, your PR will be politely closed by a bot and you'll be
+redirected to Issues.
+
+If you have a bug or idea, please file it here instead:
+https://github.com/kao273183/mk-qa-master/issues/new/choose
+
+Owner / collaborator PRs: delete this comment block and describe the change below.
+-->
+
+## Summary
+
+
+## Linked issue
+Closes #
+
+## Test plan
+- [ ]

mk_qa_master-0.5.0/.github/workflows/external-pr-policy.yml

@@ -0,0 +1,63 @@
+name: External PR policy
+
+# Closes PRs from non-OWNER / non-COLLABORATOR / non-MEMBER authors with a
+# friendly message redirecting to Issues. This repo welcomes ideas + bug
+# reports, but the codebase is maintained solo — see CONTRIBUTING in the
+# README for the rationale.
+#
+# `pull_request_target` runs in the base repo's context, so we get a
+# GITHUB_TOKEN with write perms even when the PR comes from a fork. We
+# only read PR metadata; never check out fork code here.
+
+on:
+  pull_request_target:
+    types: [opened, reopened]
+
+permissions:
+  pull-requests: write
+  issues: write
+
+jobs:
+  gate:
+    runs-on: ubuntu-latest
+    if: >-
+      github.event.pull_request.author_association != 'OWNER' &&
+      github.event.pull_request.author_association != 'COLLABORATOR' &&
+      github.event.pull_request.author_association != 'MEMBER'
+    steps:
+      - name: Comment and close
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const pr = context.payload.pull_request;
+            const body = [
+              `Hi @${pr.user.login}, thanks for taking the time to contribute! 🙏`,
+              ``,
+              `This repository is **maintained solo** and does not accept external pull requests at this time.`,
+              `If you found a bug or have an idea, please open an **Issue** instead — I read every one and will implement it myself if it fits the project's direction.`,
+              ``,
+              `→ https://github.com/${context.repo.owner}/${context.repo.repo}/issues/new/choose`,
+              ``,
+              `---`,
+              ``,
+              `Hi @${pr.user.login}，感謝你願意貢獻 🙏`,
+              ``,
+              `這個 repo **由我一人維護**，目前不收外部 PR。`,
+              `如果你發現 bug 或有想法，歡迎開 **Issue** — 我每一則都會看，覺得方向對的我會自己實作。`,
+              ``,
+              `Closing this PR for now. No offense intended.`
+            ].join('\n');
+
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: pr.number,
+              body,
+            });
+
+            await github.rest.pulls.update({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: pr.number,
+              state: 'closed',
+            });

mk_qa_master-0.5.0/.github/workflows/publish.yml

@@ -0,0 +1,80 @@
+name: Publish to PyPI
+
+# Triggered by every published GitHub Release. Releases are created
+# manually (via `gh release create` or the GitHub UI) so we keep
+# control over what hits PyPI — no auto-publish on tag push.
+#
+# Authentication: PyPI Trusted Publishing (OIDC). No API token stored;
+# instead a one-time setup on PyPI links this repo + workflow file to
+# the project name. Setup steps live in the README "Publishing" section.
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  # OIDC token exchange for Trusted Publishing — no PYPI_API_TOKEN secret needed.
+  id-token: write
+  contents: read
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tooling
+        run: python -m pip install --upgrade build twine
+
+      - name: Verify pyproject version matches the release tag
+        # The release tag (e.g. `v0.4.2`) must equal `v<pyproject.version>`.
+        # Catches the "tagged but forgot to bump pyproject" failure mode
+        # before we ship a wrong-versioned wheel.
+        run: |
+          set -eu
+          TAG="${GITHUB_REF_NAME#v}"
+          PY_VER=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+          echo "release tag (without v) = $TAG"
+          echo "pyproject version       = $PY_VER"
+          test "$TAG" = "$PY_VER"
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      - name: Validate distribution metadata
+        # Catches malformed README, missing classifiers, etc. before upload.
+        run: twine check dist/*
+
+      - name: Upload distribution artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    # Pin to an environment so PyPI's Trusted Publisher config can scope
+    # to this exact workflow + env name; protects against a compromised
+    # PR ever auto-publishing.
+    environment:
+      name: pypi
+      url: https://pypi.org/project/mk-qa-master/
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        # No `with: password:` — Trusted Publishing uses OIDC token in
+        # the runner's environment automatically.

mk_qa_master-0.5.0/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+.venv/
+venv/
+.pytest_cache/
+tests_project/report.json
+tests_project/report.html
+tests_project/optimization-plan.md
+tests_project/junit.xml
+tests_project/test-results/
+.DS_Store

mk_qa_master-0.5.0/CNAME

@@ -0,0 +1 @@
+mcp.chenjundigital.com

mk_qa_master-0.5.0/Dockerfile

@@ -0,0 +1,30 @@
+# MK QA Master container — built primarily so Glama (and any other MCP
+# catalog that introspects servers in a sandbox) can boot the server,
+# send `initialize` + `tools/list` over stdio, and confirm a clean
+# JSON-RPC response.
+#
+# Day-to-day use stays `uvx mk-qa-master` on the host: real test runs
+# need access to the user's project files, browsers, simulators, etc.
+# that live outside any sane container. This image is deliberately
+# minimal — enough to answer introspection, not enough to actually run
+# pytest / playwright / maestro.
+
+FROM python:3.12-slim
+
+# Install from local source so the image always reflects the current
+# commit (introspection should pass even before a PyPI release).
+WORKDIR /srv
+COPY pyproject.toml README.md LICENSE ./
+COPY src/ ./src/
+RUN pip install --no-cache-dir .
+
+# Defaults for the introspection probe. QA_PROJECT_ROOT just needs to
+# resolve to a writable path — config.py only `.resolve()`s it, doesn't
+# require it to exist until a real run happens (which we don't expect
+# inside this container).
+ENV QA_RUNNER=pytest \
+    QA_PROJECT_ROOT=/tmp/qa-project \
+    PYTHONUNBUFFERED=1
+
+WORKDIR /tmp/qa-project
+ENTRYPOINT ["python", "-m", "mk_qa_master.server"]

mk_qa_master-0.5.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jack Kao
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

mk_qa_master-0.5.0/LICENSE.zh-TW.md

@@ -0,0 +1,28 @@
+# MIT 授權條款（中文翻譯）
+
+> ⚠️ **本份為英文版 [`LICENSE`](LICENSE) 的中文翻譯，僅供理解參考之用。**
+> **若文義或法律爭議發生，以英文原版為準。**
+
+著作權所有 (c) 2026 Jack Kao
+
+謹此免費授予任何取得本軟體與相關說明文件（以下簡稱「本軟體」）副本之人，
+不受限制地處理本軟體之權利，包括但不限於使用、複製、修改、合併、出版、
+散布、再授權及／或販售本軟體之副本，並允許接受本軟體之人在符合下列條件
+之情況下進行上述行為：
+
+上述著作權聲明及本許可聲明應包含於本軟體之所有副本或實質部分之中。
+
+本軟體係「按現狀」提供，不附帶任何形式之明示或默示擔保，包括但不限於
+適售性、適合特定目的及不侵權之擔保。在任何情況下，作者或著作權持有人
+均不對任何索賠、損害或其他責任負責，無論係於合約訴訟、侵權行為或其他
+情形下，因本軟體、本軟體之使用或其他相關事宜所引起、所致或所連帶發生
+之責任。
+
+---
+
+## 白話摘要（非法律條文）
+
+- ✅ 你可以用、改、散布、再授權、商用
+- ✅ 改寫之後不必開源、私有閉源也行
+- ⚠️ **唯一要求**：你的 copy 裡要保留原作者的 copyright + 這份授權聲明
+- ❌ **不附保證**：用了出問題作者不負責，不能反過來追究