assay-ui 0.1.0__tar.gz

assay_ui-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 assay contributors
+
+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.

assay_ui-0.1.0/PKG-INFO

@@ -0,0 +1,325 @@
+Metadata-Version: 2.4
+Name: assay-ui
+Version: 0.1.0
+Summary: Find out whether a generated web page actually works.
+Author: awss1i
+License: MIT
+Project-URL: Homepage, https://github.com/awss1i/assay
+Project-URL: Source, https://github.com/awss1i/assay
+Project-URL: Issues, https://github.com/awss1i/assay/issues
+Project-URL: Changelog, https://github.com/awss1i/assay/releases
+Keywords: testing,llm,codegen,playwright,evaluation,qa,ai-agents,browser-testing
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Environment :: Console
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: playwright>=1.40
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Dynamic: license-file
+
+# assay
+
+[![python](https://img.shields.io/badge/python-3.10%2B-blue)](pyproject.toml)
+[![licence](https://img.shields.io/badge/licence-MIT-blue)](LICENSE)
+
+**Find out whether a generated web page actually works.**
+
+<img src="https://raw.githubusercontent.com/awss1i/assay/main/docs/run.svg" alt="A terminal running assay against a
+generated paint program. Twenty-five cases planned from the page itself,
+twenty-three passed, and two failed: one because the canvas took the first
+stroke and ignored the second, one because Undo answered the second press and
+not the first.">
+
+<p align="center"><i>Checking a generated paint program. Nobody wrote a test.</i></p>
+
+Point it at a page. assay opens it in a real browser, measures every control
+it renders, works out a test plan from what it finds, drives all of it, and
+tells you what broke.
+
+## Highlights
+
+- **No tests to write.** The plan comes from the page, so a program written
+  ten seconds ago can be checked ten seconds later.
+- **No LLM. Purely mechanical.** No API key, no tokens, no rate limit, nothing
+  to bill. It gives the same answer twice.
+- **No baseline images and no recordings.** Nothing to capture first, nothing
+  to keep in step with the design.
+- **It says why.** Not *case 14 failed*, but *the first press did nothing and
+  the second did something, so this control is one behind*.
+
+## Contents
+
+- [Install](#install)
+  - [CLI](#cli)
+  - [Skills and Plugins](#skills-and-plugins)
+- [Use](#use)
+  - [CLI](#cli-1)
+  - [Skills](#skills)
+  - [Plugins](#plugins)
+- [Benchmarks](#benchmarks)
+  - [Generated Programs](#generated-programs)
+  - [Planted Bugs](#planted-bugs)
+- [How It Works](#how-it-works)
+- [Why](#why)
+- [Limits Worth Knowing](#limits-worth-knowing)
+- [Contributing](#contributing)
+- [Licence](#licence)
+
+## Install
+
+### CLI
+
+```bash
+pip install assay-ui
+```
+
+The command is `assay`. The first run fetches a browser if there is not one
+already, so there is no second command to forget.
+
+To hack on it, clone and install it in place:
+
+```bash
+git clone https://github.com/awss1i/assay.git && cd assay
+pip install -e ".[dev]"
+```
+
+### Skills and Plugins
+
+Fifteen harnesses, one command each. All of them want the CLI above first.
+
+**[Install it in your harness →](docs/harnesses.md)**
+
+## Use
+
+### CLI
+
+```console
+assay ./my-app                    # check the page in this folder
+assay ./my-app/todo.html          # check one page by name
+assay ./my-app -e app.html        # or name the page inside a folder
+
+assay ./my-app --report out.html  # write an HTML report with screenshots
+assay ./my-app --json             # print the whole run as JSON
+assay ./my-app --one-line         # print one sentence, for a script to relay
+assay ./my-app --surface          # list the controls it found, then stop
+```
+
+There is a broken drawing program in this repository. Run it yourself:
+
+```console
+$ assay bench/programs/dsh/gpt-oss-120b/37_draw2
+23 case(s) planned, 23 carried out, 22 passed, 1 failed
+
+C013 [ok] use canvas: click it, drag on it, and press the keys a program like this is driven with
+C014 [ok] draw on canvas, then draw somewhere else on it
+C015 [FAILED] draw on canvas twice, then press Undo twice
+    → the first press did nothing and the second did something, from the same state, so this control is one behind
+C016 [ok] draw on canvas twice, then press Redo twice
+C017 [ok] draw on canvas twice, then press Clear twice
+```
+
+Drawing works. Redo works. Clear works. Undo is one press behind, and nothing
+about the source says so.
+
+**Where the results go.** Everything goes to stdout and **nothing is written
+to disk unless you ask**, because a CI check that only cares about the exit
+code should not litter. `--report FILE` writes one self-contained HTML page
+plus a `shots/` folder of screenshots beside it. `--json` prints the whole run
+for piping. The exit code is non-zero if anything failed.
+
+`--report` gives you every case with the page as the browser drew it, before
+and after:
+
+<img src="https://raw.githubusercontent.com/awss1i/assay/main/docs/report.png" alt="One case from an assay report: the
+act that was performed, the reason it failed, and screenshots of the page
+before and after">
+
+**From Python.** The same run, as an object.
+
+```python
+from assay import check
+
+report = check("./my-app")
+print(report.summary())
+for result in report.failing:
+    print(result.case.what, "->", result.detail)
+```
+
+### Skills
+
+*Claude Code, DeepSeek Harness, opencode, Antigravity, Codex App, Codex CLI,
+Cursor, Devin CLI, Factory Droid, Gemini CLI, GitHub Copilot CLI, Grok Build
+CLI, Kimi Code, Pi, Hermes Agent.*
+
+One markdown file. Your agent runs assay when it finishes a page and prints
+what came back:
+
+```
+assay: checked todo/todo.html, 8 checks, nothing flagged.
+```
+
+One line, every time, whether or not it found anything. It reports and never
+fixes: the agent hands over what it pressed and what happened, and does not
+edit code on the strength of it.
+
+**[How the skill behaves →](plugins/assay/README.md#the-skill)**
+
+### Plugins
+
+*Claude Code, DeepSeek Harness.*
+
+The same skill plus a hook, so the check happens at the end of every turn
+that touched a page, whether or not the agent thought to run it.
+
+```
+/plugin marketplace add awss1i/assay
+/plugin install assay@assay
+```
+
+**[How the plugin behaves →](plugins/assay/README.md#the-plugin)**
+
+## Benchmarks
+
+A checker nobody has checked is an opinion with a progress bar. Two sets,
+built differently, both checked in.
+
+### Generated Programs
+
+225 programs written to 75 objectives by three harnesses. A person opened
+every one and drove it before assay saw it. 20 are broken.
+
+<!-- score2 -->
+
+**Across 225 pages checked by hand, assay found 15 of the 20 real defects and raised 0 false alarms.** When it reports a problem it is a real one 15 times out of 15.
+
+<!-- /score2 -->
+
+**[The benchmark →](bench/README.md)**
+
+### Planted Bugs
+
+Ten working programs, and a copy of each with five bugs put in by a
+different harness and model. Fifty defects known by construction, and the
+harder set: pages that work and are wrong, not pages that stopped.
+
+<!-- planted -->
+
+**assay found 10 of the 50 planted bugs and flagged 0 of the 10 working originals.**
+
+<!-- /planted -->
+
+**[The planted set →](bench/planted/README.md)**
+
+Both reproduce with `python bench/score.py` and `python bench/planted/score.py`.
+No key, no network.
+
+## How It Works
+
+**It waits until the page stops arriving**, watching whether the set of
+controls is still changing rather than pausing for a fixed time. **It measures
+the surface** from the rendered page and never the markup, down to a grid of
+plain divs, because a pointer cursor is the page saying *click this* and a
+handler attached in JavaScript cannot be read any other way. **It derives a
+plan from that** and carries all of it out in a fresh tab, measuring painted
+pixels per canvas, their centroid and mean colour, an exact pixel hash, the
+visible text, and a hash over every element's style.
+
+**It is deliberately narrow about what counts as a failure.** A plan derived
+from the page cannot know what a control is *for*, so a button only has to
+survive being pressed. Demanding that every press change something would fail
+a working program for having a Clear button on an empty canvas.
+
+What it can judge without knowing the design is whether the program
+contradicts itself. A surface that took the first stroke has to take the
+second. A control that does nothing on its first press and something on its
+second, from the same state, is one press behind. And if nothing on the page
+responds to anything, the script probably never ran.
+
+**It never says a page is broken.** It says what it pressed and what
+happened:
+
+```
+C006 [FAILED] type into Quantity then press +
+    → nothing on the page changed at all
+```
+
+A verdict makes you change code. A measurement makes you look first, and
+sometimes you find the page was right and the check was aimed at the wrong
+thing. That is the cheaper mistake to make, and it reads the same either way
+round: a person knows where to start, and an agent gets a precise place to
+look instead of a whole file to re-read.
+
+**It serves the folder and never builds it.** The page is served over
+loopback rather than opened off the disk, because a `file://` origin blocks
+every module the page loads. What it will not do is run your build: `npm
+install` executes whatever the dependency tree asks for, as whoever typed the
+command, and this is a tool for checking code nobody has read. Point it at a
+source tree and it says so:
+
+```console
+$ assay ./my-vite-app
+assay: index.html loads /src/main.jsx, which a browser cannot run. This is a source tree, not a built one.
+  Build it first, in your own shell, then check the output:
+    npm install && npm run build && assay ./my-vite-app/dist
+```
+
+**[Every rule →](docs/how-it-works.md)**
+
+## Why
+
+A lot of code is written by models now, and *"does this actually run?"* is
+mostly still answered by a person opening it and clicking around.
+
+Every existing tool needs something you do not have for a program that was
+generated ten seconds ago. Playwright and Cypress need tests somebody wrote.
+Visual regression needs a golden image to compare against. Benchmarks like
+SWE-bench use the repository's own suite.
+
+So the thing most people reach for instead is another model: paste the code in
+and ask whether it looks right. **That is a reader guessing about code.** assay
+opens the page and drives it, which is the only way to find out that a button
+does nothing.
+
+|  | needs tests written | needs a baseline | runs the program |
+|---|---|---|---|
+| Playwright / Cypress | yes | no | yes, the parts you wrote |
+| Percy / Chromatic | no | **yes** | it screenshots it |
+| ask a model to review it | no | no | **no. It reads the source** |
+| **assay** | **no** | **no** | **yes, all of it** |
+
+## Limits Worth Knowing
+
+- **Browser programs.** It opens a page. A program with no page is not
+  something it can measure.
+- **Coverage cannot judge intent.** A control that works mechanically and does
+  the wrong thing passes. Criteria are the answer, and you have to write those.
+- **A game that ends looks like a page that died.** When a program finishes
+  and offers no way to start again, it stops responding to anything, and a
+  plan derived from the page cannot tell that apart from a page that broke.
+- **Built output, not source trees.** It will not run your build. Point it at
+  a source tree and it says so and names the command.
+- **Single-page programs.** It checks the page you point it at and does not
+  crawl. A multi-page site means running it per page, and client-side routing
+  is untested.
+- **Generated pages, not the live web.** It is built for programs somebody
+  just generated, not for sites with a login, a cookie banner or live network
+  calls.
+
+## Contributing
+
+Issues and pull requests are welcome. Setup, tests, benchmarks and what a PR
+needs are in **[CONTRIBUTING.md](CONTRIBUTING.md)**.
+
+## Licence
+
+MIT.

assay_ui-0.1.0/README.md

@@ -0,0 +1,296 @@
+# assay
+
+[![python](https://img.shields.io/badge/python-3.10%2B-blue)](pyproject.toml)
+[![licence](https://img.shields.io/badge/licence-MIT-blue)](LICENSE)
+
+**Find out whether a generated web page actually works.**
+
+<img src="https://raw.githubusercontent.com/awss1i/assay/main/docs/run.svg" alt="A terminal running assay against a
+generated paint program. Twenty-five cases planned from the page itself,
+twenty-three passed, and two failed: one because the canvas took the first
+stroke and ignored the second, one because Undo answered the second press and
+not the first.">
+
+<p align="center"><i>Checking a generated paint program. Nobody wrote a test.</i></p>
+
+Point it at a page. assay opens it in a real browser, measures every control
+it renders, works out a test plan from what it finds, drives all of it, and
+tells you what broke.
+
+## Highlights
+
+- **No tests to write.** The plan comes from the page, so a program written
+  ten seconds ago can be checked ten seconds later.
+- **No LLM. Purely mechanical.** No API key, no tokens, no rate limit, nothing
+  to bill. It gives the same answer twice.
+- **No baseline images and no recordings.** Nothing to capture first, nothing
+  to keep in step with the design.
+- **It says why.** Not *case 14 failed*, but *the first press did nothing and
+  the second did something, so this control is one behind*.
+
+## Contents
+
+- [Install](#install)
+  - [CLI](#cli)
+  - [Skills and Plugins](#skills-and-plugins)
+- [Use](#use)
+  - [CLI](#cli-1)
+  - [Skills](#skills)
+  - [Plugins](#plugins)
+- [Benchmarks](#benchmarks)
+  - [Generated Programs](#generated-programs)
+  - [Planted Bugs](#planted-bugs)
+- [How It Works](#how-it-works)
+- [Why](#why)
+- [Limits Worth Knowing](#limits-worth-knowing)
+- [Contributing](#contributing)
+- [Licence](#licence)
+
+## Install
+
+### CLI
+
+```bash
+pip install assay-ui
+```
+
+The command is `assay`. The first run fetches a browser if there is not one
+already, so there is no second command to forget.
+
+To hack on it, clone and install it in place:
+
+```bash
+git clone https://github.com/awss1i/assay.git && cd assay
+pip install -e ".[dev]"
+```
+
+### Skills and Plugins
+
+Fifteen harnesses, one command each. All of them want the CLI above first.
+
+**[Install it in your harness →](docs/harnesses.md)**
+
+## Use
+
+### CLI
+
+```console
+assay ./my-app                    # check the page in this folder
+assay ./my-app/todo.html          # check one page by name
+assay ./my-app -e app.html        # or name the page inside a folder
+
+assay ./my-app --report out.html  # write an HTML report with screenshots
+assay ./my-app --json             # print the whole run as JSON
+assay ./my-app --one-line         # print one sentence, for a script to relay
+assay ./my-app --surface          # list the controls it found, then stop
+```
+
+There is a broken drawing program in this repository. Run it yourself:
+
+```console
+$ assay bench/programs/dsh/gpt-oss-120b/37_draw2
+23 case(s) planned, 23 carried out, 22 passed, 1 failed
+
+C013 [ok] use canvas: click it, drag on it, and press the keys a program like this is driven with
+C014 [ok] draw on canvas, then draw somewhere else on it
+C015 [FAILED] draw on canvas twice, then press Undo twice
+    → the first press did nothing and the second did something, from the same state, so this control is one behind
+C016 [ok] draw on canvas twice, then press Redo twice
+C017 [ok] draw on canvas twice, then press Clear twice
+```
+
+Drawing works. Redo works. Clear works. Undo is one press behind, and nothing
+about the source says so.
+
+**Where the results go.** Everything goes to stdout and **nothing is written
+to disk unless you ask**, because a CI check that only cares about the exit
+code should not litter. `--report FILE` writes one self-contained HTML page
+plus a `shots/` folder of screenshots beside it. `--json` prints the whole run
+for piping. The exit code is non-zero if anything failed.
+
+`--report` gives you every case with the page as the browser drew it, before
+and after:
+
+<img src="https://raw.githubusercontent.com/awss1i/assay/main/docs/report.png" alt="One case from an assay report: the
+act that was performed, the reason it failed, and screenshots of the page
+before and after">
+
+**From Python.** The same run, as an object.
+
+```python
+from assay import check
+
+report = check("./my-app")
+print(report.summary())
+for result in report.failing:
+    print(result.case.what, "->", result.detail)
+```
+
+### Skills
+
+*Claude Code, DeepSeek Harness, opencode, Antigravity, Codex App, Codex CLI,
+Cursor, Devin CLI, Factory Droid, Gemini CLI, GitHub Copilot CLI, Grok Build
+CLI, Kimi Code, Pi, Hermes Agent.*
+
+One markdown file. Your agent runs assay when it finishes a page and prints
+what came back:
+
+```
+assay: checked todo/todo.html, 8 checks, nothing flagged.
+```
+
+One line, every time, whether or not it found anything. It reports and never
+fixes: the agent hands over what it pressed and what happened, and does not
+edit code on the strength of it.
+
+**[How the skill behaves →](plugins/assay/README.md#the-skill)**
+
+### Plugins
+
+*Claude Code, DeepSeek Harness.*
+
+The same skill plus a hook, so the check happens at the end of every turn
+that touched a page, whether or not the agent thought to run it.
+
+```
+/plugin marketplace add awss1i/assay
+/plugin install assay@assay
+```
+
+**[How the plugin behaves →](plugins/assay/README.md#the-plugin)**
+
+## Benchmarks
+
+A checker nobody has checked is an opinion with a progress bar. Two sets,
+built differently, both checked in.
+
+### Generated Programs
+
+225 programs written to 75 objectives by three harnesses. A person opened
+every one and drove it before assay saw it. 20 are broken.
+
+<!-- score2 -->
+
+**Across 225 pages checked by hand, assay found 15 of the 20 real defects and raised 0 false alarms.** When it reports a problem it is a real one 15 times out of 15.
+
+<!-- /score2 -->
+
+**[The benchmark →](bench/README.md)**
+
+### Planted Bugs
+
+Ten working programs, and a copy of each with five bugs put in by a
+different harness and model. Fifty defects known by construction, and the
+harder set: pages that work and are wrong, not pages that stopped.
+
+<!-- planted -->
+
+**assay found 10 of the 50 planted bugs and flagged 0 of the 10 working originals.**
+
+<!-- /planted -->
+
+**[The planted set →](bench/planted/README.md)**
+
+Both reproduce with `python bench/score.py` and `python bench/planted/score.py`.
+No key, no network.
+
+## How It Works
+
+**It waits until the page stops arriving**, watching whether the set of
+controls is still changing rather than pausing for a fixed time. **It measures
+the surface** from the rendered page and never the markup, down to a grid of
+plain divs, because a pointer cursor is the page saying *click this* and a
+handler attached in JavaScript cannot be read any other way. **It derives a
+plan from that** and carries all of it out in a fresh tab, measuring painted
+pixels per canvas, their centroid and mean colour, an exact pixel hash, the
+visible text, and a hash over every element's style.
+
+**It is deliberately narrow about what counts as a failure.** A plan derived
+from the page cannot know what a control is *for*, so a button only has to
+survive being pressed. Demanding that every press change something would fail
+a working program for having a Clear button on an empty canvas.
+
+What it can judge without knowing the design is whether the program
+contradicts itself. A surface that took the first stroke has to take the
+second. A control that does nothing on its first press and something on its
+second, from the same state, is one press behind. And if nothing on the page
+responds to anything, the script probably never ran.
+
+**It never says a page is broken.** It says what it pressed and what
+happened:
+
+```
+C006 [FAILED] type into Quantity then press +
+    → nothing on the page changed at all
+```
+
+A verdict makes you change code. A measurement makes you look first, and
+sometimes you find the page was right and the check was aimed at the wrong
+thing. That is the cheaper mistake to make, and it reads the same either way
+round: a person knows where to start, and an agent gets a precise place to
+look instead of a whole file to re-read.
+
+**It serves the folder and never builds it.** The page is served over
+loopback rather than opened off the disk, because a `file://` origin blocks
+every module the page loads. What it will not do is run your build: `npm
+install` executes whatever the dependency tree asks for, as whoever typed the
+command, and this is a tool for checking code nobody has read. Point it at a
+source tree and it says so:
+
+```console
+$ assay ./my-vite-app
+assay: index.html loads /src/main.jsx, which a browser cannot run. This is a source tree, not a built one.
+  Build it first, in your own shell, then check the output:
+    npm install && npm run build && assay ./my-vite-app/dist
+```
+
+**[Every rule →](docs/how-it-works.md)**
+
+## Why
+
+A lot of code is written by models now, and *"does this actually run?"* is
+mostly still answered by a person opening it and clicking around.
+
+Every existing tool needs something you do not have for a program that was
+generated ten seconds ago. Playwright and Cypress need tests somebody wrote.
+Visual regression needs a golden image to compare against. Benchmarks like
+SWE-bench use the repository's own suite.
+
+So the thing most people reach for instead is another model: paste the code in
+and ask whether it looks right. **That is a reader guessing about code.** assay
+opens the page and drives it, which is the only way to find out that a button
+does nothing.
+
+|  | needs tests written | needs a baseline | runs the program |
+|---|---|---|---|
+| Playwright / Cypress | yes | no | yes, the parts you wrote |
+| Percy / Chromatic | no | **yes** | it screenshots it |
+| ask a model to review it | no | no | **no. It reads the source** |
+| **assay** | **no** | **no** | **yes, all of it** |
+
+## Limits Worth Knowing
+
+- **Browser programs.** It opens a page. A program with no page is not
+  something it can measure.
+- **Coverage cannot judge intent.** A control that works mechanically and does
+  the wrong thing passes. Criteria are the answer, and you have to write those.
+- **A game that ends looks like a page that died.** When a program finishes
+  and offers no way to start again, it stops responding to anything, and a
+  plan derived from the page cannot tell that apart from a page that broke.
+- **Built output, not source trees.** It will not run your build. Point it at
+  a source tree and it says so and names the command.
+- **Single-page programs.** It checks the page you point it at and does not
+  crawl. A multi-page site means running it per page, and client-side routing
+  is untested.
+- **Generated pages, not the live web.** It is built for programs somebody
+  just generated, not for sites with a login, a cookie banner or live network
+  calls.
+
+## Contributing
+
+Issues and pull requests are welcome. Setup, tests, benchmarks and what a PR
+needs are in **[CONTRIBUTING.md](CONTRIBUTING.md)**.
+
+## Licence
+
+MIT.

assay_ui-0.1.0/pyproject.toml

@@ -0,0 +1,42 @@
+[project]
+name = "assay-ui"
+version = "0.1.0"
+description = "Find out whether a generated web page actually works."
+keywords = ["testing", "llm", "codegen", "playwright", "evaluation", "qa",
+            "ai-agents", "browser-testing"]
+authors = [{ name = "awss1i" }]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: MIT License",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Environment :: Console",
+  "Topic :: Software Development :: Testing",
+]
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "MIT" }
+dependencies = ["playwright>=1.40"]
+
+[project.urls]
+Homepage = "https://github.com/awss1i/assay"
+Source = "https://github.com/awss1i/assay"
+Issues = "https://github.com/awss1i/assay/issues"
+Changelog = "https://github.com/awss1i/assay/releases"
+
+[project.scripts]
+assay = "assay.cli:main"
+
+[project.optional-dependencies]
+dev = ["pytest>=7"]
+
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.packages.find]
+where = ["src"]

assay_ui-0.1.0/setup.cfg

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