tally-cli 0.9.4 → 0.9.6

package/README.md

@@ -2,9 +2,10 @@
 
 [![codecov](https://codecov.io/gh/wharflab/tally/graph/badge.svg?token=J3vK0hyLkf)](https://codecov.io/gh/wharflab/tally)
 
-tally keeps Dockerfiles and Containerfiles clean, modern, and consistent — using BuildKit's own parser and checks (the same foundation behind
-`docker buildx`) plus safe auto-fixes. It runs fast, doesn't require Docker Desktop or a daemon, and fits neatly into CI. If that sounds like your
-workflow, try `tally lint .`.
+tally is a production-grade **Dockerfile/Containerfile linter + formatter** that keeps build files clean, modern, and consistent.
+
+It uses **BuildKit's official parser and checks** (the same foundation behind `docker buildx`) plus a **safe auto-fix** engine. It runs fast,
+doesn't require Docker Desktop or a daemon, and fits neatly into CI.
 
 ```bash
 # Lint everything in the repo (recursive)
@@ -14,7 +15,20 @@ tally lint .
 tally lint --fix Dockerfile
 ```
 
-## Why tally?
+## Why tally
+
+Modern Dockerfiles deserve modern tooling. tally is opinionated in the right places:
+
+- **BuildKit-native**: understands modern syntax like heredocs, `RUN --mount=...`, `COPY --link`, and `ADD --checksum=...`.
+- **Fixes, not just findings**: `--fix` applies safe, mechanical rewrites; `--fix-unsafe` unlocks opt-in risky fixes (including AI).
+- **Modernizes on purpose**: converts eligible `RUN`/`COPY` instructions to heredocs, prefers `ADD --extract`, and more.
+- **Broad rule coverage**: combines Docker's official BuildKit checks, Hadolint-compatible rules, and tally-specific rules.
+- **Registry-aware without Docker**: uses a Podman-compatible registry client for image metadata checks (no daemon required).
+- **Editor + CI friendly**: VS Code extension (`wharflab.tally`, powered by `tally lsp`) and outputs for JSON, SARIF, and GitHub Actions annotations.
+- **Easy to install anywhere**: Homebrew, Go, npm, pip, and RubyGems.
+- **Written in Go**: single fast binary, built on production-grade libraries.
+
+Quality bar: **92% code coverage on Codecov** and **2,900+ Go tests executed in CI**.
 
 Dockerfile linting usually means picking a compromise:
 
@@ -23,16 +37,19 @@ Dockerfile linting usually means picking a compromise:
 - **`docker buildx --check`** runs Docker's official BuildKit checks, but it requires the Docker/buildx toolchain and can be heavier than a pure
   static linter (and not always available if you're using Podman/Finch/other runtimes).
 
-tally exists to bring modern linter ergonomics to container builds:
+Roadmap: more auto-fixes, more Hadolint parity, richer registry-aware checks, and higher-level rules (cache & tmpfs mount recommendations,
+tooling-aware checks for uv/bun, line-length and layer optimizations).
 
-- **BuildKit-native parsing**: understands modern syntax like heredocs, `RUN --mount=...`, and `ADD --checksum=...`.
-- **Fixes, not just findings**: applies safe, mechanical fixes automatically (`--fix`), with per-rule control when you need it.
-- **Easy to install anywhere**: available via Homebrew, Go, npm, pip, and RubyGems — so it can flow through your existing artifact mirrors.
-- **Container ecosystem friendly**: supports Dockerfile/Containerfile conventions and `.dockerignore`/`.containerignore`.
-- **A growing ruleset**: combines official BuildKit checks, Hadolint-compatible rules, and tally-specific rules.
+## Optional: AI AutoFix via ACP
 
-Roadmap: editor integrations (VS Code, Zed), more auto-fixes, and higher-level rules (cache & tmpfs mount recommendations, tooling-aware checks for
-uv/bun, line-length and layer optimizations).
+tally supports **opt-in AI AutoFix** for the kinds of improvements that are hard to express as a deterministic rewrite.
+
+Instead of asking you for an API key, tally integrates with **ACP (Agent Client Protocol)** so you can use the agent you already trust (Gemini CLI,
+OpenCode, GitHub Copilot CLI, and more), while tally keeps linting fast and validates proposed changes before applying them.
+
+AI fixes are **rule-driven** (one narrow transformation at a time) and **verified** (re-parse + re-lint) before anything is applied.
+
+- Guide: [`docs/guide/ai-autofix-acp.md`](docs/guide/ai-autofix-acp.md)
 
 ## Supported Rules
 
@@ -354,6 +371,20 @@ tally lint --fail-level style Dockerfile
 
 Available levels (from most to least severe): `error`, `warning`, `info`, `style` (default), `none`
 
+## IDE Integration
+
+### VS Code
+
+Install the official **[tally extension](https://marketplace.visualstudio.com/items?itemName=wharflab.tally)** from the Visual Studio Marketplace for real-time linting and diagnostics.
+
+### Other Editors
+
+Any editor that supports the [Language Server Protocol](https://microsoft.github.io/language-server-protocol/) can use tally's built-in LSP server over stdio:
+
+```bash
+npx -y tally-cli lsp --stdio
+```
+
 ## Development
 
 ### Running Tests

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tally-cli",
-  "version": "0.9.4",
+  "version": "0.9.6",
   "description": "A fast, configurable linter for Dockerfiles and Containerfiles",
   "repository": {
     "type": "git",
@@ -31,13 +31,13 @@
     "node": ">=18.0.0"
   },
   "optionalDependencies": {
-    "@wharflab/tally-darwin-arm64": "0.9.4",
-    "@wharflab/tally-darwin-x64": "0.9.4",
-    "@wharflab/tally-linux-arm64": "0.9.4",
-    "@wharflab/tally-linux-x64": "0.9.4",
-    "@wharflab/tally-windows-arm64": "0.9.4",
-    "@wharflab/tally-windows-x64": "0.9.4",
-    "@wharflab/tally-freebsd-x64": "0.9.4"
+    "@wharflab/tally-darwin-arm64": "0.9.6",
+    "@wharflab/tally-darwin-x64": "0.9.6",
+    "@wharflab/tally-linux-arm64": "0.9.6",
+    "@wharflab/tally-linux-x64": "0.9.6",
+    "@wharflab/tally-windows-arm64": "0.9.6",
+    "@wharflab/tally-windows-x64": "0.9.6",
+    "@wharflab/tally-freebsd-x64": "0.9.6"
   },
   "publishConfig": {
     "access": "public"