Skip to content

agent-rules-kit v0.3.0

Choose a tag to compare

View all tags
@CoderDeltaLAN CoderDeltaLAN released this 19 Jun 02:12
v0.3.0
c3c7b3e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.3.0 Release Notes

Status: published GitHub Release.

Date published: 2026-06-19.

Version: 0.3.0.

GitHub Release: v0.3.0.

PyPI: agent-rules-kit==0.3.0.

Release summary

agent-rules-kit v0.3.0 moves the project from a check-focused diagnostic CLI toward a small local-first instruction-governance toolkit.

The release keeps the product boundary:

  • local CLI;
  • read-only diagnosis commands;
  • no runtime network calls;
  • no runtime LLM calls;
  • no execution of commands from analyzed repositories;
  • no security-scanner claim;
  • no proof-of-safety claim.

Main changes

v0.3.0 includes:

  • doctor, a read-only repository-level diagnosis summary;
  • budget, a read-only local size and context-pressure approximation;
  • explain, a read-only local explanation command for known governance rule IDs;
  • output and exit-code contract documentation for the implemented command surface;
  • golden output and regression coverage for the expanded command surface;
  • updated release documentation for the v0.3.0 release train.

Command surface

The v0.3.0 command surface is:

  • agent-rules-kit --version;
  • agent-rules-kit check;
  • agent-rules-kit init --dry-run;
  • agent-rules-kit init --write;
  • agent-rules-kit doctor;
  • agent-rules-kit budget;
  • agent-rules-kit explain.

Security and support notes

This project is not a security scanner and does not prove that a repository is safe.

Support remains best-effort. There is no commercial SLA, no guaranteed response time, no production-readiness guarantee, and no stable public API guarantee before v1.0.

Private vulnerability reporting must not be claimed as enabled unless the repository setting is verified.

Not included

v0.3.0 does not claim:

  • stable public API compatibility;
  • production readiness;
  • security certification;
  • complete governance coverage;
  • complete secret scanning;
  • dependency vulnerability scanning;
  • model-specific token counting;
  • repository packaging for LLMs;
  • automatic rewriting or fixing;
  • runtime network access;
  • runtime LLM behavior.

Release status

The v0.3.0 GitHub Release is published.

The exact v0.3.0 tag exists.

Final release assets are attached to the GitHub Release.

PyPI publication has been completed and verified with a clean install smoke test.

Future release work should happen in a new explicit phase.

Assets 5
Loading