rung-cli 0.1.2__tar.gz

rung_cli-0.1.2/.claude-plugin/marketplace.json

@@ -0,0 +1,12 @@
+{
+  "name": "rung",
+  "description": "Rung: a verification ledger for codebases where coding agents write much of the code.",
+  "owner": { "name": "CalQuity" },
+  "plugins": [
+    {
+      "name": "rung",
+      "source": "./",
+      "description": "Skills to set up and use Rung in a repository."
+    }
+  ]
+}

rung_cli-0.1.2/.claude-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "rung",
+  "description": "Set up Rung in a repository: record tests and security scans as checks, gate pull requests in CI, and teach coding agents the verification rules.",
+  "version": "0.1.2",
+  "author": { "name": "CalQuity" },
+  "homepage": "https://github.com/CalQuity/rung",
+  "repository": "https://github.com/CalQuity/rung",
+  "license": "Apache-2.0",
+  "keywords": ["verification", "testing", "security", "tla+", "lean", "coding-agents"]
+}

rung_cli-0.1.2/.gitignore

@@ -0,0 +1,24 @@
+__pycache__/
+*.pyc
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.coverage
+htmlcov/
+.hypothesis/
+
+# Rung's local cache and evidence; the verdicts in .rung/verdicts/ are meant to be committed.
+.rung/cache/
+.rung/runs/
+# Evidence artifacts can be large; the ledger keeps their hashes. Upload them from CI.
+.rung/evidence/
+
+# The example starts clean on every clone.
+examples/*/.rung/
+
+# Lean and TLC build output
+.lake/
+states/
+*.st

rung_cli-0.1.2/CHANGELOG.md

@@ -0,0 +1,60 @@
+# Changelog
+
+All notable changes to Rung. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and versions follow the policy in [CONTRIBUTING.md](CONTRIBUTING.md#versioning).
+
+## 0.1.2 (unreleased)
+
+The first release on PyPI, as `rung-cli`.
+
+### Changed
+- Verdicts are one small file per check, `.rung/verdicts/<check>.json`, bound to a digest of the
+  files the check covers. They replace the shared, hash-chained `.rung/ledger.jsonl`, so parallel
+  branches no longer conflict and the files stay a few hundred bytes. Per-file digests and the run
+  history move to the git-ignored `.rung/cache/`. Re-run your checks after upgrading.
+- Commands run without a shell, and shell syntax (`&&`, `|`, `;`, redirects, a leading `cd`) is a
+  configuration error. Use `cwd`, or `sh -c "..."` explicitly.
+- An option a check kind does not understand is a configuration error, with a suggestion.
+- Scan and deps verdicts expire (`max_age_days`, default 1 day for deps and osv-scanner), because
+  advisory databases change without any file changing.
+- The Claude Code Stop hook compares against the merge base, so committing edits does not hide them.
+
+### Added
+- A setup skill for coding agents, published as a Claude Code plugin (`/rung:setup`).
+- The GitHub Action lists pull request edits to policy files (rung.toml, LAWS.md, waivers,
+  baselines, scanner configs); `policy-changes: fail` fails the gate on them.
+- A pre-commit hook (`.pre-commit-hooks.yaml`).
+- A `shortcuts` check that blocks new type-checker silencers (`@ts-ignore`, `# type: ignore`,
+  `as any`), lint disables, skipped, focused and deleted tests, lowered coverage thresholds and
+  relaxed type-checker settings. `rung init` adds it, plus the type checkers and linters the
+  project already configures.
+- `rung draft property`: Hypothesis or fast-check properties for a law, kept only when they pass
+  on the real code and catch at least half of the deliberate one-token bugs planted in a disposable
+  copy of the project (under pytest, Vitest, Jest or `node --test`).
+- Drafted checks record the model: the one Claude Code reports having used, or Codex's configured
+  model, marked as such (`drafted_by`).
+- Attested evidence: an `evidence` check without `run` takes recordings an agent made with its own
+  browser or computer-use tool (Claude in Chrome, Codex, computer use), or a person made by hand,
+  through `rung attest <check> <files> --by <tool> --note ...`. The verdict holds until a covered
+  file changes.
+
+### Fixed
+- TLA+ checks fail when the config declares no invariant or property, instead of passing.
+- Lean checks audit every theorem's axioms, and reject `sorry` warnings, `sorryAx` and
+  attribute-prefixed axioms.
+- Redacted secret findings are fingerprinted by the flagged text, so swapping one secret for another
+  on the same line is a new finding. Every scanner's messages are redacted before they are stored.
+- Rung's own `.rung/` state is never scanned for findings.
+- `requirements` includes cannot loop or leave the repository; malformed manifests are errors.
+- Zero-byte files no longer count as evidence.
+- Unexpected errors exit 2 with a one-line message (`RUNG_DEBUG=1` shows the traceback).
+
+## 0.1.1
+
+### Changed
+- CI pins every action by commit SHA, and Rung checks its own pull requests with its own action.
+
+## 0.1.0
+
+- First tagged version: command, evidence, scan, deps, TLA+, Lean and differential-testing checks,
+  the verdict ledger, `LAWS.md`, model-drafted specs and proofs, agent skills and the GitHub Action.

rung_cli-0.1.2/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+a private message to the maintainers listed in [.github/CODEOWNERS](.github/CODEOWNERS) on GitHub.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

rung_cli-0.1.2/CONTRIBUTING.md

@@ -0,0 +1,75 @@
+# Contributing
+
+```bash
+uv sync
+uv run pre-commit install    # ruff, ruff format and pyright on every commit, as in CI
+uv run pytest -q --cov       # the example integration test skips without TLC/Lean
+uv run pyright               # type check (editors read the same [tool.pyright] settings)
+actionlint                   # workflows, if you change .github/ (CI also shellchecks action.yml)
+```
+
+To run the integration test locally, install Java 11+, put
+[`tla2tools.jar`](https://github.com/tlaplus/tlaplus/releases) at
+`~/.cache/rung/tla2tools.jar` (or set `RUNG_TLA2TOOLS`), and install Lean with
+[elan](https://lean-lang.org/install/). `rung doctor` shows what is missing.
+
+## Layout
+
+Each layer imports only from the layers below it.
+
+| Path | What |
+|---|---|
+| `src/rung/cli/` | Argument parsing, terminal/JSON output, and `commands/` (`setup`, `run`, `manage`, `draft`) |
+| `src/rung/agents/` | Agent skills and the AGENTS.md section (`install`), the Claude Code Stop hook (`hooks`) |
+| `src/rung/drafting/` | Model providers with structured output, and the TLA+, Lean and runtime drafters |
+| `src/rung/guides/` | Markdown guidance used both as drafting prompts and as agent skills |
+| `src/rung/analysis/` | Repository survey, recommended plan, report |
+| `src/rung/checks/` | Check kinds (`registry` maps kinds to checkers), the `runner`, scan presets, baselines and waivers, fix proofs |
+| `src/rung/engines/` | Tool wrappers with no knowledge of `rung.toml`: TLC, Lean, differential testing, SARIF |
+| `src/rung/core/` | Config, ledger, laws, git, errors |
+| `examples/lease-queue` | The worked example, used by the integration test |
+
+To add a check kind, subclass `rung.checks.base.Checker`, register it in `rung/checks/registry.py`,
+add the kind to `CHECK_KINDS` in `rung/core/config.py`, and document its fields in `docs/CONFIG.md`.
+To change what models or agents are told, edit the Markdown in `src/rung/guides/`.
+
+## Rules for changes
+
+- Rung has no runtime dependencies. Keep it that way unless a dependency removes a
+  real risk.
+- A runner must never report `pass` when its tool did not actually confirm the result.
+  When in doubt, report `error`.
+- New file formats or fields are part of the public contract; document them in
+  `docs/DESIGN.md` in the same change.
+- Every runner change comes with a test that uses recorded tool output, so the suite
+  runs without the tool installed.
+
+## Releasing
+
+1. Move the CHANGELOG.md entries out of "unreleased". Bump the version in `pyproject.toml`, `src/rung/__init__.py` and `.claude-plugin/plugin.json`, and the
+   `CalQuity/rung@v…` references in `README.md` and `skills/setup/SKILL.md`.
+   `tests/test_release_consistency.py` fails if any of them disagree.
+2. Merge to `main` through a pull request.
+3. A maintainer pushes the tag (`git tag -a vX.Y.Z -m "Rung X.Y.Z" && git push origin vX.Y.Z`); only
+   admins can create `v*` tags. `release.yml` checks the tag matches the version, tests, and publishes
+   `rung-cli` to PyPI through Trusted Publishing.
+
+## Versioning
+
+Rung follows semantic versioning, read the 0.x way: until 1.0, a minor release (0.2, 0.3) may change
+the public contract, and a patch release (0.1.3) does not. The public contract is:
+
+- the `rung.toml` format and the meaning of each check option;
+- the files under `.rung/` that are committed (verdicts, baselines, waivers, `verify/`);
+- `LAWS.md`, the `--json` output, and the exit codes;
+- the GitHub Action's inputs and outputs.
+
+Every change to it is listed in CHANGELOG.md under **Changed**, with what to do after upgrading.
+Options are deprecated with a warning for at least one minor release before they are removed.
+
+## The setup skill and plugin
+
+`skills/setup/SKILL.md` is what developers give their coding agents to set Rung up; `.claude-plugin/`
+publishes it as a Claude Code plugin (`/plugin install rung --marketplace CalQuity/rung`, then
+`/rung:setup`). Validate changes with `claude plugin validate .`. The skills Rung installs *into* a
+project (`rung agents`) live in `src/rung/guides/` instead.

rung_cli-0.1.2/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+