Skip to content

v0.4.5: See what each agent receives as a shareable page: qikly --explain CALC_TAX --html

Choose a tag to compare

@github-actions github-actions released this 15 Sep 07:54
· 315 commits to main since this release

Most of this changes the repository and test.qikly.com rather than the installed
tool. --explain --html and the README that PyPI shows ship in the package.

Changed

  • test.qikly.com counts visits with GoatCounter, which sets no cookies and
    stores no personal data: page views, the source a visitor came from, and
    clicks on the page's outbound links. The counter loads only after the page has
    finished, so a network that blocks it cannot slow the page down.
  • The README and the landing page read in a clearer order: what each agent
    sees comes before the comparison of code-derived and spec-derived suites,
    both under their own headings, and the README's tables are lists so they fit a
    phone.

Added

  • qikly --explain TASK --html writes the withholding as a page to share.
    Both views side by side, the task file as test generation receives it with
    every withheld line highlighted, and the same file as the coding agent
    receives it, in one HTML file that loads nothing from anywhere. The terminal
    output was the most persuasive thing the tool printed and the hardest to pass
    on. It defaults to qikly_explain_<TASK>.html where you ran the command, and
    marks exactly the lines the terminal output counts.
  • A badge for projects that use qikly, "tested with qikly", with the
    Markdown to paste in the README and the quick start.
  • CONTRIBUTING.md and a task proposal form for contributing example
    tasks, since users are encouraged to contribute their own: what makes a good
    task, how to name it, the files it needs, the checks to run before sending
    it, and how it is credited. tests/test_bundled_task_names.py fails the build
    when a task id breaks the FAMILY_SUBJECT convention, ends in _VERIFY,
    differs from another only in case, or leaves a data folder behind.

Fixed

  • The diagram shows on PyPI. PyPI prints a mermaid block as source, so the
    project page showed forty lines of flowchart code where the README's diagram
    should be. The README now shows an image of the diagram, rendered from the
    one in docs/design_1_case_study.md by tools/render_flow_diagram.py, and a
    test fails when the image falls behind that source. GitHub shows the same
    image.
  • The README's example of an exact pin named @v0.3.4, three releases
    old. The check for stale pins only looked for the full gal-a/qikly@v...
    form, so a bare @v0.3.4 in a sentence slipped past it. It now catches both.